| Finding ID |
Severity |
Title |
Description |
|
V-243226
|
Medium |
The network device must not be configured to have any feature enabled that calls home to the vendor. |
Call-home services will routinely send data such as configuration and diagnostic information to the vendor for routine or emergency analysis and troubleshooting. There is a risk that transmission of sensitive data sent to unauthorized persons could result in data loss or downtime due to an attack. (See SRG-NET-000131-RTR-000083.) |
|
V-243225
|
Medium |
The network device must be configured to only permit management traffic that ingresses and egresses the out-of-band management (OOBM) interface. |
The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the... |
|
V-243224
|
Medium |
Wireless access points and bridges must be placed in dedicated subnets outside the enclave's perimeter. |
If an adversary is able to compromise an access point or controller that is directly connected to an enclave network, the adversary can easily surveil and attack other devices from that beachhead. A defense-in-depth approach requires an additional layer of protection between the WLAN and the enclave network. This is... |
|
V-243222
|
Medium |
WLAN EAP-TLS implementation must use certificate-based PKI authentication to connect to DoD networks. |
DoD certificate-based PKI authentication is strong, two-factor authentication that relies on carefully evaluated cryptographic modules. Implementations of EAP-TLS that are not integrated with certificate-based PKI could have security vulnerabilities.
For example, an implementation that uses a client certificate on laptop without a second factor could enable an adversary with access... |
|
V-243221
|
Medium |
WLAN components must be FIPS 140-2 or FIPS 140-3 certified and configured to operate in FIPS mode. |
If the DoD WLAN components (WLAN AP, controller, or client) are not NIST FIPS 140-2/FIPS 140-3 (Cryptographic Module Validation Program, CMVP) certified, the WLAN system may not adequately protect sensitive unclassified DoD data from compromise during transmission. |
|
V-243220
|
Medium |
WLAN must use EAP-TLS. |
EAP-TLS provides strong cryptographic mutual authentication and key distribution services not found in other EAP methods, and thus provides significantly more protection against attacks than other methods.
Additionally, EAP-TLS supports two-factor user authentication on the WLAN client, which provides significantly more protection than methods that rely on a password or... |
|
V-243219
|
Medium |
WLAN components must be Wi-Fi Alliance certified with WPA2 or WPA3. |
Wi-Fi Alliance certification ensures compliance with DoD interoperability requirements between various WLAN products. |
|
V-243218
|
Medium |
The WLAN inactive/idle session timeout must be set for 30 minutes or less. |
A WLAN session that never terminates due to inactivity may allow an opening for an adversary to highjack the session to obtain access to the network. |
|
V-243216
|
Medium |
The site must conduct continuous wireless Intrusion Detection System (IDS) scanning. |
DoD networks are at risk and DoD data could be compromised if wireless scanning is not conducted to identify unauthorized WLAN clients and access points connected to or attempting to connect to the network.
DoD Components must ensure that a Wireless Intrusion Detection System (WIDS) is implemented that allows for... |
|
V-243223
|
Low |
WLAN signals must not be intercepted outside areas authorized for WLAN access. |
Most commercially available WLAN equipment is preconfigured for signal power appropriate to most applications of the WLAN equipment. In some cases, this may permit the signals to be received outside the physical areas for which they are intended. This can occur when the intended area is relatively small, such as... |
|
V-243217
|
Low |
WLAN SSIDs must be changed from the manufacturer's default to a pseudo random word that does not identify the unit, base, organization, etc. |
An SSID identifying the unit, site, or purpose of the WLAN or that is set to the manufacturer default may cause an OPSEC vulnerability. |
