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

MP-3.3 Targeted application scope is specified and documented based on the system's capability, established context…

Targeted application scope is specified and documented based on the system’s capability, established context, and AI system categorization. Scope is bounded in writing and justified by capability and context, which is what keeps the risk mapping and the evaluation resources tractable.

Source: NIST AI RMF 1.0, MP-3.3. 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
1
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 any scope extension and the re-assessment that accompanied it · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • The documented targeted application scope and its boundaries · Policy repository / GRC workspace
  • The capability and context basis for the scope chosen · Policy repository / GRC workspace
  • Controls that keep use inside the stated scope · 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

MP-3.2 Potential costs, including non-monetary costs, which result from expected or realized AI errors or system… · MP-3.4 Processes for operator and practitioner proficiency with AI system performance and trustworthiness, and…