# Endpoints

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

Requires: Device 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](https://dts-identity.com/docs/endpoints/device-client.md) 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](https://dts-identity.com/docs/endpoints/device-settings.md): 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](https://dts-identity.com/docs/security/conditional-access/device-compliance-policies.md), 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](https://dts-identity.com/docs/endpoints/legacy-client.md).

## Pages in this section

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

## Related areas

- [Security → Device compliance policies](https://dts-identity.com/docs/security/conditional-access/device-compliance-policies.md): the rules evaluated against device state.
- [Audit logs](https://dts-identity.com/docs/monitoring/audit-logs.md): where device status changes and remote actions are recorded.
- [Plans & add-ons](https://dts-identity.com/docs/getting-started/plans-and-addons.md): the DIAM add-on and the deviceTrust feature.
