# NIST SP 800-53 Rev. 5 SC-7(14) — Protect Against Unauthorized Physical Connections - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-7-14-protect-against-unauthorized-physical-connections - 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) › SC — System and Communications Protection - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SC-7(14)`·critical·Component: **System and Communications Protection** ## What this control requires > Protect against unauthorized physical connections at organization-defined managed interfaces. This can be achieved through physical separation of cable trays, connection frames, and patch panels, with access controls enforcing limited access to authorized personnel only. This control supports the Physical Access Control Mechanisms capability within the System and Communications Protection family. > > — NIST SP 800-53 Rev. 5, Control SC-7(14) ### In plain English Protect against unauthorized physical connections at organization-defined managed interfaces. 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 **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 **System and Communications Protection**, the assessor will trace your implementation back to the catalogue reference (Control SC-7(14)) 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. - **Physical.** Document the trigger, the owner and the cadence. - **Separation.** 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, access control, organization, system, only, personnel, controls, 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: Protect Against Unauthorized Physical Connections. ## 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. - [**CIS Controls v8 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control) - [**NIST SP 800-171 Rev. 3 3.10.8** — Access Control for Transmission](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-10-8-access-control-for-transmission) - [**SOC 2 (2017 TSC) CC6.4** — Physical Access Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-4-physical-access-controls) - [**BSI C5:2020 PS-04** — Physical site access control](https://support.icompaas.com/compliance/bsi-c5-2020/ps-04-physical-site-access-control) - [**ISO/IEC 27001:2022 A.8.2** — Privileged access rights](https://support.icompaas.com/compliance/iso-27001-2022/a-8-2-privileged-access-rights) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control MP-2(1)** — Automated Restricted Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-2-1-automated-restricted-access) - [**Control SC-7(11)** — Restrict Incoming Communications Traffic](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-7-11-restrict-incoming-communications-traffic) - [**Control MP-2** — Media Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-2-media-access) - [**Control AC-5** — Separation Of Duties](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-5-separation-of-duties) - [**Control SC-7(3)** — Access Points](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-7-3-access-points) - [**Control SC-42(1)** — Reporting To Authorized Individuals Or Roles](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-42-1-reporting-to-authorized-individuals-or-roles) ## 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 SC-7(14)` Topics: identity accessidentity managementaccess reviewprivileged accesspatch 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.