Virtual Private Network (VPN) Security Requirements Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-NET-000041
<GroupDescription></GroupDescription>Group -
The Remote Access VPN Gateway and/or client must display the Standard Mandatory DoD Notice and Consent Banner before granting remote access to the network.
<VulnDiscussion>Display of a standardized and approved use notification before granting access to the network ensures privacy and security no...Rule Medium Severity -
SRG-NET-000042
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>The banner must be acknowledged by the user prior to allowing the user access to the network. This provides assurance that th...Rule Medium Severity -
SRG-NET-000043
<GroupDescription></GroupDescription>Group -
The publicly accessible VPN Gateway must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
<VulnDiscussion>Display of a standardized and approved use notification before granting access to the publicly accessible VPN gateway ensures...Rule Medium Severity -
SRG-NET-000053
<GroupDescription></GroupDescription>Group -
The VPN Gateway must limit the number of concurrent sessions for user accounts to 1 or to an organization-defined number.
<VulnDiscussion>VPN gateway management includes the ability to control the number of users and user sessions that utilize a VPN gateway. Limi...Rule Medium Severity -
SRG-NET-000062
<GroupDescription></GroupDescription>Group -
The TLS VPN Gateway must use TLS 1.2, at a minimum, to protect the confidentiality of sensitive data during transmission for remote access connections.
<VulnDiscussion>Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and u...Rule High Severity -
SRG-NET-000063
<GroupDescription></GroupDescription>Group -
The remote access VPN Gateway must use a digital signature generated using FIPS-validated algorithms and an approved hash function to protect the integrity of TLS remote access sessions.
<VulnDiscussion>Without integrity protection, unauthorized changes may be made to the log files and reliable forensic analysis and discovery ...Rule Medium Severity -
SRG-NET-000063
<GroupDescription></GroupDescription>Group -
The VPN Gateway must be configured to use IPsec with SHA-2 at 384 bits or greater for hashing to protect the integrity of remote access sessions.
<VulnDiscussion>Without strong cryptographic integrity protections, information can be altered by unauthorized users without detection. SHA-...Rule Medium Severity -
SRG-NET-000074
<GroupDescription></GroupDescription>Group -
The IPSec VPN must be configured to use a Diffie-Hellman (DH) Group of 16 or greater for Internet Key Exchange (IKE) Phase 1.
<VulnDiscussion>Use of an approved DH algorithm ensures the IKE (Phase 1) proposal uses FIPS-validated key management techniques and processe...Rule High Severity -
SRG-NET-000075
<GroupDescription></GroupDescription>Group -
If the site-to-site VPN implementation uses L2TP, L2TPv3 sessions must be authenticated prior to transporting traffic.
<VulnDiscussion>L2TPv3 sessions can be used to transport layer-2 protocols across an IP backbone. These protocols were intended for link-loca...Rule Medium Severity -
SRG-NET-000077
<GroupDescription></GroupDescription>Group -
The VPN Gateway must generate log records containing information to establish what type of events occurred.
<VulnDiscussion>Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events l...Rule Low Severity -
SRG-NET-000078
<GroupDescription></GroupDescription>Group -
The VPN Gateway must generate log records containing information to establish when (date and time) the events occurred.
<VulnDiscussion>Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to...Rule Low Severity -
SRG-NET-000079
<GroupDescription></GroupDescription>Group -
The VPN Gateway must generate log records containing information that establishes the identity of any individual or process associated with the event.
<VulnDiscussion>Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associ...Rule Medium Severity -
SRG-NET-000088
<GroupDescription></GroupDescription>Group -
The VPN Gateway must generate log records containing information to establish where the events occurred.
<VulnDiscussion>Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up t...Rule Medium Severity -
SRG-NET-000089
<GroupDescription></GroupDescription>Group -
The VPN Gateway must generate log records containing information to establish the source of the events.
<VulnDiscussion>Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up...Rule Low Severity -
SRG-NET-000091
<GroupDescription></GroupDescription>Group -
The VPN Gateway must produce log records containing information to establish the outcome of the events.
<VulnDiscussion>Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attac...Rule Medium Severity -
SRG-NET-000098
<GroupDescription></GroupDescription>Group -
The VPN Gateway must protect log information from unauthorized read access if all or some of this data is stored locally.
<VulnDiscussion>Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means...Rule Low Severity -
SRG-NET-000099
<GroupDescription></GroupDescription>Group -
The VPN Gateway log must protect audit information from unauthorized modification when stored locally.
<VulnDiscussion>If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious sy...Rule Medium Severity -
SRG-NET-000100
<GroupDescription></GroupDescription>Group -
The VPN Gateway must protect audit information from unauthorized deletion when stored locally.
<VulnDiscussion>If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious sy...Rule Medium Severity -
SRG-NET-000132
<GroupDescription></GroupDescription>Group -
The VPN Gateway must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e....Rule Medium Severity -
SRG-NET-000132
<GroupDescription></GroupDescription>Group -
The IPsec VPN Gateway must use IKEv2 for IPsec VPN security associations.
<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e....Rule Medium Severity -
SRG-NET-000132
<GroupDescription></GroupDescription>Group -
The Remote Access VPN Gateway must be configured to prohibit Point-to-Point Tunneling Protocol (PPTP) and L2F.
<VulnDiscussion>The PPTP and L2F are obsolete method for implementing virtual private networks. Both protocols may be easy to use and readily...Rule Medium Severity -
SRG-NET-000132
<GroupDescription></GroupDescription>Group -
For site-to-site VPN implementations, the L2TP protocol must be blocked or denied at the security boundary with the private network so unencrypted L2TP packets cannot traverse into the private network of the enclave.
<VulnDiscussion>Unlike GRE (a simple encapsulating header) L2TP is a full-fledged communications protocol with control channel, data channels...Rule Medium Severity -
SRG-NET-000138
<GroupDescription></GroupDescription>Group -
The VPN Gateway must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
<VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to pre...Rule Medium Severity -
SRG-NET-000140
<GroupDescription></GroupDescription>Group -
The VPN Gateway must use FIPS-validated SHA-2 or higher hash function to protect the integrity of hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification.
<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Although al...Rule Medium Severity -
The VPN Gateway must use multifactor authentication (e.g., DoD PKI) for network access to non-privileged accounts.
<VulnDiscussion>To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to ...Rule High Severity -
SRG-NET-000145
<GroupDescription></GroupDescription>Group
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.