STIGViewer Support

The VPN Gateway must use Always On VPN connections for remote computing.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-266174F5BI-AP-300163SV-266174r1024406_ruleCCI-000366medium
Description
Allowing remote users to manually toggle a VPN connection can create critical security risks. With Always On VPN, if a secured connection to the gateway is lost, hybrid-working users will simply be disconnected from the internet until the issue is solved. "Always On" is a term that describes a VPN connection that is secure and always on after the initial connection is established. An Always On VPN deployment establishes a VPN connection with the client without the need for user interaction (e.g., user credentials). The remote client must not be able to access the Internet without first established a VPN session with a DOD site. Note that device compliance checks are still required prior to connecting to DOD resources. Although out of scope for this requirement, the connection process must ensure that remote devices meet security standards before accessing DOD resources. Devices that fail to meet compliance requirements can be denied access, reducing the risk of compromised endpoints.
STIGDate
F5 BIG-IP TMOS ALG Security Technical Implementation Guide2025-06-09

Related Frameworks

2 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (9) 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.

CFG-01Configuration Management Program
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
MON-01Continuous Monitoring
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
NET-09Session Integrity
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) 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.

AC-12Session Termination
1.00
AC-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-24(1)Transmit Access Authorization Information
1.00
AC-25Reference Monitor
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) 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.4.1
1.00
3.4.2
1.00
CCI2 mappings
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) 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.

PR.PSPlatform Security
0.50

Who does this work

10 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-266174r1024406_chk)

Verify at least one of these methods is configured. Always Connected Mode: From the BIG-IP GUI: 1. Access. 2. Connectivity/VPN. 3. Connectivity. 4. Profiles. 5. Click the name of the profile. 6. At the bottom, click Customize Package >> Windows. 7. Click "BIG-IP Edge Client" on the left. 8. Verify "Enable Always connected mode" is enabled. Machine Tunnels: From the BIG-IP GUI: 1. Access. 2. Connectivity/VPN. 3. Connectivity. 4. Profiles. 5. Click the name of the profile. 6. At the bottom, click Customize Package >> Windows. 7. Verify "Machine Tunnel Service" is checked. If the BIG-IP VPN Gateway is not configured to use an Always On VPN connection for remote computing, this is a finding.

Fix Text (F-70001r1023769_fix)

Configure at least one of these methods. Always Connected Mode: From the BIG-IP GUI: 1. Access. 2. Connectivity/VPN. 3. Connectivity. 4. Profiles. 5. Click the name of the profile. 6. At the bottom, click Customize Package >> Windows. 7. Click "BIG-IP Edge Client" on the left. 8. Check the box next to "Enable Always connected mode". Note: Always connected mode requires at least one host be listed in the Server list of the Connectivity Profile. Edit the Connectivity Profile to add an entry, if necessary. 9. Click "Download" to save the settings and download the installer. Machine Tunnels: From the BIG-IP GUI: 1. Access. 2. Connectivity/VPN. 3. Connectivity. 4. Profiles. 5. Click the name of the profile. 6. At the bottom, click Customize Package >> Windows. 7. Check "Machine Tunnel Service". 8. Optionally, click "Machine Tunnel Service" on the left and check "Enable NLA for Machine Tunnel". Note: To configure DNS Suffixes for NLA, edit the Connectivity Profile >> Win/Mac Edge Client > Location DNS List. 9. Click "Download" to save the settings and download the installer.