Details

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.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

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 archivepath

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.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_IBM_DB2_V10-5_V1R4_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Unix.

References

• 800-53|AU-3(2)
• CAT|II
• CCI|CCI-001844
• Rule-ID|SV-89241r1_rule
• STIG-ID|DB2X-00-007300
• Vuln-ID|V-74567

Source

• Tenable.com/audits