LLM01: Prompt Injection
Adversarial inputs that override system instructions, bypass safety guardrails, or coerce the model into unintended behaviour.
Last reviewed July 2026
The gap LLM01 closes
In OWASP LLM Top 10, Prompt Injection addresses input surface. Adversarial inputs that override system instructions, bypass safety guardrails, or coerce the model into unintended behaviour. Penaxtra records this control at critical severity and establishes its state by exercising it against the running system, so the result reflects observed behavior rather than a documented assertion.
How Penaxtra delivers LLM01
Penaxtra ships adversarial probe families that target prompt injection directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by three independent judges and a meta-judge before it is recorded as a finding under the LLM01 identifier. The OWASP LLM Top 10 LLM01 identifier is attached when the finding is created, so it appears in the exported evidence pack already mapped to the control. Where the same weakness maps to another framework, the finding carries those control identifiers as well.
LLM01 capabilities
Findings tagged with the OWASP LLM Top 10 LLM01 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
LLM01 compliance mapping
Findings for LLM01 carry the OWASP LLM Top 10 LLM01 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 LLM01 (Prompt Injection)?
Adversarial inputs that override system instructions, bypass safety guardrails, or coerce the model into unintended behaviour. It is a OWASP LLM Top 10 control; Penaxtra assesses it at critical severity.
How does Penaxtra test for LLM01?
Penaxtra ships adversarial probe families that target prompt injection directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by three independent judges and a meta-judge before it is recorded as a finding under the LLM01 identifier.
Does a finding for LLM01 help with an audit?
Each finding is tagged with the OWASP LLM Top 10 LLM01 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.