Features and enhancements in IBM Security QRadar SOAR Platform 51.0.6.0

Take action on multiple attachments

You can now take action on multiple attachments, including delete, move from task to incident, and run manual rules and playbooks.

For more information, see Changed in 51.0.6.0 Managing incident and task attachments.

Create your own connectors for low code integration

You can now create your custom connectors and connector functions directly in SOAR, without using OpenAPI 3.x specification files, to build integrations with little or no coding required.

Also, the OAuth 2.0 authentication scheme is now supported.

For more information, see Changed in 51.0.6.0 Connectors and functions.

What's new feature on playbook export and import

When exporting a playbook, you can optionally enter details for the playbook. When importing a playbook, the details entered are available to provide better context about the purpose of the playbook.

For more information, see Changed in 51.0.6.0 Exporting and importing playbooks.

Changes to security and optional package naming

Both SOAR and App Host now use a YYYY-MM-DD-GMT timestamp suffix, rather than a version number. This is to better reflect when they were generated and to indicate they are not version bound to the SOAR and App Host application .run files. Security updates to the SOAR virtual appliance and App Host software might be released between new version releases. You should always apply the latest security updates, regardless of whether you upgrade the SOAR or App Host. This naming change does not indicate any functional or deployment changes.

App Host V1.15.5 updates

App Host V1.15.5.0 is the immediate next new release after App Host V1.13.x and there is no 1.14.x release for IBM Security QRadar SOAR. App Host 1.15.3.x versions upgrade successfully to 1.15.5.0.

App Host containers are updated to use Java 17.0.14.0.

The App Host .run and .ova files now support 5 digits, for example, 1.15.5.0.2.run and apphost_redhat8_1.15.5.0.2.ova.

Managing the jdk_certs password

The password for the IBM JDK 11 keystore is now randomized and stored securely in the SOAR keyvault. If you installed SOAR previously, after installing the latest version of SOAR, the password for the IBM JDK 11 keystore is changed and stored in the SOAR keyvault.

For more information, see Changed in 51.0.6.0 Managing KeyVault secrets.