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

1.2.3 Accurate network diagram of CDE connections

The entity must keep one or more accurate network diagrams that show each connection linking the cardholder data environment to other networks, wireless networks included. Applicability: an up-to-date network diagram, or some other technical or topological means of identifying devices and network connections, can satisfy this requirement. Objective under the customized approach: a current depiction of the boundaries separating the CDE from every trusted and every untrusted network is kept and can be produced when needed.

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

  • Diagram revision history with dates of update and approver names · Cloud console / configuration management
  • Change records showing diagram updates triggered by network changes · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Current network diagram(s) showing CDE boundaries, connections to other networks and wireless segments · Policy repository / GRC workspace
  • Comparison of the diagram against routing tables, NSC configurations or a discovery tool output · Policy repository / GRC workspace

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.2.2 Network connection and NSC changes under change control · 1.2.4 Accurate data-flow diagram for account data