How to meet it
OWASP AISVS v1.01
Orchestration & Agentic Security · Agent Authorization, Delegation, and Continuous Enforcement
Pass the user's permissions down the chain
Verify that when an agent acts on a user's behalf, the runtime propagates an integrity-protected, scope-limited token that carries the user's authorization context and is enforced at every downstream call.
OWASP AISVS v1.01, requirement 9.5.2
In plain English
When an agent acts for a user, pass along a protected token that carries that user's permissions, and check it at every downstream call.
What good looks like
- A scoped, signed token carries the user's identity and permissions.
- Every downstream service checks it.
- The agent cannot widen the token.
How teams usually do it
- OAuth token exchange to get downstream tokens on behalf of the user.
Evidence an auditor would accept
- Token flow design and service validation code.
Common mistakes
- Calling downstream services with the agent's own broad credentials.
Not sure which requirements apply to your system? Take the assessment.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.