Traffic leaving the cardholder data environment must be restricted so that (a) only necessary traffic is permitted and (b) everything else is explicitly denied. The guidance explains the aim is to stop malicious users or compromised components from talking to untrusted external hosts, and recommends evaluating all outbound traffic, whatever its destination, against authorised rules. Applicability: no special notes; applies to every assessed entity. Customized approach objective: traffic that is not authorised is unable to leave the CDE.
This control maps to 59 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 1.3.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.