This is an IBM Automation portal for Cloud Management and AIOps 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).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Our security policy does not accept files with permission to write and execute inside the directory "/tmp", as INSTANA creates this type of file in "/tmp/.instana" we have several issues of vulnerability. We verified in the Instana documentation that these files cannot be removed, we also tried to change their permissions but every time the Instana agent is restarted it returns to the original permissions with (read, write and execute) we would like these files to keep only permission to read, even after restarting the Instana agent.
As per the IBM's ITSS for Linux Redhat v7/8 servers is not allowed to use word-writable files and it’s considered as a security deviation (Section IZ.22.214.171.124, "Protecting Resources - non-OSRs"). But, if you can remove the “write for all” from that file that won’t be a deviation (it might not to be really needed to have write access to that jar file for all users). Basically just 777 and 776 permissions are not allowed.
Also you can take a look at the sticky bit configuration for directories with world-writable access - it might be useful:
Do not place IBM confidential, company confidential, or personal information into any field.