Detections
Analytics

DB2X-00-012200 - DB2 must generate audit records for all direct access to the database(s)

Information

In this context, direct access is any query, command, or call to the DBMS that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all activity from administrative and non-standard sources.

Solution

Run the following command to define an audit policy with the needed subset using the CREATE AUDIT POLICY SQL statement:
DB2> CREATE AUDIT POLICY <DB audit policy name>
 CATEGORIES VALIDATE STATUS BOTH, CONTEXT STATUS BOTH
 ERROR TYPE AUDIT

To modify an existing audit policy, replace 'CREATE' with 'ALTER' in the preceding statement. Only the categories explicitly named in the statement will be affected. In this case, the changes take effect immediately.

If CREATE was used above, run the following command to apply the policy created above to the database:
DB2> AUDIT DATABASE USING POLICY <DB audit policy name>

See Also

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

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-12c., CAT|II, CCI|CCI-000172, Rule-ID|SV-213761r879879_rule, STIG-ID|DB2X-00-012200, STIG-Legacy|SV-89251, STIG-Legacy|V-74577, Vuln-ID|V-213761

Plugin: IBM_DB2DB

Control ID: ad55fc3f6a08f3c2610ae86e6e8b00c5bb2ffe323383a67ec63a6d543f2f6df6