Send SentinelOne logs to LogPulse
SentinelOne threats, STAR and custom-rule alerts and the activity log through the Management API, with a read-only service user token.
Configure → Sources → Cloud. LogPulse reads the SentinelOne Management API v2.1 itself, without an agent. Events land in the endpoint, audit indexes with source sentinelone and fill the Alert, Cloud Audit data models.Overview
- SentinelOne Management API v2.1 to Integration poller
- Integration poller to index=endpoint
- Integration poller to index=audit
LogPulse signs in to SentinelOne with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- Your console URL
- A service user API token with at least the Viewer role
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in SentinelOne
| Field in LogPulse | Where you find it |
|---|---|
| Console URL | The address of your console, such as https://<your-console>.sentinelone.net. |
| API token | Create a service user with the Viewer role (Settings, Users, Service Users) and use its token. Stored encrypted and never shown again. |
| Site IDs (optional) | Comma-separated. Leave empty for every site the token can see. |
| Isolation token (optional) | A service user whose role may disconnect endpoints from the network (for example IR Team). Stored encrypted and never shown again. |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose SentinelOne. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| Threats | endpoint | sentinelone | sentinelone_threat | Threats with confidence, mitigation status, verdict, file, hash and MITRE techniques. Sent again when their status changes. |
| STAR and custom-rule alerts | endpoint | sentinelone | sentinelone_alert | Cloud detection alerts with rule, severity and the process that triggered them. |
| Activity log | audit | sentinelone | sentinelone_activity | Console and agent activity: policy changes, agents uninstalled or disabled, console logins. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find SentinelOne without changes.
Fields and data models
| Data model | What you get |
|---|---|
| Alert | Threats and alerts in the shared alert shape with mitigation status and techniques. |
| Cloud Audit | Console and agent activity, with agent uninstall and disable marked as tampering. |
Events are mapped to the data models above, with the same field names as other sources of the same kind. See field names.
The original record of SentinelOne is kept with each event under raw, so nothing the vendor sent is lost.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (endpoint, audit) source IN (sentinelone)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| SentinelOne API token refused. | Create a service user under Settings, Users, Service Users with at least the Viewer role and use its token. Tokens expire; create a new one when it has. |
| consoleUrl must be https://<name>.sentinelone.net | Use the address of your management console. |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. SentinelOne may also simply have had nothing new. |
Frequently asked questions
- How do I send SentinelOne logs to LogPulse?
- Add the SentinelOne cloud integration under Configure, Sources, Cloud in LogPulse and fill in Console URL, API token. LogPulse reads the SentinelOne Management API v2.1 itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in SentinelOne?
- Your console URL. A service user API token with at least the Viewer role. Read access is enough for collecting logs.
- Which index does SentinelOne data go to?
- The index is the kind of data: endpoint, audit. The source is the product: sentinelone. Each data source has its own sourcetype, listed on this page.
- Which data models does SentinelOne fill?
- Alert, Cloud Audit. Detection rules and dashboards written for a data model work on SentinelOne without changes.