AT · Plan wizard

Awareness and Training Plan

Documents how the system's user, administrator, and developer populations are trained in security awareness, role-based duties, insider-threat indicators, social-engineering / phishing recognition, and how training records are maintained. Covers the controls of the AT family in NIST SP 800-53 r5 and aligns with NIST SP 800-50 (Building an Information Technology Security Awareness and Training Program), NIST SP 800-181 r1 (NICE Workforce Framework), DoD 8140.03 (Cyberspace Workforce Qualification and Management), and Federal Information Security Modernization Act (FISMA) annual training requirements.

1
Full official name of the information system.
Short identifier used in headings and references.
Role or named individual accountable for the system.
Describe what falls inside the authorization boundary - components, services, networks, data flows.
2
Determines which controls in this family appear in your plan.
3
Approach basics → §4.x

Platforms and roles that anchor the rest of the plan.

Where awareness + role-based training is delivered (e.g., 'KnowBe4 (commercial)', 'DoD CyberAwareness Challenge via JKO', 'Internal Moodle deployment with SCORM courses').
Authoritative system for training records (often the LMS itself, or a separate HRMS module that aggregates LMS + classroom + external).
Pointer to the org's insider-threat program — typically CISA-aligned for federal. Reference for AT-2(2) coordination.
Role accountable for phishing simulations (e.g., 'Security Awareness Lead under CISO', 'Enterprise SOC Phishing Operations').
Senior role accountable for the awareness-and-training program (often Chief Learning Officer / CISO delegate).
One-line summary of annual cadence (e.g., 'AT-2 baseline annually + on initial onboarding; AT-3 role-based at hire + annually + on role change'). Detail goes in the dedicated sub-section.
Literacy Training and Awareness (AT-2) → §4.x

Baseline security training that all users receive.

When training is delivered (e.g., 'Within 5 business days of onboarding; annually thereafter; within 30 days of role change'). AT-2 ODV.
What counts as 'complete' (e.g., 'Module completion + 80% on knowledge check; failed attempt → retake').
How often the awareness curriculum is reviewed for currency (typical: 'Annually + on regulatory change'). AT-2 ODV.
Per AT-2(1) — content updates triggered by significant events (incident affecting org, new threat, regulatory change). Even though AT-2(1) may not be in moderate baseline, this is good practice.
Insider-Threat Awareness (AT-2(2)) → §4.x

Per AT-2(2), training on indicators and reporting paths.

How an observer reports a concern (anonymous hotline, ISSO direct, EAP-assisted referral). Reference org insider-threat program contact.
Anti-retaliation policy, anonymity preservation. Reference org whistleblower policy.
Social-Engineering and Phishing (AT-2(3)) → §4.x

Per AT-2(3), training plus simulated exercises.

How often phishing simulations are run (e.g., 'Quarterly broad-cast; monthly targeted'). AT-2(3) ODV.
How simulation difficulty escalates over time (e.g., 'Easy generic in Q1; spear-phishing tied to system context in Q3; voice-phishing exercises annually').
What happens when a user clicks / enters credentials in a simulation. Just-in-time micro-training, manager notification, repeated-failure escalation. Reference PS-8 only as last resort.
How users report suspected phishing in production (e.g., 'PhishAlarm button in Outlook; submitted to SOC for analysis').
Targets for the program (e.g., 'Click rate <5%; report rate >40% on simulations within 60 minutes').
Role-Based Training (AT-3) → §4.x

Per AT-3, training tailored to the security responsibilities of each role.

Crosswalk from each role to required training (e.g., 'Privileged users: MIS-525 plus CompTIA Security+; Developers: SSDF familiarization + secure-coding + threat-modeling; Incident responders: SANS FOR-508 or equivalent'). Often summarized as a separate appendix.
When AT-3 training is delivered (e.g., 'At hire / role assignment; annually thereafter; on significant role expansion'). AT-3 ODV.
Roles that require external certification (e.g., 'CISSP for ISSO; Security+ CE for privileged users per DoD 8140; OSCP for red-team members'). Time-to-attain after role start.
How CE units are tracked (e.g., '40 hours per role per year; CISSP renewal at 120 CPEs / 3 years').
Training Records (AT-4) → §4.x

Per AT-4, recordkeeping requirements.

How long training records are retained. AT-4 ODV. Common: 'Per NARA records-retention schedule'; 'Length of employment + 5 years'.
How often training records are reviewed for completeness / accuracy (e.g., 'Quarterly reconciliation against personnel roster').
How changes to training records are themselves audited (immutable LMS log, separate audit table). Reference AU plan.
Training Scope and Coverage → §2.x

Quantitative scope numbers that anchor metrics later in the plan.

Approximate count of all personnel requiring AT-2 baseline training.
Approximate count of personnel in AT-3 roles.
Number of distinct role-based training tracks (e.g., '8 — System Owner, ISSO, Privileged User, Developer, IR Analyst, etc.').
Approximate count of users targeted in phishing simulations (typically all email-capable personnel).
Awareness-and-Training Metrics & KPIs → §6.x

Metrics tracked to demonstrate AT control effectiveness.

    Suggested:
    Training-Access Enforcement → §6.x

    How training currency is tied to access.

    Days after due date before enforcement action (e.g., '14 days for privileged accounts; 30 days for standard').
    Cross-references to other RMF artifacts → §7

    Where this plan plugs into the broader RMF package.

    Where in the SSP the AT control implementations are summarized (e.g., 'SSP §13.2').
    Convention for AT-related POA&M items (e.g., 'POAM-AT-' for general).
    How PS-6 access agreements pair with AT-2 awareness training; PS-9 position descriptions cite AT-3 requirements.
    How AT-2(3) phishing-simulation results feed IR detection; insider-threat indicators escalate via the same path.
    How AT-3 developer-training underwrites SA-3 SDLC integration. Where the developer-training catalog lives.
    How AT delivers the visitor-escort and physical-security awareness PE-3 / PE-6 implicate.
    How CA-2 assessments validate AT outcomes (training-effectiveness assessment, knowledge-check sampling, behavioral metrics).
    Pointer to the CA-7 monitoring strategy document tying AT continuous-monitoring metrics to the broader ConMon plan.
    4

    Pick a baseline in section 2 and the applicable controls will appear here. Each control gets a card with the official text, related controls, linked CCIs, and fields for your implementation status, narrative, responsible role, and evidence.

    5