GS-2 Define and implement enterprise segmentation/separation of duties strategy
Define and implement an enterprise segmentation and separation of duties strategy that segments access to assets using a combination of identity, network, application and subscription or account controls.
4
artefacts
0
held by a system
1
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
- Review record confirming the strategy still matches the estate · Cloud console / configuration management
governing documentDocuments that govern the control
- Documented segmentation strategy and the boundaries it defines · Policy repository / GRC workspace
- Mapping of controls used at each boundary · Policy repository / GRC workspace
- Separation of duties matrix for sensitive functions · 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 decided per project with no enterprise view
- boundaries defined on network only, ignoring identity
- strategy documented once and never revisited as the estate grew
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 sheetGS-1 Align organization roles, responsibilities and accountabilities · GS-3 Define and implement data protection strategy