STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 7 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

IBM DB2 V10.5 LUW Security Technical Implementation Guide

Version

V2R1

Release Date

Jun 11, 2023

SCAP Benchmark ID

IBM_DB2_V10-5_LUW_STIG

Total Checks

93

Tags

other
CAT I: 6CAT II: 87CAT III: 0

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (93)

V-213670MEDIUMDB2 must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.V-213671MEDIUMDB2 must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-213672MEDIUMDB2 must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-213673MEDIUMDB2 must protect against a user falsely repudiating having performed organization-defined actions.V-213674MEDIUMDB2 must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.V-213675MEDIUMDB2 must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.V-213676MEDIUMDB2 must generate audit records when privileges/permissions are retrieved.V-213677MEDIUMDB2 must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.V-213678MEDIUMDB2 must initiate session auditing upon startup.V-213679MEDIUMDB2 must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.V-213680MEDIUMDB2 must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.V-213681MEDIUMUnless it has been determined that availability is paramount, DB2 must, upon audit failure, cease all auditable activity.V-213682MEDIUMThe audit information produced by DB2 must be protected from unauthorized read access.V-213683MEDIUMThe audit information produced by DB2 must be protected from unauthorized modification.V-213684MEDIUMThe audit information produced by DB2 must be protected from unauthorized deletion.V-213685MEDIUMDB2 must protect its audit features from unauthorized access.V-213686MEDIUMDB2 must protect its audit configuration from unauthorized modification.V-213687MEDIUMDB2 must protect its audit features from unauthorized removal.V-213688MEDIUMDB2 must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to DB2.V-213689MEDIUMThe OS must limit privileges to change the DB2 software resident within software libraries (including privileged programs).V-213690MEDIUMThe DB2 software installation account must be restricted to authorized users.V-213691MEDIUMDatabase software, including DBMS configuration files, must be stored in dedicated directories, separate from the host OS and other applications.V-213692MEDIUMDatabase objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to DB2, etc.) must be owned by database/DBMS principals authorized for ownership.V-213693MEDIUMThe role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to DB2, etc.) must be restricted to authorized users.V-213694MEDIUMDefault demonstration and sample databases, database objects, and applications must be removed.V-213695MEDIUMUnused database components, DBMS software, and database objects must be removed.V-213696MEDIUMUnused database components which are integrated in DB2 and cannot be uninstalled must be disabled.V-213697MEDIUMAccess to external executables must be disabled or restricted.V-213698MEDIUMDB2 must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.V-213699MEDIUMIf passwords are used for authentication, DB2 must transmit only encrypted representations of passwords.V-213700HIGHApplications using the database must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.V-213701HIGHWhen using command-line tools such as db2, users must use a Connect method that does not expose the password.V-213702HIGHDB2 must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.V-213703MEDIUMDB2 must separate user functionality (including user interface services) from database management functionality.V-213704MEDIUMDB2 must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-213705MEDIUMIn the event of a system failure, DB2 must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.V-213706MEDIUMDB2 must protect the confidentiality and integrity of all information at rest.V-213707MEDIUMDB2 must isolate security functions from non-security functions.V-213708MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-213709MEDIUMAccess to database files must be limited to relevant processes and to authorized, administrative users.V-213710MEDIUMDB2 must check the validity of all data inputs except those specifically identified by the organization.V-213711MEDIUMDB2 and associated applications must reserve the use of dynamic code execution for situations that require it.V-213712MEDIUMDB2 and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.V-213713MEDIUMDB2 must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.V-213714MEDIUMDB2 must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.V-213715MEDIUMDB2 must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.V-213716MEDIUMWhen supporting applications that require security labeling of data, DB2 must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-213717MEDIUMWhen supporting applications that require security labeling of data, DB2 must associate organization-defined types of security labels having organization-defined security label values with information in process.V-213718HIGHDB2 must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.V-213719MEDIUMDB2 must utilize centralized management of the content captured in audit records generated by all components of DB2.V-213720MEDIUMDB2 must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.V-213721MEDIUMDB2 must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.V-213722MEDIUMDB2 must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.V-213723MEDIUMDB2 must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-213724MEDIUMDB2 and the operating system must enforce access restrictions associated with changes to the configuration of DB2 or database(s).V-213725MEDIUMDB2 must produce audit records of its enforcement of access restrictions associated with changes to the configuration of DB2 or database(s).V-213726MEDIUMDB2 must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.V-213728MEDIUMDB2 must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.V-213729MEDIUMDB2 must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.V-213730MEDIUMDB2 must implement and/or support cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.V-213731MEDIUMDB2 must maintain the confidentiality and integrity of information during preparation for transmission.V-213732MEDIUMDB2 must maintain the confidentiality and integrity of information during reception.V-213733MEDIUMWhen invalid inputs are received, DB2 must behave in a predictable and documented manner that reflects organizational and system objectives.V-213734HIGHSecurity-relevant software updates to DB2 must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).V-213735MEDIUMDB2 must generate audit records when security objects are accessed.V-213736MEDIUMDB2 must generate audit records when unsuccessful attempts to access security objects occur.V-213737MEDIUMDB2 must generate audit records when categorized information (e.g., classification levels/security levels) are accessed.V-213738MEDIUMDB2 must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.V-213739MEDIUMDB2 must generate audit records when privileges/permissions are added.V-213740MEDIUMDB2 must generate audit records when unsuccessful attempts to add privileges/permissions occur.V-213741MEDIUMDB2 must generate audit records when privileges/permissions are modified.V-213742MEDIUMDB2 must generate audit records when unsuccessful attempts to modify privileges/permissions occur.V-213743MEDIUMDB2 must generate audit records when security objects are modified.V-213744MEDIUMDB2 must generate audit records when unsuccessful attempts to modify security objects occur.V-213745MEDIUMDB2 must generate audit records when categorized information (e.g., classification levels/security levels) is modified.V-213746MEDIUMDB2 must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.V-213747MEDIUMDB2 must generate audit records when privileges/permissions are deleted.V-213748MEDIUMDB2 must generate audit records when unsuccessful attempts to delete privileges/permissions occur.V-213749MEDIUMDB2 must generate audit records when security objects are deleted.V-213750MEDIUMDB2 must generate audit records when unsuccessful attempts to delete security objects occur.V-213751MEDIUMDB2 must generate audit records when categorized information (e.g., classification levels/security levels) is deleted.V-213752MEDIUMDB2 must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.V-213753MEDIUMDB2 must generate audit records when successful logons or connections occur.V-213754MEDIUMDB2 must generate audit records when unsuccessful logons or connection attempts occur.V-213755MEDIUMDB2 must generate audit records for all privileged activities or other system-level access.V-213756MEDIUMDB2 must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.V-213757MEDIUMDB2 must generate audit records showing starting and ending time for user access to the database(s).V-213758MEDIUMDB2 must generate audit records when concurrent logons/connections by the same user from different workstations occur.V-213759MEDIUMDB2 must generate audit records when successful accesses to objects occur.V-213760MEDIUMDB2 must generate audit records when unsuccessful accesses to objects occur.V-213761MEDIUMDB2 must generate audit records for all direct access to the database(s).V-213762MEDIUMDB2 must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.V-253507HIGHDB2 must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements.