Ensure that access to SYSIBM.SYSOBJROLEDEP is restricted

MediumLevel 1Manual reviewdb2-zos

Description

The SYSIBM.SYSOBJROLEDEP table lists the dependent objects for each role. PUBLIC should be restricted from accessing this table. PUBLIC should not see the dependent objects for roles because doing so can expose those dependent objects to attackers. Exposing dependent objects for roles can enable attackers to gain access to the objects.

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 FROM SYSIBM.SYSTABAUTH WHERE TCREATOR = 'SYSIBM' AND TTNAME = 'SYSOBJROLEDEP' AND GRANTEE = 'PUBLIC'; Output that contains zero rows is considered a successful finding. Otherwise, PUBLIC has SELECT privilege and the remediation steps should be followed. For external security users: Issue the RACF RLIST command to list the profile that controls access to the SYSIBM.SYSOBJROLEDEP table in the MDSNTB class. Examine the universal access (UACC) and ... (full steps: CIS section 2.2.11)

How it is fixed

Fix method: Guidance or infrastructure patch

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

Properties

Operating systems: Any
Tags: db2-zospermissions
Reference: CIS IBM Db2 13 for z/OS Benchmark v1.0.0 - 2.2.11 Ensure that access to SYSIBM.SYSOBJROLEDEP is restricted