Probe and check coverage aligned to MP-2
3 (AI system data sources are documented).
Inventory + provenance for every training, fine-tune, RAG data source.
Last reviewed June 2026
AI system data sources are documented sits in the map surface, and NIST AI 600-1 rates it high. Inventory + provenance for every training, fine-tune, RAG data source. For teams shipping LLM and agentic features, a control like this is only as good as the evidence that it was actually tested - an unverified control is a finding waiting for an auditor.
Penaxtra turns this NIST AI 600-1 obligation into testable, recurring evidence: scheduled scans and posture checks produce findings tied to MP-2.3, and the append-only audit log records what was tested and when, which is exactly what an assessor asks for. Every relevant finding is created with the NIST AI 600-1 MP-2.3 identifier already attached, so it lands in the audit-evidence pack mapped to the control rather than as a screenshot someone has to translate later. Where the same weakness touches another framework, the cross-framework overlap means one finding satisfies several control cells at once.
3 (AI system data sources are documented).
3 control identifier.
Findings for MP-2.3 carry the NIST AI 600-1 MP-2.3 identifier and cross-map to the related controls in the other five frameworks Penaxtra covers.
Inventory + provenance for every training, fine-tune, RAG data source. It is part of NIST AI 600-1, rated high.
Penaxtra turns this NIST AI 600-1 obligation into testable, recurring evidence: scheduled scans and posture checks produce findings tied to MP-2.3, and the append-only audit log records what was tested and when, which is exactly what an assessor asks for.
Yes. Each finding is tagged with the NIST AI 600-1 MP-2.3 control identifier and exported in the PDF and JSON evidence pack, so it maps straight onto the auditor control list instead of needing manual translation.
Scoped walkthrough of the NIST AI 600-1 / MP-2.3 surface against your environment. No credit card.