Skip to Content

Endpoints

Manage the endpoints your users work on: enrollment, posture, vulnerabilities, and remote actions.

RequiresDevice Identity (DIAM)

Add-on required: This area is part of the DIAM (Device Identity) add-on.

The Endpoints area covers the devices your users work on. Endpoints enroll with the platform through the endpoint agent and then appear in the device inventory, where you review each device's posture, its status, installed software, missing patches, known vulnerabilities and policy compliance, and run remote actions such as isolating a compromised machine.

How the pieces fit together:

  • The client runs on the endpoint. It enrolls the device, reports posture on a schedule, and executes the commands you send.
  • Enrollment is anchored once under Device settings: a device registration certificate plus the client build for your instance.
  • The inventory lists every enrolled device with its status, owner and reported state, and is the place you act from.
  • Device compliance policies define what makes a device compliant. They are authored under Security → Conditional access, and their results show up per device and as fleet-wide violations.
  • Conditional access can then require a compliant device before granting access to sensitive applications.

The endpoint agent runs on Windows, macOS and Linux; isolation works on all three, MFA at sign-in is a Windows feature. Devices that still run the previous Windows client are covered under Legacy client.

Pages in this section

  • Device inventory: enrolled devices, statuses, the detail tabs, and investigating a device that changed state.
  • Software inventory: the products installed across the fleet, with versions and device counts.
  • Vulnerabilities: CVEs matched against the reported software, with severity and exploitation data.
  • Policy violations: failed compliance checks across the fleet and how they open and resolve.
  • Remote actions: isolation, MFA enrollment, queued commands for offline devices, and the API.
  • Endpoint agent: supported platforms, installing, updating and removing the agent, and what it reports.
  • Device settings: enrollment mode, the client installer, registration certificates and fleet-wide options.
  • MFA at Windows sign-in: a second factor at the Windows sign-in screen, and what to weigh before enabling it.
  • Legacy client: the previous Windows client, what only it does, and moving its devices to the endpoint agent.

On this page