Table of contents
6 min
H2 title on one or more lines.
Speak to a Sekoia expert

Your security challenges deserve expert answers. Get a tailored demo and discover how Sekoia helps your team detect and respond to threats faster.

Get a demo

Share

Copied !

SentinelOne and Sekoia Integration

Sekoia SOC integrates with SentinelOne EDR for robust cybersecurity. Explore threat event detection, playbooks, and automated actions.

Expanding tech stack and increasing number of tools urge security operations teams to seek a one-stop solution for centralizing events and alerts.

Under these conditions of growing risks, the Sekoia SOC platform becomes a silver-bullet solution for backing up SOC teams. It serves as a control tower for cybersecurity and easily collects, correlates, and analyzes events and alerts from all over the information system. 

Sekoia.io offers 170+ integrations with our SOC platform. In this blog post, we’ll dive into integrating our platform with SentinelOne EDR solution.

Collect SentinelOne EDR Threat and Activity events in the Sekoia SOC platform

Sekoia.io leverages SentinelOne’s management SDK to collect threat and activity events from the SentinelOne management console.

Sekoia detection rules for SentinelOne

The Sekoia SOC platform relies on several Sigma rules that determine which SentinelOne Threat events should raise an alert in the Sekoia platform. This granularity reduces alert fatigue, enabling analysts to focus on alerts that weren’t blocked or mitigated by the SentinelOne EDR agent.

Detection rules for SentinelOne Threat events

In addition, Sekoia.io offers specific detection rules to identify potential malicious activity on the SentinelOne management console, such as successful brute force attacks or agents being disabled from the console.

Detection rules for SentinelOne Activity events

SentinelOne events ingested in Sekoia.io are normalized to the ECS format. Other detection rules from the Sekoia.io catalog can apply as well. For example, it’s possible to use the Sekoia Intelligence Feed rule to search for IoCs from Sekoia.io CTI in events. 

In the example below, a malicious code detected by SentinelOne also generated an alert raised by the Sekoia Intelligence Feed detection rule. This allows analysts to obtain more information about threats detected or blocked by the SentinelOne EDR agent. The alert contains information about a threat, campaign, and threat actor obtained from Sekoia.io CTI.

Sekoia Intelligence Feed alert on SentinelOne Threats

Analysts use the Sekoia platform to correlate SentinelOne Threat events with other logs collected by the platform, such as proxy, firewall, or NDR events. This approach makes it possible to retrace every step that led to the threat event.

Graph investigation of combined events and alerts from different sources (SentinelOne Threat event and Windows events)

Another feature of the Sekoia SOC platform is playbooks. SOC analyst launch them to remediate a threat from a SentinelOne alert. 

For instance, following an analysis of a SentinelOne alert, the analyst might deactivate the user account in Azure Active Directory. This action helps mitigate risks for user accounts with compromised credentials.

Launching a playbook from a SentinelOne alert

Ingest telemetry events in the Sekoia SOC platform

In addition to SentinelOne Threat and Activity events, it’s possible to ingest telemetry events in our SOC platform using SentinelOne Cloud Funnel 2.0. Telemetry events are activities captured by the SentinelOne EDR agent, such as process execution, network connections, DNS resolutions, and registry actions, even though the SentinelOne EDR agent triggers no threat events for them.

Check our public documentation to find more integration configuration details.

These events are beneficial to extend the detection capabilities using Sekoia. Sigma detection rules. More than 250 rules are currently available and compatible with this integration. 

The Sekoia Intelligence Feed rule, which looks for IoCs from Sekoia CTI in events, effectively assists in detecting threats based on the SentinelOne telemetry events. The Sekoia SOC platform's automatic retrohunt capabilities look for new IoCs in past telemetry events up to 30 days before the addition of new IoCs in the Sekoia database.

Sekoia Intelligence Feed alert

The example above shows that the SentinelOne EDR agent recorded a connection from an endpoint to a public IP address identified as malicious by Sekoia.io. Analysts can access all the context related to that IP address, such as malware, campaigns, and intrusion sets. 

Automating actions in SentinelOne from Sekoia

Playbooks can be launched from alerts to automate enrichment or remediation actions. Our SOC platform has several playbook actions, which allow customers to interact with different security solutions from the platform. The documentation for these actions is available here.

Current list of playbook actions available for SentinelOne

Enrichment or remediation actions can help to build a playbook for isolating an endpoint with the SentinelOne EDR agent from any alert raised by the Sekoia SOC platform.

Playbook to isolate an endpoint using SentinelOne EDR agent

In the future, the Sekoia.io team plans to add playbook actions for SentinelOne to the catalog. For example, we’ll add an action to disseminate IoCs from Sekoia to the SentinelOne management console.

Wrapping up

We’ve overviewed different integrations between the Sekoia SOC platform and the SentinelOne EDR agent, from retrieval of threat events to task automation. 

The partnership between SentinelOne and Sekoia.io is another milestone in building new integrations that bring more value to clients by combining the best cybersecurity solutions.