Owned, Managed, Trusted: Why Your Device List Isn’t an Access Policy

Ask most security teams which devices are accessing their resources, and they’ll point to a CMDB or an MDM console.

But a list of devices you own isn’t the same as a list of devices you trust. Owned devices might be sitting in a closet. Managed devices might be spread across three MDMs after an acquisition. And trusted devices might include contractor laptops you don’t own at all.

If you want to enforce a trusted-device policy, you need a trusted-device inventory.

In this webinar, we’ll explore how to build a single source of device trust across Jamf, Intune, Fleet and other MDMs, and how to enforce it where access actually happens.

We’ll cover:

• The difference between owned, managed and trusted devices, and why it matters for access
• Reconciling device records across multiple MDMs and operating systems
• Bringing Linux, unmanaged and contractor devices into the same trust model
• Three ways to enforce device identity: at the resource, in the SSO flow and at the network edge
• Why checking a device once at login isn’t the same as continuously proving it

We’ll also walk through a live demo showing how Smallstep builds a canonical device inventory from your MDMs and uses hardware attestation to enforce it across SSO, Wi-Fi and VPN.