This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Dear Ryszard, Thank you for submitting this enhancement request. The Db2 for z/OS development team reviewed it and will not be considering this idea. Please be aware that the authorization checks performed between Db2 native and RACF exit were never intended to be identical for all operations, as both products have different security model. Customers choose the authorization control that works better for them.
The following ideas were considered for this Aha idea:
Honor implicit ownership for all authorization checks:
With RACF exit authorization, the access due to implicit ownership is currently supported for some privileges. This Aha idea is to honor implicit ownership for all authorization checks. The implicit ownership check is done in the access control authorization exit. Since RACF is not involved, the access due to implicit ownership check cannot be audited in RACF. The industry best practice is to have audit trail for all access checks in the audited product. Hence, it is not consistent with Db2 product direction to support all implicit ownership checks for RACF authorization.
ICH408I message for EXPLAIN statement when the operation is successful:
To issue the SQL EXPLAIN statement, EXPLAIN is the least privilege required. Db2 first checks for EXPLAIN privilege and if the user does not have EXPLAIN privilege, Db2 then checks for the statement-level privilege. The EXPLAIN statement can be successful if the user has statement-level privilege. If EXPLAIN privilege check fails, ICH408I message may be issued depending on the RACF configuration. If IFCID 140 trace is turned ON to audit failures, an audit record is written for EXPLAIN authorization failure. Hence, it is consistent with Db2 native behavior of how failures are audited. It is high cost to suppress the ICH408I message for the EXPLAIN check and re-drive the authorization checks for audit purposes.
ICH408I message for BIND process when the operation is successful:
During BIND process, Db2 can check multiple IDs as documented. Db2 first checks the owner for the required privileges. If the owner does not have the privileges, then the binder is checked for administrative authority. The bind process is successful if the binder has administrative authority. Depending on the RACF configuration, ICH408I message may be issued if the owner does not have the least privileges required for bind. If IFCID 140 trace is turned ON to audit failures, an audit record is written for this owner authorization failure. Hence, it is consistent with Db2 native behavior of how failures are audited. Since two different IDs are checked for authorization in this scenario, the failure messages cannot be suppressed.
We appreciate your input to the Db2 for z/OS development team. And we hope that you will continue to submit enhancement suggestions for improvements as customer feedback is a key component to shaping the future direction of Db2 for z/OS.
Sincerely,
Db2 for z/OS Team
One of the worst inconsistencies today is where false ICH408I messages are given but the actual operation completes successfully .... How to explain this to an auditor I do not know.