| V-65107 | | The DataPower Gateway 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 se... |
| V-65165 | | The DataPower Gateway must use SNMPv3. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authenticati... |
| V-64981 | | The DataPower Gateway 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 syst... |
| V-65063 | | The DataPower Gateway must enforce approved authorizations for controlling the flow of management information within DataPower based on information flow control policies. | A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If management informati... |
| V-65067 | | The DataPower Gateway must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until the administrator acknowledges the usage conditions and takes explicit actions to log on for further access. | The banner must be acknowledged by the administrator prior to allowing the administrator access to the network device. This provides assurance that th... |
| V-65069 | | The DataPower Gateway must provide audit record generation capability for DoD-defined auditable events within DataPower. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-65071 | | The DataPower Gateway must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the ... |
| V-65073 | | The DataPower Gateway must 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 notificatio... |
| V-65075 | | The DataPower Gateway must 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 ac... |
| V-65077 | | The DataPower Gateway must 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 ne... |
| V-65079 | | The DataPower Gateway must protect audit tools from unauthorized modification. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ne... |
| V-65081 | | The DataPower Gateway must protect audit tools from unauthorized deletion. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ne... |
| V-65085 | | The DataPower Gateway must prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization. | Changes to any software components can have significant effects on the overall security of the network device. Verifying software components have been... |
| V-65087 | | The DataPower Gateway must limit privileges to change the software resident within software libraries. | Changes to any software components of the network device can have significant effects on the overall security of the network. Therefore, only qualifie... |
| V-65089 | | The DataPower Gateway must have SSH and web management bound to the management interface and Telnet disabled. | In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types... |
| V-65091 | | The DataPower Gateway 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-65093 | | The DataPower Gateway must 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... |
| V-65095 | | If multifactor authentication is not supported and passwords must be used, the DataPower Gateway 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 measur... |
| V-65097 | | If multifactor authentication is not supported and passwords must be used, the DataPower Gateway 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... |
| V-65099 | | If multifactor authentication is not supported and passwords must be used, the DataPower Gateway 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... |
| V-65101 | | If multifactor authentication is not supported and passwords must be used, the DataPower Gateway 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... |
| V-65103 | | The DataPower Gateway must map the authenticated identity to the user account for PKI-based authentication. | Authorization for access to any network device requires an approved and assigned individual account identifier. To ensure only the assigned individual... |
| V-65105 | | The DataPower Gateway must 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 con... |
| V-65109 | | The DataPower Gateway must generate unique session identifiers using a FIPS 140-2 approved random number generator. | Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session ident... |
| V-65111 | | The DataPower Gateway must 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 securi... |
| V-65113 | | The DataPower Gateway must generate alerts that can be forwarded to the administrators and 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 t... |
| V-65115 | | The DataPower Gateway must generate alerts that can be forwarded to the administrators and 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 t... |
| V-65117 | | The DataPower Gateway must generate alerts that can be forwarded to the administrators and ISSO when accounts are disabled. | When application accounts are disabled, administrator accessibility is affected. Accounts are utilized for identifying individual device administrator... |
| V-65119 | | The DataPower Gateway must generate alerts that can be forwarded to the administrators and ISSO when accounts are removed. | When application accounts are removed, administrator accessibility is affected. Accounts are utilized for identifying individual device administrators... |
| V-65121 | | The DataPower Gateway must automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect. | Automatic session termination addresses the termination of administrator-initiated logical sessions in contrast to the termination of network connecti... |
| V-65123 | | The DataPower Gateway must provide a logout capability for administrator-initiated communication sessions. | If an administrator cannot explicitly end a device management session, the session may remain open and be exploited by an attacker; this is referred t... |
| V-65125 | | The DataPower Gateway must display an explicit logout message to administrators indicating the reliable termination of authenticated communications sessions. | If an explicit logout message is not displayed and the administrator does not expect to see one, the administrator may inadvertently leave a managemen... |
| V-65127 | | The DataPower Gateway must 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 t... |
| V-65129 | | The DataPower Gateway must 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 t... |
| V-65131 | | The DataPower Gateway must be compliant with at least one IETF standard authentication protocol. | Protecting access authorization information (i.e., access control decisions) ensures that authorization information cannot be altered, spoofed, or oth... |
| V-65135 | | If the DataPower Gateway uses discretionary access control, the DataPower Gateway must enforce organization-defined discretionary access control policies over defined subjects and objects. | Discretionary Access Control (DAC) is based on the notion that individual network administrators are "owners" of objects and therefore have discretion... |
| V-65137 | | If the DataPower Gateway uses role-based access control, the DataPower Gateway must enforce 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 organizationa... |
| V-65139 | | The DataPower Gateway must audit the execution of privileged functions. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromise... |
| V-65141 | | The DataPower Gateway must provide the capability for organization-identified individuals or roles to change the auditing to be performed based on all selectable event criteria within near-real-time. | If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not... |
| V-65143 | | The DataPower Gateway must 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 ... |
| V-65153 | | The DataPower Gateway 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 in... |
| V-65155 | | The DataPower Gateway must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generate... |
| V-65157 | | The DataPower Gateway must implement organization-defined 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. Cha... |
| V-65159 | | The DataPower Gateway must 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... |
| V-65161 | | The DataPower Gateway must 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 attack... |
| V-65163 | | The DataPower Gateway must require users to re-authenticate when privilege escalation or role changes occur. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When devices provide the capability ... |
| V-65167 | | The DataPower Gateway 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-65169 | | The IBM DataPower Gateway must only allow the use of protocols that implement cryptographic mechanisms to protect the integrity and confidentiality of management communications. | This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instea... |
| V-65171 | | The DataPower 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 s... |
| V-65173 | | The DataPower Gateway must use automated mechanisms to alert security personnel to threats identified by authoritative sources (e.g., CTOs) and in accordance with CJCSM 6510.01B. | By immediately displaying an alarm message, potential security violations can be identified more quickly even when administrators are not logged into ... |
| V-65175 | | The DataPower Gateway must generate audit log events for a locally developed list of auditable events. | Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack... |
| V-65177 | | The DataPower Gateway must 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 de... |
| V-65179 | | The DataPower Gateway must 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 de... |
| V-65181 | | The DataPower Gateway must 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 de... |
| V-65183 | | The DataPower Gateway must support organizational requirements to conduct 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 configurat... |
| V-65185 | | The DataPower Gateway must 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 exp... |
| V-65187 | | The DataPower Gateway must obtain its public key certificates from an appropriate certificate policy through an approved service provider. | For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agenci... |
| V-65189 | | The DataPower Gateway must not use 0.0.0.0 as the management IP address. | If 0.0.0.0 as the management IP address, the DataPower appliance will listen on all configured interfaces for management traffic. This can allow an at... |
| V-65065 | | The DataPower Gateway 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-65083 | | The DataPower Gateway must back up audit records at least every seven days onto a different system or system component than the system or component being audited. | Protection of log data includes assuring log data is not accidentally lost or deleted. Regularly backing up audit records to a different system or ont... |
| V-65145 | | The DataPower Gateway must 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 expansio... |
| V-65147 | | The DataPower Gateway must generate an immediate real-time alert of all audit failure events. | 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-65149 | | The DataPower Gateway must compare internal information system clocks at least every 24 hours with an authoritative time server. | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular ev... |
| V-65151 | | The DataPower Gateway must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second. | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular ev... |
