Add Custom Alert and Incident Statuses and Resolution Reasons - User Guide - 2 - Cortex XPANSE - Cortex - Security Operations

Cortex Xpanse Expander User Guide

Product
Cortex XPANSE
Version
2
Creation date
2024-03-28
Last date published
2024-05-22
Category
User Guide
Solution
Cloud
Abstract

Create custom alert and incident statuses and custom resolution reasons that are tailored to your workflow.

Warning

Before you add a custom status, please review the built-in options. For more information see Alert Status and Incident Status.

We recommend using the built-in statuses and resolution reasons where possible. Custom statuses and resolution reasons might not be supported by all content, and status syncing can take time.

In addition, custom statuses affect ability of Cortex Xpanse to learn, correctly identify, and score future incidents.

You can create custom alert and incident statuses and custom resolution reasons that are tailored to your workflow. Custom statuses and resolution reasons apply to both incident and alert statuses, and can also be used in playbooks.

Custom resolution types are always nonterminal (or reopenable). That means an incident that is resolved with a custom resolution will be reopened with the status New if scans detect the asset again an an alert is generated. An alert that is resolved with a custom resolution will be reopened with the status Reopened.

Adding custom incident statuses and resolution reasons requires a View/Edit RBAC permission for Incident Properties (under Object Setup).

  1. Go to SettingsConfigurationsObject SetupIncidents.

    The existing statuses and resolution types are listed.

  2. In the Add another status field, type a new status and click Save.

  3. Click Edit to rearrange the order of the statuses. This order is presented when you set a status or select a resolution type.