National Vulnerability Database

National Vulnerability Database

National Vulnerability
Database

IBM DB2 V10-5 LUW STIG Ver 1, Rel 3 Checklist Details (Checklist Revisions)

Supporting Resources:

Target:

Target CPE Name
IBM DB2 V10-5 for Linux, Unix, and Windows (LUW) cpe:/a:ibm:db2:10.5 (View CVEs)

Checklist Highlights

Checklist Name:
IBM DB2 V10-5 LUW STIG
Checklist ID:
782
Version:
Ver 1, Rel 3
Type:
Compliance
Review Status:
Final
Authority:
Governmental Authority: Defense Information Systems Agency
Original Publication Date:
05/23/2017

Checklist Summary:

The IBM DB2 V10 for Linux, UNIX, and Windows (DB2 LUW) STIG provides the technical security policies, requirements, and implementation details for applying security concepts to DB2 LUW. This guidance is to be used in conjunction with the applicable operating system and network STIGs to provide comprehensive coverage of pertinent vulnerabilities. DB2 is a relational Database Management System (DBMS), together with associated software tools, some of which come bundled with the DBMS, and some as separate products. The language used for data definition, data manipulation, security management, etc., is Structured Query Language (SQL). DB2 extends this declarative language with SQL PL, which provides the full power of a programming language within the database itself. Programs written in SQL PL are known as stored procedures. Applications communicate with DB2 by sending it SQL or SQL PL commands, usually known as queries, which typically are invocations of stored procedures. Applications can be written in any language capable of handling DB2’s interface conventions. Applications may run on the same server as the DBMS, but typically—and especially in the DoD—will run on dedicated web servers or client machines.

Checklist Role:

  • Database Management System

Known Issues:

Not provided.

Target Audience:

Not provided.

Target Operational Environment:

  • Managed
  • Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

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.

Comments/Warnings/Miscellaneous:

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.

Disclaimer:

Not provided.

Product Support:

Not provided.

Point of Contact:

disa.stig_spt@mail.mil

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

Updated URL to reflect change to the DISA website - http --> https
updated to v1,r2 - 02/16/2018
Updated to FINAL - 3/18/2018
Updated to Ver 1, Rel 3- 10/25/18
Updated to FINAL - 11/26/18
Updated URLs - 6/6/19

Dependency/Requirements:

URL Description

References:

Reference URL Description
https://dl.dod.cyber.mil/wp-content/uploads/stigs/pdf/U_IBM_DB2_V10-5_LUW_V1R1_STIG_Release_Memo.pdf IBM DB2 V10-5 LUW STIG Ver 1 Release Memo

NIST checklist record last modified on 06/06/2019