DB2X-00-000800 - DB2 must generate audit records when privileges/permissions are retrieved - table SYSIBM.SYSSEQUENCEAUTH

Information

Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically make such information available through views or functions.

This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.

Solution

Define the audit policy using the CREATE AUDIT POLICY SQL statement:
DB2> CREATE AUDIT POLICY CATALOGAUDIT CATEGORIES CONTEXT STATUS BOTH, EXECUTE 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, apply the correct audit policy to either the database as a whole or to the specific catalog tables using one of these two statements:
DB2> AUDIT DATABASE USING POLICY CATALOGAUDIT
Or
DB2> AUDIT TABLE <table name> USING POLICY CATALOGAUDIT

Note: The Database level policy in the Check category, covered in SRG-DB2X-00-000600, generates audit events of successful/unsuccessful read attempts on views based on these catalog tables.

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-213676r879561_rule, STIG-ID|DB2X-00-000800, STIG-Legacy|SV-89115, STIG-Legacy|V-74441, Vuln-ID|V-213676

Plugin: IBM_DB2DB

Control ID: 0f35d1773c68f682cb9f15443d2c3de04be3566c9ae4ec868923c6f87e520879