TaegisXDR (Deprecated)
Secureworks Pack.#
This Integration is part of theDeprecated
Use TaegisXDR v2 instead.
#
Configure Taegis XDR on Cortex XSOARNavigate to Settings > Integrations > Servers & Services.
Search for Taegis XDR
Click Add instance to create and configure a new integration instance.
Parameter Description Required Taegis Environment The environment to utilize True Client ID Client ID as described in the Taegis Documentation True Client Secret Client Secret as described in the Taegis Documentation True Use system proxy settings Defines whether the system proxy is used or not False Click Test to validate the URLs, token, and connection.
#
CommandsYou can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.
#
taegis-archive-investigation#
Base Command!taegis-archive-investigation
#
InputsArgument Name | Description | Required |
---|---|---|
id | The investigation id to archive | True |
#
Command Example#
Context Example#
taegis-create-comment#
Base Command!taegis-create-comment
#
InputsArgument Name | Description | Required |
---|---|---|
comment | The comment string to add to the investigation | True |
parent_id | The investigation ID to add the comment to | True |
#
Command Example#
Context Example#
taegis-create-investigation#
Base Command!taegis-create-investigation
#
InputsArgument Name | Description | Required |
---|---|---|
description | The subject or description of the investigation | True |
priority | The priority for the investigiation [Default: 3] | False |
#
Command Example#
Context Example#
taegis-execute-playbook#
Base Command!taegis-execute-playbook
#
InputsArgument Name | Description | Required |
---|---|---|
id | Playbook instance ID to execute | True |
inputs | JSON object of inputs to pass into the playbook execution | False |
#
Command Example#
Context Example#
taegis-fetch-alerts#
Base Command!taegis-fetch-alerts
#
InputArgument Name | Description | Default | Required |
---|---|---|---|
ids | A list of alerts by IDs | 936c1cc1-db8f-430c-837c-1c914fcca35a | False |
limit | Number of results to when ids is not defined | 10 | False |
offset | The result to start from when ids is not defined | 0 | False |
cql_query | The query to utilize when searching for Alerts | from alert severity >= 0.6 and status='OPEN' | False |
#
Command Examples#
Context Example#
taegis-fetch-assets#
Base Command!taegis-fetch-assets
#
InputArgument Name | Description | Default | Required |
---|---|---|---|
page | 0 | False | |
page_size | 10 | False | |
endpoint_type | False | ||
host_id | ID of the asset to fetch | e43b545a-580a-4047-b489-4338c1cc4ba1 | False |
hostname | False | ||
investigation_id | False | ||
ip_address | False | ||
mac_address | False | ||
os_family | False | ||
os_version | False | ||
sensor_version | False | ||
username | False |
#
Command Examples#
Context Example#
taegis-fetch-comment#
Base Command!taegis-fetch-comment
#
InputsArgument Name | Description | Required |
---|---|---|
id | The ID of the comment to fetch | True |
#
Command Example#
Context Example#
taegis-fetch-comments#
Base Command!taegis-create-comments
#
InputsArgument Name | Description | Required |
---|---|---|
parent_id | The investigation ID to fetch comments for | True |
#
Command Example#
Context Example#
taegis-fetch-endpoint#
Base Command!taegis-fetch-endpoint
#
InputsArgument Name | Description | Required |
---|---|---|
id | Endpoint ID to fetch | True |
#
Command Example#
Context Example#
taegis-fetch-investigation#
Base Command!taegis-fetch-investigation
#
InputsArgument Name | Description | Required |
---|---|---|
id | Investigation ID to lookup | True |
#
Command Example#
Context Example#
taegis-fetch-investigation-alerts#
Base Command!taegis-fetch-investigation-alerts
#
InputsArgument Name | Description | Required |
---|---|---|
id | Investigation ID to lookup | True |
#
Command Example#
Context Example#
taegis-fetch-investigations#
Base Command!taegis-fetch-investigations
#
InputsArgument Name | Description | Required |
---|---|---|
page | False | |
page_size | False |
#
Command Example#
Context Example#
taegis-fetch-playbook-execution#
Base Command!taegis-fetch-playbook-execution
#
InputsArgument Name | Description | Required |
---|---|---|
id | Playbook execution ID to fetch | True |
#
Command Example#
Context Example#
taegis-fetch-users#
Base Command!taegis-fetch-users
#
InputsArgument Name | Description | Required |
---|---|---|
id | The id of the user, in auth0 format | False |
The email of the user | False | |
status | The users to find based on status | False |
page | False | |
page_size | False |
#
Command Example#
Context Example#
taegis-isolate-asset#
Base Command!taegis-isolate-asset
#
InputArgument Name | Description | Default | Required |
---|---|---|---|
id | ID of the asset to isolate | e43b545a-580a-4047-b489-4338c1cc4ba1 | True |
reason | The reason for the isolation | See ticket 12345 | True |
#
Command Examples#
Context Example#
taegis-update-alert-status#
Base Command!taegis-update-alert-status
#
InputArgument Name | Description | Default | Required |
---|---|---|---|
ids | A comma-separated list of alerts by IDs | alert://priv:crowdstrike:11772:1666269058114:59284e28-4ec8-542b-a4a1-452c3688bc1a | True |
status | The status to update the alert(s) with | FALSE_POSITIVE | True |
reason | A comment/reason for the alert status update | See ticket 13245 | False |
#
Permitted Status Values- FALSE_POSITIVE
- NOT_ACTIONABLE
- OPEN
- TRUE_POSITIVE_BENIGN
- TRUE_POSITIVE_MALICIOUS
#
Command Examples#
Context Example#
taegis-update-comment#
Base Command!taegis-update-comment
#
InputsArgument Name | Description | Required |
---|---|---|
comment | The comment string to add to the investigation | True |
id | The comment ID to update | True |
#
Command Example#
Context Example#
taegis-update-investigation#
Base Command!taegis-update-investigation
#
InputsArgument Name | Description | Required |
---|---|---|
id | Investigation ID to update | True |
key_findings | False | |
prioirity | The priority of the Investigation (1-5) | False |
service_desk_id | An ID or ticket # to relate to an Investigation | False |
service_desk_type | The type of id related to an investigation (e.g. Jira) | False |
status | The current status of the Investigation | False |
assignee_id | The id of a user to assign, in `auth0 | 12345` format |
Note: At least 1 of the above inputs (in addition to id) must be defined
#
Permitted Status Values- Active
- Awaiting Action
- Closed: Authorized Activity
- Closed: Confirmed Security Incident
- Closed: False Positive Alert
- Closed: Inconclusive
- Closed: Informational
- Closed: Not Vulnerable
- Closed: Threat Mitigated
- Open
- Suspended
#
Command Example#
Context Example#
taegis-unarchive-investigation#
Base Command!taegis-unarchive-investigation
#
InputsArgument Name | Description | Required |
---|---|---|
id | The investigation id to unarchive | True |