Skip to Main Content
IBM Security Ideas Portal

Shape the future of IBM Security

We invite you to shape the future of IBM, including the product roadmap, by submitting enhancement 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 vote for them if they matter to you,

  1. Post an idea

  2. Vote for 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 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.

Post an Idea

To post a new idea - click on the "Add a new idea" button and where asked select the appropriate category this idea relates to. Provide requested information to allow us to get a better understanding of your request.

"Missing" Security Products?

If you cannot find the IBM Security product you are looking for then it is probably located in the IBM Security Private Ideas Portal. Check that site to open an idea.

Idea visibility

All ideas submitted via this portal are visible to all other portal users, though personal information fields remain hidden. If you would rather have your idea visible to only you and IBM then use the IBM Security Private Ideas Portal instead.

Please note: The purpose of the Ideas Portal is to tap the creativity of the IBM Security community so that we can enhance our products for everyone! If you need to report a defect or get help, please use our normal support channel. Click here to open a support ticket.

Want to see all of your IBM ideas in one place? Find them at



Process design

Showing 85 of 3465

Variable Forms for Playbooks

Having variable Forms based on conditions could make working with Playbooks more versatile and would reduce the amount of similar Playbooks.
9 days ago in QRadar SOAR / Process design 2 Needs more information

Allow Incident Level Attachments on Tasks

Widgets Associated to Task Attachments are available for the Layout of a Task. This does not include any Incident level Attachments, which ensures that while on an Attachments Tab on the Incident itself you will see the entirety of the attachments...
4 months ago in QRadar SOAR / Process design 1 Future consideration
136 VOTE

Allow Fields to be set Mandatory by Condition(s)

I request the ability to set mandatory requirements for Fields using conditions, much like how conditions are are used to trigger Rules. There are a few reasons why I would like to have this ability: We've found out that having any field within th...
over 4 years ago in QRadar SOAR / Process design 7 Future consideration

Role Creation: Playbook Only

There should be the option for a Role that only allows you to create a Playbook, without adding all Administrative & Customization settings. This would be appropriate for those with a role of use case development, rather than administrative ac...
about 1 month ago in QRadar SOAR / Process design 2 Submitted
102 VOTE

Parent/Child incident relationships

Parent” to “Child” relationships. I.e. – We have an incident that occurs and following that incident there are several other incidents that are related to the “Master” (basically all root cause details are the same) IE: Phishing. The incident is ...
about 4 years ago in QRadar SOAR / Process design 11 Future consideration

Step-back in workflow

Currently it is not possible to re-enable under certain conditions a closed task inside the playbook designer. However some playbooks require to ask analyst few questions and depending on his answers to go back to a certain previous step inside th...
over 4 years ago in QRadar SOAR / Automations / Process design 5 Future consideration

Version control of Playbooks / all Resilient content (fields, tasks, scripts, workflows, rules...)

It would be useful for Resilient to provide version control of entire Playbooks, Processes, and it's individual content. To perform this at the Playbook level, it's content will need to be tagged as part of that Playbook. From there a snapshot/arc...
over 4 years ago in QRadar SOAR / Process design 3 Future consideration

Ability to add pre-defined Tasks to an INC

Currently, when adding a New Task to an existing Incident, you must manually fill our all of the task fields. Most of our tasks are already pre-defined. It would be great if we could select on of our pre-defined tasks to add to the Incident.
over 4 years ago in QRadar SOAR / Process design 5 Future consideration

Create Unique Incident Views based on User Group

Updated title to reflect group focus following RFE review. Original Request ============= It would be useful, specifically for Tasks but I assume for other use cases, to have views dependent upon the viewer. For instance, there should be a Conditi...
over 3 years ago in QRadar SOAR / Process design 9 Future consideration

Option to make Closed Incidents read-only

We would like to preserve closed Incidents from alteration as they are often recalled for review and the possibility - however remote - of tampering with them in the closed state should be eliminated. Possibly only an Admin could lift the 'read on...
over 4 years ago in QRadar SOAR / Administration / Process design 3 Future consideration