EvidenceSheet
NIST AI RMF 1.0 · MAP - NIST AI RMF 1.0

MP-2.2 Information about the AI system's knowledge limits and how system output may be utilized and overseen by…

Information about the AI system’s knowledge limits and how system output may be utilized and overseen by humans is documented. Documentation provides sufficient information to assist relevant AI actors when making informed decisions and taking subsequent actions. The system's knowledge limits are written down alongside how output should be used and overseen, in enough detail for a downstream actor to make an informed decision.

Source: NIST AI RMF 1.0, MP-2.2. 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

  • Documented knowledge limits, including the conditions the system was not built for · Document repository
  • Guidance on permitted use and interpretation of system output · Document repository
  • The human oversight expected over the output, and by whom · Document repository
  • Evidence this documentation reaches downstream deployers and operators · 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

MP-2.1 The specific task, and methods used to implement the task, that the AI system will support is defined · MP-2.3 Scientific integrity and TEVV considerations are identified and documented, including those related to…