EvidenceSheet
NIST AI RMF 1.0 · MEASURE - NIST AI RMF 1.0

MS-2.9 The AI model is explained, validated, and documented, and AI system output is interpreted within its context…

The AI model is explained, validated, and documented, and AI system output is interpreted within its context – as identified in the MAP function – and to inform responsible use and governance. Explanations are validated for fidelity to actual model behaviour and are pitched at the audience that must act on them, and the interpretation of output is bound to the mapped context.

Source: NIST AI RMF 1.0, MS-2.9. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST AI RMF 1.0 in the compliance library.

4
artefacts
0
held by a system
0
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • The explanation method used and validation of its fidelity to model behaviour · Document repository
  • Model documentation covering how the model reaches its outputs · Document repository
  • Guidance on interpreting output within the deployment context · Policy repository / GRC workspace
  • Identification of the audiences for explanation and what each needs · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

MS-2.8 Risks associated with transparency and accountability as identified in the MAP function are examined and… · MS-2.10 Privacy risk of the AI system as identified in the MAP function is examined and documented