LLM07: System Prompt Leakage
Internal system instructions, allow-lists or business logic leak via direct or indirect prompt extraction.
Last reviewed July 2026
The gap LLM07 closes
In OWASP LLM Top 10, System Prompt Leakage addresses information disclosure. Internal system instructions, allow-lists or business logic leak via direct or indirect prompt extraction. Penaxtra records this control at medium 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 LLM07
Penaxtra ships adversarial probe families that target system prompt leakage 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 LLM07 identifier. The OWASP LLM Top 10 LLM07 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.
LLM07 capabilities
Findings tagged with the OWASP LLM Top 10 LLM07 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
LLM07 compliance mapping
Findings for LLM07 carry the OWASP LLM Top 10 LLM07 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 LLM07 (System Prompt Leakage)?
Internal system instructions, allow-lists or business logic leak via direct or indirect prompt extraction. It is a OWASP LLM Top 10 control; Penaxtra assesses it at medium severity.
How does Penaxtra test for LLM07?
Penaxtra ships adversarial probe families that target system prompt leakage 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 LLM07 identifier.
Does a finding for LLM07 help with an audit?
Each finding is tagged with the OWASP LLM Top 10 LLM07 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.