SentinelOne Search Source
The SentinelOne Search Source collects alerts, agent inventory, vulnerabilities, and assets from a SentinelOne management console. Cribl Stream pulls the records on a schedule through the SentinelOne API.
Type: Pull | TLS Support: Yes | Event Breaker Support: Yes
TLS is enabled through HTTPS on the SentinelOne API.
Prerequisites
This Source needs an active Leader for job management.
Configure a SentinelOne Search Source
- On the top bar, select Products, and then select Cribl Stream. Under Worker Groups, select a Worker Group. Next, you have two options:
- To configure via QuickConnect, navigate to Routing > QuickConnect. Select Add Source and select SentinelOne Search from the list, choosing either Select Existing or Add New.
- To configure via the Routes, select Data > Sources. Select SentinelOne Search. Next, select Add Source.
- In the New Source modal, configure the following under General Settings:
- Input ID: Enter a unique name to identify this SentinelOne Search Source definition. If you clone this Source, Cribl Stream adds
-CLONEto the original Input ID. - Description: Optionally, enter a description.
- SentinelOne API token (text secret): Select or create a stored text secret that contains the API token.
- Management hostname: Enter the console hostname without the domain suffix, such as
usea1-yourorg. Omit the scheme, domain suffix, port, path, and credentials. - Domain suffix: Host suffix for the console. Defaults to
sentinelone.net. Selectsentinelone.milfor US military environments, or enter a custom suffix as dot-separated labels. - Tags: Metadata tags used for categorization and filtering in the Cribl Stream UI. These tags aren’t added to processed events. Use a tab or hard return between tag names.
- Input ID: Enter a unique name to identify this SentinelOne Search Source definition. If you clone this Source, Cribl Stream adds
- Under Content Types, review the collection schedules.
- Optionally, you can adjust the Processing, Retries, and Advanced settings, or Connected Destinations.
- Select Save, then Commit & Deploy.
Content Types
The content types are prefilled. Request parameters, pagination, and the request body are prefilled. Change the cron schedule, earliest time, and latest time when you need a different window.
| Content type | What it collects | Default cron | State tracking | Default state |
|---|---|---|---|---|
| Alerts | Cloud detection alerts | */5 * * * * | On | On |
| Agents | Agent inventory | 5 4,18 * * * | Off | On |
| Vulnerabilities | Application management risks | 2 */2 * * * | On | On |
| Alerts (Singularity) | Unified alerts from the Singularity Operations Center | */5 * * * * | On | Off |
| Vulnerabilities (Singularity) | Vulnerabilities from the Singularity Operations Center | 2 */2 * * * | On | Off |
| Assets | Asset surface endpoint inventory | 5 4,18 * * * | On | On |
Processing Settings
Fields
In this section, you can define new fields or modify existing ones using JavaScript expressions, similar to the Eval function.
- The Field Name can either be a new field (unique within the event) or an existing field name to modify its value.
- The Value is a JavaScript expression (enclosed in quotes or backticks) to compute the field’s value (can be a constant). Select this field’s advanced mode icon (far right) if you’d like to open a modal where you can work with sample data and iterate on results.
This flexibility means you can:
- Add new fields to enrich the event.
- Modify existing fields by overwriting their values.
- Compute logic or transformations using JavaScript expressions.
Pre-Processing
Auto parse: Toggle on to detect each event’s Datatype and extract top-level fields from _raw before Source Fields and before the pre-processing Pipeline or Pack. The toggle is off by default. Because Fields runs after automatic parsing, values you add there take precedence over same-named fields extracted from _raw. For Datatypes that automatic parsing can detect, see the List of Stock v2 Datatypes. For field behavior, prevention of duplicate parsing, and performance considerations, see Automatic Parsing.
Pipeline: Select an existing Pipeline or Pack to process data from this Source before routing.
Retries
Adjust how failed HTTP requests are retried.
Retry type: Defaults to Backoff.
Initial retry interval (ms): Defaults to 1000. Maximum 20000.
Retry limit: Defaults to 5.
Backoff multiplier: Defaults to 2.
Retry HTTP codes: Defaults to 429 and 503.
Honor Retry-After header: Defaults to toggled on. Cribl Stream caps the delay at 20 seconds.
Retry connection timeout: Toggle on to retry once after a connection timeout (ETIMEDOUT). Defaults to toggled off.
Retry connection reset: Toggle on to retry after a connection reset (ECONNRESET). Defaults to toggled off.
Advanced Settings
Request timeout (seconds): HTTP inactivity timeout. Defaults to 0, which disables the timeout.
Time to live: How long to keep the job’s artifacts on disk after the job finishes. Defaults to 4h.
Environment: If you’re using GitOps, optionally use this field to specify a single Git branch on which to enable this configuration. If empty, the configuration is enabled everywhere.
Connected Destinations
Select Send to Routes to enable conditional routing, filtering, and cloning of this Source’s data via the Routing table.
Select QuickConnect to send this Source’s data to one or more Destinations via independent, direct connections.
Troubleshooting
The Source’s configuration modal has helpful tabs for troubleshooting:
Live Data: Try capturing live data to see real-time events as they are ingested. On the Live Data tab, click Start Capture to begin viewing real-time data.
Logs: Review and search the logs that provide detailed information about the ingestion process, including any errors or warnings that may have occurred.
You can also view the Monitoring page that provides a comprehensive overview of data volume and rate, helping you identify ingestion issues. Analyze the graphs showing events and bytes in/out over time.