Supported Cortex XSOAR versions: 5.5.0 and later.
This playbook performs the following steps:
- Creates a compliance search.
- Starts a compliance search.
- Waits for the compliance search to complete.
- Gets the results of the compliance search.
- Gets the preview results, if specified.
- Deletes the search results (Hard/Soft).
This playbook uses the following sub-playbooks, integrations, and scripts.
- O365 - Security And Compliance - Search
- Hard delete
- Soft delete
- O365 - Security And Compliance - Search Action - Preview
|search_name||The name of the compliance search. If not specified will have prefix of "XSOAR-" and GUID e.g. XSOAR-d6228fd0-756b-4e4b-8721-76776df91526.||Optional|
|case||The name of a Core eDiscovery case to associate with the new compliance search.||Optional|
|kql||Text search string or a query that is formatted using the Keyword Query Language (KQL).||Required|
|description||Description of the compliance search.||Optional|
|allow_not_found_exchange_locations||Whether to include mailboxes other than regular user mailboxes in the compliance search. Default is "false".||true||Optional|
|exchange_location||Comma-separated list of mailboxes/distribution groups to include, or use the value "All" to include all.||Required|
|exchange_location_exclusion||Comma-separated list of mailboxes/distribution groups to exclude when you use the value "All" for the exchange_location parameter.||Optional|
|force||Whether to replace the existing search. If "true", the existing search will be removed and a new search will be created. If "false", the existing search will be used and any new search configurations will be ignored.||false||Required|
|preview||Whether to preview the results using the search action "Preview". Possible values are: "true" and "false" or leave empty to select manually.||true||Required|
|delete_type||Specify the delete type to perform on the search results. Possible values are Hard and Soft or leave empty to select manually. (Hard = Unrecoverable, Soft=Recoverable)||Soft||Required|
There are no outputs for this playbook.
- Each security and compliance command creates a PSSession (PowerShell session). The security and compliance PowerShell limits the number of concurrent sessions to 3. Since this affects the behavior of multiple playbooks running concurrently it we recommend that you retry failed tasks when using the integration commands in playbooks.
- In order to handle sessions limits, A retry mechanism is applied which will retry for 10 time with 30 sec breaks. (The retry isn't applied on the generic polling as its not supported yet)