Skip to main content

SentinelOne

SentinelOne is an endpoint protection and threat response tool. You can bring application application install, device, threat intelligence, and security data from SentinelOne into Brinqa to construct a unified view of your attack surface and strengthen your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with SentinelOne and how to obtain that information from SentinelOne. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select SentinelOne from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate SentinelOne with Brinqa:

  • Server URL: The SentinelOne Server URL. The default URL format is https://<tenant>.sentinelone.com.

  • API token: The API token associated with the SentinelOne account, which must have permissions to log in to the API server and return data.

Generate a SentinelOne API token

For the SentinelOne connector to use the SentinelOne API, you must provide an API token from SentinelOne. SentinelOne does not allow retrieving the API token for an existing user. To generate a new API token, follow these steps:

  1. Log in to your organization's SentinelOne server as an administrator.

  2. Navigate to Settings > Users.

  3. Select the user for which you want to generate a new API token.

  4. Next to API Token, click Generate.

    Your new API token displays. You can not view the token again after this. Copy and save it to a secure location.

note

If you do not have the permissions to create a SentinelOne API token, contact your SentinelOne administrator. Consult SentinelOne documentation for accuracy.

Additional settings

The SentinelOne connector contains additional options for specific configuration:

  • Page size: The maximum number of records to get per API request. The default setting is 1000. It is not recommended to go over 1000.

  • Maximum retries: The maximum number of times that the integration attempts to connect to the SentinelOne API before giving up and reporting a failure. The default setting is 10.

  • Skip certificate verification: Select this option to allow for untrusted certificates.

Types of data to retrieve

The SentinelOne connector can retrieve the following types of data from the SentinelOne API:

Table 1: Data retrieved from SentinelOne

Connector ObjectRequiredMaps to Data Model
ApplicationNoPackage
Application InstallNoInstalled Package
DeviceYesHost
ThreatNoIncident
Threat DefinitionNoIncident Definition
VulnerabilityYesVulnerability
Vulnerability DefinitionYesVulnerability Definition
info

For detailed steps on how to view the data retrieved from SentinelOne in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

Application

Table 2: Application attribute mappings

Source Field NameSDM Attribute
app.nameNAME
app.osTypeOS_TYPE
app.publisherPUBLISHER
app.signedSIGNED
app.sizeSIZE
app.typeCATEGORIES
app.typeKIND
app.versionREVISION
Generated (MD5 of publisher, name, and version)UID
Application Install

Table 3: Application Install attribute mappings

Source Field NameSDM Attribute
app.agentComputerNameAGENT_NAME
app.agentIdAGENT_ID
app.agentIdTARGETS
app.createdAtSOURCE_CREATED_DATE
app.idUID
app.installedAtINSTALLED_DATE
app.riskLevelRISK
app.uidTYPE
app.updatedAtSOURCE_LAST_MODIFIED
Device

Table 4: Device attribute mappings

