The Juniper SRX Services Gateway VPN must disable split-tunneling for remote clients VPNs.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-214695 | JUSX-VN-000028 | SV-214695r856579_rule | CCI-002397 | medium |
| Description | ||||
| Split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. A VPN hardware or software client with split tunneling enabled provides an unsecured backdoor to the enclave from the Internet. With split tunneling enabled, a remote client has access to the Internet while at the same time has established a secured path to the enclave via an IPsec tunnel. A remote client connected to the Internet that has been compromised by an attacker in the Internet, provides an attack base to the enclave’s private network via the IPsec tunnel. Hence, it is imperative that the VPN gateway enforces a no split-tunneling policy to all remote clients. Traffic to the protected resource will go through the specified dynamic VPN tunnel and will therefore be protected by the Juniper SRX firewall’s security policies. | ||||
| STIG | Date | |||
| Juniper SRX Services Gateway VPN Security Technical Implementation Guide | 2024-12-20 | |||
Related Frameworks
1 mapping across 4 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V3R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (2) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V3R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V3R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
NIST 800-1710 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
3.13.7
1.00
- DISA STIG Benchmark (XCCDF)V3R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- NIST SP 800-171 Rev 2, Appendix DRev 2 (Feb 2020, errata Jan 2021)equal to(normalised)
CCI1 mapping
CCI-002397
1.00
- DISA STIG Benchmark (XCCDF)V3R2intersects(normalised)
Details
Check Text (C-214695r856579_chk)
Verify split-tunneling is disabled.
[edit]
show security dynamic-vpn access-profile <dynamic-vpn-access-profile>
If split-tunneling is not disabled, this is a finding.
Fix Text (F-15894r297673_fix)
Configure the VPN tunnel to control what is sent out in clear text. The “remote-protected-resources” command defines what is routed through the tunnel. The “remote-exceptions” command defines what traffic is sent out in clear text. The following is an example.
[edit]
set security dynamic-vpn access-profile <dynamic-vpn-access-profile>
set security dynamic-vpn clients all ipsec-vpn <ipsec-vpn-name>
set security dynamic-vpn clients all remote-protected-resources <IP-address/mask>
set security dynamic-vpn clients all remote-exceptions 0.0.0.0/0