Skip to main content

CPL-06.1: Non-Conformity Corrective Action

CPL 7 — High Govern

Mechanisms exist to implement corrective action to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations.

Renumbered: Formerly CPL-02.3 in SCF 2025.4.

Control Question: Does the organization take corrective action to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations?

General (1)
Framework Mapping Values
ISO 29100 2024 6.12
US (3)
Framework Mapping Values
USA Federal CERT RMM 1.2 COMP:SG3.SP3
USA Federal FFIEC ITEH 2016 IV.A.2.d
USA Federal 33 CFR Part 101 Subpart F 101.625(d)(7)
EMEA (3)
Framework Mapping Values
EMEA EU AI Act Article 79.4 Article 80.4 Article 80.5 Article 82.2 Article 93.1(a) Article 93.1(b) Article 93.1(c)
EMEA EU DORA RTS 2024 Article 28.6 Article 41.2(g)
EMEA LUX CCSF 20/750 2020 3.3.6-27
APAC (4)
Framework Mapping Values
APAC Australia SOCI 2028 30DM
APAC India RBI Digital Payments 2021 4.g
APAC Malaysia RMiT 2025 8.5
APAC Singapore CCOP CII 2026 2.1.2 2.1.2(a) 2.1.2(b) 2.1.2(c) 2.1.4 3.9.3(c)

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

Compliance (CPL) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with CPL domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Compliance management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Compliance efforts are narrowly-limited to certain compliance requirements. ▪ IT and/or cybersecurity personnel use an informal process to govern statutory, regulatory and contractual compliance obligations.

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.

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 take corrective action to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations.

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. CPL-06.1_A01 corrective action is implemented to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations.

Evidence Requirements

E-CPL-05 Internal Audit (IA) Findings

Documented evidence of a centrally-managed and prioritized repository Internal Audit (IA) findings.

Compliance
E-RSK-03 Plan of Actions & Milestones (POA&M) / Risk Register

Documented evidence of a POA&M, or risk register, that tracks control deficiencies from identification through remediation.

Risk Management

Technology Recommendations

Micro/Small

  • Corrective action log (spreadsheet)
  • Documented remediation plans for audit findings

Small

  • Corrective action register with remediation tracking
  • Management review of open findings

Medium

  • Formal corrective action plan process
  • GRC platform for finding tracking and remediation
  • Management review of open findings

Large

  • Enterprise corrective action management program
  • GRC platform with workflow-driven remediation tracking
  • Executive reporting on open findings

Enterprise

  • Enterprise GRC platform for corrective action management
  • Automated finding tracking and escalation workflows
  • Board-level reporting on material findings

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.