Skip to main content

TPM-04.2: Limit Potential Harm

TPM 9 — Critical Identify

Mechanisms exist to utilize security safeguards to limit harm from potential adversaries who identify and target the organization's supply chain.

Renumbered: Formerly TPM-03.2 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, TPM-04.2 was External Connectivity Requirements - Identification of Ports, Protocols & Services. That control is now TPM-12.4.

Control Question: Does the organization utilize security safeguards to limit harm from potential adversaries who identify and target its supply chain?

General (18)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC9.1 P6.4-POF2 P6.5-POF1 P6.5-POF2 P6.6-POF1
CIS CSC 8.1 15.4
CIS CSC 8.1 IG2 15.4
CIS CSC 8.1 IG3 15.4
CSA IoT SCF 2 RSM-03
ISO 27002 2022 5.19 5.20
ISO 27018 2025 5.19 5.20
NIST 800-53 R4 SA-12(5)
NIST 800-53 R5.2 SR-03(02)
NIST 800-82 R3 SR-03(02)
NIST 800-160 Vol2 R1 SR-03(02)
NIST 800-171 R3 (source) 03.17.03.a 03.17.03.b
NIST 800-171A R3 (source) A.03.17.03.a[01] A.03.17.03.b
NIST CSF 2.0 (source) GV.SC-06 GV.SC-07
OWASP Top 10 2025 A03:2025
SWIFT CSF 2025 2.8
UN R155 7.2.2.5
UN ECE WP.29 7.2.2.5
US (5)
EMEA (3)
Framework Mapping Values
EMEA Spain CCN-STIC 825 op.ext.1
EMEA EU NIS2 2022 Article 21.3
EMEA Saudi Arabia CSCC-1 2019 4-1-1-1 4-1-1-2
APAC (1)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-1567
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.17.03.A 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.

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 utilize security safeguards to limit harm from potential adversaries who identify and target the organization's supply chain.

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

  1. TPM-04.2_A01 controls to limit harm from potential supply chain adversaries are defined.
  2. TPM-04.2_A02 controls are employed to limit harm from potential adversaries identifying and targeting the organizational supply chain.

Technology Recommendations

Micro/Small

  • Cybersecurity Supply Chain Risk Management (C-SCRM) program
  • Data Protection Impact Assessment (DPIA)
  • Liability clause in contracts

Small

  • Cybersecurity Supply Chain Risk Management (C-SCRM) program
  • Data Protection Impact Assessment (DPIA)
  • Liability clause in contracts

Medium

  • Cybersecurity Supply Chain Risk Management (C-SCRM) program
  • Data Protection Impact Assessment (DPIA)
  • Liability clause in contracts

Large

  • Cybersecurity Supply Chain Risk Management (C-SCRM) program
  • Data Protection Impact Assessment (DPIA)
  • Liability clause in contracts

Enterprise

  • Cybersecurity Supply Chain Risk Management (C-SCRM) program
  • Data Protection Impact Assessment (DPIA)
  • Liability clause in contracts

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.