EvidenceSheet

MP-3.4 Processes for operator and practitioner proficiency with AI system performance and trustworthiness, and relevant technical standards and certifications, are defined, assessed and documented

Processes for operator and practitioner proficiency with AI system performance and trustworthiness – and relevant technical standards and certifications – are defined, assessed and documented. Operator proficiency is def

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

  • Assessment records showing proficiency was tested, not assumed · Document repository

governing documentDocuments that govern the control

  • Defined proficiency requirements for operators and practitioners of the system · Document repository
  • Relevant technical standards or certifications identified for the role · Policy repository / GRC workspace
  • Refresh arrangements when the system or its performance changes · 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

MP-3.3 Targeted application scope is specified and documented based on the system's capability, established context, and AI system categorization · MP-3.5 Processes for human oversight are defined, assessed, and documented in accordance with organizational policies from the GOVERN function