Minor Releases

Cortex XSOAR 6.8 minor releases, maintenance releases.
Cortex XSOAR Minor Release
Release Date
July 17, 2022

Cortex XSOAR 6.8.0 (B3261002)

Cortex XSOAR 6.8.0 (B3261002) is a maintenance release that delivers the following enhancements and bug fixes:
New Feature
Added the following server configuration for situations when trying to view the
Related Incidents
tab of a selected incident and Cortex XSOAR is taking too long to access the data:
Key
Value
incident.cluster.query.parallel.limit
Default is 2
Note that a larger value means greater CPU/memory usage.
Enhancements
  • (
    Multi-tenant
    ) Improvements have been made to multi-tenant deployments with large numbers of hosts. Cortex XSOAR no longer automatically creates all installers and does not query offline hosts.
  • (
    Multi-tenant
    ) When selecting incidents from more than one account, a message is now displayed that the selected incidents are from different accounts.
Fixed Issues
  • When creating a new incident with a slash (
    /
    ) in the name, the incident could not be edited.
  • In the Deployment Wizard
    Configure Playbook and Parameters
    task, the default main playbook sometimes changed.
  • When selecting
    Use this instance for external authentication only
    in an Active Directory Authentication integration, and then selecting
    Require users to authenticate
    in a data collection task in a playbook, the user could not log into Cortex XSOAR, and an error message appeared.
  • The Deployment Wizard was missing a note to users that the modal could not close without filling in required fields.
  • After first time installation, clicking the Deployment Wizard
    Fetch Integration
    caused an error.
  • After upgrading to Cortex XSOAR 6.8, in some cases, if using Live Backup, the server repeatedly restarted and users were unable to access the UI.
  • In some cases, the Cortex XSOAR server restarted due to a concurrency error.
  • In the Deployment Wizard, the default incident type was detached when the wizard steps were completed.
  • In the playbook editor with multiple tabs open, long playbook names did not display correctly.
  • Indicators that were changed or created in the last day of any month were not expired.
  • Recurring scheduled tasks caused the server to crash.
  • Although some sub-playbook tasks progressed in the server, they did not appear, unless when refreshing the page.
  • After creating a new field and adding it to all incident types, the field did not appear on the
    New Incident
    form.
  • When viewing an incident, if you viewed the incident
    Summary
    tab, switched to a different tab, and then returned to the
    Summary
    tab, the incident name no longer appeared in the tab header.
  • In the
    Incidents
    page, if no incidents were returned in a search, clicking the
    How to search in Cortex XSOAR
    link did not go to the correct page.
  • When creating a playbook and then navigating to the
    Manual Tasks
    tab from the
    Task Library
    window, the tab did not load.
  • In some cases, customers with a TIM only license were not able to run Cortex XSOAR operations.
  • In some cases, scheduled jobs caused the server to hang.
  • (
    Live Backup
    ) In some cases, due to a golang concurrent map read/write error, the Cortex XSOAR server would restart.
  • (
    Remote Repository
    ) If there were conflicts between the development and production machines, clicking on the
    Resolve Conflicts
    button led users to a blank page and conflicts could not be resolved.
  • (
    High Availability
    ) In some cases, some web services message data was empty when sent from one app server to another.
  • (
    High Availability
    ) In some cases, when an app server ran a playbook, a user looking at the investigation while connected to a different app server did not see updated task information.
  • (
    Multi-tenant
    ) Accounts on remote hosts would sometimes enter deactivated mode.
  • (
    Multi-tenant
    ) Cortex XSOAR failed when there were timeouts from a large number of hosts.
  • (
    Multi-tenant
    ) In some scenarios, the host deleted all of its local users. This triggered all users to be deleted from the host’s accounts as well, along with their related API keys, preventing any access to those accounts.
  • (
    Multi-tenant
    ) When exporting custom layouts from a main account, the files were truncated to 32KB and could not be used.
  • (
    Multi-tenant with High Availability
    ) In some cases, an empty high availability group remained in the database, causing panics.
Installation file hash:
ce9c38e7c5d6e7d03cd0d5cf4ebdc4c001a877f586bfca2619af14c4ab2aabe4

Recommended For You