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

GV-6.1 Policies and procedures are in place that address AI risks associated with third-party entities, including…

Policies and procedures are in place that address AI risks associated with third-party entities, including risks of infringement of a third party’s intellectual property or other rights. Third-party AI risk is addressed by policy covering data, models, software and services obtained externally, including the rights position on training data and model outputs.

Source: NIST AI RMF 1.0, GV-6.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
Vendor register / contract 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

  • Due diligence records for third-party AI components in use · Vendor register / contract repository

governing documentDocuments that govern the control

  • Third-party AI policy covering data, pre-trained models, software and services · Vendor register / contract repository
  • Contract terms addressing intellectual property, data rights and liability for AI components · Vendor register / contract repository
  • The intellectual property position recorded for training data and model outputs · HR system / LMS

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-5.2 Mechanisms are established to enable AI actors to regularly incorporate adjudicated feedback from relevant AI… · GV-6.2 Contingency processes are in place to handle failures or incidents in third-party data or AI systems deemed…