# NIST SP 800-53 Rev. 5 PE-16 — Delivery And Removal - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-16-delivery-and-removal - 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) › PE — Physical and Environmental Protection - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `PE-16`·medium·Component: **Physical and Environmental Protection** ## What this control requires > Authorize and control entry/exit of organization-defined system components (e.g., servers, storage devices) in facilities like data centers. Maintain records of these components to ensure security and accountability. This control supports the Access Control and Tracking System capability within the Physical and Environmental Protection family. > > — NIST SP 800-53 Rev. 5, Control PE-16 ### In plain English Authorize and control entry/exit of organization-defined system components (e.g., servers, storage devices) in facilities like data centers. 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. ## 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 **Physical and Environmental Protection**, the assessor will trace your implementation back to the catalogue reference (Control PE-16) 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. - **Security.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Physical.** Document the trigger, the owner and the cadence. - **Authorize.** Document the trigger, the owner and the cadence. - **Scope:** management, access control, organization, system, removal, e, records, protection. ## 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: Delivery And Removal. ## 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.15.2** — System Security Plan](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-15-2-system-security-plan) - [**CIS Controls v8 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control) - [**SOC 2 (2017 TSC) CC6.4** — Physical Access Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-4-physical-access-controls) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control PE-2(2)** — Two Forms Of Identification](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-2-2-two-forms-of-identification) - [**Control PE-3(1)** — System Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-3-1-system-access) - [**Control PE-3(8)** — Access Control Vestibules](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-3-8-access-control-vestibules) - [**Control PE-4** — Access Control For Transmission](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-4-access-control-for-transmission) - [**Control PE-7** — Visitor Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-7-visitor-control) - [**Control PE-14(2)** — Monitoring With Alarms And Notifications](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-14-2-monitoring-with-alarms-and-notifications) ## 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 PE-16` Topics: identity accessdata protectionidentity managementaccess reviewprivileged access ## 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.