CPL-06: Non-Conformity Oversight
Mechanisms exist to identify and document instances of non-conformity with statutory, regulatory and/or contractual obligations, in order to develop appropriate risk mitigation actions.
Renumbered: Formerly CPL-01.1 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, CPL-06 was Government Surveillance. That control is now CPL-20.
Control Question: Does the organization document and review instances of non-compliance with statutory, regulatory and/or contractual obligations to develop appropriate risk mitigation actions?
General (19)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | M1.2-POF6 M1.2-POF7 M9.1-POF4 M9.1-POF5 |
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC1.1-POF4 CC1.5 CC4.2 CC4.2-POF1 CC4.2-POF2 CC4.2-POF3 |
| BSI Standard 200-1 | 7.4 |
| COBIT 2019 | MEA01.02 MEA01.05 MEA02.04 |
| COSO 2013 | 17.0 |
| CSA CCM 4.1.0 | A&A-05 A&A-06 |
| CSA IoT SCF 2 | GVN-04 |
| ISO 22301 2019 | 10.1.1 10.1.2 10.1.2(a) 10.1.2(a)(1) 10.1.2(a)(2) 10.1.2(b) 10.1.2(b)(1) 10.1.2(b)(2) 10.1.2(b)(3) 10.1.2(c) 10.1.2(d) 10.1.2(e) 10.1.3 10.1.3(a) 10.1.3(b) |
| ISO 27001 2022 (source) | 9.1 9.1(a) 9.1(b) 9.1(c) 9.1(d) 9.1(e) 9.1(f) 10.2 10.2(a) 10.2(a)(1) 10.2(a)(2) 10.2(b) 10.2(b)(1) 10.2(b)(2) 10.2(b)(3) 10.2(c) 10.2(d) 10.2(e) 10.2(f) 10.2(g) |
| ISO 27701 2025 | 10.2 10.2(a) 10.2(b) 10.2(c) 10.2(d) 10.2(e) |
| ISO 29100 2024 | 6.12 |
| ISO 31010 2009 | 4.3.6 5.6 |
| NAIC Insurance Data Security Model Law (MDL-668) | 4.E(2)(b) |
| NIST 800-171 R3 (source) | 03.12.02.a.01 03.12.02.a.02 |
| NIST 800-171A R3 (source) | A.03.12.02.a.01 A.03.12.02.a.02 |
| PCI DSS 4.0.1 (source) | 12.4.2 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 12.4.2 |
| SCF DPMP 2026 | 11.6 |
| TISAX ISA 6.0.3 | 1.5.1 |
US (7)
| Framework | Mapping Values |
|---|---|
| USA Federal DHS CISA TIC 3.0 | 3.UNI.PEPAR |
| USA Federal C2M2 2.1 | RISK-2l ARCHITECTURE-1i |
| USA Federal CERT RMM 1.2 | COMP:SG3.SP3 |
| USA Federal IRS 1075 2021 | 2.D.9 |
| USA Federal FCA CRM 2023 | 609.930(c)(1)(ii) |
| USA California CCPA 2025 | 7123(b)(3) |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.4(b)(6) |
EMEA (7)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | COM-03.03B |
| EMEA Spain CCN-STIC 825 | op.mon.2 |
| EMEA EU AI Act | Article 10.2(h) Article 16(j) Article 20.1 Article 41.5 |
| EMEA EU EBA GL/2019/04 | 3.3.6.27 |
| EMEA EU NIS2 2022 | Article 21.4 |
| EMEA LUX CCSF 22/806 2022 | 101.a |
| EMEA Saudi Arabia IoT CGIoT-1 2024 | 1-7-3 |
APAC (5)
| Framework | Mapping Values |
|---|---|
| APAC Australia SOCI 2028 | 30DM |
| APAC India RBI Digital Payments 2021 | 4.g |
| APAC Japan ISMAP | 4.6.1.1 4.7.1.1 4.7.1.2 |
| APAC New Zealand NZISM 3.9 | 1.1.68.C.01 1.1.69.C.01 1.1.69.C.02 |
| APAC Singapore CCOP CII 2026 | 2.1.1 |
Americas (2)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.12.02.A.01 03.12.02.A.02 |
| Americas Canada OSFI B-13 2022 | 1.3.1 |
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
Compliance (CPL) 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 CPL domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with CPL 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 CPL domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Compliance management controls-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Compliance management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ External compliance requirements for cybersecurity and data privacy are identified and documented, based on applicable laws, regulations and contractual obligations. ▪ IT and/or cybersecurity perform an informal annual review of existing compliance requirements and research evolving or new requirements.
Level 3 — Well Defined
Compliance (CPL) 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 CPL 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 CPL domain capabilities are well-documented and kept current by process owners. ▪ A Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain CPL domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance operations (e.g., GRC platform). ▪ 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 CPL 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 document and review instances of non-compliance with statutory, regulatory and/or contractual obligations to develop appropriate risk mitigation actions.
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
- CPL-06_A01 instances of non-conformity with statutory, regulatory and/or contractual obligations are documented, including the reason(s) for non-conformity.
- CPL-06_A02 instances of non-conformity with statutory, regulatory and/or contractual obligations are formally reviewed to develop risk mitigation actions.
- CPL-06_A03 instances of non-conformity with statutory, regulatory and/or contractual obligations are centrally governed to maintain situational awareness.
- CPL-06_A04 instances of non-conformity with statutory, regulatory and/or contractual obligations are assigned to individuals or teams for remediation.
- CPL-06_A05 risk mitigation actions for instances of non-conformity with statutory, regulatory and/or contractual obligations are documented.
- CPL-06_A06 instances of non-conformity with statutory, regulatory and/or contractual obligations are identified.
Evidence Requirements
- E-CPL-05 Internal Audit (IA) Findings
-
Documented evidence of a centrally-managed and prioritized repository Internal Audit (IA) findings.
Compliance - E-CPL-09 Non-Compliance Oversight Reporting
-
Documented evidence of governance oversight reporting of non-compliance to the organization's executive leadership.
Compliance
Technology Recommendations
Micro/Small
- GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.)
Small
- GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.)
Medium
- GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.)
Large
- GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.)
Enterprise
- GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.)