SC.L2-3.13.4 Shared Resource Control
Prevent information from being transferred, intentionally or unintentionally, between users through shared system resources.
Source: CMMC 2.0, SC.L2-3.13.4. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
- Testing results showing residual data is not accessible · Document repository
governing documentDocuments that govern the control
none for this control
First move
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