1.4.3 Anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network.
Defined Approach Requirements
1.4.3 Anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network.
Customized Approach Objective
Packets with forged IP source addresses cannot enter a trusted network.
Defined Approach Testing Procedures
1.4.3 Examine vendor documentation and configurations for NSCs to verify that anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network.
Purpose
Filtering packets coming into the trusted network helps to, among other things, ensure packets are not "spoofed" to appear as if they are coming from an organization's own internal network. For example, anti-spoofing measures prevent internal addresses originating from the Internet from passing into the DMZ.
Good Practice
Products usually come with anti-spoofing set as a default and may not be configurable. Entities should consult the vendor's documentation for more information.
Normally, a packet contains the IP address of the computer that originally sent it so other computers in the network know where the packet originated.
Malicious individuals will often try to spoof (or imitate) the sending IP address to fool the target system into believing the packet is from a trusted source.
purpose
Prevent IP spoofing attacks.
whats required for compliance
- NSCs configured with anti-spoofing controls.
- Block forged source IPs.
compliance strategies
- Ingress filtering
- uRPF (Unicast Reverse Path Forwarding)
- Vendor-recommended anti-spoofing settings
typical policies procedures
- Anti-Spoofing Standard
- Packet Logging
common pitfalls failures
- IPv6 spoofing overlooked
type
Technical Control
difficulty
Moderate
key risks
- IP impersonation attacks
product vendor recommendations
- Enable BCP38/BCP84 on routers
Eligible SAQ
- SAQ-A-EP
- SAQ-B-IP
- 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