This portal is to open public enhancement requests against IBM System Storage products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
When the change-command to change the command list itself has to be approved (after set commandapproval) security is at the same level as it is now. An attacker thus will not be able to change the list nor execute the commands protected.
This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.
i think it is not useful if the list of commands for the command approval is changeable, because from my point of view this represents a security gap. a potential attacker could intentionally remove the commands he wants to use for destruction from the command approval.
Even though this is primarily not a security feature, it should be possible to limit/lock down who can change the command approval configuration and add/remove approvers to enhance security. As of now any Admin with SYSTEM level auth can change the command approval configuration and change approvers.
In many organisations Admins with SYSTEM level authority is the norm, thus making it possible to modify this feature.
A new per admin attribute or perhaps a new SECURITY level auth for administrators could perhaps be implemented to make it possible to secure this feature.