---
title: "Threat and Risk Management"
slug: "threat-and-risk-management"
status: "update"
updated: 2025-10-28T13:13:32Z
published: 2025-10-28T13:13:32Z
canonical: "trusted.jamf.com/threat-and-risk-management"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://trusted.jamf.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Threat and Risk Management

Just because a device is [sanctioned](https://trusted.jamf.com/docs/resource-access-control) doesn't mean that the device is *[safe](https://trusted.jamf.com/docs/macos-ztna-risk-signaling)*.

For this reason, the Trusted Access solution calls for on-device and in-network endpoint protection technologies that ensure devices are:

* Protected from inbound threats to the maximum extent possible.
* Compliant against a company's security baselines.
* Able to report their activity to security analytics tools (EDR/XDR) to enable sophisticated threat hunting.
* Provided a risk level given each devices instantaneous state and health to drive [risk-based access controls](/v1/docs/risk-based-access-controls).
* Are able to self-remediate or request assistance from the device's end user.

Jamf provides first party endpoint security tools for macOS, iOS/iPadOS, and Android devices.  Refer to the [Device Trust, User Identity, and Deployment](/v1/docs/device-trust-identity-and-deployment) for details on how to deploy and configure Jamf Protect or Jamf Trust across these platforms and ownership modes.

Most importantly, you will need to [define your organization's security policy](/v1/docs/defining-security-policy) across your macOS, iOS/iPadOS, and Android devices.

More advanced security organizations can then steam threat and activity metadata to the [SIEM or XDR ](/v1/docs/siem-xdr-integration), or various Jamf [API Interfaces](/v1/docs/security-apis) for custom workflows.