Breadcrumbs

Location Data Handling for SentinelOne

Connector Applicability

Applies to Source Connectors

SentinelOne

Applies to Destination Connectors

All

Assumptions

These instructions assume you have already setup a source connection in CI Sync for SentinelOne using the CI Sync instructions here: Add SentinelOne to SaaS Agent .

Pre-Read

Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.

  1. Understanding the use of CI Sync Connection Settings

  2. Rule 11 - Automatic Creation of new Location Master Data Records in ServiceNow for SentinelOne

  3. Rule 12 - Standard Asset Location Determination Rules for SentinelOne

  4. Rule 4 – Custom Asset Location Determination Rules

Locating and Amending the Connection Setting in the CI Sync UI

  1. Navigate to the Settings page

  2. Under the Source Connections heading (list), locate your SentinelOne connection.

  3. Click the Update link on the right hand side of the SentinelOne connection.

  4. Scroll down and locate the Section Heading and view the Individual Settings.

CleanShot 2026-06-24 at 17.48.48-20260624-074931.png


The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.

  1. Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.

Setting

Type

Additional Notes

Synchronize Locations

Slider

When enabled, the Location attribute will be set on each CI as a sys_id reference to the ServiceNow cmn_location table.

If not enabled, the Location attribute will not be set on each CI.

Synchronize Master Data

Slider

When enabled, unique Location values read from SentinelOne will be inserted to the Servicenow cmn_location table (i.e. the cmn_location table will be extended with new values read from SentinelOne).

If not enabled, the cmn_location table will not be extended with new Location values read from SentinelOne.

  1. After modify the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.

  2. You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.

Importantly

Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).

For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.

Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.