TMA-DB2-ZOS-2.1.7
Secure object ownership by using Db2 roles
Descripción
Db2 roles can be used to control access to enterprise objects in a way that parallels the structure of the enterprise. It is recommended that you use roles to separate object ownership from individual users and manage context-specific access outside of user privileges. Assigning object ownership to a role prevents authorization IDs from obtaining implicit ownership privileges.
Cómo se verifica
Método de auditoría: Revisión manual
Esta recomendación no se puede verificar automáticamente. Un escaneo la lista con estas instrucciones cuando se pasa --include-manual.
1. Issue the following SQL statement to verify that roles are defined and associated with trusted contexts. SELECT NAME FROM SYSIBM.SYSROLES; SELECT NAME, CONTEXTID, SYSTEMAUTHID, DEFAULTROLE, OBJECTOWNERTYPE, ENABLED, ALLOWPUBLIC, AUTHENTICATEPUBLIC FROM SYSIBM.SYSCONTEXT; SELECT CONTEXTID, AUTHID, AUTHENTICATE, ROLE FROM SYSIBM.SYSCONTEXTAUTHIDS; 2. Review the roles and trusted contexts definition.
Cómo se corrige
Método de corrección: Guía o parche de infraestructura
1. Create roles and trusted contexts and assign roles as object owners based on the rules of your organization. 2. Issue the SQL TRANSFER OWNERSHIP statement to transfer the ownership of existing database and system objects to roles.
Propiedades
- Sistemas operativos
- Cualquiera
- Etiquetas
- db2-zospermissions
- Referencia
- CIS IBM Db2 13 for z/OS Benchmark v1.0.0 - 2.1.7 Secure object ownership by using Db2 roles