Cymulate
Cymulate Pack.#
This Integration is part of the#
Configure Cymulate on Cortex XSOAR- Navigate to Settings > Integrations > Servers & Services.
- Search for Cymulate.
- Click Add instance to create and configure a new integration instance.
- Name: a textual name for the integration instance.
- X-token
- Fetch incidents
- Incident type
- Show only 'penatrated' incidents
- Click Test to validate the URLs, token, and connection.
#
Fetched Incidents Data#
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.
- cymulate_get_incident_info
#
1. cymulate_get_incident_infoThis commands return full cymulate's incidents information
#
Base Commandcymulate_get_incident_info
#
InputArgument Name | Description | Required |
---|---|---|
attack_id | The attack unique identifier | Required |
incident_id | The incident unique identifier | Required |
module_type | The Cymulate module_type | Required |
#
Context OutputPath | Type | Description |
---|---|---|
Cymulate.Incident.Payload | String | The Cymulatepayload that generated this incident |
Cymulate.Incident.Name | String | The name of the incident |
Cymulate.Incident.Status | String | The attack status |
Cymulate.Incident.Attack_Type | String | The incident Attack_Type |
Cymulate.Incident.Attack_Vector | String | The incident ID |
Cymulate.Incident.Timestamp | String | The incident ID |
Cymulate.Incident.Attack_Payload | String | The incident ID |
Cymulate.Incident.Md5 | String | The incident ID |
Cymulate.Incident.Mitigation | String | The incident ID |
Cymulate.Incident.Module | String | The incident ID |
Cymulate.Incident.Penetration_Vector | String | The incident ID |
Cymulate.Incident.Sha1 | String | The incident ID |
Cymulate.Incident.Sha256 | String | The incident ID |
#
Command Example!cymulate_get_incident_info attack_id="5e71e8cc7df91d6b4d460943" incident_id="9bc6591182ca40f3a3bfb3b46e3be025" module_type="IMMEDIATE_THREATS"
#
Context Example#
Human Readable Output#
Cymulate ResutlsID | Name | Status | Attack Type | Attack Vector | Timestamp |
---|---|---|---|---|---|
cd61447e5fc76ebd2a35de651f211ff9 | Chinese Hackers Use New Malware to Backdoor Microsoft SQL Servers | Penetrated | Antivirus | Endpoint Security | 25/12/2019 15:03:15 |
1595f452a74e5743fae63c8063eed9e6 | Chinese Hackers Use New Malware to Backdoor Microsoft SQL Servers | Penetrated | Antivirus | Endpoint Security | 25/12/2019 15:03:14 |
dc2a1e9b835b5caf685960bb7d9bdfea | Chinese Hackers Use New Malware to Backdoor Microsoft SQL Servers | Penetrated | Files | Web Gateway | 25/12/2019 15:01:29 |
b2aa30c32e06762d09bac485d7c490a5 | Chinese Hackers Use New Malware to Backdoor Microsoft SQL Servers | Penetrated | Files | Web Gateway | 25/12/2019 15:01:29 |
#
cymulate-get-incident-infoThis commands return full cymulate's incidents information
#
Base Commandcymulate-get-incident-info
#
InputArgument Name | Description | Required |
---|---|---|
attack_id | The attack unique identifier. | Required |
module_type | The Cymulate module_type. | Required |
incident_id | The incident unique identifier. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
Cymulate.Incident.Payload | String | The Cymulate payload that generated this incident |
Cymulate.Incident.Name | String | The name of the incident |
Cymulate.Incident.Status | String | The attack status (Enum Values- Penetrated, Blocked, Dead) |
Cymulate.Incident.ID | String | The incident ID |
Cymulate.Incident.Md5 | String | The Md5 |
Cymulate.Incident.Attack_Vector | String | The Attack Vector |
Cymulate.Incident.Sha256 | String | The Sha256 |
Cymulate.Incident.Sha1 | String | The Sha1 |
Cymulate.Incident.Cymulate_ID | String | The cymulate's ID of the incident |
Cymulate.Incident.Attack_ID | String | The cymulate's Attack ID of the incident |