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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Let a change of a SYS*_GROUP in the dbm cfg be reflected in the db2audit secmaint.del-file next to/instead of in db2diag.log
For security monitoring purposes every 30 minutes our production db2audit-files are archived, extracted and uploaded to a special security server for analysis purposes. However very important information is missing: when changing a SYS*_GROUP, the change from what to what it exactly has been changed will not be registrered in one of the db2audit-files (it it can be found in the db2diag.log however). Instead some rather cryptical non informative information is registered like (ai2gijui is the db2-instance btw): "2015-12-11-188.8.131.525652","SECMAINT","UPDATE_DBM_CFG",0,0,""," ai2gijui","AI2GIJUI",0,0,"*LOCAL_APPLICATION"," db2flacc",,,,,,,,,,,,,,,,,,,,,,,,, We would like to see the exact change also (or only) be reflected in the db2audit-files, the place where imho it belongs to be in the first place, so we have a complete overview of security changes on a DB2-instance level and abuse/hacking can be noticed sooner and easier.
Do not place IBM confidential, company confidential, or personal information into any field.