- Add insider-threat indicators — data hoarding, off-hours access without a reason, disgruntlement paired with unusual system interest — to the existing awareness program rather than building a separate course.
- Name and publicize the reporting channel, and make it usable without accusing anyone: a concern raised early is a conversation, not a case.
- Keep the content factual and behavioral; training that reads as 'watch your coworkers' erodes the trust a small team runs on.
3.2.3OFFICIAL STATEMENT BELOWDERIVED REQUIREMENTPENDING NIST SME REVIEW
3.2.3 — Insider-threat awareness
3.2 Awareness and Training · NIST SP 800-171 Rev. 2 · The heading label is this site's navigational shorthand; the official language is the statement below.
Official requirement statement (verbatim)
Provide security awareness training on recognizing and reporting potential indicators of insider threat.
NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A — Assessing Security Requirements for CUI ↗Independent interpretation
What this requirement is after
People need to be able to recognize the warning signs that a colleague or contractor may be misusing their access — and to know exactly where to report a concern. The requirement is about awareness content and a working reporting path, not about surveillance of the workforce.
Across revisions
Withdrawn as a standalone requirement in Rev. 3 (the 03.02.03 slot is marked withdrawn); insider-threat recognition rides inside Literacy Training and Awareness, 03.02.01.
Mapped practices
Brilliant at the Basics practices that support this requirement
No practice maps to this requirement — deliberately.
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Doing the work
Implementation considerations and evidence
- Training content demonstrably covering insider-threat indicators and the reporting path
- Completion records showing the population that received it
Suggested owners, derived from the mapped practices and artifacts: Executive sponsor or HR lead. Ownership is a named person in your organization, not a role on a website.
Artifacts
Templates and worksheets with a mapped relationship
The other revision
Where this lands in Rev. 3
Provenance
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |