STIGViewer Support

The Remote Access VPN Gateway and/or client must enforce a policy to retain the Standard Mandatory DOD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-207186SRG-NET-000042-VPN-000120SV-207186r1056164_ruleCCI-000050medium
Description
The user must acknowledge the banner before being allowed access to the network. This provides assurance that the user has seen the message and accepted the conditions for access. If the user does not acknowledge the consent banner, DOD will not be in compliance with system use notifications required by law. In most VPN implementations, the banner is configured in the management backplane (NDM SRG) and serves as the presentation for the VPN client connection as well as for administrator logon to the device management tool/backplane. This requirement remains applicable for Always-on. Consult the product-specific STIG or vendor documentation for specific configuration. To establish acceptance of the application usage policy, a click-through banner at application logon is required. The VPN gateway must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK". This applies to gateways that have the concept of a user account and have the logon function residing on the gateway or the gateway acts as a user intermediary.
STIGDate
Virtual Private Network (VPN) Security Requirements Guide2025-09-10

Related Frameworks

1 mapping across 4 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.

SEA-18System Use Notification (Logon Banner)
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (16) 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-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-7Unsuccessful Logon Attempts
1.00
AC-8System Use Notification
1.00
IA-2(1)Multi-factor Authentication to Privileged Accounts
1.00

+6 more (top 10 by confidence shown)

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.1.9
1.00
CCI1 mapping

Details

Check Text (C-207186r1056164_chk)

If the user/remote client connection banner is the same as the banner configured as part of the NDM SRG, this is not applicable. Verify the ALG retains the Standard Mandatory DOD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access. If the Remote Access VPN Gateway and/or client does not retain the Standard Mandatory DOD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access, this is a finding.

Fix Text (F-7446r1056129_fix)

Configure the Remote Access VPN Gateway and/or client to retain the Standard Mandatory DOD-approved Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.