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
Start by posting 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 offering manager 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 a 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.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to email@example.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Missing documentation for security events in the IBM DataPower log and APIConnect.
Current DataPower log documentation is not including good categorization, sequence nor details explaining which log categories and event codes are including potential security issues. Documentation mainly includes plain event code and name without the details.
We are looking for the possibilities to monitor API's against the modern security threats, issues and vulnerabilities which IBM DataPower and APIConnect engines can catch (eg from OWASP API TOP 10 security issue list or defined by API Security Encyclopedia.)
We are looking for the event category and events catching:
API1:2019 Broken Object Level Authorization
API2:2019 Broken User Authentication - authentication and authorization issues,
API4:2019 Lack of Resources & Rate Limiting - overconsumption of the API comparing with the throttling and quota parameters,
API9:2019 Improper Assets Management
API7:2019 Security Misconfiguration - eg once the certificates or any of the security configuration items are misconfigured.
API8:2019 Injection - when data power protection for injection are triggered or other issue in this area is occuring.
API10:2019 Insufficient Logging & Monitoring - occurs when above is not handled well as there is no good documentation explaining how to catch the issues.
Do not place IBM confidential, company confidential, or personal information into any field.