- Wire HR events to identity actions: the termination workflow must reach every identity store, including cloud applications, VPN, and any OT or shop-floor accounts, not just the primary directory.
- Set the disablement time period honestly and meet it; same-day disablement for involuntary departures is common practice.
- Treat transfers as re-authorization — the receiving role's access replaces the old, and shared credentials the person knew get rotated.
03.09.02OFFICIAL TITLEPENDING NIST SME REVIEW
03.09.02 — Personnel Termination and Transfer
03.09 Personnel Security · NIST SP 800-171 Rev. 3
Independent summary of the official requirement
Requires, on termination of employment, disabling system access within an organization-defined time period, terminating or revoking the individual's authenticators and credentials, and retrieving security-related system property; and, on reassignment or transfer, reviewing the continuing operational need for current logical and physical access and modifying access accordingly.
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
Departures and transfers are when access most often outlives the need for it. Terminations run on a clock — access disabled within the defined period, credentials revoked, badges and devices recovered — and transfers get a genuine access review instead of quiet accumulation.
Across revisions
Rev. 2's general 'protect systems during and after personnel actions' becomes concrete: Rev. 3 enumerates the termination and transfer steps and adds an organization-defined disablement time period.
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
- Offboarding records with disablement timestamps against the defined period
- Property-recovery checklists for badges, tokens, and devices
- Transfer access-review records
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 |