SC.L2-3.13.7 Split Tunneling
Prevent a remote device from holding a connection to organizational systems while simultaneously connecting through another path to external network resources, the split tunneling case.
Source: CMMC 2.0, SC.L2-3.13.7. 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
- VPN or remote client configuration disabling split tunneling · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence the setting is enforced and not user changeable · Document repository
governing documentDocuments that govern the control
- Coverage across all remote client platforms · Document repository
First move
Common gaps auditors find
- Split tunneling disabled by policy but user configurable
- Some client platforms or vendor clients still permit it
- Exceptions granted for bandwidth with no compensating control
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.6 Network Communication by Exception · SC.L2-3.13.8 Data in Transit