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

1.4.1 NSCs between trusted and untrusted networks

Network security controls must be implemented between trusted and untrusted networks. The guidance explains this lets the entity monitor and control every connection into and out of trusted networks; the Requirement 1 overview lists the internet, business-to-business links, wireless, carrier and third-party networks, and corporate networks outside PCI DSS scope as examples of untrusted networks. Applicability: no special notes; applies to every assessed entity. Customized approach objective: unauthorised traffic cannot cross the boundary between trusted and untrusted networks.

Source: PCI DSS v4.0.1, 1.4.1. 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
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Network diagram marking each trusted/untrusted boundary and the NSC at that point · Policy repository / GRC workspace
  • Configuration standard specifying boundary NSC requirements, including DMZ design · Policy repository / GRC workspace
  • NSC configurations at internet, partner and out-of-scope corporate network boundaries · Policy repository / GRC workspace
  • Inventory of external connections (ISP links, partner VPNs, cloud interconnects) · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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.3.3 NSCs between wireless networks and the CDE · 1.4.2 Restricting traffic entering trusted networks from outside