Playbook Blocks
Playbooks Blocks is a new feature designed to reduce repetition and save time when creating playbooks. You can create a Playbook block once and then reuse it in multiple Playbooks. This reusable block ensures greater versatility and reduces the need for multiple playbooks. In addition, because it’s an inserted block and not an Attach Playbook action, the Playbook waits for this block to complete before continuing with its actions.
The Playbook block is also unique in that it uses Inputs, either from the parent Playbook or manually configurable and return an output response into the parent Playbook. It can be also added manually as a stand alone Playbook to an existing Case.

For a video tutorial on this topic, please refer to Creating Playbook Blocks.

Support for High Availability (HA)
Siemplify platform can now be installed with HA support. For full information on installation, please refer to the High Availability Installation Guide

Playbooks – Fallback Branch in Conditions
Previously, you could define a Playbook to continue running even if an action failed (using Skip Step). However, the Playbook would still fail when it reached a Condition branch. With this Release a full solution has been found as Siemplify now allows you to define a fallback branch for conditions. This means that even if a condition step cannot be executed due to previous action failure, the Playbook continues along the Fallback branch. So instead of the Playbook simply failing as would happen in previous versions, the security engineer can now define which branch to follow to ensure smooth Playbook completion.

For more information, please refer to Playbooks > Flow in the User Guide.

Playbook Flow Change
The Case Data Condition in the Flow section of the Playbooks will be removed and replaced by Condition. All customer Playbooks will undergo this change automatically and seamlessly with migration to 5.3.0. There will be zero risk for existing Playbooks.

View Only User with new License
With this Release, organizations can now add View-Only users to the Siemplify platform. This can come in useful, for example, for MSSPs who want to allow their customers just to view their own environments, or as another example, non SOC users who want to view Reports. The View Only users have a special “light” license. For pricing details, please contact your Account Manager. Note that regular users are now referred to as Standard Users in the platform in order to highlight the difference.
For full details on this feature, please refer to Create View Only Users

Data Retention
In order to improve resources and performance, and to comply with legal regulations, Siemplify users can now define the period of time after which data will be deleted. This feature is active by default and can be configured in the Platform system wide or per environment. If you want to deactivate it, please contact your Siemplify Account Manager.

Easier Navigation for Placeholders within Playbook Actions
To support the need for the analyst to view all the placeholders under each category – an internal scroll bar has been added thereby improving the Search functionality.

Support for Python version 3.7
Siemplify has added support for Python 3.7 side by side with Python 2.7.

Add JSON Result Checkbox for IDE
Now, when creating or editing a new action in the IDE, you can decide if it returns a JSON result. This now allows better alignment with Playbook Actions.

Online Feedback
New Feedback option added to question mark icon at top of screen to enable you to quickly jot down your thoughts and suggestions to us.

Announcements
Siemplify has added the ability to roll out Announcements for all important information that needs to be relayed to customers.

UX Enhancements
Enhancements are added with each release to improve overall look, feel and functionality of the Siemplify platform.

Offline Installer
Offline Installer is now supported.

Need more help with this?
Click here to open a Support ticket

Thanks for your feedback.