DB2X-00-000500 - DB2 must protect against a user falsely repudiating having performed organization-defined actions - table policies

Information

Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message.

Non-repudiation protects against later claims by a user of not having created, modified, or deleted a particular data item or collection of data in the database.

In designing a database, the organization must define the types of data and the user actions that must be protected from repudiation. The implementation must then include building audit features into the application data tables, and configuring the DBMS' audit tools to capture the necessary audit trail. Design and implementation also must ensure that applications pass individual user identification to the DBMS, even where the application connects to the DBMS with a standard, group account.

Solution

Define the audit policy using the following Create Audit Policy SQL statement:
DB2> CREATE AUDIT POLICY <audit policy name>
CATEGORIES CONTEXT STATUS BOTH, EXECUTE STATUS BOTH
ERROR TYPE AUDIT

Apply such a policy to either the database as a whole or to the specific application tables using one of these two statements:
DB2> AUDIT DATABASE USING POLICY <audit policy name>
Or
DB2> AUDIT TABLE <table name> USING POLICY <audit policy name>

Note : While DB2 does provide basic audit capabilities, IBM highly recommends investing in and using a dedicated enterprise audit tool such as the IBM Security Guardium Data Activity Monitor in order to provide a comprehensive audit solution.

See Also

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

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-12, CAT|II, CCI|CCI-000166, Rule-ID|SV-89109r1_rule, STIG-ID|DB2X-00-000500, Vuln-ID|V-74435

Plugin: IBM_DB2DB

Control ID: 6bd09fd10f883a4dce07dda4aacaf8dc60e0c17bbb1f28b428d8776f962efbcc