AML.T0051: LLM Prompt Injection
Override an LLM's intended behaviour via crafted prompt content.
Last reviewed September 2026
Why AML.T0051 evidence is hard
In MITRE ATLAS, LLM Prompt Injection addresses initial access. Override an LLM's intended behaviour via crafted prompt content. 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 AML.T0051
Penaxtra maps its probe families to this ATLAS technique, so activity matching llm prompt injection surfaces as a finding carrying the AML.T0051 technique identifier for threat tracking and reporting. The MITRE ATLAS AML.T0051 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.
AML.T0051 capabilities
Findings tagged with the MITRE ATLAS AML.T0051 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
AML.T0051 control coverage
Findings for AML.T0051 carry the MITRE ATLAS AML.T0051 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 AML.T0051 (LLM Prompt Injection)?
Override an LLM's intended behaviour via crafted prompt content. It is a MITRE ATLAS control; Penaxtra assesses it at critical severity.
How does Penaxtra test for AML.T0051?
Penaxtra maps its probe families to this ATLAS technique, so activity matching llm prompt injection surfaces as a finding carrying the AML.T0051 technique identifier for threat tracking and reporting.
Does a finding for AML.T0051 help with an audit?
Each finding is tagged with the MITRE ATLAS AML.T0051 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.