STIGQter STIGQter: STIG Summary: IBM DB2 V10.5 LUW Security Technical Implementation Guide Version: 1 Release: 4 Benchmark Date: 25 Oct 2019: DB2 must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

DISA Rule

SV-89117r2_rule

Vulnerability Number

V-74443

Group Title

SRG-APP-000091-DB-000325

Rule Version

DB2X-00-000900

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Define an audit policy using the CREATE AUDIT POLICY SQL statement:

DB2> CREATE AUDIT POLICY <audit policy name> 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 <audit policy name>
Or
DB2> AUDIT TABLE <table name> USING POLICY <audit policy name>

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

Check Contents

To monitor who/what is reading the privilege/permission/role information from catalog tables a minimum audit set of CONTEXT and EXECUTE (with data) categories on the following catalog tables are required:

SYSIBM.SYSINDEXAUTH
SYSIBM.SYSPLANAUTH
SYSIBM.SYSPASSTHRUAUTH
SYSIBM.SYSROUTINEAUTH
SYSIBM.SYSSCHEMAAUTH
SYSIBM.SYSSECURITYLABELACCESS
SYSIBM.SYSSECURITYPOLICYEXEMPTIONS
SYSIBM.SYSSEQUENCEAUTH
SYSIBM.SYSSURROGATEAUTHIDS
SYSIBM.SYSTABAUTH
SYSIBM.SYSTBSPACEAUTH
SYSIBM.SYSXSROBJECTAUTH
SYSIBM.SYSCOLAUTH
SYSIBM.SYSLIBRARYAUTH
SYSIBM.SYSMODULEAUTH
SYSIBM.SYSROLEAUTH
SYSIBM.SYSVARIABLEAUTH
SYSIBM.SYSWORKLOADAUTH
SYSIBM.SYSDBAUTH
SYSIBM.SYSUSERAUTH

Run the following SQL statement to ensure that an audit policy is defined upon the above catalog tables and/or the database:

DB2> SELECT AUDITPOLICYNAME, OBJECTSCHEMA, OBJECTNAME, OBJECTTYPE
FROM SYSCAT.AUDITUSE WHERE OBJECTTYPE IN ('T',' ')

If no rows are returned, this is a finding.

If a row with the OBJECTTYPE of ' ' (Database; value is a blank) exists in the output, it is a database level policy.

If a row with OBJECTTYPE of 'T' exists in the output, it is a table level policy.

For each audit policy returned in the statement above, run the following SQL statement to confirm that the CONTEXT and EXECUTE categories are part of that policy:

DB2> SELECT AUDITPOLICYNAME, CONTEXTSTATUS, EXECUTESTATUS, ERRORTYPE AS ERRORTYPE
FROM SYSCAT.AUDITPOLICIES

If the values for CONTEXTSTATUS and EXECUTESTATUS in the database audit policy are not 'F' (Failure) or 'B' (Both) or ERRORTYPE is not 'A' (Audit), this is a finding.

If a database policy does not exist or does not cover CONTEXTSTATUS or EXECUTESTATUS then check if the appropriate policies are defined for all the required tables listed above.

If audit policies for the required tables do not have the values for the CONTEXTSTATUS and EXECUTESTATUS columns set to 'F' (Failure) or 'B' (Both) or ERRORTYPE is not 'A' (Audit), this is a finding.

Vulnerability Number

V-74443

Documentable

False

Rule Version

DB2X-00-000900

Severity Override Guidance

To monitor who/what is reading the privilege/permission/role information from catalog tables a minimum audit set of CONTEXT and EXECUTE (with data) categories on the following catalog tables are required:

SYSIBM.SYSINDEXAUTH
SYSIBM.SYSPLANAUTH
SYSIBM.SYSPASSTHRUAUTH
SYSIBM.SYSROUTINEAUTH
SYSIBM.SYSSCHEMAAUTH
SYSIBM.SYSSECURITYLABELACCESS
SYSIBM.SYSSECURITYPOLICYEXEMPTIONS
SYSIBM.SYSSEQUENCEAUTH
SYSIBM.SYSSURROGATEAUTHIDS
SYSIBM.SYSTABAUTH
SYSIBM.SYSTBSPACEAUTH
SYSIBM.SYSXSROBJECTAUTH
SYSIBM.SYSCOLAUTH
SYSIBM.SYSLIBRARYAUTH
SYSIBM.SYSMODULEAUTH
SYSIBM.SYSROLEAUTH
SYSIBM.SYSVARIABLEAUTH
SYSIBM.SYSWORKLOADAUTH
SYSIBM.SYSDBAUTH
SYSIBM.SYSUSERAUTH

Run the following SQL statement to ensure that an audit policy is defined upon the above catalog tables and/or the database:

DB2> SELECT AUDITPOLICYNAME, OBJECTSCHEMA, OBJECTNAME, OBJECTTYPE
FROM SYSCAT.AUDITUSE WHERE OBJECTTYPE IN ('T',' ')

If no rows are returned, this is a finding.

If a row with the OBJECTTYPE of ' ' (Database; value is a blank) exists in the output, it is a database level policy.

If a row with OBJECTTYPE of 'T' exists in the output, it is a table level policy.

For each audit policy returned in the statement above, run the following SQL statement to confirm that the CONTEXT and EXECUTE categories are part of that policy:

DB2> SELECT AUDITPOLICYNAME, CONTEXTSTATUS, EXECUTESTATUS, ERRORTYPE AS ERRORTYPE
FROM SYSCAT.AUDITPOLICIES

If the values for CONTEXTSTATUS and EXECUTESTATUS in the database audit policy are not 'F' (Failure) or 'B' (Both) or ERRORTYPE is not 'A' (Audit), this is a finding.

If a database policy does not exist or does not cover CONTEXTSTATUS or EXECUTESTATUS then check if the appropriate policies are defined for all the required tables listed above.

If audit policies for the required tables do not have the values for the CONTEXTSTATUS and EXECUTESTATUS columns set to 'F' (Failure) or 'B' (Both) or ERRORTYPE is not 'A' (Audit), this is a finding.

Check Content Reference

M

Target Key

3161

Comments