NIST SP 800-53 Rev. 5 PS-6(3) — Post-Employment Requirements

What this control requires

Notify individuals of applicable, legally binding post-employment requirements for the protection of organizational information and require them to sign an acknowledgment of these requirements as part of granting initial access to covered information. This control supports the Governance capability within the Personnel Security family.

In plain English

Notify individuals of applicable, legally binding post-employment requirements for the protection of organizational information and require them to sign an acknowledgment of these requirements as part of granting initial access to covered information. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Personnel Security, the assessor will trace your implementation back to the catalogue reference (Control PS-6(3)) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Information. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Protection. Document the trigger, the owner and the cadence.
• Scope: management, information, personnel, protection, identity, review, capability, requirements.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Post-Employment Requirements.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-171 Rev. 3 3.9.1 — Personnel Screening
• ISO/IEC 27001:2022 A.5.15 — Access control
• CIS Controls v8 9.2 — Use DNS Filtering Services
• SOC 2 (2017 TSC) CC6.6 — Boundary Protection
• ISO/IEC 27701:2025 A.3.8 — Identity management

Related controls in NIST SP 800-53 Rev. 5

• Control PS-6(2) — Classified Information Requiring Special Protection
• Control PS-3(3) — Information Requiring Special Protection Measures
• Control PS-9 — Position Descriptions
• Control PS-6(1) — Information Requiring Special Protection
• Control SC-42(1) — Reporting To Authorized Individuals Or Roles
• Control IA-5(6) — Protection Of Authenticators

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control PS-6(3)

Topics: identity accessidentity managementaccess reviewprivileged access