III - Administrative Classified
Rules and Groups employed by this XCCDF Profile
-
SRG-NET-000147
Group -
The TLS VPN must be configured to use replay-resistant authentication mechanisms for network access to nonprivileged accounts.
A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be ...Rule Medium Severity -
SRG-NET-000147
Group -
The IPsec VPN Gateway must use anti-replay mechanisms for security associations.
Anti-replay is an IPsec security mechanism at a packet level, which helps to avoid unwanted users from intercepting and modifying an ESP packet.Rule Medium Severity -
SRG-NET-000148
Group -
The VPN Gateway must uniquely identify all network-connected endpoint devices before establishing a connection.
Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For distributed architectures (e.g., service-oriented architectures), the d...Rule Medium Severity -
SRG-NET-000164
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.
Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. To meet this requirement, the information...Rule Medium Severity -
SRG-NET-000165
Group -
The site-to-site VPN, when using PKI-based authentication for devices, must enforce authorized access to the corresponding private key.
If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key use...Rule Medium Severity -
SRG-NET-000166
Group -
The Remote Access VPN Gateway must use a separate authentication server (e.g., LDAP, RADIUS, TACACS+) to perform user authentication.
The VPN interacts directly with public networks and devices and should not contain user authentication information for all users. AAA network security services provide the primary framework through...Rule Medium Severity -
SRG-NET-000166
Group -
The VPN Gateway must map the authenticated identity to the user account for PKI-based authentication.
Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. This re...Rule Medium Severity -
SRG-NET-000168
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.
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Although allowed by SP800-131Ar2 for some applications, SHA-1 is considered a compr...Rule Medium Severity -
SRG-NET-000169
Group -
The VPN Gateway must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
Lack of authentication and identification enables non-organizational users to gain access to the network or possibly a VPN gateway that provides opportunity for intruders to compromise resources wi...Rule Medium Severity -
SRG-NET-000205
Group -
The VPN Gateway must be configured to route sessions to an IDPS for inspection.
Remote access devices, such as those providing remote access to network devices and information systems, which lack automated, capabilities increase risk and makes remote user access management dif...Rule Medium Severity -
SRG-NET-000213
Group -
The VPN Gateway must terminate all network connections associated with a communications session at the end of the session.
Idle TCP sessions can be susceptible to unauthorized access and hijacking attacks. By default, routers do not continually test whether a previously connected TCP endpoint is still reachable. If one...Rule Low Severity -
SRG-NET-000230
Group -
The VPN Gateway must use FIPS 140-2 compliant mechanisms for authentication to a cryptographic module.
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified, and therefore cannot be relied upon to provide confidentiality or integrity and DoD data may be ...Rule Medium Severity -
SRG-NET-000230
Group -
The IPSec VPN must be configured to use FIPS-validated SHA-2 at 384 bits or higher for Internet Key Exchange (IKE).
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Although allowed by SP800-131Ar2 for some applications, SHA-1 is considered a compr...Rule High Severity -
SRG-NET-000231
Group -
The VPN Gateway must invalidate session identifiers upon user logoff or other session termination.
Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and continuing to employ previously valid session IDs. Session IDs are tokens...Rule Medium Severity -
SRG-NET-000233
Group -
The VPN Gateway must recognize only system-generated session identifiers.
VPN gateways (depending on function) utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the session identifier, or can inject or manu...Rule Medium Severity -
SRG-NET-000234
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.
Both IPsec and TLS gateways use the RNG to strengthen the security of the protocols. Using a weak RNG will weaken the protocol and make it more vulnerable.Rule Medium Severity -
SRG-NET-000235
Group -
The VPN Gateway must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. VPN gateways that fail suddenly and with no incor...Rule Medium Severity -
SRG-NET-000313
Group -
The VPN Gateway must be configured to perform an organization-defined action if the audit reveals unauthorized activity.
Remote access devices, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and makes remote user access manage...Rule Medium Severity -
SRG-NET-000314
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.
Without the ability to immediately disconnect or disable remote access, an attack or other compromise taking progress would not be immediately stopped. Remote access functionality must have the ca...Rule Medium Severity -
SRG-NET-000317
Group -
The IPsec VPN Gateway must use AES encryption for the Internet Key Exchange (IKE) proposal to protect confidentiality of remote access sessions.
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DoD non-public information ...Rule High Severity -
SRG-NET-000334
Group -
The VPN Gateway must off-load audit records onto a different system or media than the system being audited.
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. Th...Rule Medium Severity -
SRG-NET-000335
Group -
The VPN Gateway must generate a log record or an SNMP trap that can be forwarded as an alert to, at a minimum, the SCA and ISSO, of all log failure events where the detection and/or prevention function is unable to write events to either local storage or the centralized server.
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impe...Rule Medium Severity -
SRG-NET-000337
Group -
The VPN Gateway must renegotiate the IPsec security association (SA) after eight hours or less.
The IPsec SA and its corresponding key will expire either after the number of seconds or amount of traffic volume has exceeded the configured limit. A new SA is negotiated before the lifetime thres...Rule Medium Severity -
SRG-NET-000337
Group -
The VPN Gateway must renegotiate the IKE security association (SA) after eight hours or less.
When a VPN gateway creates an IPsec SA, resources must be allocated to maintain the SA. These resources are wasted during periods of IPsec endpoint inactivity, which could result in the gateway’s i...Rule Medium Severity -
SRG-NET-000341
Group -
The VPN Gateway must accept the Common Access Card (CAC) credential.
The use of Personal Identity Verification (PIV) credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC as the PIV credential to su...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.