1.4.2 Inbound traffic from untrusted networks restricted
Inbound traffic from untrusted networks to trusted networks is restricted to communications with authorized publicly accessible system components.
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 restricting inbound to DMZ only · Cloud console / configuration management
- External port scan results · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Penetration test report · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- DMZ architecture diagram · Policy repository / GRC workspace
- List of publicly accessible components · Document repository
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
- Internal hosts reachable from internet
- DMZ used as transit to internal
- Unapproved public services
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.1 NSCs between trusted and untrusted networks · 1.4.3 Anti-spoofing measures implemented