IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

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,
1. Post an idea
2. Upvote ideas that matter most to you
3. 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 notifications 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.

Provide control over who can use the SNODEID parameter

This idea was previously raised for CDz CONDIRECTZ-I-8, however, it was informed by CDz L3 that the enhancement in CDz will not be able to work on remote Distributed CD nodes. Therefore, this request is raised for similar function on distributed platforms. Details of the requirement is a below:


With SPOE, the SNODEID presents a security vulnerability. The SNODEID is hard-coded in the process in clear text. Anyone authorized to use CDZ and able to read the file where the SNODEID is coded, typically in the process library, can create and submit their own process and have access on the remote node granted to the SNODEID under SPOE. Knowing the SNODEID a malicious actor could:

  • Retrieve the same production data that was sent by the local node to the remote node.

  • Retrieve the same production data that was or will be sent by the remote node to the local node.

  • Send bogus data from the local node to a production file on the remote node.

To mitigate this risk, we would like to have the capability to limit the use of the SNODEID by the user ID (ACID) submitting the process. A given ACID would need to be permissioned to use a particular SNODEID for a particular remote node. If the ACID were not correctly permissioned, then the process submit should fail. Ideally, the management of ACID permissions to use SNODEID's would be handled through the ESM (enterprise security manager) allowing proper separation of responsibilities between CD administrators and engineers and security administrators.

  • Guest
  • Jul 12 2021
  • Planned for future release
What is your industry? Financial Markets
How will this idea be used?

If this idea is implemented we will restrict the use of most SNODEIDs to the ACIDs used by the production job scheduler. This will prevent unauthorized use of SNODEIDs as explained in the idea description.

  • Admin
    Chris Sanders commented
    31 Aug 01:02pm

    Thank you for opening this enhancement request with us. I have reviewed it with my team and we believe it would be worthwhile to offer more granular control over who can use the SNODEID parameter on distributed C:D systems. I will accept this request and we'll look to add it to the roadmap moving forward.

    Sincerely,

    Chris Sanders

    Connect:Express Product Manager

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.