| V-279248 | | The Edge SWG must be configured to use FIPS mode. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-279249 | | The Edge SWG must be configured to use tlsv1.2 or greater. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-279250 | | The Edge SWG must be configured to assign appropriate user roles or access levels to authenticated users. | Successful identification and authentication must not automatically give an entity full access to a network device or security domain. The lack of aut... |
| V-279251 | | The Edge SWG must be configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access. | Before continuing, the site must follow the configuration steps in SYME-ND-000100.
Centralized management of authentication settings increases the se... |
| V-279252 | | The Edge SWG must be configured to send log data to at least one central log server for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO). | Before continuing, the site must follow the configuration steps under SYME-ND-000800.
The aggregation of log data kept on a syslog server can be used... |
| V-279264 | | The Edge SWG must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after five 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 se... |
| V-279275 | | The Edge SWG 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 vulnerabilit... |
| V-279253 | | The Edge SWG 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, ... |
| V-279254 | | The Edge SWG must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the device. | Display of the DOD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is c... |
| V-279255 | | The Edge SWG must produce audit records containing information to establish when (date and time) the events occurred. | It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done to... |
| V-279256 | | The Edge SWG 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 da... |
| V-279257 | | The Edge SWG 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 ... |
| V-279258 | | The Edge SWG must enforce password complexity by requiring at least one uppercase character be used. | Use of a complex passwords helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measur... |
| V-279259 | | The Edge SWG must enforce a 60-day password lifetime. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-279260 | | The Edge SWG must enforce password complexity by requiring at least one lowercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-279261 | | The Edge SWG must enforce password complexity by requiring at least one numeric character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-279262 | | The Edge SWG must enforce password complexity by requiring at least one special character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-279263 | | The Edge SWG must require that when a password is changed, the characters are changed in at least eight of the positions within the password. | If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increa... |
| V-279265 | | The Edge SWG must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | Network devices must be able to allocate audit record storage capacity to ensure sufficient storage capacity in which to write the audit logs. The tas... |
| V-279266 | | The Edge SWG must generate an immediate real-time alert of all audit failure events requiring real-time alerts. | 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 aler... |
| V-279268 | | The Edge SWG 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 authenticati... |
| V-279269 | | The Edge SWG must authenticate Network Time Protocol 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... |
| V-279270 | | The Edge SWG must prohibit the use of cached authenticators after an organization-defined time period. | Some authentication implementations can be configured to use cached authenticators.
If cached authentication information is out-of-date, the validity... |
| V-279271 | | The Edge SWG must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-279272 | | The Edge SWG must be configured to conduct backups of system-level information contained in the information system when changes occur. | System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configurat... |
| V-279273 | | The Edge SWG must obtain its public key certificates from an appropriate certificate policy through an approved service provider. | Before continuing, the site must follow the configuration steps in SYME-ND-000100.
For user certificates, each organization obtains certificates from... |
| V-279274 | | The Edge SWG must limit the number of concurrent management sessions to a maximum of three. | Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of al... |
| V-279276 | | The Edge SWG must be configured to allow user selection of long passwords and passphrases, including spaces and all printable characters for password-based authentication. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-279277 | | The Edge SWG must be configured to implement a local cache of revocation data to support path discovery and validation for public key-based authentication. | Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certific... |
| V-279283 | | The Edge SWG must be configured to verify when users create or update passwords, and that the passwords are not found on the list of commonly used, expected, or compromised passwords in IA-5 (1) (a) for password-based authentication. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
