Skip to main content

TPM-04.4: Third-Party Processing, Storage and Service Locations

TPM 10 — Critical Identify

Mechanisms exist to restrict the location of information processing/storage based on business requirements.

Control Question: Does the organization restrict the location of information processing/storage based on business requirements?

General (27)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC2.1-POF9 CC9.1
COBIT 2019 APO10.03
CSA IoT SCF 2 POL-02
GovRAMP High SA-09(05)
ISO/SAE 21434 2021 RQ-07-01
ISO 27002 2022 5.21
ISO 27017 2015 6.1.3
MPA Content Security Program 5.1 OR-3.4
NIST 800-53 R4 SA-9(5)
NIST 800-53 R5 (source) PE-23 SA-9(5)
NIST 800-53 R5 (NOC) (source) PE-23 SA-9(5)
NIST 800-161 R1 SA-9(5)
NIST 800-161 R1 Level 3 SA-9(5)
NIST 800-171 R3 (source) 03.16.03.a
NIST CSF 2.0 (source) GV.SC-06
OWASP Top 10 2021 A02:2021 A05:2021
PCI DSS 4.0.1 (source) 3.2.1 12.5.2
PCI DSS 4.0.1 SAQ A (source) 3.2.1
PCI DSS 4.0.1 SAQ A-EP (source) 3.2.1
PCI DSS 4.0.1 SAQ D Merchant (source) 3.2.1 12.5.2
PCI DSS 4.0.1 SAQ D Service Provider (source) 3.2.1 12.5.2
PCI DSS 4.0.1 SAQ P2PE (source) 3.2.1
SWIFT CSF 2023 2.8A
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) TPM-04.4
SCF CORE ESP Level 1 Foundational TPM-04.4
SCF CORE ESP Level 2 Critical Infrastructure TPM-04.4
SCF CORE ESP Level 3 Advanced Threats TPM-04.4
US (13)
Framework Mapping Values
US C2M2 2.1 THIRD-PARTIES-1.E.MIL2 THIRD-PARTIES-1.F.MIL3
US CMS MARS-E 2.0 SA-9(5)
US FedRAMP R4 SA-9(5)
US FedRAMP R4 (moderate) SA-9(5)
US FedRAMP R4 (high) SA-9(5)
US FedRAMP R5 (source) SA-9(5)
US FedRAMP R5 (moderate) (source) SA-9(5)
US FedRAMP R5 (high) (source) SA-9(5)
US GLBA CFR 314 2023 (source) 314.4(f)(1)
US HIPAA HICP Large Practice 9.L.C
US IRS 1075 2.C.7 2.C.10 SA-9(5)
US - CA CCPA 2025 7123(c)(15)
US - TX TX-RAMP Level 2 SA-9(5)
EMEA (15)
APAC (7)
Americas (6)

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to restrict the location of information processing/storage based on business requirements.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to restrict the location of information processing/storage based on business requirements.

Level 2 — Planned & Tracked

Third-Party Management (TPM) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Require TSP to follow secure engineering practices as part of a broader Cybersecurity Supply Chain Risk Management (C-SCRM) initiative. o Contain "break clauses" in all TSP contracts to enable penalty-free, early termination of a contract for cause, based on the TSP's cybersecurity and/ or data privacy practices deficiency(ies).

  • Third-party management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • IT/cybersecurity personnel identify cybersecurity and data protection controls to address applicable statutory, regulatory and contractual requirements for third-party management.
  • A procurement function maintains a list of all active Third-Party Service Providers (TSP), including pertinent contract information that will assist in a risk assessment.
  • A Shared Responsibility Matrix (SRM) is documented for every TSP that directly or indirectly affects sensitive/regulated data.
  • Procurement contracts:
Level 3 — Well Defined

Third-Party Management (TPM) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data with regards to third-party management. o Operates the Cybersecurity Supply Chain Risk Management (C-SCRM) program to identify and mitigate supply chain-related risks and threats. o Evaluates risks associated with weaknesses or deficiencies in supply chain elements identified during first and/ or third-party reviews. o Enables the implementation of third-party management controls. o Ensures the Information Assurance Program (IAP) evaluates applicable cybersecurity and data protection controls as part of “business as usual” pre-production testing. o Maintains a list of all active Third-Party Service Providers (TSP), including pertinent contract information that will assist in a risk assessment. o Requires TSP to follow secure engineering practices as part of a broader Cybersecurity Supply Chain Risk Management (C-SCRM) initiative. o Includes "break clauses" in all TSP contracts to enable penalty-free, early termination of a contract for cause, based on the TSP's cybersecurity and/ or data privacy practices deficiency(ies). o Controls changes to services by suppliers, taking into account the criticality of business information, systems and processes that are in scope by the third-party. o Requires a risk assessment prior to the acquisition or outsourcing of technology-related services. o Monitors, regularly reviews and audits supplier service delivery for compliance with established contract agreements. o Uses tailored acquisition strategies, contract tools and procurement methods for the purchase of unique systems, system components or services.

  • Procurement contracts and layered defenses provide safeguards to limit harm from potential adversaries who identify and target the organization's supply chain.
  • A Governance, Risk & Compliance (GRC) function, or similar function;
  • A procurement team, or similar function:
  • A Shared Responsibility Matrix (SRM) is documented for every TSP that directly or indirectly affects sensitive/regulated data.
Level 4 — Quantitatively Controlled

Third-Party Management (TPM) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • 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.
  • Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to restrict the location of information processing/storage based on business requirements.

Assessment Objectives

  1. TPM-04.4_A01 locations where information processing and data storage is/are to be restricted are defined.
  2. TPM-04.4_A02 requirements or conditions for restricting the location of information processing, information storage or information services are defined.
  3. TPM-04.4_A03 based on requirements, information processing, information storage or information services is/are restricted to locations.
  4. TPM-04.4_A04 the location or site of the facility where the system resides is planned considering physical and environmental hazards.
  5. TPM-04.4_A05 for existing facilities, physical and environmental hazards are considered in the organizational risk management strategy.

Evidence Requirements

E-AST-23 Geolocation Inventory

Documented evidence of designated internal and third-party facilities where organizational data is stored, transmitted and/or processed.

Asset Management

Technology Recommendations

Micro/Small

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

Small

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

Medium

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

Large

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

Enterprise

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

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.