SentinelOne¶
The SentinelOne integration will download data about hosts, and any CVE data. It fetches hosts known to SentinelOne, using the Agents and Network Discovery API, or Rouges API. The Agents API will collect host data from its network interfaces for the “secured” hosts. The Network Discovery (Rangers) API will be utilized for the “unsupported”, “unknown”, and “unsecured” hosts. If Network Discovery is not enabled, the integration will utilize the Rogues API. For CVE data collection, the Application Management Risks endpoint will be utilized.
Once downloaded, the data will be used to create two separate Input Framework files. One file includes CVE information, and the other contains Host information. These files can be used by Zeek scripts to generate new logs, or enrich existing logs, such as the known_hosts.log or suricata_corelight.log.
The input file will be published with any other input files from other integrations (if there are any). If “input” in enabled in the “push_content” settings, the file will automatically get pushed to the Fleet Manager policy and/or all sensors in the policy. See Push content settings for more details.
If the ‘interval_hours’ is set to 0, the integration will attempt to download additional content each time the Corelight-update service runs. See Configuration settings
Settings¶
sentinelone:
hosts_enabled: false
hosts_filename: hosts_data.tsv
cve_enabled: false
cve_filename: cve_data.tsv
interval_hours: 0
url: "" # required field
api_key: "" # required field
request_limit: 1000
debug: false
Hosts Input file¶
The input file contains the following information (if it’s available):
IP address (required)
MAC address
Hostname
Host Unique ID
OS version
Endpoint status
Machine domain
Description
Endpoint information source (required)
The following is a sample input file created by this integration, using tab-separated values.
#fields ip mac hostname host_uid os_version status machine_domain desc source
192.168.56.103 00-50-56-A3-B1-C2 WEF ced83f0c26493b638086fdc7b8b2c01d - Secured - Endpoint Host Data SentinelOne
10.21.0.102 00-50-56-A1-B1-C4 DC c53fdc3178ba36759c471d6b6655e324 - Unsecured - Endpoint Host Data SentinelOne
192.168.56.104 00-50-56-A2-B1-C2 WIN10 abb6c27309cf3730bb73e8cfd732d838 Windows 10 - lab.local Endpoint Host Data SentinelOne
192.168.1.155 92-91-E0-3E-66-A8 ss2oh 9caa11e26d1f371797e73e9b9199d481 - - - Endpoint Host Data SentinelOne
192.168.1.120 00-0C-29-AB-75-05 fleet 81f845fe72ae32168aba94707fc8a49f - - - Endpoint Host Data SentinelOne
192.168.12.1 - - 613cd0e8a671350e83dec735143db1e0 - - - Endpoint Host Data SentinelOne
192.168.12.210 - - 5f67453d7e833b0f82ac1d7a5788142a - - - Endpoint Host Data SentinelOne
192.168.12.222 - - 5abcec34b3443f3cb7fe17c4f7100e02 - - - Endpoint Host Data SentinelOne
192.168.12.212 00-50-56-A1-1F-07 skynet 439293445449716808dec735143db1e9 Ubuntu 22.04 - - Endpoint Host Data SentinelOne
CVE Input file¶
The input file contains the following information (if it’s available):
IP address (required)
Hostname
Host Unique ID
Machine domain
OS version
Endpoint information source (required)
CVE list
The following is a sample input file created by this integration, using tab-separated values.
#fields ip hostname host_uid machine_domain os_version source cve_list
192.168.56.10X DC fb5946b0422e4da49e4575995fb8XXXX windomain.local Windows Server 2016 SentinelOne Agents CVE-2022-26904,CVE-2022-34701,CVE-2020-0911,CVE-2022-24479,CVE-2020-1477
10.21.0.10X fleet 04a15f26ace249f68c583fd7be70XXXX - Ubuntu 20.04 SentinelOne Agents CVE-2020-12313,CVE-2020-12319,CVE-2022-36402,CVE-2022-38096,CVE-2022-38457
192.168.1.15X ss2oh 62c850ec617843f8959f1442843bXXXX - Ubuntu 20.04 SentinelOne Agents CVE-2020-12313,CVE-2020-12319,CVE-2022-36402,CVE-2022-38096,CVE-2022-38457
192.168.1.15X skynet fae3f73ce1404e0aae1626dbddfcXXXX - Ubuntu 22.04 SentinelOne Agents CVE-2020-12313,CVE-2016-1585,CVE-2022-36227,CVE-2022-45884,CVE-2023-22995,CVE-2022-38457
192.168.56.10X DC 34a6b864b61146d6ad051a9d63a5XXXX windomain.local Windows Server 2016 SentinelOne Agents CVE-2017-11771,CVE-2022-34718,CVE-2019-0736,CVE-2022-35744
192.168.56.10X WEF c6f3d2351739482baf36cc6e4af6XXXX windomain.local Windows Server 2016 SentinelOne Agents CVE-2017-11771,CVE-2022-34718,CVE-2019-0736,CVE-2022-35744
192.168.56.10X WEF 0bb70f50a9a3470dbc3e09bd6eb1XXXX windomain.local Windows Server 2016 SentinelOne Agents CVE-2022-26904,CVE-2022-34701,CVE-2020-0911,CVE-2022-24479
192.168.56.10X WIN10 a71be784db1a40e5b0fd7e6b73f6XXXX windomain.local Windows 10 SentinelOne Agents CVE-2021-36965,CVE-2021-43217,CVE-2022-22012,CVE-2020-9633,CVE-2021-24077
192.168.56.10X WIN10 23fac76b0e5246f8b8ba22d1bbd6XXXX windomain.local Windows 10 SentinelOne Agents CVE-2022-23279,CVE-2020-1286,CVE-2021-33784,CVE-2022-23299,CVE-2020-1391
Attention
The integration only creates the Input Framework files to be loaded on sensors. Additional Zeek scripts are required to be loaded on the sensors to use this data. If you enable these integrations, Corelight-update will upload the input files to the sensor. But if the desired script isn’t available on the sensor, the input data won’t be used.
See Zeek package management for information about using Corelight-update to manage Zeek package bundles.
See Zeek-Endpoint-Enrichment for an example of a Zeek package that can use this data.