1.4.5 The disclosure of internal IP addresses and routing information is limited to only authorized parties.
Defined Approach Requirements
1.4.5 The disclosure of internal IP addresses and routing information is limited to only authorized parties.
Customized Approach Objective
Internal network information is protected from unauthorized disclosure.
Defined Approach Testing Procedures
1.4.5.a Examine configurations of NSCs to verify that the disclosure of internal IP addresses and routing information is limited to only authorized parties.
1.4.5.b Interview personnel and examine documentation to verify that controls are implemented such that any disclosure of internal IP addresses and routing information is limited to only authorized parties.
Purpose
Restricting the disclosure of internal, private, and local IP addresses is useful to prevent a hacker from obtaining knowledge of these IP addresses and using that information to access the network.
Good Practice
Methods used to meet the intent of this requirement may vary, depending on the specific networking technology being used. For example, the controls used to meet this requirement may be different for IPv4 networks than for IPv6 networks.
Methods to obscure IP addressing may include, but are not limited to:
- IPv4 Network Address Translation (NAT).
- Placing system components behind proxy servers/NSCs.
- Removal or filtering of route advertisements for internal networks that use registered addressing.
- Internal use of RFC 1918 (IPv4) or use IPv6 privacy extension (RFC 4941) when initiating outgoing sessions to the internet.
purpose
Prevent leakage of sensitive network information.
whats required for compliance
- NSCs and systems configured to limit IP/routing info disclosure.
- Only authorized parties may access internal network details.
compliance strategies
- NAT/proxy use
- Suppress route advertisements
- Remove internal info from external communications
typical policies procedures
- IP Obfuscation Procedure
- External Communication Standards
common pitfalls failures
- Leakage via HTTP headers
type
Technical Control
difficulty
Moderate
key risks
- Network reconnaissance
product vendor recommendations
- Deploy proxies (F5, NGINX)
Eligible SAQ
- SAQ-A-EP
- 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