EvidenceSheet

MS-2.2 Evaluations involving human subjects meet applicable requirements including human subject protection and are representative of the relevant population

Evaluations involving human subjects meet applicable requirements (including human subject protection) and are representative of the relevant population. Where evaluation involves human subjects or data captured from the

4
artefacts
0
held by a system
2
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 the applicable human subject protection requirements were met, including any approval obtained · Document repository
  • Consent and data handling records for subject data used in evaluation · Data governance / DLP tooling

governing documentDocuments that govern the control

  • Identification of evaluations involving human subjects or human subject data · Document repository
  • Analysis of representativeness against the relevant population · 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

MS-2.1 Test sets, metrics, and details about the tools used during test, evaluation, validation, and verification are documented · MS-2.3 AI system performance or assurance criteria are measured qualitatively or quantitatively and demonstrated for conditions similar to deployment settings, and measures are documented