You can also download a PDF of this detection strategy guide.

Product Overview

SentinelOne's Singularity Data Lake is a unified, AI-powered platform designed to centralize and transform security and IT data into actionable intelligence. It converges SIEM, XDR, and analytics solutions into a comprehensive data ecosystem.

Detection Strategy for SIEM integrations

Detection

SIEM technology provides us with a helpful detection "backstop" for event telemetry. The detections are not authored by us, so how we ingest and action on the SIEM's alerts depends on the SIEM's category.

This SIEM integration is categorized as investigative-only. This means no alerts from the SIEM are ingested, but the SIEM can still be used by us for investigation telemetry. Therefore we strongly recommend you set up this integration in Workbench to increase the available investigative support.

Response

SIEM telemetry provides additional information that can be useful for us to disposition alerts. With the exception of investigative-only SIEMs, we will follow our normal event triage process and create an Expel Alert that is sent to our SOC analysts for analysis. We may also run queries against your SIEM logs to search for additional types of data, which we use to enrich our alerts with additional context.

What We Support for SentinelOne - Singularity Data Lake

To see a comprehensive list of the most up-to-date Expel detection rules, vendor detection rules, opt-in detections, and available DUETs (did you expect this) that we support for SentinelOne - Singularity Data Lake, you can visit the Detections page in Workbench, or ask your Sales or Support rep for the most recent download.

Additional Details & Common Questions

Console Access

A SIEM alert does not typically include all of the contextual timeline activity surrounding the event of interest. Because this integration does not allow us to get all necessary data via the API, we will ask you for a certain level of console access during onboarding. Granting it is optional, but is strongly recommended.

The level of access that we require is meant to support essential triage and research activities, and to help us determine the vector and extent of attacker activity for an identified threat. At minimum, we will ask for visibility into alert data, timeline events recorded, and live response/real time response shell (if applicable).

Historic Volume

We use historic volume to determine projected SIEM alert volume, which helps us decide whether or not a particular detection is appropriate to send to our SOC. We target 30 days as the ideal period of time to check on volume, and two weeks as the minimum.  This gives us the confidence we need to properly evaluate incoming SIEM alerts in a way that does not flood the SOC with benign activity.

DUET

A DUET (did you expect this) rule flags certain SIEM alerts as needing an immediate verification or notification, and bypasses the normal internal event triage process. The alerts subject to DUET rules contain behaviors that are not typically indicative of true security incidents, as they are related to policy violations or potential risk. 

There are a number of workflows that a DUET may follow. When enabled, the activity will be flagged for investigation and will be routed to you (rather than to us) to take a specified first action. To see the specific DUET rules currently supported for this integration, visit the Detections page in Workbench.

Use Cases Not Supported