What evidence do auditors commonly ask for on 1.3.2 Outbound CDE traffic restricted?

NSC configuration standard defining permitted outbound destinations from the CDE; Egress rulesets on CDE boundary NSCs with explicit or implicit deny; List of approved external destinations (for example processor endpoints, patch sources) with justification; Egress test results showing blocked connections to arbitrary internet hosts.

What is the most common gap auditors find on 1.3.2?

CDE servers can reach any internet destination on ports 80 and 443

PCI DSS v4.0.1 · Req 1: Network Security Controls

`1.3.2` Outbound CDE traffic restricted

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.

Source: PCI DSS v4.0.1, 1.3.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

artefacts

held by a system

at each review

easy

to go live

Cloud console / configuration management

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

NSC configuration standard defining permitted outbound destinations from the CDE · Cloud console / configuration management
Egress rulesets on CDE boundary NSCs with explicit or implicit deny · Cloud console / configuration management
List of approved external destinations (for example processor endpoints, patch sources) with justification · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

Egress test results showing blocked connections to arbitrary internet hosts · Source control / CI pipeline

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

CDE servers can reach any internet destination on ports 80 and 443
Egress controls exist on the perimeter firewall but not on cloud CDE workloads
Outbound rules were never reviewed because focus was only on inbound filtering

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

1.3.1 Inbound CDE traffic restricted · 1.3.3 NSCs between wireless networks and the CDE