Probe and check coverage aligned to MG-3
2 (Risks are tracked through to remediation).
MG-3.2: Risks are tracked through to remediation
Open findings reach a documented terminal state.
Last reviewed July 2026
The gap MG-3.2 closes
In NIST AI 600-1, Risks are tracked through to remediation addresses manage. Open findings reach a documented terminal state. 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 MG-3.2
Penaxtra turns this NIST AI 600-1 obligation into recurring, testable evidence: scheduled scans and posture checks produce findings tied to MG-3.2, and the append-only audit log records what was tested and when. The NIST AI 600-1 MG-3.2 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.
MG-3.2 capabilities
Findings tagged with the NIST AI 600-1 MG-3
2 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
MG-3.2 compliance mapping
Findings for MG-3.2 carry the NIST AI 600-1 MG-3.2 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 MG-3.2 (Risks are tracked through to remediation)?
Open findings reach a documented terminal state. It is a NIST AI 600-1 control; Penaxtra assesses it at high severity.
How does Penaxtra test for MG-3.2?
Penaxtra turns this NIST AI 600-1 obligation into recurring, testable evidence: scheduled scans and posture checks produce findings tied to MG-3.2, and the append-only audit log records what was tested and when.
Does a finding for MG-3.2 help with an audit?
Each finding is tagged with the NIST AI 600-1 MG-3.2 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.