Source Field NameSDM Attribute
agent.accountIdACCOUNT_ID
agent.accountNameACCOUNT_NAME
agent.activeDirectory.computerDistinguishedNameCOMPUTER_DN
agent.activeDirectory.computerMemberOfCOMPUTER_MEMBER_OF
agent.activeDirectory.lastUserDistinguishedNameLAST_USER_DN
agent.activeDirectory.lastUserMemberOfLAST_USER_MEMBER_OF
agent.activeThreatsACTIVE_THREATS
agent.agentVersionAGENT_VERSION
agent.allowRemoteShellALLOW_REMOTE_SHELL
agent.appsVulnerabilityStatusVULNERABILITY_STATUS
agent.cloudProviders.*.cloudInstanceIdINSTANCE_ID
agent.computerNameDNS_NAMES
agent.computerNameHOSTNAMES
agent.computerNameNAME
agent.computerNamePRIVATE_DNS_NAMES
agent.consoleMigrationStatusCONSOLE_MITIGATION_STATUS
agent.coreCountCORE_COUNT
agent.cpuCountCPU_COUNT
agent.cpuIdCPU_ID
agent.createdAtSOURCE_CREATED_DATE
agent.detectionStateDETECTION_STATE
agent.domainDOMAIN
agent.encryptedApplicationsENCRYPTED_APPLICATIONS
agent.externalIdEXTERNAL_ID
agent.externalIpIP_ADDRESSES
agent.externalIpPUBLIC_IP_ADDRESSES
agent.firewallEnabledFIREWALL_ENABLED
agent.groupIdGROUP_ID
agent.groupNameGROUP_NAME
agent.idAGENT_ID
agent.idUID
agent.inRemoteShellSessionIN_REMOTE_SHELL_SESSION
agent.infectedINFECTED
agent.installerTypeINSTALLER_TYPE
agent.isActiveIS_ACTIVE
agent.isDecommissionedIS_DECOMMISSIONED
agent.isDecommissionedSTATUS
agent.isPendingUninstallIS_PENDING_UNINSTALL
agent.isUninstalledIS_UNINSTALLED
agent.isUpToDateIS_UPTO_DATE
agent.lastActiveDateLAST_ACTIVE
agent.lastActiveDateLAST_SEEN
agent.lastIpToMgmtIP_ADDRESSES
agent.lastIpToMgmtPRIVATE_IP_ADDRESSES
agent.lastLoggedInUserNameLAST_LOGGED_IN_USERNAME
agent.lastSuccessfulScanDateLAST_SUCCESSFUL_FULL_SCAN
agent.locations.nameLOCATIONS
agent.machineTypeCATEGORIES
agent.machineTypeMACHINE_TYPE
agent.machineSidMACHINE_SID
agent.mitigationModeMITIGATION_MODE
agent.mitigationModeSuspiciousMITIGATION_MODE_SUSPICIOUS
agent.modelNameMODEL
agent.networkInterfaces.inetIP_ADDRESSES
agent.networkInterfaces.inetPRIVATE_IP_ADDRESSES
agent.networkInterfaces.physicalMAC_ADDRESSES
agent.networkStatusNETWORK_STATUS
agent.operationalStateOPERATIONAL_STATE
agent.osArchOS_ARCH
agent.osNameOS_NAME
agent.osRevisionOS_REVISION
agent.osStartTimeLAST_STARTED
agent.osStartTimeOS_START_TIME
agent.osTypeOS_TYPE
agent.osType, agent.osRevision, agent.osArchDESCRIPTION
agent.osType, agent.osRevision, agent.osArchOPERATING_SYSTEM
agent.osUsernameOS_USERNAME
agent.rangerStatusRANGER_STATUS
agent.rangerVersionRANGER_VERSION
agent.registeredAtFIRST_SEEN
agent.registeredAtREGISTERED_AT
agent.scanAbortedAtSCAN_ABORTED_AT
agent.scanFinishedAtSCAN_FINISHED_AT
agent.scanStartedAtSCAN_STARTED_AT
agent.scanStatusSCAN_STATUS
agent.serialNumberSERIAL_NUMBER
agent.siteIdSITE_ID
agent.siteNameSITE_NAME
agent.threatRebootRequiredTHREAT_REBOOT_REQUIRED
agent.totalMemoryTOTAL_MEMORY
agent.updatedAtSOURCE_LAST_MODIFIED
agent.userActionsNeededUSER_ACTION_NEEDED
agent.uuidAGENT_UUID
Threat

Table 5: Threat attribute mappings

Source Field NameSDM Attribute
threat.agentRealtimeInfo.agentUuidTARGETS
threat.idUID
threat.threatInfo.createdAtFIRST_FOUND
threat.threatInfo.filePathPATH
threat.threatInfo.fileSizeFILE_SIZE
threat.threatInfo.incidentStatusDescriptionSOURCE_STATUS
threat.threatInfo.incidentStatusDescriptionSTATUS
threat.threatInfo.incidentStatusDescriptionSTATUS_CATEGORY
threat.threatInfo.mitigationStatusDescriptionMITIGATION_STATUS
threat.threatInfo.threatNameTYPE
threat.threatInfo.updatedAtLAST_FOUND
Threat Definition

Table 6: Threat Definition attribute mappings

Source Field NameSDM Attribute
threat.threatInfo.classificationCATEGORIES
threat.threatInfo.confidenceLevelCONFIDENCE_LEVEL
threat.threatInfo.threatNameNAME
threat.threatInfo.threatNameUID
Vulnerability

Table 7: Vulnerability attribute mappings

Source Field NameSDM Attribute
Generated (MD5 of vendor, name, and version)TARGETS
vulnerability.cveIdTYPE
vulnerability.daysDetectedDAYS_DETECTED
vulnerability.detectionDateFIRST_FOUND
vulnerability.endpointIdTARGETS
vulnerability.idUID
vulnerability.lastScanDateLAST_FOUND
vulnerability.lastScanResultLAST_SCAN_RESULT
vulnerability.markTypeMARK_TYPE
vulnerability.markedByMARKED_BY
vulnerability.markedDateMARKED_DATE
vulnerability.reasonREASON
vulnerability.statusPROVIDER_STATUS
vulnerability.statusSOURCE_STATUS
vulnerability.statusSTATUS
vulnerability.statusSTATUS_CATEGORY
Vulnerability Definition

Table 8: Vulnerability Definition attribute mappings

Source Field NameSDM Attribute
vulnerability.baseScoreCVSS_V3_BASE_SCORE
vulnerability.cveIdCVE_IDS
vulnerability.cveIdCVE_RECORDS
vulnerability.cveIdNAME
vulnerability.cveIdUID
vulnerability.publishedDatePUBLISHED_DATE
vulnerability.severitySEVERITY
vulnerability.severitySEVERITY_SCORE
vulnerability.severitySOURCE_SEVERITY

Data lifecycle management (DLM) strategy

The following table details the DLM strategy for the SentinelOne connector:

Table 9: SentinelOne DLM strategy

