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...

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 i...

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...

When SOC assigns tasks with clear instructions to as in what customer end Security officers should perform. They only look into the task to know the Incident related information and action to be taken.And when they have huge list of tasks assigned...

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.

Wiki Articles should be made available for download in a PDF or other format, and available for Export & Import into other organizations.

The request here is to make Tasks set as "Mandatory", required for Incident closure. Currently, Tasks that are Mandatory only dictate Phase changes. In order to enforce Task completion a script must a created or a Task must be added as part of ...

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/arch...

Add the ability to Disable (rather than delete) Notifications and Rules much like how we can disable Tasks. Rules and Notifications are complex, based on sometimes multiple Condition and Actions which take time and effort to construct. Rules and N...

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 o...