Implementation guide
OWASP AISVS v1.01
AI-Assisted Secure Coding (Appendix C) · Compromise Containment & Automated Remediation
Revoke agent identities quickly
Verify that AI agent identities (keys, tokens, OIDC trust grants) can be rapidly revoked and quarantined, with a target time-to-revoke that is written down and tested at least once a year.
OWASP AISVS v1.01, requirement AC.14.3
In plain English
You should be able to revoke and quarantine an AI agent's identities (keys, tokens and OIDC trust grants) quickly. Write down a target time for it, and test that you can hit the target at least once a year.
What good looks like
- Revocation steps are documented for every kind of agent credential.
- A target time-to-revoke is written down.
- Revocation is tested at least once a year, and the measured time is recorded.
- An inventory lists every agent identity and where it is trusted.
How teams usually do it
- Central management of agent identities, so one action disables an agent everywhere.
- A runbook or script that revokes tokens, uninstalls or suspends the app identity and removes OIDC trust relationships in the cloud accounts.
- Short-lived credentials, so revocation is mainly a matter of stopping re-issuance.
Suggested evidence
- The runbook.
- The inventory of agent identities.
- Test results with the time taken against the target.
Common mistakes
- Agent credentials scattered across systems with no single point of revocation.
- Revoking the token and leaving the OIDC trust policy that would mint a new one.
- A target time nobody has ever measured.
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.