WithPCI Logo
WithPCI.com

1.2.5 All services, protocols, and ports allowed are identified, approved, and have a defined business need.

Original requirement from PCI DSS v4.0.1

Defined Approach Requirements

1.2.5 All services, protocols, and ports allowed are identified, approved, and have a defined business need.

Customized Approach Objective

Unauthorized network traffic (services, protocols, or packets destined for specific ports) cannot enter or leave the network.

Defined Approach Testing Procedures

1.2.5.a Examine documentation to verify that a list exists of all allowed services, protocols, and ports, including business justification and approval for each.

1.2.5.b Examine configuration settings for NSCs to verify that only approved services, protocols, and ports are in use.

Purpose

Compromises often happen due to unused or insecure services (for example, telnet and FTP), protocols, and ports, since these can lead to unnecessary points of access being opened into the CDE. Additionally, services, protocols, and ports that are enabled but not in use are often overlooked and left unsecured and unpatched. By identifying the services, protocols, and ports necessary for business, entities can ensure that all other services, protocols, and ports are disabled or removed.

Good Practice

The security risk associated with each service, protocol, and port allowed should be understood.

Approvals should be granted by personnel independent of those managing the configuration.

Approving personnel should possess knowledge and accountability appropriate for making approval decisions.

purpose

Limit attack surface by only permitting necessary network traffic.

whats required for compliance

  • Maintain a list of all allowed services, protocols, and ports.
  • Each must have business justification and approval.

compliance strategies

  • Service/port inventory
  • Business justification documentation
  • Regular review and validation

typical policies procedures

  • Service Approval Process
  • Protocol Whitelisting Policy

common pitfalls failures

  • Legacy protocols (FTP/Telnet) enabled
  • Orphaned rules for decommissioned systems

type

Technical Control

difficulty

High

key risks

  • Exploitation of unused services

product vendor recommendations

  • Use NAC solutions (Cisco ISE)

Eligible SAQ

  • SAQ-D MERCHANT
  • SAQ-D SERVICE PROVIDER

Your perspective on this PCI DSS requirement matters! Share your implementation experiences, challenges, or questions below. Your insights help other organizations improve their compliance journey and build a stronger security community.Comment Policy