Db2 for z/OS
TMA-DB2-ZOS-2.2.10
Ensure that access to SYSIBM.SYSINDEXES is restricted
Description
The SYSIBM.SYSINDEXES table records one row for every index. PUBLIC should be restricted from accessing this table. This table contains all index information and can be used as an attack vector. Exposing index information can enable attackers to gain access to your organization's data.
How it is checked
Audit method: Manual review
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 = 'SYSINDEXES' 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.SYSINDEXES table in the MDSNTB class. Examine the universal access (UACC) and user ... (full steps: CIS section 2.2.10)
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.SYSINDEXES 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.10 Ensure that access to SYSIBM.SYSINDEXES is restricted