TPM-16: Third-Party Scope Review
Mechanisms exist to perform recurring validation of the Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to ensure security, compliance and resilience control assignments accurately reflect current: (1) Contractual obligations for the External Service Provider (ESP); (2) Business practices; (3) Applicable stakeholders; and (4) Deployed Technology Assets, Applications and/or Services (TAAS).
Renumbered: Formerly TPM-05.5 in SCF 2025.4.
Control Question: Does the organization perform recurring validation of the Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to ensure security, compliance and resilience control assignments accurately reflect current: (1) Contractual obligations for the External Service Provider (ESP); (2) Business practices; (3) Applicable stakeholders; and (4) Deployed Technology Assets, Applications and/or Services (TAAS)?
General (18)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC2.2-POF9 CC3.4-POF5 CC9.2-POF7 CC9.2-POF12 |
| CIS CSC 8.1 | 15.0 |
| ISO 42001 2023 | 4.3 |
| NIST 800-171 R3 (source) | 03.16.03.c 03.17.02 03.17.03.a 03.17.03.b |
| NIST 800-171A R3 (source) | A.03.16.03.c A.03.17.02[05] A.03.17.02[06] A.03.17.03.a[02] A.03.17.03.b |
| NIST CSF 2.0 (source) | GV.SC-06 |
| PCI DSS 4.0.1 (source) | 12.5.2.1 12.5.3 12.8 12.8.1 A3.2.1 A3.2.3 |
| PCI DSS 4.0.1 SAQ A (source) | 12.8.1 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 12.8.1 |
| PCI DSS 4.0.1 SAQ B (source) | 12.8.1 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 12.8.1 |
| PCI DSS 4.0.1 SAQ C (source) | 12.8.1 |
| PCI DSS 4.0.1 SAQ C-VT (source) | 12.8.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 12.8.1 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 12.5.2.1 12.5.3 12.8.1 |
| PCI DSS 4.0.1 SAQ P2PE (source) | 12.8.1 |
| SCF DPMP 2026 | 10.4 |
| SWIFT CSF 2025 | 2.8 |
US (3)
| Framework | Mapping Values |
|---|---|
| USA Federal C2M2 2.1 | THIRD-PARTIES-2d |
| USA California CCPA 2025 | 7123(c)(15) |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.11(a)(3) 500.11(a)(4) |
EMEA (4)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | OIS-03.03B |
| EMEA EU EBA GL/2019/04 | 3.5.55 |
| EMEA EU NIS2 2022 | Article 21.3 |
| EMEA LUX CCSF 22/806 2022 | 40.d.iv |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1793 |
| APAC Malaysia RMiT 2025 | 10.49(a) |
| APAC Singapore MAS TRM 2021 | 3.4.3 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.16.03.C 03.17.02 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 perform recurring validation of the Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to ensure security, compliance and resilience control assignments accurately reflect current: (1) Contractual obligations for the External Service Provider (ESP); (2) Business practices; (3) Applicable stakeholders; and (4) Deployed Technology Assets, Applications and/or Services (TAAS).
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-16_A01 recurring validation of the Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, is performed to ensure cybersecurity / data privacy control assignments accurately reflect current business practices, compliance obligations, technologies and stakeholders.
- TPM-16_A02 processes, methods, and techniques to monitor security requirement compliance by external service providers on an ongoing basis are implemented.
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
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