11.4.6 Segmentation testing (service providers) every 6 months
Additional requirement for service providers: if segmentation is used, segmentation penetration testing is performed at least once every six months and after any changes to segmentation controls or methods.
5
artefacts
1
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Remediation tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Semi-annual segmentation test reports · Cloud console / configuration management
- Change-triggered test reports · Document repository
- Customer-facing attestation · Vendor register / contract repository
governing documentDocuments that govern the control
- Engagement letters · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Annual instead of semi-annual
- Change-triggered tests missed
- Customer attestation absent
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.5 Segmentation testing · 11.4.7 Multi-tenant pen test support