1.2.6 Security features are defined and implemented for all services, protocols, and ports that are in use and considered to be insecure, such that the risk is mitigated.
Defined Approach Requirements
1.2.6 Security features are defined and implemented for all services, protocols, and ports that are in use and considered to be insecure, such that the risk is mitigated.
Customized Approach Objective
The specific risks associated with the use of insecure services, protocols, and ports are understood, assessed, and appropriately mitigated.
Defined Approach Testing Procedures
1.2.6.a Examine documentation that identifies all insecure services, protocols, and ports in use to verify that for each, security features are defined to mitigate the risk.
1.2.6.b Examine configuration settings for NSCs to verify that the defined security features are implemented for each identified insecure service, protocol, and port.
Purpose
Compromises take advantage of insecure network configurations.
Good Practice
If insecure services, protocols, or ports are necessary for business, the risk posed by these services, protocols, and ports should be clearly understood and accepted by the organization, the use of the service, protocol, or port should be justified, and the security features that mitigate the risk of using these services, protocols, and ports should be defined and implemented by the entity.
Further Information
For guidance on services, protocols, or ports considered to be insecure, refer to industry standards and guidance (for example, from NIST, ENISA, OWASP).
purpose
Ensure insecure services/protocols are only used with compensating controls.
whats required for compliance
- Identify insecure services/protocols/ports in use.
- Define and implement mitigating security features for each.
compliance strategies
- Strong encryption/wrappers
- Network segmentation
- Documented risk acceptance
typical policies procedures
- Risk Acceptance Documentation
- Compensating Controls Plan
common pitfalls failures
- Lack of compensating controls
- Misconfigured encryption
type
Technical Control
difficulty
High
key risks
- Man-in-the-middle attacks
product vendor recommendations
- Replace insecure protocols with modern alternatives
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