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

1.4.4 Cardholder data stores not reachable from untrusted networks

System components that store cardholder data must not be directly reachable from untrusted networks. Applicability: this does not target account data held in volatile memory, but it does apply where memory is used as persistent storage (for example a RAM disk); account data may sit in volatile memory only for as long as the related business process needs it, such as until the payment transaction completes. Objective under the customized approach: stored cardholder data cannot be reached from untrusted networks.

Source: PCI DSS v4.0.1, 1.4.4. 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
3
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 rules demonstrating no direct path from untrusted networks to databases or file stores holding cardholder data · Cloud console / configuration management
  • Cloud database network settings showing public access disabled · Cloud console / configuration management
  • External scan or penetration test results confirming data stores are not exposed · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Data-flow and network diagrams showing cardholder data stores placed on internal trusted segments · 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.4.3 Anti-spoofing measures at trusted boundary · 1.4.5 Internal IP and routing disclosure limited