Special Notices

This section highlights key operational changes in FortiSOAR release 7.6.1 that administrators need to know.

Upgrade to FortiSOAR 7.6.1 causes the TAXII Server to be disabled and MIME Type fields to be reset

The impact of upgrading to FortiSOAR 7.6.1 on the TAXII Server and MIME Type settings are as follows:

• TAXII Server Disabled: The TAXII server configuration will be automatically disabled. You must manually re-enable the TAXII server. For details, see the Threat Intel Management Solution Pack documentation.
• MIME Type Settings Reset: Any custom MIME type validations for file uploads, added based on your organization's policies in the Restricted File MIME Types field, will be reset to their default values. You will need to manually re-add these MIME types to the Restricted File MIME Types field. For details, see the Enabling MIME type validations for file uploads topic in the "Administration Guide."

NOTE: These issues will be addressed in FortiSOAR 7.6.2.

FortiSOAR MEA discontinued for FortiAnalyzer and FortiManager

Starting with release 7.6.1, the FortiSOAR Management Extension Application (MEA) is discontinued for FortiAnalyzer and FortiManager.

Change in Playbook Execution Logs API behavior

In release 7.6.1, the Playbook Execution Logs API is divided into 'recent' and 'historical' execution logs. To retrieve consolidated records i.e., both the recent and historical playbook execution logs use the /api/wf/api/workflows API. To retrieve historical playbook execution logs, use the /api/wf/api/historical-workflows/ API. Previously, the single API (/api/wf/api/workflows/) was used.

Added a maximum allowable wait time for playbooks that include a wait, manual input, or approval step

For playbook optimization, playbooks that remain in the 'awaiting' state for more than 7 days will be automatically terminated. As a result, the maximum allowable wait time for a playbook is now 7 days. Previously, there was no maximum wait time.

Change in the behavior of purging executed playbook logs

Starting with release 7.6.1, the purge function excludes 'Recent' playbook logs and playbooks executed on the same day when purging 'Historical' logs.

Playbook execution logs movement to historical storage

Once you have upgraded your FortiSOAR system to 7.6.1, existing playbook execution logs are moved to historical storage to optimize workflow logs storage. This background process could take some time depending on the size of existing playbook execution logs; however, this will not affect FortiSOAR's functionality.