11.4.5 Segmentation testing
If segmentation is used to isolate the CDE, penetration testing is performed at least every 12 months and after changes to segmentation controls, to verify segmentation effectiveness.
5
artefacts
0
held by a system
2
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
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Annual segmentation test report · Cloud console / configuration management
- Post-change segmentation test reports · Cloud console / configuration management
governing documentDocuments that govern the control
- Segmentation test scope document · Policy repository / GRC workspace
- Findings tracker and remediation · Policy repository / GRC workspace
- Network diagrams confirming segmentation · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Segmentation not tested
- Scope misses some boundaries
- Findings unaddressed
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 sheet11.4.4 Pen test findings remediated · 11.4.6 Segmentation testing (service providers) every 6 months