---
title: "NIST 800-171 3.9.2 (PS.L2-3.9.2): Personnel Actions"
description: "NIST SP 800-171 3.9.2 Personnel Actions: 5 SPRS points, not allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/personnel-security/3.9.2
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/personnel-security/3.9.2
records: 7
digest: sha3:ef5599be21e22ee1ab551687b6c4d4e0424e9cf7c6e80a3a4fc17dd7f8e247c5
---

# NIST 800-171 3.9.2 (PS.L2-3.9.2): Personnel Actions

NIST 800-171 / Personnel Security / 3.9.2

"Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers." ([NIST SP 800-171 Rev. 2, requirement 3.9.2](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice PS.L2-3.9.2.

## What 3.9.2 means in practice

When someone leaves or moves to another job, their access ends or changes at the same time: accounts disabled, credentials and badges collected, and shared passwords changed. Assessors compare HR departure dates with account disable dates.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: PS.L2-3.9.2
- **SPRS points**: 5 points. When it is not met, the DoD Assessment Methodology subtracts 5 from the score of 110.
- **CMMC POA&M**: Not allowed. It is worth 5 points, and 32 CFR 170.21(a)(2)(ii) admits only requirements worth 1 point, with one exception: 3.13.11 when encryption is used but not FIPS validated.

Sources: [NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## What an assessor checks for 3.9.2

NIST SP 800-171A gives 3 determination statements for 3.9.2, each found satisfied or other than satisfied. Determine if:

- 3.9.2[a] a policy and/or process for terminating system access and any credentials coincident with personnel actions is established.
- 3.9.2[b] system access and credentials are terminated consistent with personnel actions such as termination or transfer.
- 3.9.2[c] the system is protected during and after personnel transfer actions.

[NIST SP 800-171A (June 2018), assessment objectives for 3.9.2](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.9.2 is met

- The offboarding and transfer procedure.
- HR termination and transfer records matched to the dates accounts were disabled or changed.
- Records of returned equipment, badges and tokens.

## How PolicyCortex gathers the evidence

PolicyCortex reads this evidence with the collectors below, read only, and grades 3.9.2 from it. Each line says what the product checks.

- **BambooHR: Leavers and joiners; Microsoft Entra ID and Okta: Leaver account lookups.** Reads who left in the last 90 days from BambooHR and checks that each leaver's Microsoft Entra ID and Okta accounts were disabled within the removal window and not used after the termination date.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.9.2 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-PS)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 2 Personnel Security requirements (3.9).](https://policycortex.com/nist-800-171/personnel-security)
- **Previous**: [3.9.1: Personnel Screening](https://policycortex.com/nist-800-171/personnel-security/3.9.1)
- **Next**: [3.10.1: Physical Access](https://policycortex.com/nist-800-171/physical-protection/3.10.1)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | 2570934b41cc | baef07255295 |
| REC 0001 | MEANING | 0c976ffb0a06 | 2570934b41cc |
| REC 0002 | POINTS AND POA&M | dd26d1327e63 | 0c976ffb0a06 |
| REC 0003 | ASSESSMENT OBJECTIVES | c9d26f63ebaa | dd26d1327e63 |
| REC 0004 | EVIDENCE | 7fbb7fb7d196 | c9d26f63ebaa |
| REC 0005 | COLLECTORS | 8263df7ec03c | 7fbb7fb7d196 |
| REC 0006 | RELATED | ef5599be21e2 | 8263df7ec03c |

Head sha3:ef5599be21e22ee1ab551687b6c4d4e0424e9cf7c6e80a3a4fc17dd7f8e247c5. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.