SC.L2-3.13.4 Shared Resource Control
Prevent information from being transferred, intentionally or unintentionally, between users through shared system resources.
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 evidence for object reuse and memory or storage clearing · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence of isolation between users in shared and virtualized environments · Cloud console / configuration management
governing documentDocuments that govern the control
- Testing results showing residual data is not accessible · Document repository
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
- Shared and virtualized environments assumed isolated without verification
- Temporary files and shared directories accessible across users
- Object reuse protections disabled for performance
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.3 Role Separation · SC.L2-3.13.5 Public-Access System Separation