Gate access on managed devices
A valid SSO token from a stolen laptop is still a valid token. Root Herald supplies the hardware-attested device half of the decision, so “only managed devices reach production” becomes a verdict rather than a fragile MDM integration.
Root Herald does not replace your IdP or SSO. It answers one question — is this a real, IT-provisioned, healthy device? — and returns it as a hardware-rooted verdict from a server→server rh.verify() call. You feed that into the access controls, conditional-access engine, or MDM signals you already run.
The problem
Most workforce SSO proves the user — WebAuthn, push, TOTP — the IdP issues an id token, and the app authorises. What is missing is the device. A valid token produced by a session-stealing extension on an unmanaged personal laptop looks identical to one from the engineer's corporate machine.
The usual defence is wiring Intune or Jamf into your IdP's conditional-access engine and keeping it synced: fragile, expensive, MDM-vendor-specific, and only as strong as the MDM's ability to observe the device at the moment of token issuance.
Pre-register the fleet
Set the project's acceptance policy to rootherald:builtin:enterprise-managed-only and pre-register your fleet's hardware keys from your Intune or Jamf inventory export. From that point only IT-provisioned devices can pass at all — an unmanaged laptop fails before any policy nuance applies.
Gate on the verdict at sign-in
At sign-in the device's collector produces a sealed hardware proof answering a one-time challenge your backend minted, and your backend verifies it server-to-server. The verdict carries attestationType, the assurance level (acr) and earStatus. Feed those into your conditional-access engine and gate production behind “managed device + high assurance”, the same way you already gate behind MFA.
Resist the temptation to make Root Herald the authorisation decision. It answers the device question well and nothing else — identity, group membership and session lifetime stay where they already live.
BYOD and unmanaged devices
For personal machines you can't pre-register, the same verdict is still useful as an advisory signal rather than a gate: it tells you the device is real, distinct and boot-healthy even when it isn't yours. Many teams gate production behind managed devices and use the advisory verdict to scope what a BYOD session may reach.