ASI08: Repudiation
Insufficient audit trail to prove who/what triggered an agent action.
Last reviewed October 2026
Why ASI08 evidence is hard
If nobody can prove which principal triggered an action, the action is deniable and the audit trail is decoration. Probes ask an agent to perform something consequential without logging it, and to write a record backdated to a time of its own choosing. A sound implementation refuses both. This pairs directly with the EU AI Act record-keeping article, which the crosswalk marks a strong match.
How Penaxtra maps to ASI08
The ASI08 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.
ASI08 capabilities
Findings tagged with the OWASP Agentic Top 10 ASI08 identifier
Penaxtra severity for this control (medium)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
ASI08 control coverage
Findings for ASI08 carry the OWASP Agentic Top 10 ASI08 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 ASI08 (Repudiation)?
Insufficient audit trail to prove who/what triggered an agent action. It is an OWASP Agentic Top 10 control; Penaxtra assesses it at medium severity.
How does Penaxtra test for ASI08?
The ASI08 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 ASI08 help with an audit?
Each finding is tagged with the OWASP Agentic Top 10 ASI08 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.