1.4.4 Account data not stored on internet-accessible systems
System components that store cardholder data are not directly accessible from untrusted networks.
5
artefacts
2
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Firewall rules between DMZ and data tier · Cloud console / configuration management
- Internal scan results · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Database server network placement evidence · Cloud console / configuration management
governing documentDocuments that govern the control
- Architecture diagram of three-tier design · Policy repository / GRC workspace
- Penetration test confirming non-accessibility · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Database server reachable through DMZ pivot
- Storage in same VLAN as web
- Missing internal segmentation
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 sheet1.4.3 Anti-spoofing measures implemented · 1.4.5 Internal IP and routing information protected