NIST AI 600-1 / MS-2.3

MS-2.3: AI system performance is evaluated regularly

Continuous evaluation against benchmarks + drift detection.

Last reviewed June 2026

Problem

The gap MS-2.3 closes

AI system performance is evaluated regularly sits in the measure surface, and NIST AI 600-1 rates it high. Continuous evaluation against benchmarks + drift detection. 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.

How Penaxtra approaches it

How Penaxtra delivers MS-2.3

Penaxtra turns this NIST AI 600-1 obligation into testable, recurring evidence: scheduled scans and posture checks produce findings tied to MS-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 MS-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.

Technical capabilities

MS-2.3 capabilities

Probe and check coverage aligned to MS-2

3 (AI system performance is evaluated regularly).

Findings tagged with the NIST AI 600-1 MS-2

3 control identifier.

Severity context (NIST AI 600-1 rates this high)

Cross-framework overlap so one finding maps to several control cells

PDF and JSON audit-evidence export with the control id attached

Compliance mapping

MS-2.3 compliance mapping

Findings for MS-2.3 carry the NIST AI 600-1 MS-2.3 identifier and cross-map to the related controls in the other five frameworks Penaxtra covers.

FAQ

Frequently asked

What is MS-2.3 (AI system performance is evaluated regularly)?

Continuous evaluation against benchmarks + drift detection. It is part of NIST AI 600-1, rated high.

How does Penaxtra test for MS-2.3?

Penaxtra turns this NIST AI 600-1 obligation into testable, recurring evidence: scheduled scans and posture checks produce findings tied to MS-2.3, and the append-only audit log records what was tested and when, which is exactly what an assessor asks for.

Does a finding for MS-2.3 help with an audit?

Yes. Each finding is tagged with the NIST AI 600-1 MS-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.

Request a demo

Scoped walkthrough of the NIST AI 600-1 / MS-2.3 surface against your environment. No credit card.

Request a demo Explore AI-SPM platform