TPM-19: Break Clauses
Mechanisms exist to include "break clauses" within contracts for failure to meet contract criteria for security, compliance and/or resilience controls.
Renumbered: Formerly TPM-05.7 in SCF 2025.4.
Control Question: Does the organization include "break clauses" within contracts for failure to meet contract criteria for security, compliance and/or resilience controls?
General (14)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | D6.5-POF1 D6.6-POF1 |
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC9.2-POF8 CC9.2-POF9 P6.4-POF2 P6.5-POF1 P6.5-POF2 P6.6-POF1 |
| NIST 800-53 R5.2 | SA-09(03) |
| NIST 800-82 R3 | SA-09(03) |
| NIST 800-161 R1 | SA-9(3) |
| NIST 800-161 R1 Level 1 | SA-9(3) |
| NIST 800-161 R1 Level 2 | SA-9(3) |
| NIST 800-161 R1 Level 3 | SA-9(3) |
| NIST 800-171 R3 (source) | 03.17.01.a 03.17.02 03.17.03.b |
| NIST 800-171A R3 (source) | A.03.17.01.a[01] A.03.17.02[05] A.03.17.02[06] A.03.17.03.b |
| NIST CSF 2.0 (source) | GV.SC-06 |
| SWIFT CSF 2025 | 2.8 |
| UN R155 | 7.2.2.5 |
| UN ECE WP.29 | 7.2.2.5 |
US (4)
| Framework | Mapping Values |
|---|---|
| USA Federal CISA CPG 2022 | 1.H |
| USA Federal IRS 1075 2021 | SA-9(CE-3) |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.504(e)(2)(iii) |
| USA California CCPA 2025 | 7053(a)(5) 7123(c)(15) |
EMEA (4)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | SSO-06.01B SSO-06.02B SSO-06.02B.1 SSO-06.02B.2 SSO-06.02B.3 SSO-06.02B.4 |
| EMEA EU DORA 2023 | Article 28.7 Article 28.7(a) Article 28.7(b) Article 28.7(c) Article 28.7(d) Article 28.8 Article 28.8(a) Article 28.8(b) Article 28.8(c) |
| EMEA EU NIS2 2022 | Article 21.3 |
| EMEA LUX CCSF 22/806 2022 | 14.e 40.f 77.q 80.g 101 101.a 101.b 101.c 101.d 101.e 109 |
APAC (5)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1804 |
| APAC Australia Prudential Standard CPS230 2023 | 54(g) |
| APAC India RBI Digital Payments 2021 | 24.d |
| APAC India SEBI CSCRF 2024 | GV.SC.S3 |
| APAC Malaysia RMiT 2025 | 10.48(f) 10.50(h) A10-B7(a) |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.17.01.A 03.17.02 03.17.03.B |
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
Third-Party Management (TPM) 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 TPM domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with TPM 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 TPM domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Third-party management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Contracts with ESP contain break clauses to enable penalty-free, early termination of a contract for cause, based on ESP cybersecurity and/or data protection practices deficiency(ies).
Level 3 — Well Defined
Third-Party Management (TPM) 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 TPM 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 TPM domain capabilities are well-documented and kept current by process owners. ▪ A procurement team, or similar function, is appropriately staffed and supported to implement and maintain TPM domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of third-party management operations (e.g., TPRM risk management solution and vendor management solution). ▪ 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 TPM 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 include "break clauses" within contracts for failure to meet contract criteria for security, compliance and/or resilience controls.
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
- TPM-19_A01 contracts with third-parties include "break clauses" to enable the organization to exit a contract due to a third-party's non-compliance with contract requirements for cybersecurity / data privacy controls.
Evidence Requirements
- E-TPM-05 Break Clauses
-
Documented evidence of "break clauses" in third-party contracts.
Third-Party Management
Technology Recommendations
Micro/Small
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
Small
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
Medium
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
Large
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
Enterprise
- Cybersecurity Supply Chain Risk Management (C-SCRM) program