ASI03: Privilege Compromise
Agent escalates privileges via chained tool calls or impersonation of another principal.
Last reviewed October 2026
Why ASI03 evidence is hard
Escalation in an agent rarely looks like an exploit. It looks like a chain - a context inherited from a caller who had more rights, an object id incremented until it lands in another tenant, an admin function invoked because nothing checked the caller's role. All three shapes are probed, alongside impersonation of a second principal, at critical severity.
How Penaxtra maps to ASI03
The ASI03 identifier is written onto the finding at the moment it is created, not mapped in afterwards, so the JSON and PDF exports come out already in your assessor's structure. Every finding carries the probe that was sent, a SHA-256 digest of the response it provoked, the tier that decided the verdict and its status history from first observation to close. Identity survives a re-scan: a control you closed and that comes back reopens under the same row with a reopen count, rather than arriving as a new issue.
ASI03 capabilities
Findings tagged with the OWASP Agentic Top 10 ASI03 identifier
Penaxtra severity for this control (critical)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
ASI03 control coverage
Findings for ASI03 carry the OWASP Agentic Top 10 ASI03 identifier along with the corresponding control identifiers in the other frameworks Penaxtra maps, so one result is reflected across each mapped framework.
Frequently asked
What is ASI03 (Privilege Compromise)?
Agent escalates privileges via chained tool calls or impersonation of another principal. It is an OWASP Agentic Top 10 control; Penaxtra assesses it at critical severity.
How does Penaxtra test for ASI03?
The ASI03 identifier is written onto the finding at the moment it is created, not mapped in afterwards, so the JSON and PDF exports come out already in your assessor's structure. Every finding carries the probe that was sent, a SHA-256 digest of the response it provoked, the tier that decided the verdict and its status history from first observation to close. Identity survives a re-scan: a control you closed and that comes back reopens under the same row with a reopen count, rather than arriving as a new issue.
Does a finding for ASI03 help with an audit?
Each finding is tagged with the OWASP Agentic Top 10 ASI03 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.