ASI04: Resource Overload
Looped or recursive agent actions exhaust CPU/quota budgets.
Last reviewed October 2026
Why ASI04 evidence is hard
Loops are cheap to write and expensive to run. The probes here ask an agent to fan out without bound and to recurse on its own output, while the load harness measures what the endpoint does about it under a request budget we impose on ourselves. That budget is counted against the authorisation that allowed the spend rather than per endpoint, so a test covering four endpoints does not quietly issue four times the agreed number of requests.
How Penaxtra maps to ASI04
The ASI04 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.
ASI04 capabilities
Findings tagged with the OWASP Agentic Top 10 ASI04 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
ASI04 control coverage
Findings for ASI04 carry the OWASP Agentic Top 10 ASI04 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 ASI04 (Resource Overload)?
Looped or recursive agent actions exhaust CPU/quota budgets. It is an OWASP Agentic Top 10 control; Penaxtra assesses it at medium severity.
How does Penaxtra test for ASI04?
The ASI04 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 ASI04 help with an audit?
Each finding is tagged with the OWASP Agentic Top 10 ASI04 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.