Probe and check coverage aligned to Art
11 (Technical Documentation).
Art.11: Technical Documentation
Maintain technical docs sufficient for conformity assessment.
Last reviewed July 2026
The gap Art.11 closes
In EU AI Act, Technical Documentation addresses documentation. Maintain technical docs sufficient for conformity assessment. 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 Art.11
Penaxtra turns this EU AI Act obligation into recurring, testable evidence: scheduled scans and posture checks produce findings tied to Art.11, and the append-only audit log records what was tested and when. The EU AI Act Art.11 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.
Art.11 capabilities
Findings tagged with the EU AI Act Art
11 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
Art.11 compliance mapping
Findings for Art.11 carry the EU AI Act Art.11 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 Art.11 (Technical Documentation)?
Maintain technical docs sufficient for conformity assessment. It is a EU AI Act control; Penaxtra assesses it at high severity.
How does Penaxtra test for Art.11?
Penaxtra turns this EU AI Act obligation into recurring, testable evidence: scheduled scans and posture checks produce findings tied to Art.11, and the append-only audit log records what was tested and when.
Does a finding for Art.11 help with an audit?
Each finding is tagged with the EU AI Act Art.11 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.