11.4.7 Multi-tenant pen test support
Additional requirement for multi-tenant service providers: support customer requests for external penetration testing of their hosted environments.
5
artefacts
0
held by a system
2
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
none for this control
periodic reviewEvidence produced at each review
- Coordination evidence (rules of engagement, scoping) · Document repository
- Post-test debrief records · Document repository
governing documentDocuments that govern the control
- Documented customer pen test request procedure · Policy repository / GRC workspace
- Sample customer request approvals · Document repository
- Customer agreement clauses · Vendor register / contract repository
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
- No process
- Requests denied without reason
- Coordination informal
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.6 Segmentation testing (service providers) every 6 months · 11.5.1 IDS/IPS in place