Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XDR

Review an initiative

Track the progress of a Cortex XDR initiative, take snapshots on demand, and fix snapshot failures.

Everything shown on an initiative comes from its snapshot history. For how snapshots, filter-based membership, and the resolution cutoff work, see Case initiatives. To change an initiative's filter, details, or target date, see Create an initiative.

Track initiative progress

  1. On the Cases page, click the dropdown next to All Cases and select the Initiatives view. Open the initiative.

  2. Check the snapshot status line at the top of the initiative.

    Last snapshot: shows when the most recent snapshot was taken. N/A means no snapshot exists yet. Taking snapshot means a snapshot is running. Snapshot Failed means the last snapshot did not complete. For details, see Fix a failed snapshot.

  3. Review the summary widgets:

    • Overall Progress: Shows the number of resolved issues as a percentage of all issues in the initiative.

    • Total Open Issues: Shows the number of issues in the initiative that are still open.

    Both values come from the last snapshot, not from live data.

  4. Review the snapshot graph:

    • In Time range, select 24H, 1W, or 1M.

    • The graph plots Open Issues, Resolved Issues, and Total Issues at each snapshot.

    • Last Added and Last Resolved show how many issues were added and resolved between snapshots. Use them to see whether new issues are arriving faster than existing ones are resolved.

    • Hover over a point in the graph to see the snapshot time and its values.

  5. To see the details of a snapshot, click the expand icon on the hover card.

    The Initiative Snapshot panel opens. It shows:

    • Snapshot timestamp, Snapshot type, and the Record ID.

    • Initiative SLA and Initiative Progress.

    • All Issues, Open Issues, and Resolved Issues.

    • Last Added and Last Resolved, compared with the previous snapshot. Click View last added issues or View last resolved issues to see the issues.

    • Assignment breakdown: Open issues per assignee, including Unassigned. Use it to find workload bottlenecks.

Tip

New matching issues keep joining the initiative, so the open-issue count doesn't reflect remediation progress on its own. Compare Last Added with Last Resolved to see whether your team is resolving issues faster than new ones arrive.

Review snapshot history in the timeline

Every snapshot is recorded in the initiative timeline.

  1. Open the initiative and switch the view from Overview to Timeline.

  2. Find records with the record type Snapshot Taken and the record name Initiative Snapshot.

    Each entry shows what triggered the snapshot:

    Subtype
    Triggered by

    System - Scheduled

    The automatic schedule. The first snapshot after you create an initiative also uses this subtype.

    Manual

    A user taking a snapshot. See Take a snapshot manually.

    System - Initiative Edited

    A saved change to the initiative filter.

Snapshot records are created by the system only. You cannot add them yourself, and you cannot mark them as evidence.

Take a snapshot manually

Take a snapshot when you need current numbers before the next scheduled snapshot, for example before a program review or after a large remediation push.

  1. Open the initiative.

  2. In the snapshot status line, click the camera icon next to Last snapshot:.

    The status line changes to Taking snapshot. When it finishes, Cortex XDR writes a snapshot with the subtype Manual and updates the widgets and graph.

You can take one manual snapshot every 2 hours per initiative. If the previous snapshot finished less than 2 hours ago, the icon shows "Snapshots can be taken every 2 hours." and the next available time. The 2-hour wait applies only after a successful snapshot. If a snapshot fails, you can try again right away.

The camera icon is not shown in the following cases:

  • The initiative is resolved. Resolved initiatives are also excluded from scheduled snapshots.

  • A snapshot is already running.

  • You are viewing a child tenant from an MSSP parent tenant.

Note

You don't need to take a snapshot after editing the filter. Saving a filter change takes a snapshot automatically.

Fix a failed snapshot

A snapshot will fail if the filter matches more than 10,000 issues. This can happen even if the filter was within the limit when you saved it, for example after new assets are onboarded or a new detection starts firing.

When this happens:

  • The status line shows Snapshot Failed.

  • No snapshot is written, and issue associations stay as they were after the last successful snapshot.

  • The widgets and graph continue to show the last successful snapshot. No data is lost.

To fix it:

  1. Hover over Snapshot Failed.

  2. Click Edit Filter.

  3. On the Define scope modal, narrow the filter, for example by severity, asset group, or issue subcategory.

    If the issue grid still shows Issues exceed the 10K limit, keep narrowing. Cortex XDR lets you save a filter that is over the limit, but the next snapshot will fail again.

  4. Click Save.

    Cortex XDR takes a snapshot with the subtype System - Initiative Edited.

Editing the filter resets the resolution cutoff

If you can't narrow the filter without losing the point of the program, split it into several initiatives along a natural boundary, such as business unit, cloud account, or asset group.

Troubleshoot

A snapshot failed, but the issue count is under 10,000

The last successful snapshot is still shown. Click the camera icon to try again right away. Scheduled snapshots also continue as usual.

Saving a filter change fails

You can't save a filter change while a snapshot is running or about to run. The change is rejected, not queued, and an update-failed message is shown. Wait until the status line no longer shows Taking snapshot, and then save again.

Expected issues are missing from the initiative

Check the following, in order:

  1. Issue domain. Only Posture issues can be part of an initiative.

  2. Issue state. Open matching issues are added. Resolved issues are included only if they were resolved after the initiative was created or after the last filter edit, whichever is later.

  3. Access scope. The initiative includes only issues within the access scope of the user who last saved the filter.

  4. Snapshot recency. Issues that started matching after the last snapshot are added at the next snapshot. To add them now, take a snapshot manually.

An issue disappeared from the initiative

Issues that no longer match the filter are removed at the next snapshot, whether they are open or resolved. This is expected. You can't link issues to an initiative or unlink them manually. Change the filter instead.

Case actions that are not available for initiatives

Because an initiative tracks a program rather than a single threat, some case actions do not apply:

  • You cannot merge an initiative with other cases.

  • You cannot link an issue to an initiative from the issue's Link to case action.

  • Initiatives do not show a case score.

Last updated

Was this helpful?