# NIST SP 800-53 Rev. 5 PS-5 — Personnel Transfer

- Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ps-5-personnel-transfer
- Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › PS — Personnel Security
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**NIST SP 800-53 Rev. 5**·Control `PS-5`·high·Component: **Personnel Security**

## What this control requires

> Review the operational need for current logical and physical access when individuals are reassigned or transferred, initiate necessary actions, and modify access as needed to align with new operational roles. This control supports the Governance capability within the Personnel Security family.
> 
> — NIST SP 800-53 Rev. 5, Control PS-5

### In plain English

Review the operational need for current logical and physical access when individuals are reassigned or transferred, initiate necessary actions, and modify access as needed to align with new operational roles. 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-5) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Physical Security

**Inheritance.** For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.

### Operational checklist

-   **Access.** Document the trigger, the owner and the cadence.
-   **Security.** Document the trigger, the owner and the cadence.
-   **Physical.** Document the trigger, the owner and the cadence.
-   **Modify.** Document the trigger, the owner and the cadence.
-   **Review.** Document the trigger, the owner and the cadence.
-   **Scope:** management, modify, actions, personnel, identity, review, capability, physical access.

## 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: Personnel Transfer.

## 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](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-9-1-personnel-screening)
-   [**SOC 2 (2017 TSC) CC6.1** — Logical Access Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-1-logical-access-controls)
-   [**CIS Controls v8 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control)
-   [**ISO/IEC 27001:2022 A.5.15** — Access control](https://support.icompaas.com/compliance/iso-27001-2022/a-5-15-access-control)
-   [**BSI C5:2020 PS-04** — Physical site access control](https://support.icompaas.com/compliance/bsi-c5-2020/ps-04-physical-site-access-control)

## Related controls in NIST SP 800-53 Rev. 5

-   [**Control PS-6(3)** — Post-Employment Requirements](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ps-6-3-post-employment-requirements)
-   [**Control PS-4(2)** — Automated Actions](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ps-4-2-automated-actions)
-   [**Control PS-6(2)** — Classified Information Requiring Special Protection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ps-6-2-classified-information-requiring-special-protection)
-   [**Control PS-9** — Position Descriptions](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ps-9-position-descriptions)
-   [**Control PE-2** — Physical Access Authorizations](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-2-physical-access-authorizations)
-   [**Control PE-2(3)** — Restrict Unescorted Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-2-3-restrict-unescorted-access)

## References

-   [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls)
-   Catalogue identifier: `Control PS-5`

Topics: identity accessidentity managementaccess reviewprivileged accessphysical security

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement.
- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.
