
SentinelOne
Endpoint Protection- Overview
- Setup
- Data & mappings
- Operations & API
- Changelog
The SentinelOne connector integrates with the SentinelOne Singularity platform to synchronize endpoint security data into Brinqa. It collects managed devices (agents), installed applications, detected threats, and vulnerability findings, enabling continuous risk visibility across your endpoint estate. Vulnerability findings come from SentinelOne's xSPM vulnerabilities GraphQL API, which also provides each finding's resolved date and install path.
Data retrieved from SentinelOne
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Device | Yes | Host |
| Application | Yes | Package |
| Application Install | Yes | Installed Package |
| Threat | Yes | Incident |
| Threat Definition | Yes | Incident Definition |
| Vulnerability | Yes | Vulnerability |
| Vulnerability Definition | Yes | Vulnerability Definition |
Model relationships
For detailed steps on how to view the data retrieved from SentinelOne in the Brinqa Platform, see How to view your data.
Connection settings
When setting up a data integration, select SentinelOne from the Connector dropdown and provide the following:
| Setting | Required | Default | Description |
|---|---|---|---|
| Server URL | Yes | https://<tenant>.sentinelone.com | SentinelOne server URL |
| API token | Yes | — | SentinelOne API token |
| Page size | No | 1000 | Maximum number of records to get per API request |
| Maximum retries | No | 10 | The maximum number of retry attempts before giving up a request |
| Request timeout (secs) | No | 60 | Maximum seconds allotted before a request will time out. Maximum allowed value 1800 |
| Connect timeout (secs) | No | 180 | Maximum seconds to wait for a connection to SentinelOne to be established. Maximum allowed value 1800 |
| SSL / TLS | No | false | Skip certificate verification |
Authentication
SentinelOne uses a static API token passed in the Authorization header of every request.
Endpoint
| Method | URL |
|---|---|
| N/A — token is provisioned in the SentinelOne console | https://<tenant>.sentinelone.net/ |
Request Headers
| Header | Value |
|---|---|
Authorization | ApiToken <your-api-token> |
Accept | application/json |
Connectivity Test
On configuration, the connector validates the token by issuing a minimal request:
GET /web/api/v2.1/agents?skip=0&limit=1
Authorization: ApiToken <your-api-token>
Accept: application/json
Sample Response
{
"pagination": {
"totalItems": 1,
"nextCursor": null
},
"data": [
{
"id": "930561763530188959",
"uuid": "84099bea98d64f14af5c84d162504a35",
"computerName": "sentinelone-win-1"
}
]
}
A 2xx response confirms the token is valid; a 4xx response (parsed by the connector's error handler) indicates an invalid token or insufficient permissions.
Usage
Every API call includes the token directly in the request header — there is no token exchange or expiry flow:
Authorization: ApiToken <your-api-token>
The token is provisioned in the SentinelOne management console under Settings → Users → Service Users.
The Vulnerability and Vulnerability Definition models query the xSPM vulnerabilities GraphQL API with the same token. These requests are POSTs with a JSON body, so they also send Content-Type: application/json:
POST /web/api/v2.1/xspm/findings/vulnerabilities/graphql
Authorization: ApiToken <your-api-token>
Content-Type: application/json
Sync Behavior
The connector uses a mix of incremental and full syncs, depending on the model. Device, Application, Application Install, Vulnerability, and Vulnerability Definition support incremental (delta) syncs: the connector maintains a sync token between runs and applies it as an incremental timestamp filter, so each run re-processes only the records that changed after the previous sync. The initial run retrieves the complete data set; later runs are incremental. Threat and Threat Definition do not apply an incremental filter, so every run re-fetches all threats. The behavior and timestamp field for each object are documented under that object's Sync Duration Parameter.
How to obtain SentinelOne credentials
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:
-
Log in to your organization's SentinelOne server as an administrator.
-
Navigate to Settings > Users.
-
Select the user for which you want to generate a new API token.
-
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.
The token's user or service user needs the Extended Security Posture Management permission, at least View. A token without it can still sync devices, applications, and threats, but the Vulnerability and Vulnerability Definition syncs fail with a 404 error that names the missing permission. The xSPM API needs no additional license, and it is available on all SentinelOne-hosted consoles, including FedRAMP/GovCloud, but not on self-hosted consoles.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes:
Device
| Source Field Name | SDM Attribute |
|---|---|
agent.accountId | ACCOUNT_ID |
agent.accountName | ACCOUNT_NAME |
agent.activeDirectory.computerDistinguishedName | COMPUTER_DN |
agent.activeDirectory.computerMemberOf | COMPUTER_MEMBER_OF |
agent.activeDirectory.lastUserDistinguishedName | LAST_USER_DN |
agent.activeDirectory.lastUserMemberOf | LAST_USER_MEMBER_OF |
agent.activeThreats | ACTIVE_THREATS |
agent.agentVersion | AGENT_VERSION |
agent.allowRemoteShell | ALLOW_REMOTE_SHELL |
agent.appsVulnerabilityStatus | VULNERABILITY_STATUS |
agent.cloudProviders.*.cloudInstanceId | INSTANCE_ID |
agent.computerName | NAME |
agent.computerName | DNS_NAMES |
agent.computerName | HOSTNAMES |
agent.computerName | PRIVATE_DNS_NAMES |
agent.consoleMigrationStatus | CONSOLE_MITIGATION_STATUS |
agent.coreCount | CORE_COUNT |
agent.cpuCount | CPU_COUNT |
agent.cpuId | CPU_ID |
agent.createdAt | SOURCE_CREATED_DATE |
agent.detectionState | DETECTION_STATE |
agent.domain | DOMAIN |
agent.encryptedApplications | ENCRYPTED_APPLICATIONS |
agent.externalId | EXTERNAL_ID |
agent.externalIp | PUBLIC_IP_ADDRESSES |
agent.firewallEnabled | FIREWALL_ENABLED |
agent.groupId | GROUP_ID |
agent.groupName | GROUP_NAME |
agent.id | UID |
agent.id | AGENT_ID |
agent.infected | INFECTED |
agent.inRemoteShellSession | IN_REMOTE_SHELL_SESSION |
agent.installerType | INSTALLER_TYPE |
agent.isActive | IS_ACTIVE |
agent.isDecommissioned | STATUS |
agent.isDecommissioned | IS_DECOMMISSIONED |
agent.isPendingUninstall | IS_PENDING_UNINSTALL |
agent.isUninstalled | IS_UNINSTALLED |
agent.isUpToDate | IS_UPTO_DATE |
agent.lastActiveDate | LAST_SEEN |
agent.lastActiveDate | LAST_ACTIVE |
agent.lastIpToMgmt, agent.externalIp, agent.networkInterfaces.inet | IP_ADDRESSES |
agent.lastIpToMgmt, agent.networkInterfaces.inet | PRIVATE_IP_ADDRESSES |
agent.lastLoggedInUserName | LAST_LOGGED_IN_USERNAME |
agent.lastSuccessfulScanDate | LAST_SUCCESSFUL_FULL_SCAN |
agent.locations.name | LOCATIONS |
agent.locationType | LOCATION_TYPE |
agent.machineSid | MACHINE_SID |
agent.machineType | CATEGORIES |
agent.machineType | MACHINE_TYPE |
agent.mitigationMode | MITIGATION_MODE |
agent.mitigationModeSuspicious | MITIGATION_MODE_SUSPICIOUS |
agent.modelName | MODEL |
agent.networkInterfaces.physical | MAC_ADDRESSES |
agent.networkStatus | NETWORK_STATUS |
agent.operationalState | OPERATIONAL_STATE |
agent.osArch | OS_ARCH |
agent.osName | OS_NAME |
agent.osRevision | OS_REVISION |
agent.osStartTime | LAST_STARTED |
agent.osStartTime | OS_START_TIME |
agent.osType | OS_TYPE |
agent.osType, agent.osRevision, agent.osArch | DESCRIPTION |
agent.osType, agent.osRevision, agent.osArch | OPERATING_SYSTEM |
agent.osUsername | OS_USERNAME |
agent.rangerStatus | RANGER_STATUS |
agent.rangerVersion | RANGER_VERSION |
agent.registeredAt | FIRST_SEEN |
agent.registeredAt | REGISTERED_AT |
agent.scanAbortedAt | SCAN_ABORTED_AT |
agent.scanFinishedAt | SCAN_FINISHED_AT |
agent.scanStartedAt | SCAN_STARTED_AT |
agent.scanStatus | SCAN_STATUS |
agent.serialNumber | SERIAL_NUMBER |
agent.siteId | SITE_ID |
agent.siteName | SITE_NAME |
agent.threatRebootRequired | THREAT_REBOOT_REQUIRED |
agent.totalMemory | TOTAL_MEMORY |
agent.updatedAt | SOURCE_LAST_MODIFIED |
agent.userActionsNeeded | USER_ACTION_NEEDED |
agent.uuid | AGENT_UUID |
| Sync capture time | LAST_CAPTURED |
Application
| Source Field Name | SDM Attribute |
|---|---|
app.name | NAME |
app.osType | OS type |
app.publisher | Publisher |
app.signed | Signed |
app.size | Size |
app.type | CATEGORIES |
app.type | Kind |
app.version | Revision |
MD5(publisher:name:version) | UID |
| Sync capture time | LAST_CAPTURED |
Application Install
| Source Field Name | SDM Attribute |
|---|---|
app.agentComputerName | Agent name |
app.agentId | TARGETS |
app.agentId | Agent ID |
app.createdAt | Source created date |
app.id | UID |
app.installedAt | Installed date |
app.riskLevel | Risk |
app.uid | TYPE |
app.updatedAt | Source last modified |
| Sync capture time | LAST_CAPTURED |
Threat
| Source Field Name | SDM Attribute |
|---|---|
| Sync capture time | LAST_CAPTURED |
threat.agentRealtimeInfo.agentUuid → resolved to agent ID | TARGETS |
threat.id | UID |
threat.threatInfo.createdAt | FIRST_FOUND |
threat.threatInfo.filePath | PATH |
threat.threatInfo.fileSize | FILE_SIZE |
threat.threatInfo.incidentStatusDescription | SOURCE_STATUS |
threat.threatInfo.incidentStatusDescription | STATUS |
threat.threatInfo.incidentStatusDescription | STATUS_CATEGORY |
threat.threatInfo.mitigationStatusDescription | MITIGATION_STATUS |
threat.threatInfo.threatName | TYPE |
threat.threatInfo.updatedAt | LAST_FOUND |
Threat Definition
| Source Field Name | SDM Attribute |
|---|---|
| Sync capture time | LAST_CAPTURED |
threat.threatInfo.classification | CATEGORIES |
threat.threatInfo.confidenceLevel | CONFIDENCE_LEVEL |
threat.threatInfo.threatName | UID |
threat.threatInfo.threatName | NAME |
Vulnerability
| Source Field Name | SDM Attribute |
|---|---|
asset.category + asset.subcategory | MACHINE_TYPE |
MD5(vendor:name:version) + agent ID for asset.agentUuid | TARGETS |
software.cpeUri | CPE |
software.fixVersion | FIXED_VERSION |
software.fixVersionAvailable | FIXABLE |
software.name | APP_NAME |
software.name + software.version | APPLICATION |
software.paths | INSTALL_PATH |
software.vendor | PUBLISHER |
software.version | CURRENT_VERSION |
| Sync capture time | LAST_CAPTURED |
vulnerability.analystVerdict | ANALYST_VERDICT |
vulnerability.cve.id | TYPE |
vulnerability.detectedAt | FIRST_FOUND |
vulnerability.detectedAt to the sync time | DAYS_DETECTED |
vulnerability.externalId | UID |
vulnerability.externalId | NAME |
vulnerability.lastSeenAt | LAST_FOUND |
vulnerability.resolvedAt | LAST_FIXED |
vulnerability.status | PROVIDER_STATUS |
vulnerability.status | SOURCE_STATUS |
vulnerability.status | STATUS |
vulnerability.status | STATUS_CATEGORY |
vulnerability.updatedAt | SOURCE_LAST_MODIFIED |
Vulnerability Definition
| Source Field Name | SDM Attribute |
|---|---|
cve.epssScore | EPSS_SCORE |
cve.exploitedInTheWild | OBSERVED_IN_THE_WILD |
cve.exploitMaturity | EXPLOIT_MATURITY |
cve.id | UID |
cve.id | NAME |
cve.id | CVE_IDS |
cve.id | CVE_RECORDS |
cve.nvdBaseScore | CVSS_V3_BASE_SCORE |
cve.publishedDate | PUBLISHED_DATE |
cve.remediationLevel | REMEDIATION_LEVEL |
cve.reportConfidence | REPORT_CONFIDENCE |
cve.riskScore | RISK_SCORE |
software.type | CATEGORIES |
software.vendor + software.name | TAGS |
| Sync capture time | LAST_CAPTURED |
vulnerability.name | DESCRIPTION |
vulnerability.severity | SEVERITY |
vulnerability.severity | SEVERITY_SCORE |
vulnerability.severity | SOURCE_SEVERITY |
Operations & API
Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).
Device
Operation options
This object does not support any operation options.
Delta sync
Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on lastActiveDate.
API
- Type: REST · Endpoint:
GET /web/api/v2.1/agents - Default filters:
lastActiveDate__gte(applied only when an incrementalsinceis provided)
Application
Operation options
This object does not support any operation options.
Delta sync
Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on installedAt.
API
- Type: REST · Endpoint:
GET /web/api/v2.1/installed-applications - Default filters:
installedAt__between(applied only when an incrementalsinceis provided)
Application Install
Operation options
This object does not support any operation options.
Delta sync
Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on installedAt.
API
- Type: REST · Endpoint:
GET /web/api/v2.1/installed-applications - Default filters:
installedAt__between(applied only when an incrementalsinceis provided)
Threat
Operation options
This object does not support any operation options.
Delta sync
Not supported. The connector performs a full sync of Threat on every run and applies no incremental date filter.
API
- Type: REST · Endpoint:
GET /web/api/v2.1/threats - Default filters: None applied directly to the threats endpoint
Threat Definition
Operation options
This object does not support any operation options.
Delta sync
Not supported. The connector performs a full sync of Threat Definition on every run and applies no incremental date filter.
API
- Type: REST · Endpoint:
GET /web/api/v2.1/threats - Default filters: None applied directly to the threats endpoint
Vulnerability
Operation options
| Option | Type | Default | Description |
|---|---|---|---|
endpointTypes | String (comma-separated) | — | Endpoint machine types to sync (only findings on those endpoints are synced), for example desktop,laptop. The connector translates them into xSPM asset filters: desktop and laptop match the Desktop and Laptop asset subcategories, and server matches the Server asset category, so every kind of server is included. Any combination can be selected. Other values are logged and ignored; if none of the values is supported, the sync fails rather than syncing every asset type. |
Delta sync
Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on detectedAt.
API
- Type: GraphQL query · Endpoint:
POST /web/api/v2.1/xspm/findings/vulnerabilities/graphql - Default filters:
productisSingularity Vulnerability Management, so only findings from SentinelOne's own agent scans are synced. xSPM also holds cloud, container, and third-party findings, which the connector does not sync.
query Vulnerabilities($first: Int, $after: String, $filters: [FilterInput!],
$orFilter: OrFilterSelectionInput, $sort: SortInput) {
vulnerabilities(first: $first, after: $after, filters: $filters,
orFilter: $orFilter, sort: $sort) {
totalCount
pageInfo { hasNextPage endCursor }
edges {
node {
id externalId name status severity
detectedAt lastSeenAt updatedAt resolvedAt analystVerdict
cve { id nvdBaseScore riskScore epssScore exploitedInTheWild
exploitMaturity remediationLevel reportConfidence publishedDate }
software { name version vendor fixVersion fixVersionAvailable paths
type cpeUri }
asset { agentUuid category subcategory }
}
}
}
}
- Options written for the earlier REST risks endpoint, other than
endpointTypes, have no xSPM equivalent. They are logged and ignored instead of being sent to SentinelOne. - xSPM's search index can trail a change by a moment. Each delta window starts at the previous sync's start time, so a change made during a sync is picked up by the next one.
- Vulnerability and Vulnerability Definition share the findings fetched in a data integration run: whichever syncs first fetches them, and the other reuses them. Configure the same operation options, such as
endpointTypes, on both; otherwise the second sync uses the first one's filters.
Vulnerability Definition
Operation options
| Option | Type | Default | Description |
|---|---|---|---|
endpointTypes | String (comma-separated) | — | Endpoint machine types to sync (only CVE definitions for findings on those endpoints are synced), for example desktop,laptop. The connector translates them into xSPM asset filters: desktop and laptop match the Desktop and Laptop asset subcategories, and server matches the Server asset category, so every kind of server is included. Any combination can be selected. Other values are logged and ignored; if none of the values is supported, the sync fails rather than syncing every asset type. |
Delta sync
Supported. The connector performs an incremental (delta) sync via the since sync token, filtering on detectedAt.
API
- Type: GraphQL query · Endpoint:
POST /web/api/v2.1/xspm/findings/vulnerabilities/graphql - Default filters:
productisSingularity Vulnerability Management, so only findings from SentinelOne's own agent scans are synced. xSPM also holds cloud, container, and third-party findings, which the connector does not sync.
query Vulnerabilities($first: Int, $after: String, $filters: [FilterInput!],
$orFilter: OrFilterSelectionInput, $sort: SortInput) {
vulnerabilities(first: $first, after: $after, filters: $filters,
orFilter: $orFilter, sort: $sort) {
totalCount
pageInfo { hasNextPage endCursor }
edges {
node {
id externalId name status severity
detectedAt lastSeenAt updatedAt resolvedAt analystVerdict
cve { id nvdBaseScore riskScore epssScore exploitedInTheWild
exploitMaturity remediationLevel reportConfidence publishedDate }
software { name version vendor fixVersion fixVersionAvailable paths
type cpeUri }
asset { agentUuid category subcategory }
}
}
}
}
- Options written for the earlier REST risks endpoint, other than
endpointTypes, have no xSPM equivalent. They are logged and ignored instead of being sent to SentinelOne. - xSPM's search index can trail a change by a moment. Each delta window starts at the previous sync's start time, so a change made during a sync is picked up by the next one.
- Vulnerability and Vulnerability Definition share the findings fetched in a data integration run: whichever syncs first fetches them, and the other reuses them. Configure the same operation options, such as
endpointTypes, on both; otherwise the second sync uses the first one's filters.
Changelog
The SentinelOne connector has undergone the following changes:
| Version | Description | Migration Steps |
|---|---|---|
| 3.3.0 | New Features Resolved Date and Install Path for Vulnerabilities - Vulnerability findings now come from SentinelOne's xSPM vulnerabilities API, which adds Last fixed (the date SentinelOne resolved the finding), Install path, Fixed version and Fixable to each Vulnerability. Vulnerability Definitions add Description, Categories, Tags (the vendor and name of each affected software), EPSS score, Exploit maturity and Observed in the wild, and take CVSS v3 base score from the NVD base score. Vulnerabilities also add Source last modified (when the finding last changed in SentinelOne), Analyst verdict and CPE, and Vulnerability Definitions add SentinelOne risk score, Remediation level and Report confidence. The SentinelOne API token's user needs the Extended Security Posture Management permission (at least View); without it, the Vulnerability and Vulnerability Definition syncs fail. The xSPM API is not available on self-hosted SentinelOne consoles. Existing findings pick up the new attributes the next time they change; run a full sync to populate them for all findings at once. Vulnerability Attributes No Longer Provided - Last scan result, Mark type, Marked by, Marked date and Reason are no longer populated on Vulnerabilities, because the xSPM API does not provide them. Status changes are now reflected in the Vulnerability status instead. Vulnerability Options - The endpointTypes option (desktop, laptop, server) continues to work as before. Other values are ignored; if none of the selected values is supported, the sync fails instead of syncing every endpoint type. Other options that were passed to SentinelOne's REST risks API as filters (for example severities or osTypes) are no longer applied, so a sync that used them now also includes the findings they used to exclude; such options are noted in the connector log. Status Changes from the SentinelOne Console - Status changes made in the SentinelOne console are now synced. A finding marked Risk Acknowledged or Suppressed shows as risk accepted, and To Be Patched or On Hold as active; the REST API used previously did not report these status changes. Configurable Request Timeouts - Request timeout (secs) and Connect timeout (secs) can now be set on the integration. Large tenants whose SentinelOne API responses are slow can raise the request timeout without a connector update. Defaults are unchanged (60 and 180 seconds); the maximum is 1800 seconds. Improvements Request Failure Diagnostics - Failed SentinelOne API requests now log the HTTP status, endpoint and request parameters for every attempt, including retries, so it is clear whether a request timed out or was rejected by the API. Error responses that are not JSON, such as gateway error pages, are now logged with their content instead of a parsing stack trace. Longer Retry Window for SentinelOne Outages - A SentinelOne API request that keeps failing is now retried for up to 60 minutes before the sync fails, instead of 15. Long syncs, such as a large Vulnerability collection, can now ride out a temporary SentinelOne outage instead of failing and starting again from the beginning on the next run. The Maximum retries setting still applies: with the default 60-second request timeout, each attempt plus the wait before the next can take about 2 minutes, so set Maximum retries to 30 or more to use the full window (15 is enough if the request timeout is raised to 180 seconds). Faster Failure on Authentication Errors - A sync now fails as soon as SentinelOne rejects the API token, for example because it expired or was revoked, or lacks a required permission, instead of retrying for up to an hour first. The error message names the cause, so an expired token can be replaced straight away. Bug Fixes Per-Sync Retry Limit - A maximum-retries value set on an individual data integration sync is now applied to SentinelOne API requests. Previously it was ignored and the connector-level Maximum retries setting was always used. Incomplete Device Collection Reported as Success - A SentinelOne API error while collecting devices now fails the Device sync. Previously the error was only logged and the sync completed with the devices fetched before the error, and a Threat sync in the same run could use that incomplete device list to link threats to their devices. Partial Data Reused Across Syncs - Syncs in the same data integration run share collected data: Vulnerability Definition reuses Vulnerability data, Threat reuses Device data, Threat Definition reuses Threat data, and Application Install reuses Application data. If the first sync stopped part-way, for example during a SentinelOne outage, the later sync could reuse the partial data and report success. Data is now shared only after it has been collected in full; otherwise the later sync collects it again. | N/A |
| 3.2.10 | New Features Last Captured on All Models - Device, Application, Application Install, Threat, Threat Definition, Vulnerability, and Vulnerability Definition records now carry a Last captured attribute recording when the sync captured the record. All records from a single sync share the same value, so the attribute can be used to tell which records were refreshed by the most recent run and to spot data that has stopped being reported. Application Identity on Vulnerability - Vulnerability records now include Application, Application name, Publisher, and Current Version attributes describing the software the finding was reported against. Previously this information was only reachable through the related Application asset, so findings that shared a CVE and endpoint but affected different applications were indistinguishable in Manage Vulnerabilities. These attributes are queryable and can be used for grouping and filtering. Existing attributes and relationships are unchanged. | N/A |
| 3.2.9 | Improvements Vulnerability Definition Deduplication - When several vulnerability records report the same CVE, the resulting Vulnerability Definition now reflects the most recently processed record rather than the first one seen. This makes Vulnerability Definition deduplication consistent with the other definition models and removes a per-record lookup from the sync path. | N/A |
| 3.2.8 | Improvements Device Type Filtering for Vulnerability Sync - Vulnerability synchronization can now be restricted to specific device machine types by configuring an endpointTypes filter (for example desktop,laptop) — SentinelOne's native device-type filter on the risks endpoint. When set, only vulnerabilities for the selected device types are imported, reducing the amount of data pulled from SentinelOne. Filters that accept multiple selected values are combined and applied correctly. Machine Type on Vulnerability - Vulnerability records now include a Machine type attribute identifying the affected endpoint's device type (server, desktop, laptop, etc.). | • Vulnerability: Re-sync Vulnerability records after upgrading to populate the new Machine type attribute. |
| 3.2.7 | Bug 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. | • 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. |
| 3.2.6 | Improvements 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. | N/A |
| 3.2.5 | Bug Fixes Device Status - Corrected the Device status mapping so that decommissioned endpoints are now reported as inactive and active endpoints as active. Previously these values were inverted, which could mislabel a device's operational status. | N/A |
| 3.2.4 | Improvements Containerized Workload Visibility - Device records now include container workload counts, giving better visibility into endpoints running containerized workloads. Bug Fixes Device Serialization - Resolved a serialization issue that could prevent certain Device records from syncing reliably. | N/A |
| 3.2.3 | Improvements Device Operational State and Decommissioned Devices - Added an Operational state attribute to Device records. - The connector now retrieves both active and decommissioned endpoints and uses the decommissioned flag to determine device status, so that retired endpoints are reflected accurately. | N/A |
| 3.2.2 | Improvements Vulnerability Removals - Vulnerability syncs now always include removed vulnerabilities, ensuring that findings resolved or no longer present in SentinelOne are reflected and aged out correctly. | N/A |
| 3.2.1 | Improvements Additional Device Attributes - Device records now include additional details such as Active Directory and location information. Vulnerability Sync Accuracy - Vulnerability syncs now filter by risk-updated date and include removed vulnerabilities during incremental syncs, so that resolved findings are aged out correctly and updates are captured more reliably. | N/A |
| 3.2.0 | Bug Fixes Vulnerability Definition CVSS Score Type - Fixed the CVSS V3 Base Score attribute on Vulnerability Definition so that it is stored as a numeric value instead of text, enabling correct numeric filtering, sorting, and scoring. | • Vulnerability Definition: The CVSS V3 Base Score attribute type has changed from text to a decimal number. A full re-sync of Vulnerability Definition records is required after upgrading so the score is stored with the correct data type. |
| 3.1.18 | Improvements Device and Vulnerability Lifecycle - Device records now age out automatically when an endpoint has not been seen for several days, and Vulnerability findings follow the lifecycle of their associated device. - Added a Provider status attribute to Vulnerability records to preserve the original status reported by SentinelOne alongside the normalized status. | N/A |
| 3.1.17 | New Features Threat and Vulnerability Models - Added support for syncing Threat and Threat Definition records, surfacing SentinelOne threat detections as incidents. - Added support for syncing Vulnerability and Vulnerability Definition records, bringing SentinelOne application vulnerability data into the platform. | N/A |
| 3.1.16 | Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform. | N/A |
| 3.1.15 | Improvements Hostname Normalization and DNS Names - Device hostnames are now normalized and stored in lowercase, and DNS names and Private DNS names are now captured for each Device. This improves correlation and matching of endpoints across data sources. | • Device: Hostnames are now normalized to lowercase and additional DNS name attributes are populated. A full re-sync of Device records is required after upgrading to apply the normalized values. |
| 3.1.14 | New Features Configurable Retry Limit - Added a Maximum retries configuration option, letting you control how many times the connector retries a request before giving up. This improves resilience against transient API errors and rate limiting. Bug Fixes Application Filtering - Predefined applications are no longer incorrectly excluded during filtering, so the full set of installed applications is captured. | N/A |
| 3.0.13 | Improvements Application Type Attribute - Renamed the Application type attribute from Type to Kind to avoid conflicting with a reserved platform attribute name. | • Application: The Type attribute has been renamed to Kind. A full re-sync of Application records is required after upgrading to apply the renamed attribute. |
| 3.0.12 | Improvements Identifier Mapping - Standardized how Device, Application, and Application Install records are identified by adding the source UID as an explicit identifier. This makes record matching and correlation more consistent. | • Device, Application, Application Install: The identifier configuration for these models has changed. A full re-sync of these records is required after upgrading so they are re-keyed correctly. |
| 3.0.11 | Improvements Asset Categories - Device and Application records now populate the standard Categories attribute (replacing the prior single Category value), aligning these endpoints and applications with the platform's standard asset categorization. | • Device, Application: The single Category attribute has been replaced by the multi-valued Categories attribute. A full re-sync of these records is required after upgrading to apply the updated attribute and values. |
| 3.0.10 | Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform. | N/A |
| 3.0.9 | Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform. | N/A |
| 3.0.8 | Improvements Network Address Collection - Device records now collect private IP addresses and MAC addresses from all network interfaces into the multi-valued Private IP addresses, IP addresses, and MAC addresses attributes, replacing the prior single-value IP and MAC attributes. Loopback and placeholder addresses are excluded. | • Device: The single-value IP and MAC address attributes have been replaced by multi-valued private IP, IP, and MAC address attributes. A full re-sync of Device records is required after upgrading to apply the updated attributes. |
| 3.0.7 | Improvements Cloud Endpoint Metadata - Device records now capture cloud instance identifiers for AWS, Azure, and GCP endpoints, along with Source created date, Source last modified, and Last started timestamps. The set of attributes used to match devices was also refined to improve correlation of cloud endpoints. | • Device: The attributes used to identify and match devices have changed (cloud instance ID was added and the address-based matching was refined). A full re-sync of Device records is required after upgrading so devices are re-keyed correctly. |
| 3.0.6 | Improvements First Seen Date - Device records now include a First seen date reflecting when the endpoint was first registered with SentinelOne. | N/A |
| 3.0.5 | Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform. | N/A |
| 3.0.4 | Improvements Device Hostname and Timestamps - Device records now populate a dedicated Hostname attribute and store the Last seen and Created at timestamps as proper date/time values rather than raw numbers. The set of attributes used to match devices was also refined to use hostname instead of name. | • Device: The Last seen and Created at attributes are now stored as date/time values, and the device matching attributes changed. A full re-sync of Device records is required after upgrading to apply the updated attribute types and identifiers. |
| 3.0.3 | Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform. | N/A |
| 3.0.2 | Improvements Connector Icon - Updated the connector to use the official SentinelOne icon. | N/A |
| 3.0.1 | Bug Fixes Device Status - Fixed Device status reporting so that inactive endpoints are correctly marked as inactive. | N/A |
| 3.0.0 | Overview The SentinelOne connector integrates with SentinelOne to synchronize endpoint devices and the applications installed on them. Category: Endpoint Protection Models | N/A |