Ensure that access to the catalog tables in the communications database (CDB) is restricted

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

For Db2 internal security users: Issue the following SQL statement to check if PUBLIC has access: SELECT GRANTEE, TCREATOR, TTNAME FROM SYSIBM.SYSTABAUTH WHERE TCREATOR = 'SYSIBM' AND TTNAME IN ('LOCATIONS', 'IPNAMES', 'IPLIST', 'LUNAMES', 'LULIST', 'LUMODES', 'MODESELECT', 'USERNAMES') AND GRANTEE = 'PUBLIC'; Output that contains zero rows is considered a successful finding. Otherwise, PUBLIC has SELECT, INSERT, UPDATE, or DELETE privilege and the remediation steps should be followed. For external security users: Issue the RACF RLIST command to list the ... (full steps: CIS section 2.2.1)

How it is fixed

Fix method: Guidance or infrastructure patch

For Db2 internal security users: Issue the SQL REVOKE statement to revoke access from PUBLIC. For external security users: Issue the RACF RALTER command to update the profiles and change the UACC setting to NONE. Issue the RACF PERMIT command to remove the ID(*) and specify users or groups.