| Block reason | Description |
|---|---|
| Device risk too high |
The device was blocked because it exceeded the risk level threshold set in the security requirements of the access policy. To review or change the risk level threshold of an access policy in the Jamf Security Cloud portal, navigate to , select the policy name, and review or edit the Security settings. |
| Device not managed |
The device was blocked because the access policy requires devices to be managed, and the device is unmanaged. This may be because UEM Connect is not configured or failed to sync. To review or change the management requirements of an access policy in the Jamf Security Cloud portal, navigate to , select the policy name, and review or edit the Security settings. |
| Restricted IP range block |
The device attempted to access a private IP range via a shared or dedicated internet gateway. Only dedicated IPSec gateways can access private IP ranges. For more information about dedicated IPSec gateways, see Network Gateway Types. |
| Device not found |
The device is fully restricted because the system does not recognize the device, and cannot apply the appropriate policies. Check to make sure this device has been enrolled in Jamf Security Cloud. |
| Gateway disabled |
Device traffic sent to a disabled gateway cannot be processed. Enable the gateway assigned to the access policy and verify that it is available. |