- Define the screening standard by role and contract; many defense contracts specify minimums, and citizenship or export-control constraints may sit on top.
- Sequence provisioning behind screening — completing checks after access is granted inverts the requirement.
- Name the rescreening triggers (elevation to higher privilege, adverse information, contract requirement) rather than leaving the conditions undefined.
03.09.01OFFICIAL TITLEPENDING NIST SME REVIEW
03.09.01 — Personnel Screening
03.09 Personnel Security · NIST SP 800-171 Rev. 3
Independent summary of the official requirement
Requires screening individuals prior to authorizing access to the system and rescreening individuals in accordance with organization-defined conditions.
Rev. 3 requirement text is multi-part and parameterized with organization-defined values, so this site summarizes rather than reproduces it. The summary is independent — read the official publication for the binding wording.
NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI ↗Independent interpretation
What this requirement is after
Before someone gets access to systems handling CUI, the organization does its diligence — background checks proportionate to role and contract — and defines the events that trigger a second look later. Screening is a personnel process, but the requirement binds it to system access.
Across revisions
Rev. 2's screening requirement carries forward, with rescreening under organization-defined conditions now explicit.
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
- Screening completion records datable against access-grant dates
- The written screening and rescreening criteria
Artifacts
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
The other revision
Where this came from in Rev. 2
Provenance
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |