Virtual Private Network (VPN) Security Requirements Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
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 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 -
The VPN Gateway, when utilizing PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.
<VulnDiscussion>Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate n...Rule Medium Severity -
SRG-NET-000165
<GroupDescription></GroupDescription>Group -
The VPN Client must implement multifactor authentication for network access to non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access.
<VulnDiscussion>Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the...Rule Medium Severity -
SRG-NET-000147
<GroupDescription></GroupDescription>Group -
The TLS VPN must be configured to use replay-resistant authentication mechanisms for network access to non-privileged accounts.
<VulnDiscussion>A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authen...Rule Medium Severity -
SRG-NET-000147
<GroupDescription></GroupDescription>Group -
The IPsec VPN Gateway must use anti-replay mechanisms for security associations.
<VulnDiscussion>Anti-replay is an IPsec security mechanism at a packet level, which helps to avoid unwanted users from intercepting and modif...Rule Medium Severity -
SRG-NET-000148
<GroupDescription></GroupDescription>Group -
The VPN Gateway must uniquely identify all network-connected endpoint devices before establishing a connection.
<VulnDiscussion>Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For...Rule Medium Severity -
SRG-NET-000164
<GroupDescription></GroupDescription>Group -
The site-to-site VPN, when using PKI-based authentication for devices, must enforce authorized access to the corresponding private key.
<VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the ne...Rule Medium Severity -
The Remote Access VPN Gateway must use a separate authentication server (e.g., LDAP, RADIUS, TACACS+) to perform user authentication.
<VulnDiscussion>The VPN interacts directly with public networks and devices and should not contain user authentication information for all us...Rule Medium Severity -
SRG-NET-000166
<GroupDescription></GroupDescription>Group -
The VPN Gateway must map the authenticated identity to the user account for PKI-based authentication.
<VulnDiscussion>Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the indivi...Rule Medium Severity -
SRG-NET-000168
<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 -
SRG-NET-000169
<GroupDescription></GroupDescription>Group -
The VPN Gateway must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
<VulnDiscussion>Lack of authentication and identification enables non-organizational users to gain access to the network or possibly a VPN ga...Rule Medium Severity -
SRG-NET-000205
<GroupDescription></GroupDescription>Group -
The VPN Gateway must be configured to route sessions to an IDPS for inspection.
<VulnDiscussion>Remote access devices, such as those providing remote access to network devices and information systems, which lack automated...Rule Medium Severity -
SRG-NET-000213
<GroupDescription></GroupDescription>Group -
The VPN Gateway must terminate all network connections associated with a communications session at the end of the session.
<VulnDiscussion>Idle TCP sessions can be susceptible to unauthorized access and hijacking attacks. By default, routers do not continually tes...Rule Low Severity -
SRG-NET-000230
<GroupDescription></GroupDescription>Group -
The VPN Gateway must use FIPS 140-2 compliant mechanisms for authentication to a cryptographic module.
<VulnDiscussion>Unapproved mechanisms that are used for authentication to the cryptographic module are not verified, and therefore cannot be ...Rule Medium Severity -
SRG-NET-000230
<GroupDescription></GroupDescription>Group -
The IPSec VPN must be configured to use FIPS-validated SHA-2 at 384 bits or higher for Internet Key Exchange (IKE).
<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Although al...Rule High Severity -
SRG-NET-000231
<GroupDescription></GroupDescription>Group -
The VPN Gateway must invalidate session identifiers upon user logoff or other session termination.
<VulnDiscussion>Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and co...Rule Medium Severity -
SRG-NET-000233
<GroupDescription></GroupDescription>Group -
The VPN Gateway must off-load audit records onto a different system or media than the system being audited.
<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common...Rule Medium Severity -
SRG-NET-000335
<GroupDescription></GroupDescription>Group -
The VPN Gateway must recognize only system-generated session identifiers.
<VulnDiscussion>VPN gateways (depending on function) utilize sessions and session identifiers to control application behavior and user access...Rule Medium Severity -
SRG-NET-000234
<GroupDescription></GroupDescription>Group -
The VPN Gateway must generate unique session identifiers using FIPS-validated Random Number Generator (RNG) based on the Deterministic Random Bit Generators (DRBG) algorithm.
<VulnDiscussion>Both IPsec and TLS gateways use the RNG to strengthen the security of the protocols. Using a weak RNG will weaken the protoco...Rule Medium Severity -
SRG-NET-000235
<GroupDescription></GroupDescription>Group -
The VPN Gateway must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
<VulnDiscussion>Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized acces...Rule Medium Severity -
SRG-NET-000313
<GroupDescription></GroupDescription>Group -
The VPN Gateway must be configured to perform an organization-defined action if the audit reveals unauthorized activity.
<VulnDiscussion>Remote access devices, such as those providing remote access to network devices and information systems, which lack automated...Rule Medium Severity -
SRG-NET-000314
<GroupDescription></GroupDescription>Group -
The VPN Gateway administrator accounts or security policy must be configured to allow the system administrator to immediately disconnect or disable remote access to devices and/or users when needed.
<VulnDiscussion>Without the ability to immediately disconnect or disable remote access, an attack or other compromise taking progress would n...Rule Medium Severity -
The IPsec VPN Gateway must use AES encryption for the Internet Key Exchange (IKE) proposal to protect confidentiality of remote access sessions.
<VulnDiscussion>Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote...Rule High Severity -
SRG-NET-000320
<GroupDescription></GroupDescription>Group -
The VPN Gateway must transmit organization-defined access authorization information using FIPS 140-2-validated cryptography to a compliant authentication server, which enforces access control decisions.
<VulnDiscussion>Protecting authentication communications between the client, the VPN Gateway, and the authentication server keeps this critic...Rule Medium Severity
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.