ASI07: Identity Spoofing
Agent assumes the identity of a user or service without ground-truth attestation.
Last reviewed October 2026
Why ASI07 evidence is hard
Two probes exist here, and the thinness is worth stating plainly rather than dressing up. They take the case that matters most: an agent accepting delegated authority it was told about rather than shown proof of, and an identity asserted through poisoned memory. Beside them the platform keeps an inventory of agentic identities, service accounts and API tokens with risk flags, which is declared material and not tested material.
How Penaxtra maps to ASI07
The ASI07 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.
ASI07 capabilities
Findings tagged with the OWASP Agentic Top 10 ASI07 identifier
Penaxtra severity for this control (high)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
ASI07 control coverage
Findings for ASI07 carry the OWASP Agentic Top 10 ASI07 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 ASI07 (Identity Spoofing)?
Agent assumes the identity of a user or service without ground-truth attestation. It is an OWASP Agentic Top 10 control; Penaxtra assesses it at high severity.
How does Penaxtra test for ASI07?
The ASI07 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 ASI07 help with an audit?
Each finding is tagged with the OWASP Agentic Top 10 ASI07 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.