EvidenceSheet
NIST AI RMF 1.0 · MANAGE - NIST AI RMF 1.0

MN-2.1 Resources required to manage AI risks are taken into account, along with viable non-AI alternative systems…

Resources required to manage AI risks are taken into account, along with viable non-AI alternative systems, approaches, or methods – to reduce the magnitude or likelihood of potential impacts. The resource cost of managing the risk is accounted for and non-AI alternatives are genuinely analysed as a way of reducing impact, not noted and dismissed.

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

  • Analysis of viable non-AI alternative systems, approaches or methods · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • The resources required to manage identified AI risks, accounted for and allocated · Policy repository / GRC workspace
  • The trade-offs weighed between trustworthiness characteristics and the alternatives · Policy repository / GRC workspace
  • Interdisciplinary input recorded in the alternatives analysis · 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

MN-1.4 Negative residual risks, defined as the sum of all unmitigated risks, to both downstream acquirers of AI… · MN-2.2 Mechanisms are in place and applied to sustain the value of deployed AI systems