Access Control for API Securitys
API access control is how an API decides who is calling and what they may do. Authentication verifies identity using API keys, OAuth 2.0 access tokens or JWTs, and authorisation checks permissions on each object and function. Failures here, especially broken object-level authorisation, top the OWASP API list.
Stage: Threats · Part of the API Security roadmap · Last reviewed 19 November 2026
What to learn in Access Control
- Validate a JWT's signature, issuer, audience and expiry correctly
- Describe OAuth 2.0 flows and pick the right one for a client type
- Enforce an ownership check on every object ID in a request
- Separate function-level permissions such as admin routes from user routes
- Design short-lived access tokens with a safe refresh and revocation plan
Access Control interview questions
What is broken object level authorisation (BOLA)?
BOLA happens when an API accepts an object ID from the client, such as /orders/1234, and returns it without checking that the caller owns or may access it. Attackers simply change the ID. The fix is a server-side authorisation check on every object access, not hard-to-guess IDs.
What mistakes make JWT validation unsafe?
Common errors include accepting the none algorithm, trusting the algorithm named in the token header, skipping signature checks, ignoring expiry, issuer or audience claims, and using weak shared secrets. Always pin the allowed algorithms and verify every claim with a maintained library.
Where Access Control fits in the API Security roadmap
Access Control belongs to the Threats stage (intermediate level), which takes about 15 hours. Know the risks.
Other units in this stage
Back to the full API Security roadmap