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

MP-4.1 Approaches for mapping AI technology and legal risks of its components, including the use of third-party data…

Approaches for mapping AI technology and legal risks of its components – including the use of third-party data or software – are in place, followed, and documented, as are risks of infringement of a third-party’s intellectual property or other rights. There is a followed approach for mapping the technology and legal risk carried by each component, including data and software obtained from third parties and the rights position attached to them.

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

  • Intellectual property and rights analysis for each third-party component · Vendor register / contract repository
  • Evidence the approach was followed for the components actually in use · Vendor register / contract repository

governing documentDocuments that govern the control

  • The documented approach for mapping component technology and legal risk · Vendor register / contract repository
  • Component inventory identifying third-party data, models and software · Vendor register / contract 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-3.5 Processes for human oversight are defined, assessed, and documented in accordance with organizational… · MP-4.2 Internal risk controls for components of the AI system including third-party AI technologies are identified…