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
Internal experts who did not serve as front-line developers for the system and/or independent assessors are involved in regular assessments and updates. Domain experts, users, AI actors external to the team that develope
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
- Assessment records naming assessors and their independence from development · Document repository
- Records of consultation with domain experts, users and affected communities · Document repository
governing documentDocuments that govern the control
- The link from risk tolerance to the level of independence required · Document repository
- Findings raised by independent assessors and their disposition · 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
- Independent review performed by another team under the same delivery owner
- Consultation limited to internal users
- Independent findings recorded but closed without action
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 sheetMS-1.2 Appropriateness of AI metrics and effectiveness of existing controls is regularly assessed and updated, including reports of errors and impacts on affected communities · MS-2.1 Test sets, metrics, and details about the tools used during test, evaluation, validation, and verification are documented