Details

Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions.

Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.

Solution

Run the following command to set the auditing at the instance level:

$db2audit configure scope sysadmin status both error type audit

Run the following command to set the auditing at the database level:
DB2> CREATE AUDIT POLICY CATEGORIES SYSADMIN STATUS BOTH, CONTEXT STATUS BOTH ERROR TYPE AUDIT

Run the following command if the auditing policy exists but does not include the sysadmin category:
DB2> ALTER AUDIT POLICY SYSADMIN STATUS BOTH, CONTEXT STATUS BOTH ERROR TYPE AUDIT

If CREATE was used above, apply the policy created above to the database:
DB2> AUDIT DATABASE USING POLICY

Note: See the following page for knowledgebase information regarding the ALTER AUDIT POLICY:
http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.sql.ref.doc/doc/r0050608.html?lang=en

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: Configuration Management.This control applies to the following type of system Windows.

References

• 800-53|CM-5(1)
• CAT|II
• CCI|CCI-001814
• Rule-ID|SV-89267r1_rule
• STIG-ID|DB2X-00-008200
• Vuln-ID|V-74593

Source

• Tenable.com/audits