IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Provide control over who can use the SNODEID parameter

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 1 2018
  • Uncommitted Candidate
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.

What is your industry? Financial Markets
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 07, 2018 12:19

    I vote yes

  • Admin
    Chris Sanders commented
    August 14, 2018 13:15

    Thank you for opening this enhancement request with IBM.  I have reviewed it with my developers and we are all in agreement that this would be a worthwhile enhancement to C:D for z/OS.  We have accepted this as an Uncommitted Candidate and will look to add it to the offering roadmap moving forward.



    Chris Sanders

    Connect:Direct Offering Manager