AT-3 Role-Based Training
Provide role-based security training to personnel with significant security responsibilities before authorizing access and annually.
6
artefacts
1
held by a system
1
at each review
hard
to go live
HR system / LMS
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Phishing simulation results with click and reporting rates · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Attestation records signed at onboarding and annually · HR system / LMS
governing documentDocuments that govern the control
- Control implementation statement for AT-3 citing the system mission and inheritance from common controls · HR system / LMS
- Annual security awareness training curriculum and completion roster · HR system / LMS
- Role based training plan for privileged users and developers · Policy repository / GRC workspace
- Insider threat awareness briefing materials · HR system / LMS
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Endpoint management (MDM / EDR) on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Contractors and third parties not enrolled in mandatory training
- Role based training not refreshed when job duties change
- Phishing failures not followed by remedial coaching
- Training content not reviewed annually for current threat trends
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-2(3) Social Engineering and Mining · AT-4 Training Records