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.
-
Rule 13 – Synchronization or Suppression of Asset Tag in ServiceNow
-
Rule 15 – Which value is used for the Asset Tag attribute in ServiceNow for SentinelOne
Locating and Amending the Connection Setting in the CI Sync UI
The setting “Asset Tag Source Field” allows the selection of the source field to be mapped to the Asset Tag field in ServiceNow CIs.
Options are:
-
Serial Number - the Serial Number field value will be written to the Asset Tag field in ServiceNow CIs.
-
Null - the field value will be synchronized as null.
-
Navigate to the Settings page
-
Under the Source Connections heading (list), locate your SentinelOne connection.
-
Click the Update link on the right hand side of the SentinelOne connection.
-
Scroll down and locate the Section Heading and view the Individual Settings.
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.
-
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 |
|
Asset Tag Source Field |
Slider |
The setting “Asset Tag Source Field” allows the selection of the source field to be mapped to the Asset Tag field in ServiceNow CIs. Options are:
|
-
After modifying the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.
-
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.