If you ever need to handle security incidents you know how difficult it can be. More often than not, the system that detected the incident lacks the contextual information needed to figure out whether it’s a false positive or something that needs to be investigated further. Other systems typically don’t contain the full information either about the discovered incident. Also, automation would be of great help to tell the system: “Hey, if you see this particular incident from a similar IP address go to my firewall and block it and then inform me when you’re done”. This is where Cortex XSOAR comes in.
If these challenges sound familiar to you, then what you need is an orchestration and automation tool like Palo-Alto’s Cortex XSOAR. This tool is built for making the life of the security analyst a lot easier. It allows you to configure multiple plugins for interacting with multiple systems both automatically and manually.
Together with the flexibility and the reach of security-related information provided by Coralogix, you can easily analyze security alerts from many different sources, correlate the various Indicators of Compromise (IOCs), form a coherent evidence-based timeline, and react to the incident and even automate the handling of similar incidents. XSOAR provides all of that from a single pane of glass.
There are countless use-cases for this integration so we’ll just provide you with a few examples to get you started.
The process for adding the Coralogix integration pack is quite simple and straightforward:
|Parameter Name||Description||Required||Default Value|
|Name||The name of the Coralogix integration instance (Can be any name you like)||Yes||N/A|
|Fetches incidents||Whether or not to fetch incidents via this integration||No||Do not fetch|
|Coralogix WebAPI Endpoint URL||The Coralogix WebAPI URL||Yes (Don't change it unless instructed to do so by Coralogix personnel)||https://webapi.Cluster URL.com.|
|Private Key||Your Coralogix account Send-Your-Data API key||Yes||N/A|
|Application Name (for tags)||The Coralogix application name that will be assigned to the tags created by this instance||Yes||Cortex XSOAR|
|Subsystem Name (for tags)||The Coralogix subsystem name that will be assigned to the tags created by this instance||Yes||Cortex XSOAR|
|Coralogix ES-API Endpoint URL||The Coralogix ES-API URL||Yes||Elasticsearch-API|
|Basic incidents query||The Lucene query for fetching incidents. If not specified, will return Coralogix alerts that were sent to the Demisto webhook||No||N/A|
|Incidents Application Name||Limits the incidents query to only return incidents of a specific application name||No||N/A|
|Incidents Severity||Limits the incidents query to only return incidents of a specific severity||No||N/A|
|Incidents Name Field||The Coralogix field value that should be used as the incident's name. If not specified, the integration will use the "alert_name" field||No||N/A|
|Incidents first fetch days||The number of days to look back for incidents||No||3|
|Maximum number of incidents to fetch at a single call||Maximum number of incidents to retrieve at each call to Coralogix||No||50|
After configuring these parameters you should be able to do the following:
!coralogix-search query="security.rcode_name:\"NXDOMAIN\"" using="Coralogix_instance_1"
!coralogix-tag name="Data leak started" timestamp="2020-12-31T23:59:59"
Also, just like with any other integration of Cortex XSOAR, you can create any playbook you’d like and combine these operations with operations available from other integrations to automatically respond to security-related incidents.
Hoping you found this content helpful.