| V-217387 | High | The BIG-IP appliance must be configured to 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... |
| V-217408 | High | The BIG-IP appliance must be configured to terminate all management sessions after 10 minutes of inactivity. | If a device management session or connection remains open after management is completed, it may be hijacked by an attacker and used to compromise or damage the network device.
Nonlocal device... |
| V-228988 | High | The BIG-IP appliance must be configured to uniquely identify and authenticate organizational administrators (or processes acting on behalf of organizational administrators). | To assure accountability and prevent unauthenticated access, organizational administrators must be uniquely identified and authenticated for all network management accesses to prevent potential... |
| V-217417 | High | The BIG-IP appliance must be configured to protect against or limit the effects of all known types of Denial of Service (DoS) attacks on the BIG-IP appliance management network by limiting the number of concurrent sessions. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.
This... |
| V-229002 | Medium | The BIG-IP appliance must be configured to automatically lock the account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
| V-217388 | Medium | The BIG-IP appliance must be configured to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. |
| V-229013 | Medium | The BIG-IP appliance must be configured to employ automated mechanisms to assist in the tracking of security incidents. | Despite the investment in perimeter defense technologies, enclaves are still faced with detecting, analyzing, and remediating network breaches and exploits that have made it past the network... |
| V-229012 | Medium | The BIG-IP appliance must be configured to employ automated mechanisms to centrally verify authentication settings. | The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local... |
| V-229011 | Medium | The BIG-IP appliance must be configured to employ automated mechanisms to centrally apply authentication settings. | The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local... |
| V-229010 | Medium | The BIG-IP appliance must be configured to use automated mechanisms to alert security personnel to threats identified by authoritative sources (e.g., CTOs) and IAW with CJCSM 6510.01B. | By immediately displaying an alarm message, potential security violations can be identified more quickly even when administrators are not logged onto the network device. An example of a mechanism... |
| V-217383 | Medium | The BIG-IP appliance must automatically audit account creation. | Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account.... |
| V-228982 | Medium | Upon successful logon, the BIG-IP appliance must be configured to notify the administrator of the number of unsuccessful logon attempts since the last successful logon. | Administrators need to be aware of activity that occurs regarding their network device management account. Providing administrators with information regarding the number of unsuccessful attempts... |
| V-217381 | Medium | The BIG-IP appliance must limit the number of concurrent sessions to the Configuration Utility to 10 or an organization-defined number. | Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per... |
| V-217386 | Medium | The BIG-IP appliance must automatically audit account removal actions. | Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account removal actions will... |
| V-217384 | Medium | The BIG-IP appliance must automatically audit account modification. | Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Account management by a designated authority... |
| V-217385 | Medium | The BIG-IP appliance must automatically audit account-disabling actions. | Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account disabling actions will... |
| V-217420 | Medium | The BIG-IP appliance must be configured to employ automated mechanisms to centrally manage authentication settings. | The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local... |
| V-229007 | Medium | The BIG-IP appliance must be configured to dynamically manage user accounts. | Dynamic user account management prevents disruption of operations by minimizing the need for system restarts. Dynamic establishment of new user accounts will occur while the system is operational.... |
| V-229000 | Medium | The BIG-IP appliance must be configured to generate an immediate alert for account-enabling actions. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to... |
| V-217424 | Medium | The F5 BIG-IP must ensure SSH is disabled for root user logon to prevent remote access using the root account. | The F5 BIG-IP shell must be locked down to limit the ability to modify the configuration through the shell. Preventing attackers from remotely accessing management functions using root account... |
| V-228979 | Medium | The BIG-IP appliance must automatically remove or disable temporary user accounts after 72 hours. | Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. If temporary... |
| V-217422 | Medium | The BIG-IP appliance must be configured to create backups of information system documentation, including security-related documentation, when changes occur or weekly, whichever is sooner. | Information system backup is a critical step in maintaining data assurance and availability. Information system and security-related documentation contains information pertaining to system... |
| V-217410 | Medium | The BIG-IP appliance must be configured to automatically audit account-enabling actions. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to... |
| V-260049 | Medium | The F5 BIG-IP appliance providing user access control intermediary services must display the Standard Mandatory DOD-approved Notice and Consent Banner before granting access to SSH. | Display of the DOD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws,... |
| V-217411 | Medium | The BIG-IP appliance must be configured to enforce organization-defined role-based access control policies over defined subjects and objects. | Organizations can create specific roles based on job functions and the authorizations (i.e., privileges) to perform needed operations on organizational information systems associated with the... |
| V-217419 | Medium | The BIG-IP appliance must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. | Configuring the network device to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security... |
| V-217415 | Medium | The BIG-IP appliance must be configured to enforce access restrictions associated with changes to device configuration. | Failure to provide logical access restrictions associated with changes to device configuration may have significant effects on the overall security of the system.
When dealing with access... |
| V-217405 | Medium | The BIG-IP appliance must only transmit encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily... |
| V-217404 | Medium | The BIG-IP appliance must only store encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily... |
| V-217407 | Medium | The BIG-IP appliance must be configured to use mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance 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... |
| V-228978 | Medium | The BIG-IP appliance must provide automated support for account management functions. | Account management functions include: assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or... |
| V-217401 | Medium | If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that 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 of the effectiveness of a password in... |
| V-217400 | Medium | If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that at least one lower-case 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 of the effectiveness of a password in... |
| V-217403 | Medium | If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must require that when a password is changed, the characters are changed in at least eight (8) 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 increasing the window of opportunity for attempts at... |
| V-217402 | Medium | If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that 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 of the effectiveness of a password in... |
| V-229006 | Medium | The BIG-IP appliance must be configured to implement automated security responses if baseline configurations are changed in an unauthorized manner. | Unauthorized changes to the baseline configuration could make the device vulnerable to various attacks or allow unauthorized access to the device. Changes to device configurations can have... |
| V-228985 | Medium | The BIG-IP appliance must be configured to protect audit information from any type of unauthorized read access. | Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
If audit data were to become... |
| V-217423 | Medium | The BIG-IP appliance must be configured to obtain its public key certificates from an appropriate certificate policy through a DoD-approved service provider. | For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key... |
| V-228980 | Medium | The BIG-IP appliance must automatically disable accounts after a 35-day period of account inactivity. | Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Inactive accounts could be reactivated or... |
| V-228981 | Medium | Upon successful logon, the BIG-IP appliance must be configured to notify the administrator of the date and time of the last logon. | Administrators need to be aware of activity that occurs regarding their network device management account. Providing administrators with information regarding the date and time of their last... |
| V-217394 | Medium | The BIG-IP appliance must be configured to protect audit tools from unauthorized access. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on... |
| V-217397 | Medium | The BIG-IP appliance must be configured to ensure administrators are authenticated with an individual authenticator prior to using a group authenticator. | To assure individual accountability and prevent unauthorized access, administrators must be individually identified and authenticated.
Individual accountability mandates that each administrator... |
| V-217396 | Medium | The BIG-IP appliance must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and vulnerability assessments. | In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must... |
| V-229008 | Medium | The BIG-IP appliance must be configured to allow the use of a temporary password for system logons with an immediate change to a permanent password. | Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary... |
| V-217390 | Medium | The BIG-IP appliance must be configured to protect against an individual (or process acting on behalf of an individual) falsely denying having performed system configuration changes. | This requirement supports non-repudiation of actions taken by an administrator and is required in order to maintain the integrity of the configuration management process. All configuration changes... |
| V-217393 | Medium | The BIG-IP appliance must be configured to protect audit information from unauthorized deletion. | Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
If audit data were to become... |
| V-217392 | Medium | The BIG-IP appliance must be configured to protect audit information from unauthorized modification. | Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit network device activity.
If audit data were to become compromised,... |
| V-228987 | Medium | The BIG-IP appliance must be configured to use NIAP evaluated cryptographic mechanisms to protect the integrity of audit information at rest. | Audit records may be tampered with. If the integrity of audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is... |
| V-217413 | Medium | The BIG-IP appliance must be configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | In order to ensure network devices have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit... |
| V-228989 | Medium | The BIG-IP appliance must be configured to prohibit password reuse for a minimum of five generations. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
To meet password policy requirements, passwords need... |
| V-217399 | Medium | If multifactor authentication is not supported and passwords must be used, the BIG-IP appliance must enforce password complexity by requiring that at least one upper-case 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 measure of the effectiveness of a password in... |
| V-228993 | Medium | The application must be configured to reveal error messages only to authorized individuals (ISSO, ISSM, and SA). | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state. Additionally, sensitive account... |
| V-229001 | Medium | The BIG-IP appliance must be configured to transmit access authorization information using approved security safeguards to authorized information systems that enforce access control decisions. | Protecting access authorization information (i.e., access control decisions) ensures that authorization information cannot be altered, spoofed, or otherwise compromised during transmission.
In... |
| V-217406 | Medium | The BIG-IP appliance must be configured to obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. | To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the network device must not provide any information that would allow... |
| V-217416 | Medium | The BIG-IP appliance must be configured to audit the enforcement actions used to restrict access associated with changes to the device. | Without auditing the enforcement of access restrictions against changes to the device configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available... |
| V-228998 | Medium | The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are removed. | When application accounts are removed, administrator accessibility is affected. Accounts are utilized for identifying individual device administrators or for identifying the device processes... |
| V-217418 | Medium | The BIG-IP appliance must be configured to 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. |
| V-259332 | Medium | The F5 BIG-IP appliance must be configured to restrict a consistent inbound IP for the entire management session. | This security measure helps limit the effects of denial-of-service attacks by employing anti-session hijacking security safeguards. Session hijacking, also called cookie hijacking, is the... |
| V-217414 | Medium | The BIG-IP appliance must be configured to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions 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... |
| V-228991 | Medium | The BIG-IP appliance must be configured to enforce a 60-day maximum password lifetime restriction. | Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals.
One method of minimizing this risk is to use complex passwords and... |
| V-228990 | Medium | The BIG-IP appliance must be configured to enforce 24 hours/1 day as the minimum password lifetime. | Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement.
Restricting this setting limits the user's ability... |
| V-217398 | Medium | The BIG-IP appliance must be configured to 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... |
| V-228992 | Medium | The BIG-IP appliance must be configured to automatically remove or disable emergency accounts after 72 hours. | Emergency accounts are administrator accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation... |
| V-228995 | Medium | The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are created. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to... |
| V-228994 | Medium | The BIG-IP appliance must be configured to activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected. | Predictable failure prevention requires organizational planning to address device failure issues. If components key to maintaining the device's security fail to function, the device could continue... |
| V-228997 | Medium | The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are disabled. | When application accounts are disabled, administrator accessibility is affected. Accounts are utilized for identifying individual device administrators or for identifying the device processes... |
| V-228996 | Medium | The BIG-IP appliance must be configured to generate alerts that can be forwarded to the administrators and Information System Security Officer (ISSO) when accounts are modified. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to... |
| V-217389 | Low | The BIG-IP appliance must be configured to 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 consistent with applicable federal laws,... |
| V-229003 | Low | The BIG-IP appliance must be configured to notify the administrator, upon successful logon (access), of the location of last logon (terminal or IP address) in addition to the date and time of the last logon (access). | Administrators need to be aware of activity that occurs regarding their account. Providing them with information deemed important by the organization may aid in the discovery of unauthorized... |
| V-230217 | Low | If the BIG-IP appliance is being used to authenticate users for web applications, the HTTPOnly flag must be set. | The HttpOnly attribute directs browsers to use cookies by way of the HTTP and HTTPS protocols only, ensuring that the cookie is not available by other means, such as JavaScript function calls.... |
| V-229005 | Low | The BIG-IP appliance must be configured to generate an immediate alert when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity. | If security personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. This could lead to the loss of audit... |
| V-228983 | Low | The BIG-IP appliance must be configured to alert the ISSO and SA (at a minimum) in the event of an audit processing failure. | 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 this notification, the security personnel may be unaware of an... |
| V-229009 | Low | The BIG-IP appliance must be configured to notify the administrator of the number of successful logon attempts occurring during an organization-defined time period. | Administrators need to be aware of activity that occurs regarding their network device management account. Providing administrators with information regarding the date and time of their last... |
| V-217421 | Low | The BIG-IP appliance must create backups of system-level information contained in the information system when changes occur or weekly, whichever is sooner. | System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configuration, as well as software required for the... |
