# NIST SP 800-53 Rev. 5 PE-9(1) — Redundant Cabling - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-9-1-redundant-cabling - 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-9(1)`·critical·Component: **Physical and Environmental Protection** ## What this control requires > Employing redundant power cabling paths that are physically separated by a specified distance. This ensures that power continues to flow if one cable is cut or damaged, enhancing the reliability of the power supply. This control supports the Redundant Calling capability within the Physical and Environmental Protection family. > > — NIST SP 800-53 Rev. 5, Control PE-9(1) ### In plain English Employing redundant power cabling paths that are physically separated by a specified distance. In practice, this means you can prove you policy 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 **critical** in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping. ## 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-9(1)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Physical.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Environmental.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Scope:** management, controls, protection, capability, power, policy, supply. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: Redundant Cabling. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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. - [**HIPAA (45 CFR Part 164) 164.312(b)** — Audit Controls](https://support.icompaas.com/compliance/hipaa/164-312-b-audit-controls) - [**ISO/IEC 27001:2022 A.7.11** — Supporting utilities](https://support.icompaas.com/compliance/iso-27001-2022/a-7-11-supporting-utilities) - [**SOC 2 (2017 TSC) PI1.4** — Output Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/pi1-4-output-controls) - [**NIST SP 800-171 Rev. 3 3.13.15** — Session Authenticity](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-15-session-authenticity) - [**BSI C5:2020 SP-01** — Documentation, communication and provision of policies and instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-01-documentation-communication-and-provision-of-policies-and-instructions) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control PE-11(2)** — Alternate Power Supply -- Self-Contained](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-11-2-alternate-power-supply-self-contained) - [**Control PE-11(1)** — Alternate Power Supply -- Minimal Operational Capability](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-11-1-alternate-power-supply-minimal-operational-capability) - [**Control PE-10(1)** — Accidental And Unauthorized Activation](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-10-1-accidental-and-unauthorized-activation) - [**Control PE-12(1)** — Essential Mission And Business Functions](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-12-1-essential-mission-and-business-functions) - [**Control PE-11** — Emergency Power](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-11-emergency-power) - [**Control PE-9** — Power Equipment And Cabling](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-9-power-equipment-and-cabling) ## 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-9(1)` Topics: governance riskenvironmental controlspolicy management ## 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.