Cloud Platform

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

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 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 portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on May 1, 2019

Implement a suitable mechanism for rotation of encryption keys in UrbanCode Deploy.

We currently implement UrbanCode Deploy across an estate of around 10,000+ agents. As part of this implementation, we rely heavily on the 'Secure Properties' feature, which uses an AES encryption key.
In the event of a breach or exposure of this key, there is no mechanism in the product to replace this key whilst decrypting and re-encrypting the existing values with a new key.
It is possible to replace the key, but in doing so only newly-encrypted values will use this new key, meaning the old key would have to be retained to access the existing values.

Use Case
In the event of a breach or exposure of the existing encryption key, there is no easy mechanism for entirely replacing the encryption key and the values it encrypts. This presents a security concern as a potential attacker would still be able to decrypt previously encrypted values despite a change of keys. The old key would also have to be retained in order for the system itself to decrypt those values. The only alternative is to identify all encrypted values and reset them manually, which given the scale of our implementation is infeasible and would represent a significant resourcing overhead.
RFE ID 132572
RFE URL
RFE Product UrbanCode Deploy
Idea Priority High
  • Guest
    Apr 16, 2021

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Mar 4, 2021

    We have evaluated this request and determined that it cannot be implemented at this time because feasability is low and there is high risk of perfromance issues. However we will keep this as an evfuture enhancement.

  • Guest
    Jan 25, 2021

    UCD Dev team will investigate this. UCD mgmt will communicate an update in Q1 or earlier.