# NIST SP 800-53 Rev. 5 CP-2(7) — Coordinate With External Service Providers - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-2-7-coordinate-with-external-service-providers - 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) › CP — Contingency Planning - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `CP-2(7)`·high·Component: **Contingency Planning** ## What this control requires > Coordinate contingency plan with external service providers to ensure all contingency requirements are met, aligning expectations for third-party-dependent functions. This control supports the Integration capability within the Contingency Planning family. > > — NIST SP 800-53 Rev. 5, Control CP-2(7) ### In plain English Coordinate contingency plan with external service providers to ensure all contingency requirements are met, aligning expectations for third-party-dependent functions. In practice, this means you can prove you security 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 **Contingency Planning**, the assessor will trace your implementation back to the catalogue reference (Control CP-2(7)) 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 - **Security.** Document the trigger, the owner and the cadence. - **Chain.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Plan.** Document the trigger, the owner and the cadence. - **Contingency Plan.** Document the trigger, the owner and the cadence. - **Scope:** management, service, functions, external service providers, contingency plan, capability, requirements, security. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Coordinate With External Service Providers. ## 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. - [**ISO/IEC 27001:2022 A.5.20** — Addressing information security within supplier agreements](https://support.icompaas.com/compliance/iso-27001-2022/a-5-20-addressing-information-security-within-supplier-agreements) - [**NIST SP 800-171 Rev. 3 3.11.1** — Risk Assessment](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-11-1-risk-assessment) - [**SOC 2 (2017 TSC) CC9.2** — Vendor Risk Management](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc9-2-vendor-risk-management) - [**BSI C5:2020 OIS-03** — Interfaces and Dependencies](https://support.icompaas.com/compliance/bsi-c5-2020/ois-03-interfaces-and-dependencies) - [**CIS Controls v8 15.6** — Monitor Service Providers](https://support.icompaas.com/compliance/cis-controls-v8/15-6-monitor-service-providers) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-9(2)** — Identification Of Functions, Ports, Protocols, And Services](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-9-2-identification-of-functions-ports-protocols-and-services) - [**Control SC-7(19)** — Block Communication From Non-Organizationally Configured Hosts](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-7-19-block-communication-from-non-organizationally-configured-hosts) - [**Control SA-5(2)** — Security-Relevant External System Interfaces](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-5-2-security-relevant-external-system-interfaces) - [**Control SA-9** — External System Services](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-9-external-system-services) - [**Control SA-9(3)** — Establish And Maintain Trust Relationship With Providers](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-9-3-establish-and-maintain-trust-relationship-with-providers) - [**Control SA-13** — Trustworthiness](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-13-trustworthiness) ## 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 CP-2(7)` Topics: vendor riskvendor managementsupply chain securitythird party monitoring ## 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.