TPM-14.1: Contract Flow-Down Requirements
Mechanisms exist to ensure applicable security, compliance and resilience requirements are included in contracts that flow-down to applicable subcontractors and suppliers.
Renumbered: Formerly TPM-05.2 in SCF 2025.4.
Control Question: Does the organization ensure applicable security, compliance and resilience requirements are included in contracts that flow-down to applicable sub-contractors and suppliers?
General (20)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | D6.5-POF2 |
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC2.3-POF12 CC9.2-POF1 CC9.2-POF9 CC9.2-POF10 P6.4-POF3 |
| CSA CCM 4.1.0 | STA-11 |
| ISO 27701 2025 | 6.1.3(h) |
| NIST 800-53 R5.2 | SR-03(03) |
| NIST SP 800-66 R2 | 164.308(b)(1) 164.314(a) |
| NIST 800-82 R3 | SR-03(03) |
| NIST 800-161 R1 | SR-3(3) |
| NIST 800-161 R1 Flow Down | SR-3(3) |
| NIST 800-161 R1 Level 2 | SR-3(3) |
| NIST 800-161 R1 Level 3 | SR-3(3) |
| NIST 800-171 R2 (source) | 3.1.1 |
| NIST 800-171 R3 (source) | 03.16.03.a 03.16.03.b 03.16.03.c 03.17.02 03.17.03.b |
| NIST 800-171A R3 (source) | A.03.16.03.ODP[01] A.03.16.03.a A.03.16.03.b A.03.16.03.c A.03.17.02[05] A.03.17.03.b |
| NIST CSF 2.0 (source) | GV.OC-03 GV.SC-02 GV.SC-05 GV.SC-06 GV.SC-10 |
| SCF DPMP 2026 | 10.3 |
| SWIFT CSF 2025 | 2.8 |
| TISAX ISA 6.0.3 | 6.1.1 |
| UN R155 | 7.2.2.5 |
| UN ECE WP.29 | 7.2.2.5 |
US (15)
| Framework | Mapping Values |
|---|---|
| USA Federal Data Privacy Framework 2023 | II.7.d III.10.a.ii.1 III.10.a.ii.2 III.10.a.ii.3 III.10.a.iii |
| USA Federal CMMC 2.0 Level 1 | AC.L1-B.1.I |
| USA Federal CMMC 2.0 Level 2 | ACL2.-3.1.1 |
| USA Federal DFARS 252.204-7012 | 252.204-7012(b) 252.204-7012(m)(2)(i) |
| USA Federal NNPI (unclass) 2010 | 7-2 7-4 7-5 |
| USA Federal FAR 52.204-21 | 52.204-21(b)(1)(i) |
| USA Federal FAR 52.204-27 | 52.204-27(c) |
| USA Federal 45 CFR 155.260 | 155.260(b)(2)(v) |
| USA Federal IRS 1075 2021 | SR-3(CE-3) |
| USA Federal HIPAA Security Rule NIST SP 800-66 R2 | § 164.308(b)(1) § 164.308(b)(2) § 164.314(a)(2)(i)(B) § 164.314(a)(2)(iii) |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.308(b)(1) § 164.308(b)(2) § 164.314(a)(2)(i)(B) § 164.314(a)(2)(iii) § 164.502(e)(1)(ii) § 164.504(e)(2)(ii)(D) |
| USA California CCPA 2025 | 7051(b) 7052(b) 7053(a) 7123(c)(15) |
| USA Montana CDPA 2025 | 30-14-2813(2)(d) |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.10(a)(1) 500.11(a)(1) 500.11(a)(2) 500.11(b) 500.11(b)(1) 500.11(b)(2) 500.11(b)(3) 500.11(b)(4) |
| USA Virginia CDPA 2023 | 59.1-579.B.5 |
EMEA (12)
| Framework | Mapping Values |
|---|---|
| EMEA Germany BAIT 2017 | 9.4 |
| EMEA Germany C5 2026 | DEV-02.02B.5 SSO-01.01B.9 SSO-02.01B.7 SSO-02.01B.8 SSO-05.02B.5 SSO-07.01B.3 SSO-07.01AS.3 |
| EMEA EU DORA 2023 | Article 29.2 |
| EMEA EU EBA GL/2019/04 | 3.2.3.8 |
| EMEA EU NIS2 2022 | Article 21.3 |
| EMEA EU NIS2 Annex 2024 | 5.1.4(g) |
| EMEA UK DEFSTAN 05-138 2024 | 1401 |
| EMEA UK DEFSTAN 05-138 - L1 2024 | 1401 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 1401 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 1401 |
| EMEA LUX CCSF 22/806 2022 | 7 70.a 77.e 78 80 80.a 80.b 80.c 80.d 80.e 80.f 80.g 81 81.a 81.b 82 117 |
| EMEA Saudi Arabia ECC-1 2018 | 4-1-2-3 |
APAC (5)
| Framework | Mapping Values |
|---|---|
| APAC India DPDPA 2023 | 8(7)(b) |
| APAC India RBI PA 2025 | III.9.a IV.14.c Annex 1.1.4 |
| APAC India RBI PPI 2025 | 7.9.f 15.6 |
| APAC India SEBI CSCRF 2024 | GV.SC.S3 GV.SC.S8 |
| APAC Malaysia RMiT 2025 | 10.48(b) A1-5 A8-3(c) A10-A5(d) A10-A5(d)(i) |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.16.03.A 03.16.03.B 03.16.03.C 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. ▪ Procurement practices contractually require ESP to follow secure engineering practices as part of a broader Cybersecurity Supply Chain Risk Management (C-SCRM) initiative. ▪ A formal agreement exists between the organization and applicable third-parties that includes a Non-Disclosure Agreement (NDA) addressing shared sensitive data.
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 ensure applicable security, compliance and resilience requirements are included in contracts that flow-down to applicable sub-contractors and suppliers.
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-14.1_A01 the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.
- TPM-14.1_A02 security requirements to be satisfied by external system service providers are defined.
Evidence Requirements
- E-TPM-01 Third-Party Contracts
-
Documented evidence of third-party contractual obligations for cybersecurity & data privacy protections.
Third-Party Management
Technology Recommendations
Micro/Small
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Data Protection Impact Assessment (DPIA)
- Third-party contract requirements for cybersecurity controls
Small
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Data Protection Impact Assessment (DPIA)
- Third-party contract requirements for cybersecurity controls
Medium
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Data Protection Impact Assessment (DPIA)
- Third-party contract requirements for cybersecurity controls
Large
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Data Protection Impact Assessment (DPIA)
- Third-party contract requirements for cybersecurity controls
Enterprise
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Data Protection Impact Assessment (DPIA)
- Third-party contract requirements for cybersecurity controls