EvidenceSheet

AT-3 Role-Based Training

Provide role-based security training to personnel with significant security responsibilities before authorizing access and annually.

Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), AT-3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open FedRAMP High (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

7
artefacts
1
held by a system
2
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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Phishing simulation results with click and reporting rates · HR system / LMS

periodic reviewEvidence produced at each review

  • Role-based training completion records dated before privileged access was granted · HR system / LMS
  • Attestation records signed at onboarding and annually · HR system / LMS

governing documentDocuments that govern the control

  • SSP AT-3 statement listing roles with significant security duties (administrators, developers, incident responders) and the role-specific courses each must complete · HR system / LMS
  • Annual security awareness training curriculum and completion roster · HR system / LMS
  • Role based training plan for privileged users and developers · HR system / LMS
  • Insider threat awareness briefing materials · HR system / LMS

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your HR system / LMS 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

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

AT-2(3) Social Engineering and Mining · AT-4 Training Records