TPM-18: Third-Party Deficiency Remediation
Mechanisms exist to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements.
Renumbered: Formerly TPM-09 in SCF 2025.4.
Control Question: Does the organization address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements?
General (16)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | D6.5-POF1 D6.6-POF1 |
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC4.2 CC9.1 CC9.2-POF8 P6.4-POF2 P6.5-POF1 P6.5-POF2 P6.6-POF1 |
| COBIT 2019 | APO10.04 |
| COSO 2013 | 17.0 |
| CSA IoT SCF 2 | POL-01 |
| ISO 27002 2022 | 5.19 |
| ISO 27018 2025 | 5.19 |
| NIST 800-171 R3 (source) | 03.17.02 |
| NIST 800-171A R3 (source) | A.03.17.02[06] |
| NIST CSF 2.0 (source) | GV.SC-06 GV.SC-07 GV.SC-08 |
| OWASP Top 10 2025 | A02:2025 A05:2025 |
| PCI DSS 4.0.1 (source) | A3.3.1.2 |
| SCF DPMP 2026 | 10.0 10.4 |
| 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 CERT RMM 1.2 | EXD:SG4.SP2 |
| USA California CCPA 2025 | 7053(a)(5) 7123(c)(15) |
| USA Montana CDPA 2025 | 30-14-2815(5) |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.4(b)(6) |
EMEA (5)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | SSO-02.01B.5 SSO-05.05B SSO-05.02AC |
| EMEA Spain CCN-STIC 825 | op.ext.1 |
| EMEA EU NIS2 2022 | Article 21.3 Article 21.4 |
| EMEA LUX CCSF 22/806 2022 | 101.d 109 |
| EMEA Saudi Arabia IoT CGIoT-1 2024 | 4-1-6 |
APAC (4)
| Framework | Mapping Values |
|---|---|
| APAC India SEBI CSCRF 2024 | GV.SC.S4 |
| APAC Japan APPI 2020 | IV.5.53(4) |
| APAC Malaysia RMiT 2025 | 10.49(g) |
| APAC Singapore MAS TRM 2021 | 3.4.3 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.17.02 |
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.
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 address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements.
Level 4 — Quantitatively Controlled
Third-Party Management (TPM) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
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-18_A01 weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements are remediated.
Evidence Requirements
- E-TPM-03 Third-Party Service Reviews
-
Documented evidence of a formal, annual stakeholder review of third-party services for each External Service Provider (ESP).
Third-Party Management
Technology Recommendations
Micro/Small
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Third-party contract requirements for cybersecurity controls
Small
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Third-party contract requirements for cybersecurity controls
Medium
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Third-party contract requirements for cybersecurity controls
Large
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Third-party contract requirements for cybersecurity controls
Enterprise
- Cybersecurity Supply Chain Risk Management (C-SCRM) program
- Third-party contract requirements for cybersecurity controls