EvidenceSheet

MN-1.4 Negative residual risks, defined as the sum of all unmitigated risks, to both downstream acquirers of AI systems and end users are documented

Negative residual risks (defined as the sum of all unmitigated risks) to both downstream acquirers of AI systems and end users are documented. What remains unmitigated is totalled and documented, and communicated to down

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

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Evidence residual risk was communicated to those parties · Document repository

governing documentDocuments that govern the control

  • The documented residual risk position after treatment · Document repository
  • Identification of downstream acquirers and end users who bear residual risk · Document repository
  • The authority that accepted the residual position · Document repository

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

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.3 Responses to the AI risks deemed high priority as identified by the MAP function are developed, planned, and documented, and risk response options can include mitigating, transferring, avoiding, or accepting · MN-2.1 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