SC.L2-3.13.3 Role Separation
Separate user functionality from system management functionality so ordinary users are not presented with administrative interfaces.
Source: CMMC 2.0, SC.L2-3.13.3. 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 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
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