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

MS-4.1 Measurement approaches for identifying AI risks are connected to deployment contexts and informed through…

Measurement approaches for identifying AI risks are connected to deployment context(s) and informed through consultation with domain experts and other end users. Approaches are documented. The measurement design is informed by people who understand the deployment context, because the risks that matter there are often not visible to those running the evaluation.

Source: NIST AI RMF 1.0, MS-4.1. 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
2
at each review
hard
to go live
Policy repository / GRC workspace
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

  • Records of consultation with domain experts and end users on measurement design · Document repository
  • Evidence that consultation changed the measurement approach · Document repository

governing documentDocuments that govern the control

  • Documentation of the measurement approaches and their connection to deployment contexts · Policy repository / GRC workspace
  • Identification of the deployment contexts the measurement is meant to cover · Policy repository / GRC workspace

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-3.3 Feedback processes for end users and impacted communities to report problems and appeal system outcomes are… · MS-4.2 Measurement results regarding AI system trustworthiness in deployment contexts and across the AI lifecycle…