Breadcrumbs

PII Handling for Jamf

Connector Applicability

Applies to Source Connectors

Jamf

Applies to Destination Connectors

All

Assumptions

These instructions assume you have already setup a source connection in CI Sync for Jamf using the CI Sync instructions here: Add Jamf 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 9 - Synchronization of a Jamf User Oriented Attribute for Assigned_To or Owned_By in ServiceNow

  3. Rule 10 - Suppress Synchronization of Jamf Mobile Device PII Attributes to CI Records

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 Jamf connection.

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

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

CleanShot 2026-05-21 at 10.30.37@2x-20260521-003433.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

Suppress PII

(Suppress Mobile Device PII Attributes)

Slider

If not enabled, CI Sync will set the original/real values of the following attributes on each CI, for Jamf Mobile Devices (iPad, iPhone, Android):

  • Device Name

  • Phone Number

If enabled, CI Sync will replace the original/real values with “+SUPPRESSED+” when persisting the above attributes on each CI.

Enable assigned_to user synchronization

Slider

When enabled, CI Sync will read the userAndLocation.email attribute from each Jamf device and then do the following:

  1. Search for a matching email address in the ServiceNow sys_user table using the sys_user.email attribute.

  2. Set the Assigned_To attribute on the CI record (in the CMDB) with a reference to the corresponding user record in sys_user.

By doing the above, each Jamf CI in the CMDB should end up with an Assigned_To value set to a known ServiceNow user record.

Important note about PII

This setting may have PII implications.

The setting should only be enabled if you (the customer) have considered the PII implications.

By enabling this setting CI Sync will do the following:

  1. Transit the value of the source attribute read from Jamf (by default the email address of each user).

  2. Persist the value of the sys_user.email addresses (so CI Sync can correlate/match the incoming Jamf email address with a sys_user.email address to obtain the sys_id of the corresponding user record).

  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.