Connector ObjectInactivity ConditionPurge PolicySummary
DeviceLAST_SEEN NOT IN LAST 30 DAYS30 days after inactivityUses the LAST_SEEN attribute to identify devices that are inactive for 365 days, and then purges the records after 30 days of inactivity.
VulnerabilityInactivity is delegated to the Device object30 days after inactivityInactivity is determined by the lifecycle status of the associated device, and then purges the records after 30 days of inactivity.

Operation options

The SentinelOne connector supports the following operation options. See connector operation options for information about how to apply them.

Table 10: SentinelOne connector operation options

Connector ObjectOptionAll Possible ValuesDescriptionExample
DeviceisDecommissionedtrue, falseYou can use this option to filter retrieved devices based on their commissioned status, as determined by SentinelOne.Key: isDecommissioned Value: false. This key and value combination only retrieves devices that have not been decommissioned.
osTypeswindows, macos, linuxA comma-separated list of operating systems. You can use this option to retrieve data from SentinelOne that only contains the specified operating system.Key: osTypes Value: linux. This key and value combination only retrieves data from SentinelOne that pertains to the Linux operating system.
machineTypesdesktop, laptop, server, storage, kubernetes nodeA comma-separated list of machine types. You can use this option to retrieve data from SentinelOne that only contains the specified machine type.Key: machineTypes Value: desktop. This key and value combination only retrieves data from SentinelOne that pertains to desktop machines.
note

The option keys are case-sensitive and the possible values are in lowercase as they are shown in the documentation.

APIs

The SentinelOne connector uses the SentinelOne REST API. Specifically, it uses the following endpoints:

Table 11: SentinelOne API Endpoints

Connector ObjectAPI Endpoint
Application/web/api/v2.1/installed-applications
Application Install/web/api/v2.1/installed-applications
Device/web/api/v2.1/agents
Threat/web/api/v2.1/threats
Threat Definition/web/api/v2.1/threats
Vulnerability/web/api/v2.1/application-management/risks
Vulnerability Definition/web/api/v2.1/application-management/risks

Changelog

The SentinelOne connector has undergone the following changes:

Table 12: SentinelOne connector changelog

VersionDescriptionDate Published
3.2.7Bug Fixes
Application Install Date/Time Attributes
- Fixed the 'Application Install' model where 'Created at', 'Installed date', and 'Updated at' were stored as integer values instead of date/time. These fields now correctly reflect the timestamps returned by the SentinelOne API.
Migration Required
- 'Application Install': The 'Created at' attribute has been renamed to 'Source created date' and 'Updated at' has been renamed to 'Source last modified' to align with standard platform attributes. The 'Installed date' attribute type has changed from integer to date/time. A full re-sync of Application Install records is required after upgrading to apply the updated attribute names and types.
June 3rd, 2026
3.2.6Improvements
Dependency Upgrades
- Upgraded internal framework and storage libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform.
No Migration
June 3rd, 2026
3.2.5Code cleanup and general maintenance.October 11th, 2024
3.2.4Code cleanup and general maintenance.October 11th, 2024
3.2.3- The connector now uses the IS_DECOMMISIONED attribute to determine device status.
- Added a new operation option to filter devices by their decommissioned status: isDecommissioned.
October 10th, 2024
3.2.2Code cleanup and general maintenance.October 10th, 2024
3.2.1- Added more attributes to the Device object.
- Code cleanup and general maintenance.
October 10th, 2024
3.2.0- Changed the CVSS_V3_BASE_SCORE attribute type on the Vulnerability Definition object from string to double.
- Code cleanup and general maintenance.
October 9th, 2024
3.1.18Added support for Data lifecycle management to the Device and Vulnerability objects.September 27th, 2024
3.1.17The connector now retrieves the Threat, Threat Definition, Vulnerability, and Vulnerability Definition objects from SentinelOne.April 8th, 2024
3.1.16Updated dependencies.March 8th, 2024
3.1.15- Fixed some sync errors.
- Made the Application and Application Install objects optional.
September 13th, 2023
3.1.14Fixed an issue where the Device object sync was failing.September 13th, 2023
3.0.13Code cleanup and general maintenance.January 18th, 2023
3.0.12Code cleanup and general maintenance.December 10th, 2022
3.0.11The CATEGORY attribute on the Application and Device objects has been renamed to CATEGORIESDecember 8th, 2022
3.0.10Code cleanup and general maintenance.December 5th, 2022
3.0.9Code cleanup and general maintenance.December 5th, 2022
3.0.8Code cleanup and general maintenance.December 4th, 2022
3.0.7Added cloud metadata as a source for the Device object.December 4th, 2022
3.0.6Added the FIRST_SEEN attribute to the Device object.December 3rd, 2022
3.0.5Code cleanup and general maintenance.December 3rd, 2022
3.0.4Code cleanup and general maintenance.December 3rd, 2022
3.0.3Code cleanup and general maintenance.December 1st, 2022
3.0.2Updated the connector icon.December 1st, 2022
3.0.1Fixed an issue where the status for the Device object was not applied properly.November 15th, 2022
3.0.0Initial Integration+ release.November 14th, 2022