Most organisations can show an assessor a training completion report, yet far fewer can show that the right people received the right training before they were given access, or that last year's incidents changed what was taught. The Awareness and Training (AT) family of NIST SP 800-53 Rev. 5 is short, only six base controls with two withdrawn, but its organisation-defined parameters and its links to incident lessons make it harder to evidence than it looks. This guide walks through every AT control and enhancement, the baselines they appear in, how to set the parameters, what evidence holds up under SP 800-53A style assessment, and how to measure whether the programme changes behaviour. It is written for control owners, GRC teams, training leads and system owners preparing a System Security Plan. For the catalogue as a whole, see the NIST SP 800-53 Guide.
Key takeaways
- Four controls carry the family. AT-1 policy, AT-2 literacy training and awareness, AT-3 role-based training and AT-4 training records are in the Low, Moderate and High baselines; AT-6 training feedback is a tailoring option.
- AT-2(2) insider threat is baseline from Low upwards. AT-2(3) social engineering and mining is added at Moderate and High, so phishing and pretexting content is an explicit requirement for most federal systems.
- Timing is part of the control. AT-3 requires role-based training before access is authorised or duties are performed, which means the access request workflow, not the learning platform, is where the control really lives.
- Lessons learned are mandatory. AT-2 item d and AT-3 item c require incident and breach lessons to be fed into content, so the training owner needs a standing link to the incident response process.
- Completion is evidence, not outcome. AT-4 records prove the activity happened; reporting rates, simulation results and role-specific errors show whether it worked, and AT-6 asks you to feed those results back to named personnel.
The AT family at a glance
The AT family sits in the Rev. 5 catalogue alongside the other operational families. Rev. 5 renamed AT-2 from "Security Awareness Training" to "Literacy Training and Awareness" and added privacy throughout, so every AT control now covers both security and privacy content. Two items are withdrawn: AT-3(4) moved to AT-2(4), and AT-5 Contacts with Security Groups and Associations was incorporated into PM-15. The table below lists every current control and enhancement with its baseline allocation from the SP 800-53B baseline profiles.
| ID | Title | What it requires (summary) | Baseline |
|---|---|---|---|
| AT-1 | Policy and Procedures | Awareness and training policy and procedures, a designated official, review on a defined frequency and after defined events | Low, Moderate, High, Privacy |
| AT-2 | Literacy Training and Awareness | Security and privacy literacy training for all users at onboarding, at a defined frequency, after system changes and defined events; awareness techniques; content updates; incident lessons | Low, Moderate, High, Privacy |
| AT-2(1) | Practical Exercises | Exercises in literacy training that simulate events and incidents | Tailoring option |
| AT-2(2) | Insider Threat | Training on recognising and reporting potential indicators of insider threat | Low, Moderate, High |
| AT-2(3) | Social Engineering and Mining | Training on recognising and reporting social engineering and social mining | Moderate, High |
| AT-2(4) | Suspicious Communications and Anomalous System Behavior | Training on recognising suspicious communications and anomalous behaviour using defined indicators of malicious code | Tailoring option |
| AT-2(5) | Advanced Persistent Threat | Literacy training on the advanced persistent threat | Tailoring option |
| AT-2(6) | Cyber Threat Environment | Training on the current threat environment, and reflecting current threat information in system operations | Tailoring option |
| AT-3 | Role-based Training | Role-based security and privacy training for defined roles before access or duties, at a defined frequency and after system changes; content updates; incident lessons | Low, Moderate, High, Privacy |
| AT-3(1) | Environmental Controls | Initial and periodic training for defined personnel on operating environmental controls | Tailoring option |
| AT-3(2) | Physical Security Controls | Initial and periodic training for defined personnel on operating physical security controls | Tailoring option |
| AT-3(3) | Practical Exercises | Exercises in role-based training that reinforce training objectives | Tailoring option |
| AT-3(5) | Processing Personally Identifiable Information | Initial and periodic training for defined personnel on PII processing and transparency controls | Privacy |
| AT-4 | Training Records | Document and monitor training activities; retain individual records for a defined period | Low, Moderate, High, Privacy |
| AT-6 | Training Feedback | Feed training results back to defined personnel at a defined frequency | Tailoring option |
Note that the Moderate and High baselines contain the same AT selections. Tailoring for High systems therefore usually adds enhancements such as AT-2(1), AT-2(4) or AT-3(3) by organisational choice rather than by baseline. See the NIST SP 800-53B Control Baselines and Tailoring Guide for how to document those decisions.
AT-1: policy, procedures and the designated official
AT-1 follows the same pattern as every family's "-1" control. It asks for an awareness and training policy at one or more of organisation, mission or business process, and system level, procedures to implement it, an official designated to manage both, and review of each on a defined frequency and after defined events.
- Policy level: most organisations write one organisation-level policy and let systems inherit it. Record the inheritance in each SSP so the assessor is not hunting for a system-level document that does not need to exist.
- Designated official: name a role, not a person, for example the head of security awareness or the CISO's delegate. The same role usually owns AT-2 content.
- Review triggers: set a frequency (commonly annual for the policy) and events such as a significant incident, a change in regulatory requirements, an assessment finding or a reorganisation. AT-1's events should line up with the AT-2 and AT-3 content update events so that one trigger flows through policy and content together.
- Coordination: the policy should say how HR, the identity team, privacy and incident response feed the programme. Without that, AT-3 timing and AT-2 lessons learned have no owner.
AT-2: literacy training, awareness and its enhancements
AT-2 applies to all system users, and the control text names managers, senior executives and contractors explicitly. It has four parts, and each has an organisation-defined parameter to set in the SSP.
| AT-2 part | Parameter to define | Typical value and rationale |
|---|---|---|
| a.1 Initial and recurring training | Frequency thereafter | At onboarding before or shortly after first access, then annually; shorter refreshers quarterly where risk is high |
| a.2 Event-driven training | Events | Major system change, new data type, significant incident, role change, return from extended leave |
| b. Awareness techniques | Techniques | Phishing simulations, intranet notices, short videos, posters, team briefings, reporting button reminders |
| c. Content updates | Frequency and events | Annual content review, plus after incidents, new threat advisories or changes to policy |
| d. Lessons learned | No parameter | Each post-incident review produces a content action, tracked to closure |
The enhancements in practice
- AT-2(2) Insider threat: teach users which indicators matter (unusual data movement, attempts to obtain access outside role, disgruntlement combined with access) and, more importantly, how to report them confidentially. Align the content with the insider threat programme so reports go somewhere. See the Insider Threat Programme Guide.
- AT-2(3) Social engineering and mining: cover phishing, vishing, smishing, pretexting at the help desk and social mining (collecting organisational detail from public sources and social media). The Moderate and High baselines require it. See the Vishing and Help Desk Social Engineering Awareness Guide.
- AT-2(1) Practical exercises: simulated events, such as phishing simulations or tabletop walk-throughs for staff, satisfy this. Design simulations to teach, not to catch people out. See the Phishing Simulation Programme Guide.
- AT-2(4) Suspicious communications and anomalous system behavior: the parameter is the set of indicators of malicious code users are taught to spot, for example unexpected MFA prompts, browser pop-ups demanding credentials, sudden file renaming or encryption notes.
- AT-2(5) Advanced persistent threat and AT-2(6) Cyber threat environment: these suit organisations that are known targets. AT-2(6) part (b) goes beyond training and asks that current threat information is reflected in system operations, which ties it to the threat intelligence function and PM-16 Threat Awareness Program.
AT-3: role-based training and its enhancements
AT-3 is where most assessment findings come from. The organisation defines the roles that need role-based training, and the training must happen before access to the system or information is authorised, or before assigned duties are performed, then at a defined frequency and when system changes require it. Content must be updated on a defined frequency and after defined events, and incident lessons must be incorporated.
Defining the roles
Start from the roles the system actually has rather than job titles. A practical set for most systems:
- Privileged administrators: system, database, cloud and directory admins; content on privileged access handling, change control, logging duties and break-glass procedures.
- Developers and DevOps engineers: secure coding, secrets handling, pipeline security, dependency risk. SA-16 Developer-provided Training covers training that external developers supply about their products, which is a separate obligation.
- Security operations and incident responders: IR-2 Incident Response Training covers their incident-specific training; AT-3 covers broader role duties.
- Owners of non-human identities: people who create and own service accounts, API keys and automation credentials need content on rotation, scoping, vaulting and decommissioning. This is a role many programmes miss. See the NIST SP 800-53 IA Identification and Authentication family for the related credential controls.
- Privacy roles: staff who process PII; AT-3(5) is in the privacy baseline and pairs with the PT family. See the NIST SP 800-53 PT PII Processing and Transparency guide.
- Executives and authorising officials: risk acceptance, incident decision-making and their own targeting by social engineering.
Enhancements
- AT-3(1) Environmental controls and AT-3(2) Physical security controls: for facilities staff who operate fire suppression, HVAC, access control systems and CCTV. They pair with the PE family; see the NIST SP 800-53 PE Physical and Environmental Protection guide.
- AT-3(3) Practical exercises: labs, capture-the-flag style exercises for engineers, and restore drills for administrators.
- AT-3(5) Processing PII: initial and periodic training for defined personnel on PII processing and transparency controls.
Enforcing "before access": the reliable way to meet AT-3 timing is to make role-based training completion a precondition in the access request workflow. Map each privileged or sensitive entitlement in the identity governance tool to the training module it requires, and have the request fail or route for exception approval if the record is missing. This also produces AT-4 evidence automatically. AC-2 Account Management conditions and PS-6 Access Agreements are the natural places to anchor the check. See the NIST SP 800-53 AC Access Control and NIST SP 800-53 PS Personnel Security guides.
AT-4 and AT-6: records and feedback
AT-4 asks you to document and monitor security and privacy training activities, both literacy and role-based, and to retain individual training records for a defined period. AT-6, a tailoring option, asks you to provide feedback on training results to defined personnel at a defined frequency.
- Record content: person, role, module and version, date assigned, date completed, score where assessed, and the entitlement or role the training was tied to. Recording the module version proves that updated content (AT-2 c, AT-3 b) actually reached people.
- Retention period: set it to cover at least your assessment cycle and the employment period plus a margin agreed with records management and legal. Whatever value you choose, apply it consistently across the learning platform, HR system and any exports.
- Monitoring: overdue reports to line managers, and a feed to the identity team for overdue role-based training on privileged accounts.
- AT-6 feedback audience: typically senior leadership, system owners and the CISO, quarterly. Include behaviour metrics, not just completion.
How to evidence AT controls
SP 800-53A assessment uses examine, interview and test methods. The table lists the evidence that tends to satisfy each control. See the NIST SP 800-53A Guide for the method itself.
| Control | Examine | Interview or test |
|---|---|---|
| AT-1 | Approved policy with version history, procedures, designation of official, review records | Interview the designated official on review triggers |
| AT-2 | Curriculum, content change log, awareness calendar, completion reports, lessons-learned actions | Sample new starters and contractors for onboarding completion dates against account creation dates |
| AT-2(2), AT-2(3) | Module content covering indicators and reporting routes | Ask sampled users how they would report an insider concern or a suspicious call |
| AT-3 | Role-to-module matrix, access workflow configuration | Sample privileged accounts and compare entitlement grant date with role training completion date |
| AT-4 | Training records with retention setting | Retrieve records for a leaver from the retention window |
| AT-6 | Feedback reports and distribution list | Interview recipients on actions taken |
Implementing the AT family: a phased approach
- Inventory roles and populations. Pull user populations from HR and the directory, including contractors and third-party staff with accounts. Build the role list for AT-3 from privileged groups, entitlement catalogues and NHI ownership records.
- Set parameters. Decide the frequencies, events, techniques and retention period for AT-1, AT-2, AT-3, AT-4 and, if selected, AT-6. Write them into the SSP and the policy so the two match.
- Build or map content. Map each enhancement in your baseline (AT-2(2), AT-2(3) at Moderate and High, AT-3(5) for privacy) to a specific module. SP 800-50 Rev. 1 describes a life cycle approach to a Cybersecurity and Privacy Learning Program that is useful for structuring this.
- Pilot. Run new modules with one business unit and one technical team. Check completion time, comprehension scores and help desk tickets before wide release.
- Wire up the gates. Add role-based training checks to the access request workflow for a small set of privileged entitlements first, in report-only mode, then enforce. Keep an exception path with approval and expiry so urgent access can still be granted and later reviewed; that is your rollback.
- Connect incident response. Add a "training action" field to the post-incident review template and route those actions to the AT-1 designated official.
- Measure and feed back. Produce the AT-6 report and use it to adjust content and frequency.
Decision guidance
- Annual versus continuous: an annual module is simple to evidence but decays quickly. Short monthly content plus an annual attestation meets the frequency parameter and improves retention; record both in AT-4.
- Selecting tailoring enhancements: add AT-2(1) when you run phishing simulations anyway, because it turns existing activity into evidence. Add AT-2(4) when users are a meaningful detection source, for example in organisations with a strong reporting culture. Add AT-3(3) for engineering roles where hands-on skills matter more than knowledge.
- Small versus large organisations: a small organisation can run one literacy course and three role tracks with a spreadsheet-backed record and manual access checks. A large one needs the learning platform integrated with HR for joiners and movers and with identity governance for entitlement gates.
- Contractors: AT-2 explicitly includes contractors. Either deliver your own training or accept the supplier's, but in the second case obtain records that meet AT-4 and confirm the content covers your baseline enhancements.
- 800-53 versus 800-171: SP 800-171 Rev. 3 requirements 03.02.01 Literacy Training and Awareness and 03.02.02 Role-Based Training cover similar ground for non-federal systems. See NIST 800-53 vs 800-171.
Detection and measurement
Training controls are measured by behaviour as well as activity. Useful metrics:
- On-time onboarding completion: percentage of new users who complete literacy training within the defined window after account creation.
- Role-training gate compliance: percentage of privileged entitlement grants with completed role-based training before the grant date, and the count of exceptions open past expiry.
- Phishing report rate and time to report: share of simulated and real phishing reported by users, and median minutes from delivery to first report. A rising report rate matters more than a falling click rate.
- Lessons-learned closure: number of post-incident training actions closed within the target period.
- Content currency: percentage of modules reviewed within the defined update frequency.
- Repeat-event rate: recurrence of the same human-factor root cause in incidents after training was updated.
Framework mapping
| AT control | NIST CSF 2.0 | NIST SP 800-171 Rev. 3 | CIS Controls v8.1 | ISO/IEC 27001:2022 |
|---|---|---|---|---|
| AT-1 | GV.RR-04 | 03.15.01 | Control 14 (programme) | A.6.3 |
| AT-2 and enhancements | PR.AT-01 | 03.02.01 | Control 14 | A.6.3 |
| AT-3 and enhancements | PR.AT-02 | 03.02.02 | Control 14 | A.6.3 |
| AT-4 | PR.AT-01, PR.AT-02 | 03.02.01, 03.02.02 | Control 14 | A.6.3 |
Related controls outside the family: PM-13 Security and Privacy Workforce, PM-14 Testing, Training, and Monitoring, PM-15 Security and Privacy Groups and Associations (which absorbed AT-5), IR-2 Incident Response Training, CP-3 Contingency Training and SA-16 Developer-provided Training. See the CIS Control 14 Security Awareness and Skills Training Guide and the NIST SP 800-53 to ISO 27001 Mapping Guide.
Common failure patterns
- Training after access: privileged access is granted on day one and role-based training is assigned with a 30-day deadline, which fails the "before authorizing access" wording of AT-3.
- Contractors outside the platform: third-party staff with accounts never appear in the learning system, so AT-2 coverage reports look complete but are not.
- No lessons-learned loop: post-incident reviews identify a human factor but no content changes follow, leaving AT-2 d and AT-3 c without evidence.
- Parameters that do not match reality: the SSP says quarterly refreshers, the platform runs annual ones. Assessors test against what you wrote.
- Click rate as the only metric: punitive simulation programmes depress reporting. Track reporting behaviour and time to report as well.
- Help desk not treated as a role: social engineering of support staff to reset credentials is a recurring pattern; help desk staff need role-based content on identity verification, not only general awareness.
Practitioner checklist
- Confirm your baseline's AT selections: AT-1, AT-2, AT-2(2), AT-3, AT-4 at Low, plus AT-2(3) at Moderate and High, plus AT-3(5) for the privacy baseline.
- Write every organisation-defined parameter into the SSP and make the policy and platform settings match.
- Name the AT-1 designated official by role and set review events that match content update events.
- Build a role-to-module matrix that includes help desk staff and owners of non-human identities.
- Gate privileged entitlements on completed role-based training, with an approved, expiring exception path.
- Include contractors and third-party staff in AT-2 coverage and AT-4 records.
- Add a training action to every post-incident review and track it to closure.
- Record module versions in training records and set a retention period with records management.
- Report reporting rates, time to report and gate compliance to leadership, not just completion.
Standards and references
- NIST: SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations
- NIST: SP 800-53B, Control Baselines for Information Systems and Organizations
- NIST: SP 800-50 Rev. 1, Building a Cybersecurity and Privacy Learning Program
- NIST: SP 800-181 Rev. 1, Workforce Framework for Cybersecurity (NICE Framework)
- NIST: SP 800-171 Rev. 3, Protecting Controlled Unclassified Information
- NIST: Cybersecurity Framework 2.0
- NIST: OSCAL content, SP 800-53 Rev. 5 catalogue and baseline profiles
Related NHI Mgmt Group resources: NIST SP 800-53 Guide · NIST SP 800-53 AU Audit and Accountability · Security Awareness and Human Risk Management Guide · NIST SP 800-53 PM Program Management