Jamf
Visualize Jamf admins, users, groups, devices, and profiles, map Jamf users to employees, and monitor changes through queries and alerts.
- Installation guide
- Jamf data model
Installation
To use this integration, JupiterOne requires your Jamf hostname to interact with the API as well as a user's username and password used to authenticate with Jamf.
The JupiterOne integration uses the Classic API to fetch Jamf data.
Required Permissions:
- Read - Jamf Pro User Accounts & Groups
- Read - Users
- Read - Mobile Devices
- Read - Computers
- Read - Advanced Computer Searches
- Read - macOS Configuration Profiles
In JupiterOne
To install the Jamf integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Jamf. Click New Instance to begin configuring your integration, providing the following:
Account Name used to identify the Jamf account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when the AccountName option is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Hostname of your Jamf organization.
Username used to authenticate with Jamf.
Password associated with the username.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | jamf_account | Account |
Admin | jamf_user | User |
Computer | user_endpoint | Host , Device |
Computer Group | jamf_computer_group | Group |
Group | jamf_group | UserGroup |
Mobile Device | mobile_device | Device |
User | device_user | User |
macOS Configuration Profile | jamf_osx_configuration_profile | Configuration |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
device_user | HAS | mobile_device |
device_user | HAS | user_endpoint |
jamf_account | HAS | device_user |
jamf_account | HAS | jamf_group |
jamf_account | HAS | mobile_device |
jamf_account | HAS | jamf_osx_configuration_profile |
jamf_account | HAS | jamf_user |
jamf_account | HAS | user_endpoint |
jamf_computer_group | HAS | user_endpoint |
jamf_group | HAS | jamf_user |
user_endpoint | USES | jamf_osx_configuration_profile |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
jamf_local_account | USES | *user_endpoint* | REVERSE |
user_endpoint | INSTALLED | *macos_app* | FORWARD |