Skip to main content

SentinelOne Mgmt API Source


The SentinelOne Mgmt API Source collects data from the SentinelOne Management Console. It securely stores the required authentication, scheduling, and state tracking information.

Data collected

Polling IntervalData
5 minActivities
5 minAgents
5 minThreats


Vendor configuration

The SentinelOne Mgmt API Source requires authentication with a token associated with ApiToken. See how to generate an API Token from SentinelOne documentation. The following steps are provided as a guide.

To generate an API token:

  1. Sign in to the SentinelOne Management Console with Admin user credentials.
  2. In the Management Console, click Settings.
  3. In the Settings view, click Users.
  4. Click Service Users.
  5. Click Actions dropdown and select Create New Service User.
  6. Enter the information for the new service user.
  7. In Role, select Admin.
  8. Click Save.
  9. Log in to the SentinelOne Management Console with the credentials of the new user.
  10. Navigate to Settings > Users.
  11. Select the newly added service user.
  12. Click Options.
  13. Click Generate API token.
  14. Copy or download this API Token.

Source configuration

When you create a SentinelOne Mgmt API Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector.

To configure a SentinelOne Mgmt API Source:

  1. In the main Sumo Logic menu, select Manage Data > Collection > Collection.  
  2. On the Collectors page, click Add Source next to a Hosted Collector.
  3. Search for and select SentinelOne Mgmt API.
  4. Enter a Name to display for the Source in the Sumo web application. The description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM.

    Select Forward to SIEM only if you have Cloud SIEM installed.

  7. (Optional) Fields. Click the +Add Field link to define the fields you want to associate, each field needs a name (key) and value.
    • green check circle.png A green circle with a check mark is shown when the field exists in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema it is ignored, known as dropped. 
  8. Base URL. Provide your SentinelOne Management URL. It's in this format: https://<your_management_url>.
  9. API Token. Provide the API Token you got from the SentinelOne Management Console. See Authentication above for details.
  10. Supported APIs to collect. Select one or more of the available APIs: activities, agents, and threats.
  11. When you are finished configuring the Source, click Submit.

Metadata fields

_siemVendorSentinelOneSet when Forward To SIEM is checked.
_siemProductMGMT APISet when Forward To SIEM is checked.
_siemFormatJSONSet when Forward To SIEM is checked.
_siemEventIDactivities - {id}threats - {id}, or agentsSet when Forward To SIEM is checked and specific to the API collected.
_siemDataTypeInventorySet when Forward To SIEM is checked.

If you entered agents in Supported APIs to collect above, the _siemDataType field will be set to Inventory.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details. 

schemaRefJSON Object{"type":"SentinelOne Mgmt API"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Configuration Object

nameStringYesnullType a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source."mySource"
descriptionStringNonullType a description of the source."Testing source"
categoryStringNonullType a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details."mySource/test"
fieldsJSON ObjectNonullJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.{"_siemForward": false, "fieldA": "valueA"}
base_urlStringYesnullProvide your SentinelOne Management URL. It's in this format: https://<your_management_url>.
api_secretStringYesnullProvide your API Token from SentinelOne that you want to use to authenticate collection requests.
supported_apisArray of stringsYesnullDefine one or more of the available APIs to collect: activities, agents, and threats.
For example, for all three you'd use: ["activities","agents","threats"]

JSON example

"type":"SentinelOne Mgmt API"
Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "sentinelone_mgmt_api_source" {
collector_id =
schema_ref = {
type = "SentinelOne Mgmt API"
config = jsonencode({
resource "sumologic_collector" "collector" {
name = "my-collector"
description = "Just testing this"
Download example



Click here for more information about Cloud-to-Cloud sources.

Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.