CybleEvents v2
CybleEventsV2 Pack.#
This Integration is part of theSupported versions
Supported Cortex XSOAR versions: 6.2.0 and later.
Cyble Events for Vision Users. Must have Vision API access to use the threat intelligence. This integration was integrated and tested with version 2.0 of cybleeventsv2
#
Configure CybleEventsV2 on Cortex XSOARNavigate to Settings > Integrations > Servers & Services. Search for CybleEventsV2. Click Add instance to create and configure a new integration instance.
Parameter Description Required URL Server URL (e.g., https://example.net\) True Access Token Access Token True Collections to Fetch Select collections of incidents to be fetched from the dropdown menu False Severities to Fetch Select severities of incident to be fetched from the dropdown menu False Trust any certificate (not secure) False Use system proxy settings False Incident Fetch Limit Maximum incidents to be fetched every time. Upper limit is 50 incidents False Hide Card Details Select to hide CVV and Expiry date of card False Update Incident to Remote System Select to update changes in any incident to Vision False To ensure that fetch incidents works:
- Select the Fetches incidents radio button.
- Under Incident type, select Cyble Vision Alert V2.
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.
#
cyble-vision-subscribed-servicesGet list of Subscribed services
#
Base Commandcyble-vision-subscribed-services
#
InputThere are no input arguments for this command.
#
Context OutputPath | Type | Description |
---|---|---|
CybleEvents.SubscribedServices | String | A list of subscribed services from Cyble vision |
#
cyble-vision-fetch-iocsFetch the indicators in the given timeline.
#
Base Commandcyble-vision-fetch-iocs
#
InputArgument Name | Description | Required |
---|---|---|
ioc_type | Returns records according to their type (Domain, FileHash-MD5, FileHash-SHA1, FileHash-SHA256, IPv4, IPv6, URL, Email, Wallet-Address). Default is Domain. | Optional |
ioc | Returns records for the specified indicator value. | Optional |
from | Returns records that starts from the given page number (the value of the form parameter) in the results list. Default is 1. | Optional |
limit | Number of records to return (max 100). Using a smaller limit will get faster responses. Default is 1. | Optional |
sort_by | Sorting based on the column(last_seen,first_seen,ioc_type). Possible values are: last_seen, first_seen, ioc_type. Default is last_seen. | Optional |
order | Sorting order for ioc either Ascending or Descending based on sort by. Default is desc. | Optional |
tags | Returns records for the specified tags. | Optional |
start_date | Timeline start date in the format "YYYY-MM-DD". Should be used with start_date as timeline range. | Optional |
end_date | Timeline end date in the format "YYYY-MM-DD". Should be used with end_date as timeline range. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
CybleEvents.IoCs.Data | String | Returns indicator with risk score, confident rating, first seen and last seen |
#
cyble-vision-fetch-alertsFetch alerts based on the given parameters. The alerts would have multiple events grouped into one, based on a specific service type. This way the user will see, in some cases, more events than the limit provides.
#
Base Commandcyble-vision-fetch-alerts
#
InputArgument Name | Description | Required |
---|---|---|
limit | Number of records to return (max 50). Using a smaller limit will get faster responses. Default is 5. | Optional |
start_date | Timeline start date in the format "%Y-%m-%dT%H:%M:%S%z" (iso-8601). | Required |
end_date | Timeline end date in the format "%Y-%m-%dT%H:%M:%S%z" (iso-8601). | Required |
order_by | Sorting order for alert fetch either Ascending or Descending. Possible values are: asc, desc. Default is asc. | Optional |
from | Returns records for the timeline starting from the given indice. Default is 0. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
CybleEvents.Events.name | String | Return Event name |
CybleEvents.Events.alert_group_id | String | Return alert group id |
CybleEvents.Events.event_id | String | Return event id |
CybleEvents.Events.keyword | Unknown | Return keywords |
#
cyble-vision-fetch-alert-groupsFetch incident event group
#
Base Commandcyble-vision-fetch-alert-groups
#
InputArgument Name | Description | Required |
---|---|---|
order_by | Sorting order for alert fetch either Ascending or Descending. Possible values are: asc, desc. Default is asc. | Optional |
limit | Number of records to return (max 50). Using a smaller limit will get faster responses. Default is 5. | Optional |
start_date | Timeline start date in the format "%Y-%m-%dT%H:%M:%S%z" (iso-8601). | Required |
end_date | Timeline end date in the format "%Y-%m-%dT%H:%M:%S%z" (iso-8601). | Required |
from | `Returns records that starts from the given page number (the value of the form parameter) in the results list. Default is 0. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
CybleEvents.AlertGroup | String | Fetch all the alert groups |