SC.L2-3.13.3 Role Separation
Separate user functionality from system management functionality so ordinary users are not presented with administrative interfaces.
3
artefacts
1
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
- Configuration restricting administrative interface exposure · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence of separation between user and management interfaces · Document repository
governing documentDocuments that govern the control
- Architecture showing management plane separation · Policy repository / GRC workspace
First move
Start with the 1 of 3 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
- Administrative consoles reachable from user networks
- Separation logical in name only with shared credentials
- Management interfaces exposed to the internet
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 sheetSC.L2-3.13.2 Security Engineering · SC.L2-3.13.4 Shared Resource Control