Jamf Pro Connector

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

Jamf is a mobile device management system focused on Apple devices. Its main capabilities include Apple devices inventory management, Zero-touch deployments, and controls to manage Apple device security, including enforcement of password policies, enabling remote security features, and fully controlling data stored on a device.

Tip: For more information on how third-party integrations work, see Connectors.

Connector Details

Details Description

Supported products

Jamf Pro

Category

Asset Inventory

Ingested data

Assets only

Ingested Asset Classes

Devices

Integration type

UNI directional (data is transferred from the Connector to Tenable Exposure Management in one direction)

Supported version and type

SaaS (latest)

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

  • Identify your Jamf Pro server URL (e.g. https://yourcompany.jamfcloud.com).

  • Create a Jamf Pro user account (username and password) with READ permissions to the Computers API endpoint.

Add a Connector

To add a new connector:

  1. In the left navigation menu, click Connectors.

    The Connectors page appears.

  2. In the upper-right corner, click Add new connector.

    The Connector Library appears.

  3. In the search box, type the name of the connector.

  4. On the tile for the connector, click Connect.

    The connector configuration options appear.

Configure the Connector

To configure the connector:

  1. (Optional) In the Connector's Name text box, type a descriptive name for the connector.

  2. (Optional) To use a preconfigured on-prem connector to connect to this connector, from the Gateway drop-down, select the on-prem connector you want to use for the connector. Otherwise, select Don't use gateway.

    Note: For information about configuring a gateway, see Tenable On-Prem Connector.

  3. In the Server URL text box, type the URL of your Jamf Pro server.

  4. In the Username and Password text boxes, paste the credentials for your Jamf Pro account.

  5. Data pulling configuration: This configuration has dynamic settings tailored to the specific connector and integration type. Below are the configurations relevant to this connector.

    • In the Asset Retention text box, type the number of days after which you want assets to be removed from Tenable Exposure Management. If an asset has not been detected or updated within the specified number of days, it is automatically removed from the application, ensuring your asset inventory is current and relevant.

      Tip: For more information, see Asset Retention.

  6. In the Test connectivity section, click the Test Connectivity button to verify that Tenable Exposure Management can connect to your connector instance.

    • A successful connectivity test confirms that the platform can connect to the connector instance. It does not, however, guarantee that the synchronization process will succeed, as additional syncing or processing issues may arise.

    • If the connectivity test fails, an error message with details about the issue appears. Click Show tests for more information about the exact error.

  7. In the Connector scheduling section, configure the time and day(s) on which you want connector syncs to occur.

    Tip: For more information, see Connector Scheduling.

  8. Click Create. Tenable Exposure Management begins syncing the connector. The sync can take some time to complete.

  9. To confirm the sync is complete, do the following:

Jamf Pro in Tenable Exposure Management

Locate Connector Assets in Tenable Exposure Management

As the connector discovers assets, Tenable Exposure Management ingests those devices for reporting.

To view assets by connector:

  1. In Tenable Exposure Management, navigate to the Assets page.

  2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view assets.

    The asset list updates to show only assets from the selected connector.

  3. Click on any asset to view Asset Details.

Data Mapping

Exposure Management integrates with the connector via API to retrieve relevant weakness and asset data, which is then mapped into the Exposure Management system. The following tables outline how fields and their values are mapped from the connector to Exposure Management.

Device Mapping

Tenable Exposure Management UI Field

Jamf Pro Field
Unique Identifier id
Asset - Name general.name or udid
Asset - Operating Systems operatingSystem.name

Asset - IPv4 Adresses

Asset - IPv6 Adresses

general.lastReportedIp
Asset - MAC Addresses hardware.macAddress
Asset - First Observation Date initialEntryDate

Asset - External Tags

assetTag

site.name
Asset Custom Attributes

operatingSystem.version

general.platform

udid

hardware.serialNumber

general.barcode1

general.barcode2

general.site.name

general.remoteManagement.managed

userAndLocation.username

userAndLocation.realname

userAndLocation.email

userAndLocation.phone

hardware.make

hardware.model

hardware.modelIdentifier

Status Update Mechanisms

Every day, Tenable Exposure Management syncs with the vendor's platform to receive updates on existing findings and assets and to retrieve new ones (if any were added).

The table below describes how the status update mechanism works in the connector for findings and assets ingested into Tenable Exposure Management.

Update Type in Exposure Management

Mechanism (When?)

Archiving Assets

Asset not seen for X days according to "Last Seen". See Asset Retention
Note: Updates on the vendor side are reflected in Tenable Exposure Management only when the next scheduled connector sync time is complete (once a day).

Uniqueness Criteria

Tenable Exposure Management uses defined uniqueness criteria to determine whether an ingested asset or finding should be recognized as a distinct record. These criteria help define how assets and findings are identified and counted from each connector.

Tip:  Read all about Third-Party Data Deduplication in Tenable Exposure Management .

The uniqueness criteria for this connector are as follows:

Data

Uniqueness Criteria

Asset

id

API Endpoints in Use

API version: starting from v10.25.0
Required Permissions

api/v1/auth/token

 Read

api/v1/computers-inventory

Computer Inventory - Device Assets

 Read

Data Validation

This section shows how to validate and compare data between Tenable Exposure Management and the Jamf Pro platform.

Asset Data Validation

Objective: Ensure the number of endpoints (devices) in Jamf Pro aligns with the number of devices displayed in Tenable Exposure Management.

In Jamf Pro:

  1. Navigate to Dashboard.

  2. Note the number of Managed and Unmanaged Computers.

In Tenable Exposure Management:

  1. Locate your connector assets.

  2. Compare the total number of assets between Jamf Pro and Tenable Exposure Management.

Expected outcome: The total numbers returned in Jamf Pro and Exposure Management should match.

If an asset is not visible in Exposure Management, check the following conditions:

  • Archived based on the last observed date (last seen).

    Tip: To learn more on how assets and findings change status, see Jamf Pro Connector.