EvidenceSheet
NIST AI RMF 1.0 · GOVERN - NIST AI RMF 1.0

GV-6.2 Contingency processes are in place to handle failures or incidents in third-party data or AI systems deemed…

Contingency processes are in place to handle failures or incidents in third-party data or AI systems deemed to be high-risk. For third-party components assessed as high risk there is a worked contingency, a fallback, a redundancy or a defined manual path, and it has been tested.

Source: NIST AI RMF 1.0, GV-6.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
1
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

  • Test or exercise records demonstrating the contingency works · Document repository

governing documentDocuments that govern the control

  • Identification of third-party AI components assessed as high risk · Vendor register / contract repository
  • The contingency defined for each, naming the fallback or redundancy · Document repository
  • Trigger criteria and the named role that invokes the contingency · 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

GV-6.1 Policies and procedures are in place that address AI risks associated with third-party entities, including… · MN-1.1 A determination is made as to whether the AI system achieves its intended purpose and stated objectives and…