An organization's security team is evaluating a microservices deployment where an API gateway receives requests containing OAuth 2.0 JSON Web Tokens (JWTs) issued by a central Identity Provider. The API gateway validates the cryptographic signature of incoming tokens to verify issuer authenticity, but it immediately forwards all requests to downstream microservices without checking if the token's granted scopes permit access to the requested endpoint URI. Which pillar of the Authentication, Authorization, and Accounting (AAA) framework is improperly implemented at the API gateway layer?
- AuthorizationAnswer
- BAuthentication
- CAccounting
- DNon-repudiation
Answer
Authorization
Authorization is responsible for enforcing privilege boundaries by verifying that an authenticated subject possesses the required permissions or scopes to access a specific resource. In this scenario, verifying the JWT signature accomplishes authentication, but failing to evaluate token scopes against the target microservice endpoint means authorization is completely omitted at the gateway.
Step-by-Step Solution
Key Concept
Distinguishing Authentication (verifying identity) from Authorization (enforcing permissions) in API and token-based architectures.
Estimated Time:1m 30s