STIGQter STIGQter: STIG Summary:

IBM DB2 V10.5 LUW Security Technical Implementation Guide

Version: 2

Release: 2 Benchmark Date: 01 Jul 2026

CheckedNameTitle
☐SV-213670r960735_ruleDB2 must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.
☐SV-213671r1043176_ruleDB2 must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.
☐SV-213672r1137654_ruleDB2 must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
☐SV-213673r960864_ruleDB2 must protect against a user falsely repudiating having performed organization-defined actions.
☐SV-213674r960879_ruleDB2 must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.
☐SV-213675r960882_ruleDB2 must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
☐SV-213676r960885_ruleDB2 must generate audit records when privileges/permissions are retrieved.
☐SV-213677r960885_ruleDB2 must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
☐SV-213678r960888_ruleDB2 must initiate session auditing upon startup.
☐SV-213679r960903_ruleDB2 must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
☐SV-213680r960909_ruleDB2 must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
☐SV-213681r1043188_ruleUnless it has been determined that availability is paramount, DB2 must, upon audit failure, cease all auditable activity.
☐SV-213682r960930_ruleThe audit information produced by DB2 must be protected from unauthorized read access.
☐SV-213683r960933_ruleThe audit information produced by DB2 must be protected from unauthorized modification.
☐SV-213684r960936_ruleThe audit information produced by DB2 must be protected from unauthorized deletion.
☐SV-213685r960939_ruleDB2 must protect its audit features from unauthorized access.
☐SV-213686r960942_ruleDB2 must protect its audit configuration from unauthorized modification.
☐SV-213687r960945_ruleDB2 must protect its audit features from unauthorized removal.
☐SV-213688r960960_ruleDB2 must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to DB2.
☐SV-213689r960960_ruleThe OS must limit privileges to change the DB2 software resident within software libraries (including privileged programs).
☐SV-213690r960960_ruleThe DB2 software installation account must be restricted to authorized users.
☐SV-213691r960960_ruleDatabase software, including DBMS configuration files, must be stored in dedicated directories, separate from the host OS and other applications.
☐SV-213692r960960_ruleDatabase 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.
☐SV-213693r960960_ruleThe 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.
☐SV-213694r960963_ruleDefault demonstration and sample databases, database objects, and applications must be removed.
☐SV-213695r960963_ruleUnused database components, DBMS software, and database objects must be removed.
☐SV-213696r960963_ruleUnused database components which are integrated in DB2 and cannot be uninstalled must be disabled.
☐SV-213697r960963_ruleAccess to external executables must be disabled or restricted.
☐SV-213698r1043177_ruleDB2 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.
☐SV-213699r961029_ruleIf passwords are used for authentication, DB2 must transmit only encrypted representations of passwords.
☐SV-213700r961047_ruleApplications using the database must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
☐SV-213701r961047_ruleWhen using command-line tools such as db2, users must use a Connect method that does not expose the password.
☐SV-213702r961050_ruleDB2 must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
☐SV-213703r1137655_ruleDB2 must separate user functionality (including user interface services) from database management functionality.
☐SV-213704r1043181_ruleDB2 must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.
☐SV-213705r961125_ruleIn 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.
☐SV-213706r961128_ruleDB2 must protect the confidentiality and integrity of all information at rest.
☐SV-213707r961131_ruleDB2 must isolate security functions from non-security functions.
☐SV-213708r1137656_ruleDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.
☐SV-213709r1137658_ruleAccess to database files must be limited to relevant processes and to authorized, administrative users.
☐SV-213710r961158_ruleDB2 must check the validity of all data inputs except those specifically identified by the organization.
☐SV-213711r961158_ruleDB2 and associated applications must reserve the use of dynamic code execution for situations that require it.
☐SV-213712r961158_ruleDB2 and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.
☐SV-213713r961167_ruleDB2 must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
☐SV-213714r961170_ruleDB2 must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.
☐SV-213715r1043182_ruleDB2 must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.
☐SV-213716r1138540_ruleWhen 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.
☐SV-213717r1138541_ruleWhen 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.
☐SV-213718r961353_ruleDB2 must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
☐SV-213719r981952_ruleDB2 must utilize centralized management of the content captured in audit records generated by all components of DB2.
☐SV-213720r961392_ruleDB2 must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
☐SV-213721r961398_ruleDB2 must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.
☐SV-213722r961401_ruleDB2 must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.
☐SV-213723r981956_ruleDB2 must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.
☐SV-213724r961461_ruleDB2 and the operating system must enforce access restrictions associated with changes to the configuration of DB2 or database(s).
☐SV-213725r981958_ruleDB2 must produce audit records of its enforcement of access restrictions associated with changes to the configuration of DB2 or database(s).
☐SV-213726r961470_ruleDB2 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.
☐SV-213728r1193220_ruleDB2 must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.
☐SV-213729r1211027_ruleDB2 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.
☐SV-213730r1018553_ruleDB2 must implement and/or support cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.
☐SV-213731r961638_ruleDB2 must maintain the confidentiality and integrity of information during preparation for transmission.
☐SV-213732r961641_ruleDB2 must maintain the confidentiality and integrity of information during reception.
☐SV-213733r961656_ruleWhen invalid inputs are received, DB2 must behave in a predictable and documented manner that reflects organizational and system objectives.
☐SV-213734r1137667_ruleSecurity-relevant software updates to DB2 must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
☐SV-213735r961791_ruleDB2 must generate audit records when security objects are accessed.
☐SV-213736r961791_ruleDB2 must generate audit records when unsuccessful attempts to access security objects occur.
☐SV-213737r961797_ruleDB2 must generate audit records when categorized information (e.g., classification levels/security levels) are accessed.
☐SV-213738r961797_ruleDB2 must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.
☐SV-213739r961800_ruleDB2 must generate audit records when privileges/permissions are added.
☐SV-213740r961800_ruleDB2 must generate audit records when unsuccessful attempts to add privileges/permissions occur.
☐SV-213741r961800_ruleDB2 must generate audit records when privileges/permissions are modified.
☐SV-213742r961800_ruleDB2 must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
☐SV-213743r961803_ruleDB2 must generate audit records when security objects are modified.
☐SV-213744r961803_ruleDB2 must generate audit records when unsuccessful attempts to modify security objects occur.
☐SV-213745r961809_ruleDB2 must generate audit records when categorized information (e.g., classification levels/security levels) is modified.
☐SV-213746r961809_ruleDB2 must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.
☐SV-213747r961812_ruleDB2 must generate audit records when privileges/permissions are deleted.
☐SV-213748r961812_ruleDB2 must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
☐SV-213749r961818_ruleDB2 must generate audit records when security objects are deleted.
☐SV-213750r961818_ruleDB2 must generate audit records when unsuccessful attempts to delete security objects occur.
☐SV-213751r961821_ruleDB2 must generate audit records when categorized information (e.g., classification levels/security levels) is deleted.
☐SV-213752r961821_ruleDB2 must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.
☐SV-213753r961824_ruleDB2 must generate audit records when successful logons or connections occur.
☐SV-213754r961824_ruleDB2 must generate audit records when unsuccessful logons or connection attempts occur.
☐SV-213755r961827_ruleDB2 must generate audit records for all privileged activities or other system-level access.
☐SV-213756r961827_ruleDB2 must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
☐SV-213757r961830_ruleDB2 must generate audit records showing starting and ending time for user access to the database(s).
☐SV-213758r961833_ruleDB2 must generate audit records when concurrent logons/connections by the same user from different workstations occur.
☐SV-213759r961836_ruleDB2 must generate audit records when successful accesses to objects occur.
☐SV-213760r961836_ruleDB2 must generate audit records when unsuccessful accesses to objects occur.
☐SV-213761r961839_ruleDB2 must generate audit records for all direct access to the database(s).
☐SV-213762r961860_ruleDB2 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.
☐SV-253507r1117186_ruleDB2 must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements.