TPM-04.2: External Connectivity Requirements - Identification of Ports, Protocols & Services
Mechanisms exist to require External Service Providers (ESPs) to identify and document the business need for ports, protocols and other services it requires to operate its Technology Assets, Applications and/or Services (TAAS).
Control Question: Does the organization require External Service Providers (ESPs) to identify and document the business need for ports, protocols and other services it requires to operate its Technology Assets, Applications and/or Services (TAAS)?
General (23)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 12.6 |
| CIS CSC 8.1 IG2 | 12.6 |
| CIS CSC 8.1 IG3 | 12.6 |
| CSA CCM 4 | STA-05 UEM-14 |
| GovRAMP Low+ | SA-09(02) |
| GovRAMP Moderate | SA-09(02) |
| GovRAMP High | SA-09(02) |
| NIST 800-53 R4 | SA-9(2) |
| NIST 800-53 R4 (moderate) | SA-9(2) |
| NIST 800-53 R4 (high) | SA-9(2) |
| NIST 800-53 R5 (source) | SA-9(2) |
| NIST 800-53B R5 (moderate) (source) | SA-9(2) |
| NIST 800-53B R5 (high) (source) | SA-9(2) |
| NIST 800-82 R3 MODERATE OT Overlay | SA-9(2) |
| NIST 800-82 R3 HIGH OT Overlay | SA-9(2) |
| NIST 800-171 R2 (source) | NFO-SA-9(2) |
| OWASP Top 10 2021 | A02:2021 A05:2021 |
| PCI DSS 4.0.1 (source) | 1.2.5 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 1.2.5 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 1.2.5 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 1.2.5 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 1.2.5 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | TPM-04.2 |
US (11)
| Framework | Mapping Values |
|---|---|
| US CMS MARS-E 2.0 | SA-9(2) |
| US FedRAMP R4 | SA-9(2) |
| US FedRAMP R4 (moderate) | SA-9(2) |
| US FedRAMP R4 (high) | SA-9(2) |
| US FedRAMP R5 (source) | SA-9(2) |
| US FedRAMP R5 (moderate) (source) | SA-9(2) |
| US FedRAMP R5 (high) (source) | SA-9(2) |
| US HIPAA HICP Large Practice | 9.L.C |
| US IRS 1075 | SA-9(2) |
| US NSTC NSPM-33 | 6.4 |
| US - TX TX-RAMP Level 2 | SA-9(2) |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Israel CDMO 1.0 | 16.3 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to require Third-Party Service Providers (TSP) to identify and document the business need for ports, protocols and other services it requires to operate its Technology Assets, Applications and/or Services (TAAS).
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to require Third-Party Service Providers (TSP) to identify and document the business need for ports, protocols and other services it requires to operate its Technology Assets, Applications and/or Services (TAAS).
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 require Third-Party Service Providers (TSP) to identify and document the business need for ports, protocols and other services it requires to operate its Technology Assets, Applications and/or Services (TAAS).
Assessment Objectives
- TPM-04.2_A01 external system services that require the identification of functions, ports, protocols and other services are defined.
- TPM-04.2_A02 providers of external system services are required to identify the functions, ports, protocols and other services required for the use of such services.
Evidence Requirements
- E-CPL-06 Manufacturer Disclosure Statement for Medical Device Security (MDS2)
-
Documented Manufacturer Disclosure Statement for Medical Device Security (MDS2) that communicates information about medical device cybersecurity & data privacy characteristics to current device owners and potential buyers. [note MDS2 is specific to medical device manufacturers]
Compliance - E-TDA-07 Ports, Protocols & Services (PPS)
-
Documented evidence of all ports, protocols and services in use by the system, application or service.
Technology Design & Acquisition
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)