BCD-03: Contingency Training
Mechanisms exist to adequately train contingency personnel and applicable stakeholders in their contingency roles and responsibilities.
Control Question: Does the organization adequately train contingency personnel and applicable stakeholders in their contingency roles and responsibilities?
General (26)
| Framework | Mapping Values |
|---|---|
| COBIT 2019 | DSS04.06 |
| CSA CCM 4 | BCR-06 |
| GovRAMP Low | CP-03 |
| GovRAMP Low+ | CP-03 |
| GovRAMP Moderate | CP-03 |
| GovRAMP High | CP-03 |
| NIST 800-53 R4 | CP-3 |
| NIST 800-53 R4 (low) | CP-3 |
| NIST 800-53 R4 (moderate) | CP-3 |
| NIST 800-53 R4 (high) | CP-3 |
| NIST 800-53 R5 (source) | CP-3 |
| NIST 800-53B R5 (low) (source) | CP-3 |
| NIST 800-53B R5 (moderate) (source) | CP-3 |
| NIST 800-53B R5 (high) (source) | CP-3 |
| NIST 800-82 R3 LOW OT Overlay | CP-3 |
| NIST 800-82 R3 MODERATE OT Overlay | CP-3 |
| NIST 800-82 R3 HIGH OT Overlay | CP-3 |
| NIST 800-161 R1 | CP-3 |
| NIST 800-161 R1 C-SCRM Baseline | CP-3 |
| NIST 800-161 R1 Flow Down | CP-3 |
| NIST 800-161 R1 Level 2 | CP-3 |
| NIST 800-161 R1 Level 3 | CP-3 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | BCD-03 |
| SCF CORE ESP Level 1 Foundational | BCD-03 |
| SCF CORE ESP Level 2 Critical Infrastructure | BCD-03 |
| SCF CORE ESP Level 3 Advanced Threats | BCD-03 |
US (18)
| Framework | Mapping Values |
|---|---|
| US CERT RMM 1.2 | SC:SG3.SP5 SC:SG5.SP3 |
| US CMS MARS-E 2.0 | CP-3 |
| US FedRAMP R4 | CP-3 |
| US FedRAMP R4 (low) | CP-3 |
| US FedRAMP R4 (moderate) | CP-3 |
| US FedRAMP R4 (high) | CP-3 |
| US FedRAMP R4 (LI-SaaS) | CP-3 |
| US FedRAMP R5 (source) | CP-3 |
| US FedRAMP R5 (low) (source) | CP-3 |
| US FedRAMP R5 (moderate) (source) | CP-3 |
| US FedRAMP R5 (high) (source) | CP-3 |
| US FedRAMP R5 (LI-SaaS) (source) | CP-3 |
| US IRS 1075 | CP-3 |
| US NISPOM 2020 | 8-615 |
| US - NY DFS 23 NYCRR500 2023 Amd 2 | 500.16(c) |
| US - TX DIR Control Standards 2.0 | CP-3 |
| US - TX TX-RAMP Level 1 | CP-3 |
| US - TX TX-RAMP Level 2 | CP-3 |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Israel CDMO 1.0 | 25.3 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to adequately train contingency personnel and applicable stakeholders in their contingency roles and responsibilities.
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to adequately train contingency personnel and applicable stakeholders in their contingency roles and responsibilities.
Level 2 — Planned & Tracked
Business Continuity & Disaster Recovery (BCD) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Business Continuity / Disaster Recovery (BC/DR) management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for BC/DR management.
- BC/DR roles are formally assigned as an additional duty to existing IT/cybersecurity personnel.
- Recovery Time Objectives (RTOs) identify business-critical systems and services, which are given priority of service in alternate processing and storage sites.
- IT personnel develop Disaster Recovery Plans (DRP) to recover business-critical systems and services.
- Data/process owners conduct a Business Impact Analysis (BIA) at least annually, or after any major technology or process change, to identify assets critical to the business in need of protection, as well as single points of failure.
- IT/cybersecurity personnel work with business stakeholders to develop Business Continuity Plans (BCPs) to ensure business functions are sustainable both during and after an incident within Recovery Time Objectives (RTOs).
- IT personnel use a backup methodology (e.g., grandfather, father & s on rotation) to store backups in a secondary location, separate from the primary storage site.
- IT personnel configure business-critical systems to transfer backup data to the alternate storage site at a rate that is capable of meeting Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).
Level 3 — Well Defined
Business Continuity & Disaster Recovery (BCD) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- A formal Business Continuity & Disaster Recovery (BC/DR) program exists with defined roles and responsibilities to restore functionality in the event of a catastrophe, emergency, or significant disruptive incident that is handled in accordance with a Continuity of Operations Plan (COOP).
- BC/DR personnel work with business stakeholders to identify business-critical systems, services, internal teams and third-party service providers.
- Specific criteria are defined to initiate BC/DR activities that facilitate business continuity operations capable of meeting applicable RTOs and/or RPOs.- Application/system/process owners conduct a Business Impact Analysis (BIA) at least annually, or after any major technology or process change, to identify assets critical to the business in need of protection, as well as single points of failure.
- Recovery Time Objectives (RTOs) are defined for business-critical systems and services.
- Recovery Point Objectives (RPOs) are defined and technologies exist to conduct transaction-level recovery, in accordance with RPOs.
- Controls are assigned to sensitive/regulated assets to comply with specific BC/DR requirements to facilitate recovery operations in accordance with RTOs and RPOs.
- IT personnel work with business stakeholders to develop Disaster Recovery Plans (DRP) to recover business-critical systems and services within RPOs.
- Business stakeholders work with IT personnel to develop Business Continuity Plans (BCPs) to ensure business functions are sustainable both during and after an incident within RTOs.
- The data backup function is formally assigned with defined roles and responsibilities.
- BC/DR personnel have pre-established methods to communicate the status of recovery activities and progress in restoring operational capabilities to designated internal and external stakeholders.
- The integrity of backups and other restoration assets are verified prior to using them for restoration.
Level 4 — Quantitatively Controlled
Business Continuity & Disaster Recovery (BCD) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
- Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
- Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
- Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
- Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
- Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to adequately train contingency personnel and applicable stakeholders in their contingency roles and responsibilities.
Assessment Objectives
- BCD-03_A01 the time period within which to provide contingency training after assuming a contingency role or responsibility is defined.
- BCD-03_A02 the frequency at which to provide training to system users with a contingency role or responsibility is defined.
- BCD-03_A03 the frequency at which to review / update contingency training content is defined.
- BCD-03_A04 events necessitating review / update of contingency training are defined.
- BCD-03_A05 contingency training is provided to system users consistent with assigned roles and responsibilities within an organization-defined time period of assuming a contingency role or responsibility.
- BCD-03_A06 contingency training is provided to system users consistent with assigned roles and responsibilities when required by system changes.
- BCD-03_A07 contingency training is provided to system users consistent with assigned roles and responsibilities and frequency thereafter.
- BCD-03_A08 the contingency plan training content is reviewed / updated frequently.
- BCD-03_A09 the contingency plan training content is reviewed / updated following events.
Evidence Requirements
- E-BCM-07 COOP Training
-
Documented evidence of a Continuity of Operations Plan (COOP)-related training activity.
Business Continuity
Technology Recommendations
Micro/Small
- NIST NICE Framework
- Tabletop exercises
Small
- NIST NICE Framework
- Tabletop exercises
Medium
- NIST NICE Framework
- Tabletop exercises
Large
- NIST NICE Framework
- Tabletop exercises
- Simulated events
Enterprise
- NIST NICE Framework
- Tabletop exercises
- Simulated events