IRO-12.3: Post-Sensitive / Regulated Data Spill Operations
Mechanisms exist to ensure that organizational personnel impacted by sensitive/regulated data spills can continue to carry out assigned tasks while contaminated Technology Assets, Applications and/or Services (TAAS) are undergoing corrective actions.
Control Question: Does the organization ensure that organizational personnel impacted by sensitive/regulated data spills can continue to carry out assigned tasks while contaminated Technology Assets, Applications and/or Services (TAAS) are undergoing corrective actions?
General (9)
| Framework | Mapping Values |
|---|---|
| GovRAMP Moderate | IR-09(03) |
| GovRAMP High | IR-09(03) |
| NIST 800-53 R4 | IR-9(3) |
| NIST 800-53 R5 (source) | IR-9(3) |
| NIST 800-53 R5 (NOC) (source) | IR-9(3) |
| PCI DSS 4.0.1 (source) | 12.10.7 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 12.10.7 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 12.10.7 |
| Shared Assessments SIG 2025 | K.7 |
US (7)
| Framework | Mapping Values |
|---|---|
| US FedRAMP R4 | IR-9(3) |
| US FedRAMP R4 (moderate) | IR-9(3) |
| US FedRAMP R4 (high) | IR-9(3) |
| US FedRAMP R5 (source) | IR-9(3) |
| US FedRAMP R5 (moderate) (source) | IR-9(3) |
| US FedRAMP R5 (high) (source) | IR-9(3) |
| US - TX TX-RAMP Level 2 | IR-9(3) |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2020 | OPS-21 |
APAC (1)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2024 | ISM-0133 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to ensure that organizational personnel impacted by sensitive/regulated data spills can continue to carry out assigned tasks while contaminated Technology Assets, Applications and/or Services (TAAS) are undergoing corrective actions.
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to ensure that organizational personnel impacted by sensitive/regulated data spills can continue to carry out assigned tasks while contaminated Technology Assets, Applications and/or Services (TAAS) are undergoing corrective actions.
Level 2 — Planned & Tracked
Incident Response (IRO) 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: o Identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for incident response operations. o Implement and maintain an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
- Incident response operations are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel:
Level 3 — Well Defined
Incident Response (IR) processes 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:
- An Integrated Security Incident Response Team (ISIRT), or similar function, exists to form an on-demand, scalable and integrated team of formally-assigned cybersecurity, IT, data privacy and business function representatives that can perform coordinated incident response.
- The ISIRT, or similar function, develops and maintains a documented, program-level Integrated Incident Response Program (IIRP) that provides operational and tactical-level guidance for cybersecurity and data privacy response operations.
- A Security Operations Center (SOC), or similar function, facilitates incident management operations that includes preparation, detection and analysis, containment, eradication and recovery.
- Business Process Owners (BPOs), in conjunction with the SOC and ISIRT functions, develop and maintain a documented Incident Response Plan (IRP) specific to the business process / business unit but inclusive of the organization's larger approach to incident response operations.
- An IT Asset Management (ITAM) function, or similar function, categorizes endpoint devices according to the data the asset stores, transmits and/ or processes and provides that information to the SOC for Incident Response Operations (IRO).
- Administrative processes and technologies exist to ensure that organizational personnel impacted by sensitive/regulated data spills can continue to carry out assigned tasks while contaminated Technology Assets, Applications and/or Services (TAAS) are undergoing corrective actions.
Level 4 — Quantitatively Controlled
See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to ensure that organizational personnel impacted by sensitive/regulated data spills can continue to carry out assigned tasks while contaminated Technology Assets, Applications and/or Services (TAAS) are undergoing corrective actions.
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 ensure that organizational personnel impacted by sensitive/regulated data spills can continue to carry out assigned tasks while contaminated Technology Assets, Applications and/or Services (TAAS) are undergoing corrective actions.
Assessment Objectives
- IRO-12.3_A01 procedures to be implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems undergo corrective actions are defined.
- IRO-12.3_A02 procedures are implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.