Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Feb 6, 2024

Need Corresponding Release of Vulnerabilities Fixed by Recently Released Patches/Fix Packs

There needs to be planned release(s) of known security vulnerabilities that are addressed in recent patches, i.e. through regular channels (subscribed notifications). That seems to be how they've been released for IBM Sterling products in the past, but the information is a bit scattered over multiple bulletins sent out over time (usually a few weeks after release of the patch) based on subscribed notifications. Recently there was a list of 31 fixed vulnerabilities in fix pack release That's great, and I completely understand that in a fix list not an appropriate place to list what these vulnerabilities are since it's public information, but the information needs to be published up to OpenCVE to correspond with the release of software so their scores are identified and customers of B2Bi/SFG can notify their security teams of what the vulnerabilities are that are addressed. DB2 as an example mostly does a pretty good job of this. Some customer/host sites run regular vulnerability scans, but it seems there isn't a way to reconcile against what vulnerability applications like QUALYS might come up with in their scans of B2Bi across its ports and access points without opening potentially a plethora of cases.

If there are vulnerabilities with a CVSS of 7 or above, I need to address those as high priority (for upgrade). Otherwise my B2Bi clusters/instances sit vulnerable until I find out one way or the other; either I'm hacked because I can't get the information I need even though I AM subscribed or I get lucky and exploits aren't used to harvest information, depending on the score assigned to each vulnerability and ability to exploit it. As we've all seen with the MOVEIt hack that reared its ugly head recently, I wouldn't want to see IBM's reputation suffer because customers couldn't get the vulnerability information and mitigate it with an existing fix pack.

Also I shouldn't be applying patches out of superstition. Informed decision making is always better. Since we manage many servers with IBM Sterling software on them, having this information available is critical to day-to-day operations and helps us prioritize builds and application of patches.

What is your industry? Computer Services
How will this idea be used?

Having this information available at the time of fix pack release enables us to mitigate vulnerabilities faster based on their score. It helps us determine if, for example, we should apply a fix pack or wait to go to next level of product. It's a critical component of our maintenance schedule for software.

  • Guest
    Feb 6, 2024

    these days security vulnerability is no doubt the top priority on every customer's mind. Nobody wants their PROD environment attached by hackers or their names show up on yet another mass data leak news. IBM the s/w vendor should make the security patching mechanism as easy as possible, and as early as possible for every customer and their consultants to plug the holes.