STIGhubSTIGhub
STIGsRMF ControlsCompare

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
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM DB2 V10.5 LUW Security Technical Implementation Guide

V-213719

CAT II (Medium)

DB2 must utilize centralized management of the content captured in audit records generated by all components of DB2.

Rule ID

SV-213719r879729_rule

STIG

IBM DB2 V10.5 LUW Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-001844

Discussion

Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.

Check Content

Run the following command to find the location of the audit data and archive data directories: 

     $db2audit describe 

If this filesystem location is not compatible with the centralized  audit management system, this is a finding.

If DB2 is not used in conjunction with a centralized audit management system, this is a finding.

Fix Text

Run the following command to set the audit data directory and archive data directory to the location which is compatible with the organization's centralized system:

     $db2audit configure datapath <AUDIT DATA DIRECTORY > archivepath <AUDIT ARCHIVE DIRECTORY>

Note: See the following knowledgebase page for information regarding extracting Audit logs to syslog for any file system other than Windows: 
http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0002072.html

DB2 does not directly support syslog on windows.  Devise an alternate method of log capture.