Skip to main content

BCD-17: Telecommunications Services Availability

BCD 6 — Medium Recover

Mechanisms exist to reduce the likelihood of a single point of failure with primary telecommunications services.

Renumbered: Formerly BCD-10 in SCF 2025.4.

Control Question: Does the organization reduce the likelihood of a single point of failure with primary telecommunications services?

General (17)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) A1.2
GovRAMP CP-08 CP-08(02)
GovRAMP Core CP-08 CP-08(02)
GovRAMP Low+ CP-08
GovRAMP Moderate CP-08 CP-08(02)
GovRAMP High CP-08 CP-08(02)
NIST 800-53 R4 CP-8 CP-8(2) CP-11
NIST 800-53 R5.2 CP-08 CP-08(02) CP-11
NIST 800-53B R5 (moderate) (source) CP-08 CP-08(02)
NIST 800-53B R5 (high) (source) CP-08 CP-08(02)
NIST 800-82 R3 CP-08 CP-08(02) CP-11
NIST 800-82 R3 MODERATE OT Overlay CP-08 CP-08(02)
NIST 800-82 R3 HIGH OT Overlay CP-08 CP-08(02)
NIST 800-160 Vol2 R1 CP-11
NIST 800-161 R1 CP-8 CP-11
NIST 800-161 R1 Level 2 CP-8 CP-11
NIST 800-161 R1 Level 3 CP-8 CP-11
US (6)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 CP-8 CP-8-IS.a CP-8-IS.b CP-8(2)
USA Federal CJIS Security Policy 6.0 CP-8 CP-8(2)
USA Federal FedRAMP R5 (moderate) CP-08 CP-08(02)
USA Federal FedRAMP R5 (high) CP-08 CP-08(02)
USA Texas DIR SCSC 2.2 2025 CP-08 CP-11
USA Texas TX-RAMP Level 2 CP-08
EMEA (1)
Framework Mapping Values
EMEA EU DORA RTS 2024 Article 26.2(d)
APAC (1)
Framework Mapping Values
APAC Malaysia RMiT 2025 10.37 A7-D2(d)(iii)

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 — Planned & Tracked

Business Continuity & Disaster Recovery (BCD) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Business Continuity / Disaster Recovery (BC/DR)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ BC/DR may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.

Level 3 — Well Defined

Business Continuity & Disaster Recovery (BCD) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are well-documented and kept current by process owners. ▪ A Business Continuity & Disaster Recovery (BC/DR) team, or similar function, is appropriately staffed and supported to implement and maintain BCD domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of BC/DR operations (e.g., BC/DR planning software, Disaster Recovery as a Service (DRaaS), Orchestration and Automation Tools). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to reduce the likelihood of a single point of failure with primary telecommunications services.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. BCD-17_A01 alternative communications protocols in support of maintaining continuity of operations are defined.
  2. BCD-17_A02 the capability to employ alternative communications protocols are provided in support of maintaining continuity of operations.
  3. BCD-17_A03 system operations to be resumed for essential mission and business functions are defined.
  4. BCD-17_A04 time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailable is defined.
  5. BCD-17_A05 alternate telecommunications services, including necessary agreements to permit the resumption of system operations, are established for essential mission and business functions within an organization-defined time period when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.
  6. BCD-17_A06 alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services are obtained.

Evidence Requirements

E-BCD-18 Alternate Processing / Storage Site Agreements

Documented evidence of alternate processing site, alternate storage site and alternate telecommunications service agreements, including separation from primary sites.

Business Continuity

Technology Recommendations

Micro/Small

  • Alternate / redundant telecommunications services are maintained with more than one telecom / Internet provider.

Small

  • Alternate / redundant telecommunications services are maintained with more than one telecom / Internet provider.

Medium

  • Alternate / redundant telecommunications services are maintained with more than one telecom / Internet provider.

Large

  • Alternate / redundant telecommunications services are maintained with more than one telecom / Internet provider.

Enterprise

  • Alternate / redundant telecommunications services are maintained with more than one telecom / Internet provider.

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.