EvidenceSheet

MS-2.1 Test sets, metrics, and details about the tools used during test, evaluation, validation, and verification are documented

Test sets, metrics, and details about the tools used during test, evaluation, validation, and verification (TEVV) are documented. The TEVV record is complete enough for the evaluation to be repeated: which test sets, whi

4
artefacts
1
held by a system
0
at each review
moderate
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • The metrics computed and their definitions · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Documentation of the test sets used, including provenance and composition · Document repository
  • Tools and versions used during evaluation · Document repository
  • Sufficient detail for the evaluation to be repeated by someone else · Document repository

First move

Start with the 1 of 4 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.

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-1.3 Internal experts who did not serve as front-line developers for the system and independent assessors are involved in regular assessments and updates, and domain experts, users, AI actors external to the team, and affected communities are consulted in support of assessments as necessary per organizational risk tolerance · MS-2.2 Evaluations involving human subjects meet applicable requirements including human subject protection and are representative of the relevant population