# SailPoint Jamf Shared Signals Documentation > Jamf Shared Signals Documentation # Documentation # Connecting SailPoint with Jamf Use the following configuration options to set up the connection with Jamf: ## Adding the Receiver in SailPoint Follow these steps to configure the receiver: > [!NOTE] > > **Screenshot** > > [![Add Receiver]()]() 1. Go to **Admin \> Connections \> Shared Signals**. 2. Select **Continue** on the **Receiver Streams** card. 3. Select **Create New** button to initiate the creation of a new SSF Receiver. 4. Provide the necessary information for the new receiver: 1. **SSF Receiver Name**: Enter a descriptive name for the new receiver. Choose a name that clearly identifies the purpose or origin of the receiver. For example, `Jamf Pro SSF Receiver` 2. **Description**: Enter a brief description for the new receiver. Provide any additional details that will help distinguish this receiver from similar ones and clarify its purpose. 5. Select **Save** to create the new SSF Receiver based on the provided information. ## Connection Settings To connect to Jamf and establish the SSF integration, provide the following information: > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select the **Authentication Type** as API Token ONLY. 2. Enter the **API token** provided by Jamf for authentication. For API Token and Discovery URL, refer to [SSF Stream Registration in Jamf Security Cloud](). 3. Enter the **Discovery URL** of the Jamf transmitter to discover and connect to the SSF event stream. This URL should be provided by Jamf and is called a Well known URL in the Jamf SSF stream details page. For example, `https://ssf.caep.dev/.well-known/ssf-configuration`. 4. Select the **Event Types** as `CAEP Device Compliance` to receive the device compliance related event details from Jamf. 5. The **Stream Status** field indicates the current status of the SSF event stream connection. It will display the connection status once the configuration is saved. This field is visible only after you have created a stream. - To ensure that the stream is properly created and active, use the **Create Stream** option to create the SSF event stream. After creating the stream, the status should display as `Enabled` if the stream is successfully established. - To verify the stream status and connectivity, select the **Verify Stream** button. If the verification is successful, the stream is properly configured and ready to receive events from Jamf. For more information, refer to [When should I use the Verify button for JAMF event streams?]() # Frequently Asked Questions This Frequently Asked Questions (FAQs) section provides answers to the most commonly asked questions for the Jamf connector. ## When should I use the Verify button for Jamf event streams? Use the **Verify** button when: - Event transmission frequency is low - You need to confirm the stream is configured correctly - You want to test end-to-end delivery, including signature verification and encryption The **Verify** button allows you to send a Verification Event to confirm whether the stream is correctly configured. # Integrating SailPoint with Jamf Using SSF The Shared Signals Framework (SSF) is a security architecture that allows different security solutions to share and consume security events and alerts. This integration allows real-time sharing of security events related to Apple devices. For more information about SSF, refer to [Shared Signals Framework](). In this architecture: - Jamf acts as the Transmitter, monitoring the security state of managed Apple endpoints. - The SailPoint serves as the Receiver, enforcing access policies based on device trust signals. By leveraging the SSF Receiver, organizations can significantly reduce the time it takes to detect, respond to, and remediate identity-related threats. Jamf sends security events to SailPoint, which correlates them with identity data, providing comprehensive visibility and triggering workflow based on the received signals. Key benefits of integrating Jamf with SailPoint include: - Device State Monitoring (Jamf - Transmitter) Jamf continuously monitors all managed devices for compliance with your organization's security baseline. This includes checks for: - Operating system updates and patch level - FileVault disk encryption - Firewall and Gatekeeper configurations - Presence and status of required security tools - Compliance Deviation Detection If a device falls out of compliance, when a required setting is disabled or unauthorized software is detected, Jamf immediately flags this change. - Real-Time Signal Transmission Upon detecting a compliance change, Jamf generates a Security Event Token (SET). This token contains: - Subject Identifier - Device Identifier - Previous and current compliance status - Timestamp and contextual metadata - Jamf transmits this SET in real time to the SailPoint's SSF endpoint. - Receiver-Side Workflow: Policy Enforcement The SailPoint (Receiver) evaluates the incoming device-compliance-change signal and initiates appropriate policy response based off predefined Workflows. For example, if the device status changes to non-compliant, a Workflow would initiate the following: - Notify the device owner's manager - Admin alerts via a ticketing systems - Disable access to accounts or sensitive entitlements This real-time, event-driven architecture supports Zero Trust principles by enabling dynamic access decisions based on the current compliance state of a user's device. It eliminates reliance on periodic polling or manual intervention - delivering a scalable, automated, and secure model for device-aware access control. This guide provides specific information about configuring Jamf and SailPoint using Shared Signal Framework. ## Supported Features The SSF integration between Jamf Security Cloud (integrated with Jamf Pro) and SailPoint supports the following features: - Real-time transmission of DEVICE\_COMPLIANCE\_CHANGE events from Jamf Security Cloud to SailPoint. - Event mapping and correlation of device compliance changes with user identities in SailPoint. - Workflow triggered by CAEP Device Compliance Change Events. For more information, refer to [Workflow Triggers](). ## Prerequisites Before proceeding with the SSF integration between Jamf and SailPoint, ensure that the following prerequisites are met: - Jamf Pro integration with Jamf Security Cloud Jamf Pro should be integrated with Jamf Security Cloud using UEM Connect. For more information, refer to the [Jamf Security Cloud Setup Guide](). - SSF Stream Registration in Jamf Security Cloud Ensure to register SSF streams in Jamf Security Cloud. To register follow these steps: 1. Go to **Integrations \> SSF streams** in the Jamf Security Cloud instance. 2. Select **Create new SSF stream**. 3. In the **Audience** field, enter the URL for your SSF signal receiver and select **Create**. Ensure the URL is a unique identifier linking the Receiver to the Transmitter. For example, `https://identitynow.com` or `https://tenant.identitynow.com` or `{your-tenant-base-url}`. 4. Copy and save the token shown in the window, then select **Confirm**. 5. Verify the obtained URL. The token and Well known URL obtained during SSF stream registration will be required as input while configuring the Shared Signal Receiver in SailPoint. - Obtain the necessary API credentials from Jamf Pro and SailPoint to authenticate and authorize the SSF integration. Ensure that the API credentials have the appropriate permissions to access and manage the integration.