API Authorization Testing: BOLA, Roles and Tenant Boundaries
An authenticated API request is not necessarily an authorized one.
Authentication answers who. Authorization answers whether.#
Many API vulnerabilities appear after a legitimate user signs in. The backend validates the token but fails to check whether that user may act on the specific object, organization or function.
Three common failure patterns#
Object-level authorization: A request using a different document or invoice identifier returns another account's data.
Function-level authorization: A regular user can reach an admin endpoint even though the UI hides it.
Property-level authorization: A client can modify fields that should be server-managed, such as tenant ownership or elevated roles.
What a good check looks like#
For every sensitive backend action, identify the actor, requested action, target object, tenant and policy. Resolve object ownership on the server, enforce least privilege, and deny unexpected states by default.
What to verify in a retest#
Test both read and write operations, different user roles, cross-tenant requests, exports and indirect access through integrations. A frontend control or an identifier format change is not sufficient remediation.
See our API security testing service if you need a scoped independent review.