For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XSOAR 8.10 (On-pre8.10 (On-prem)Cortex XSOAR 8.x (On-prem

Configure incident export and delete

Configure incident export and deletion in Cortex XSOAR 8.10 On-prem.

The incident export and delete feature enables you to limit storage usage while meeting regulatory requirements for extended data retention. You can perform the following actions:

  • Export incidents on demand

  • Schedule automated incident export, automated incident deletion, or automated incident export and deletion

Incidents are exported as JSON files that contain the following:

  • Incident data, including all incident fields

  • Context data

  • Investigation data

  • War Room entries

In addition, you can choose to export incident attachments.

Exported incidents are sent to Amazon S3, an S3-compatible bucket, or to local NFS (Network File System) storage.

Warning

Note

  • The first time incidents are exported, the export may take multiple days or weeks to complete, depending on the number of incidents and the amount of data. The previous export must complete before the system begins another export.

  • Once an incident has been exported, even if the incident is not deleted and remains in the system, it is not exported again. Note that this also applies to incidents that are modified after export.

  • Retained incidents are not exported or deleted. For more information, see Retain incidents.

  • To stop an existing process (export, delete, or export then delete), you must make a POST request to the API endpoint: /xsoar/exdelete-incidents/job/abort.

Last updated

Was this helpful?