DB2 must generate audit records when unsuccessful logons or connection attempts occur.
For completeness of forensic analysis, it is necessary to track failed attempts to log on to the DBMS. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured.
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>
To meet these requirements at the VALIDATE, CONTEXT category auditing needs to be implemented at database level.
Run the following SQL statement to ensure that an audit policy is defined upon the database:
DB2> SELECT AUDITPOLICYNAME, AUDITPOLICYID
WHERE OBJECTTYPE IN (' ')
If no rows are returned, this is a finding.
Using the AUDITPOLICYID from above query find the details of audit policy:
DB2> SELECT AUDITPOLICYNAME, CONTEXTSTATUS, VALIDATESTATUS, ERRORTYPE AS ERRORTYPE
WHERE AUDITPOLICYID =
<audit policy ID>
If the values for CONTEXTSTATUS and VALIDATESTATUS are not 'B' (Both) or ERRORTYPE is not 'A' (Audit), this is a finding.