LLM02: Sensitive Information Disclosure
Models leak PII, credentials, system prompts, or training-data fragments via responses or logs.
Last reviewed September 2026
Why LLM02 evidence is hard
In OWASP LLM Top 10, Sensitive Information Disclosure addresses output surface. Models leak PII, credentials, system prompts, or training-data fragments via responses or logs. 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 maps to LLM02
Penaxtra ships adversarial probe families that target sensitive information disclosure directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by deterministic checks that run inside our own infrastructure before it is recorded as a finding under the LLM02 identifier. The OWASP LLM Top 10 LLM02 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.
LLM02 capabilities
Findings tagged with the OWASP LLM Top 10 LLM02 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
LLM02 control coverage
Findings for LLM02 carry the OWASP LLM Top 10 LLM02 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 LLM02 (Sensitive Information Disclosure)?
Models leak PII, credentials, system prompts, or training-data fragments via responses or logs. It is an OWASP LLM Top 10 control; Penaxtra assesses it at critical severity.
How does Penaxtra test for LLM02?
Penaxtra ships adversarial probe families that target sensitive information disclosure directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by deterministic checks that run inside our own infrastructure before it is recorded as a finding under the LLM02 identifier.
Does a finding for LLM02 help with an audit?
Each finding is tagged with the OWASP LLM Top 10 LLM02 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.