LLM03: Supply Chain
Compromised third-party models, fine-tunes, plugins, or training datasets introduce risk into the deployed stack.
Last reviewed July 2026
The gap LLM03 closes
In OWASP LLM Top 10, Supply Chain addresses supply chain. Compromised third-party models, fine-tunes, plugins, or training datasets introduce risk into the deployed stack. Penaxtra records this control at high 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 LLM03
Penaxtra ships adversarial probe families that target supply chain 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 LLM03 identifier. The OWASP LLM Top 10 LLM03 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.
LLM03 capabilities
Findings tagged with the OWASP LLM Top 10 LLM03 identifier
Penaxtra severity for this control (high)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
LLM03 compliance mapping
Findings for LLM03 carry the OWASP LLM Top 10 LLM03 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 LLM03 (Supply Chain)?
Compromised third-party models, fine-tunes, plugins, or training datasets introduce risk into the deployed stack. It is a OWASP LLM Top 10 control; Penaxtra assesses it at high severity.
How does Penaxtra test for LLM03?
Penaxtra ships adversarial probe families that target supply chain 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 LLM03 identifier.
Does a finding for LLM03 help with an audit?
Each finding is tagged with the OWASP LLM Top 10 LLM03 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.