CP-3 Contingency training
Requires contingency training for system users appropriate to their assigned roles, delivered within a defined period of taking on a contingency role, repeated when system changes require it and at a defined frequency, w
4
artefacts
1
held by a system
2
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Completion records showing training within the defined period of role assignment · Identity provider / directory
periodic reviewEvidence produced at each review
- Refresher training evidence at the defined frequency · HR system / LMS
- Content revision history following exercises, incidents or system changes · Document repository
governing documentDocuments that govern the control
- Contingency training syllabus mapped to contingency roles · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Only the recovery team trained while business function owners are not
- New role holders wait for the annual session rather than being trained on assignment
- Training content unchanged after an exercise exposed procedural failures
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