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

1.4.3 Anti-spoofing measures at trusted boundary

The entity must implement anti-spoofing measures that detect forged source IP addresses and stop them getting into the trusted network. The guidance gives the example of blocking packets from the internet that claim an internal source address, notes that many products enable anti-spoofing by default, and advises consulting vendor documentation. Applicability: no special notes; applies to every assessed entity. Customized approach objective: packets carrying falsified source IP addresses cannot enter a trusted network.

Source: PCI DSS v4.0.1, 1.4.3. 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.

4
artefacts
2
held by a system
0
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 showing anti-spoofing or reverse-path filtering enabled on untrusted interfaces · Cloud console / configuration management
  • Logs or alerts showing spoofed packets dropped · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Vendor documentation describing the anti-spoofing feature and its default state · Vendor register / contract repository
  • Ingress ACLs blocking internal and private address ranges arriving from the internet · Document repository

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

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.4.2 Restricting traffic entering trusted networks from outside · 1.4.4 Cardholder data stores not reachable from untrusted networks