The IBM DataPower ALG Security Technical Implementation Guide (STIG) provides the technical security policies, requirements, and implementation details for applying security concepts to the IBM DataPower platform (physical and virtual machine). This document is meant for use in conjunction with the IBM DataPower Network Device Management (NDM) STIG and is required to be used for each deployment of the IBM DataPower Gateway.
- IPv6 Border or Gateway Router
- Specialized Security-Limited Functionality (SSLF)
DoD Instruction (DoDI) 8500.01 requires that “all IT that receives, processes, stores, displays, or transmits DoD information will be […] configured […] consistent with applicable DoD cybersecurity policies, standards, and architectures” and tasks that Defense Information Systems Agency (DISA) “develops and maintains control correlation identifiers (CCIs), security requirements guides (SRGs), security technical implementation guides (STIGs), and mobile code risk categories and usage guides that implement and are consistent with DoD cybersecurity policies, standards, architectures, security controls, and validation procedures, with the support of the NSA/CSS, using input from stakeholders, and using automation whenever possible.” This document is provided under the authority of DoDI 8500.01.
DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible Authorizing Official. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure. Security guidance is provided for the Department of Defense. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied both at the device hardening level as well as the architectural level due to the fact that some of the settings may not be able to be configured in environments outside the DoD architecture.
Moved to FINAL - 08/29/2017
Updated - 11/01/2017
Update Title 11/6/2017
Updated to FINAL - 12/02/2017
Updated URLs - 6/6/19
NIST checklist record last modified on 06/06/2019