CMMC 2.0
System and Communications Protection

CMMC 2.0 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.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 15 controls across 9 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

SOC 2 · 4 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

ISO 27002:2022 · 3 controls

  • 6.7 Remote working
  • 8.20 Networks security
  • 8.22 Segregation of networks

PCI DSS 4.0 · 2 controls

  • 1.3.2 1.3.2 Outbound CDE traffic restricted
  • 1.5.1 1.5.1 Security controls on dual-connected devices
  • ANSSI-HYG-32 Secure the Network Connection of Devices Used for Mobile Working
  • ASBv3-NS-9 Connect on-premises or cloud network privately

CIS Controls v8 · 1 control

  • CIS-12.7 Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise’s AAA Infrastructure

FedRAMP High · 1 control

  • SC-7(7) Split Tunneling for Remote Devices

FedRAMP Moderate · 1 control

  • SC-7(7) Split Tunneling for Remote Devices

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in System and Communications Protection

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 SC.L2-3.13.7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 1 were rejected on the FedRAMP Moderate pair alone.

Query this from an agent

The graph holds this control, the 15 it maps to, and the evidence behind each claim, over MCP and REST.