TPM-12.1: Conflict of Interests
Mechanisms exist to ensure that the interests of external service providers are consistent with and reflect organizational interests.
Renumbered: Formerly TPM-04.3 in SCF 2025.4.
Control Question: Does the organization ensure that the interests of external service providers are consistent with and reflect organizational interests?
General (16)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC1.3-POF6 CC3.3 |
| COSO 2013 | 8.0 |
| GovRAMP | SA-09(04) |
| GovRAMP High | SA-09(04) |
| ISO 27002 2022 | 5.19 |
| ISO 27018 2025 | 5.19 |
| NIST 800-53 R4 | SA-9(4) |
| NIST 800-53 R5.2 | SA-09(03) SA-09(04) |
| NIST 800-82 R3 | SA-09(03) SA-09(04) |
| NIST 800-161 R1 | SA-9(3) SA-9(4) |
| 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) SA-9(4) |
| NIST CSF 2.0 (source) | GV.SC-06 |
| OWASP Top 10 2025 | A03:2025 |
| SWIFT CSF 2025 | 2.8 |
US (2)
| Framework | Mapping Values |
|---|---|
| USA Federal IRS 1075 2021 | SA-9(CE-3) |
| USA California CCPA 2025 | 7123(c)(15) |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA Spain CCN-STIC 825 | op.ext.1 |
| EMEA LUX CCSF 22/806 2022 | 11 34.c 40.c.v 43 44 45 46 65.e 75 |
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 ensure that the interests of external service providers are consistent with and reflect organizational interests.
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-12.1_A01 external service providers are defined.
- TPM-12.1_A02 actions to be taken to verify that the interests of external service providers are consistent with and reflect organizational interests are defined.
- TPM-12.1_A03 actions are taken to verify that the interests of external service providers are consistent with and reflect organizational interests.
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