2.2.4 Only necessary services, protocols, daemons, and functions are enabled, and all unnecessary functionality is removed or disabled.
Defined Approach Requirements
2.2.4 Only necessary services, protocols, daemons, and functions are enabled, and all unnecessary functionality is removed or disabled.
Defined Approach Testing Procedures
2.2.4.a Examine system configuration standards to verify that they require only necessary services, protocols, daemons, and functions are enabled, and all unnecessary functionality is removed or disabled.
2.2.4.b Examine system configurations to verify that only necessary functionality is enabled, and all unnecessary functionality is removed or disabled.
Purpose
Unnecessary services, protocols, or functions can provide additional attack vectors for malicious individuals. By removing or disabling all unnecessary services, protocols, daemons, and functions, organizations can focus on securing the functions that are required and reduce the risk that unknown or unnecessary functions will be exploited.
Good Practice
Enabling only necessary services, protocols, daemons, and functions prevents unauthorized access to system components through less-secure services, protocols, or functions. It also reduces the number of system functions that need to be secured.
Unnecessary functionality may include but is not limited to scripts, drivers, features, subsystems, file systems, interfaces (USB, Bluetooth, etc.) and unnecessary web servers, protocols such as FTP, DNS, ICMP, or services such as NetBIOS, file sharing, and Windows/Mac sharing.
purpose
Document and manage insecure services/protocols/ports.
whats required for compliance
- Identify and document all insecure protocols in use
- Implement compensating controls for each
compliance strategies
- Protocol whitelisting
- Network segmentation
- Cryptographic wrappers (IPsec tunnels)
typical policies procedures
- Risk Acceptance Documentation
- Legacy System Security Plan
common pitfalls failures
- Business-critical legacy apps without crypto
- Misconfigured TLS implementations
type
Technical Control
difficulty
High
key risks
- Man-in-the-middle attacks
product vendor recommendations
- Cloudflare Access
- IPsec VPN solutions
Eligible SAQ
- SAQ-A
- SAQ-A-EP
- SAQ-B-IP
- SAQ-C
- SAQ-C-VT
- 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