|The network device must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after 10 minutes of inactivity except to fulfill documented and validated mission requirements.
|Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port...
|The network device must be configured to use an authentication server to authenticate users prior to granting administrative access.
|Centralized management of authentication settings increases the security of remote and nonlocal access methods. This is particularly important protection against the insider threat. With robust...
|The network device must be configured to implement cryptographic mechanisms using a FIPS 140-2 approved algorithm to protect the confidentiality of remote maintenance sessions.
|This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking...
|The network device must be running an operating system release that is currently supported by the vendor.
|Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities.
|The network device must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services.
|To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable unused...
|The network device must enforce the assigned privilege level for each administrator and authorizations for access to all commands relative to the privilege level in accordance with applicable policy for the device.
|To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems must be properly configured to incorporate...
|The network device must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).
|Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate...
|The password configured on the WLAN access point for key generation and client access must be set to a 15-character or longer complex password as required by USCYBERCOM CTO 07-15 Rev1.
|If the organization does not use a strong passcode for client access, an adversary is significantly more likely to be able to obtain it. Once this occurs, the adversary may be able to obtain full...
|The network device must enforce a minimum 15-character password length.
|Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to...
|The network device must not have any default manufacturer passwords when deployed.
|Network devices not protected with strong password schemes provide the opportunity for anyone to crack the password and gain access to the device, which can result in loss of availability,...
|The network device must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.
|All network devices must present a DoD-approved warning banner prior to a system administrator logging on. The banner should warn any unauthorized user not to proceed. It also should provide clear...
|The network device must be configured to authenticate each administrator prior to authorizing privileges based on assignment of group or role.
|To ensure individual accountability and prevent unauthorized access, administrators must be individually identified and authenticated.
Individual accountability mandates that each administrator...
|The network device must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
|By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced.
|The network device must be configured to synchronize internal information system clocks using redundant authoritative time sources.
|The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other...
|The network device must implement replay-resistant authentication mechanisms for network access to privileged 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...
|The network device must be configured with both an ingress and egress ACL.
|Changes to the hardware or software components of the network device can have significant effects on the overall security of the network. Therefore, only qualified and authorized individuals...
|The network device must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.
|Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server...
|The network device must generate audit records when successful/unsuccessful logon attempts occur.
|Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an...
|The network device must authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based.
|If Network Time Protocol is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will...