ASI04: Resource Overload

Resource Overload sits in the availability surface, and OWASP Agentic Top 10 rates it medium. Looped or recursive agent actions exhaust CPU/quota budgets. For teams shipping LLM and agentic features, a control like this is only as good as the evidence that it was actually tested - an unverified control is a finding waiting for an auditor.

Penaxtra ships adversarial probe families that target resource overload directly. Each probe runs against your live endpoint on a schedule, and every triggering response is scored by three independent judges plus a meta-judge before it becomes a finding - so a ASI04 result is a tested verdict, not a guess. Every relevant finding is created with the OWASP Agentic Top 10 ASI04 identifier already attached, so it lands in the audit-evidence pack mapped to the control rather than as a screenshot someone has to translate later. Where the same weakness touches another framework, the cross-framework overlap means one finding satisfies several control cells at once.

Findings for ASI04 carry the OWASP Agentic Top 10 ASI04 identifier and cross-map to the related controls in the other five frameworks Penaxtra covers.