Implementation guide
OWASP AISVS v1.01
Orchestration & Agentic Security · Agent Authorization, Delegation, and Continuous Enforcement
Re-check permissions in long sessions
Verify that long-running agent sessions re-evaluate current backend authorization policy on every privileged action.
OWASP AISVS v1.01, requirement 9.5.6
In plain English
In a long-running agent session, check current permissions again before every privileged action. A user may have changed role, had access withdrawn or left the company since the session began. This is a Level 3 control.
What good looks like
- Each privileged action triggers a fresh authorisation check against the backend's current policy.
- Revoked access takes effect inside a running session.
- Decisions are not cached beyond a very short, defined period.
- A test confirms access removed mid-session is honoured.
How teams usually do it
- A call to the policy engine or authorisation service on each privileged action.
- Short-lived tokens, with token introspection or revocation checks for sensitive calls.
- Revocation signals from the identity provider, for example continuous access evaluation or the OpenID Shared Signals Framework, to end sessions promptly.
Suggested evidence
- A test where access is removed mid-session and the next privileged action fails.
- Token lifetimes and cache settings.
Common mistakes
- Checking permissions once at session start.
- A scheduled or background agent still running with the permissions of someone who left months ago.
Not sure which requirements apply to your system? Take the assessment, or browse every guide in this chapter.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.