AT.L2-3.2.2 Role-Based Training
Train personnel to perform the specific information security duties and responsibilities assigned to their roles.
3
artefacts
0
held by a system
2
at each review
hard
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
none for this control
periodic reviewEvidence produced at each review
- Role based training content and completion records · Identity provider / directory
- Evidence training precedes assumption of the duty · HR system / LMS
governing documentDocuments that govern the control
- Role to security duty mapping · Policy repository / GRC workspace
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
- One generic course used for every role
- Training delivered after the duty is already being performed
- Specialized roles such as administrators given no additional training
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 sheetAT.L2-3.2.1 Role-Based Risk Awareness · AT.L2-3.2.3 Insider Threat Awareness