Tailscale shipped hardware-backed device posture on Tuesday, letting administrators write access policies that depend on attestation from a machine's TPM, Secure Enclave, or Android StrongBox rather than on a software agent's self-report. A policy can now require that a device has secure boot enabled, full disk encryption active, and an operating system build above a specified version, with the claims signed by hardware the user cannot modify. The previous implementation asked the Tailscale client to report those facts, which worked against honest users and provided no defense against a compromised or deliberately modified endpoint.
Why software posture checks fail
Every endpoint management tool asks an agent on the device to report its state, and the agent runs with the same privileges as everything else on that machine. A user with administrative rights can modify what it reports. Malware with kernel access certainly can. The check is therefore a compliance control rather than a security control: it catches the employee who forgot to turn on encryption and does nothing against an adversary.
That distinction has been understood for years and has not changed practice, because hardware attestation is difficult to implement across platforms. Windows, macOS, Linux, iOS, and Android each expose different primitives with different guarantees and different enrollment models. Building a system that works across all of them, and that degrades sensibly on hardware without the necessary chip, is enough engineering that most vendors did not bother.
How Tailscale implemented it
On Windows the client uses TPM 2.0 attestation keys and reads platform configuration registers that record boot state, producing a signed quote. On macOS it uses the Secure Enclave and the platform's own attestation API. On Android it uses key attestation through StrongBox where available and the trusted execution environment otherwise, with the attestation certificate chain identifying which. iOS uses App Attest. Linux uses TPM where present, which on servers usually means yes and on developer laptops means it depends.
Policies express requirements in Tailscale's existing access control file, so a rule can say that access to production infrastructure requires attested secure boot and an operating system within two releases of current. Devices failing the check lose access rather than generating an alert, which is a meaningful design choice: the posture is evaluated at connection time and re-evaluated periodically, and a device that falls out of compliance is disconnected within the check interval.
The story is rarely the launch. It is what breaks, what ships, and who owns the mess at 2 a.m.
The practical problems
Linux is where this gets messy. A substantial share of developer machines run distributions with secure boot disabled because it complicates kernel module signing, and many run without a TPM configured. An organization that enables strict attestation will lock out its own engineers on day one. Tailscale's answer is per-group policies, which lets an administrator require attestation for finance and accept software posture for engineering, and which is exactly the compromise that reintroduces the weakness.
Older hardware is the second problem. Machines without TPM 2.0, which includes a meaningful fleet in most enterprises, cannot participate. Tailscale reports attestation as unavailable rather than failed, and administrators decide how to treat that. Every organization will discover during rollout that its hardware inventory is worse than it believed, which is itself useful information and is not what anyone wants to learn on a Tuesday.
How this compares to the alternatives
Google's BeyondCorp uses device certificates issued after a management enrollment that verifies hardware state, which is strong and requires full device management. Microsoft's Conditional Access can require a compliant device as reported by Intune, with attestation available for Windows through device health attestation and inconsistently elsewhere. Cloudflare's Access has posture integrations that mostly rely on third-party agents reporting.
Tailscale's differentiation is that it works without a mobile device management enrollment, which suits organizations with contractors, bring-your-own-device policies, or a culture that resists full management. That is a real segment and it comes with a real limitation: attestation proves the device booted a known-good configuration and proves nothing about what has happened since.
Where this is heading
The direction across the industry is toward continuous verification, where the question is not whether a device was trustworthy at enrollment but whether it is trustworthy right now. Hardware attestation is one input. Runtime integrity measurement, which several endpoint vendors offer, is another. Combining them meaningfully requires the access layer and the endpoint layer to share signals, which is why Okta and CrowdStrike announced an integration last week and why more of those pairings are coming.
For teams evaluating this now, the honest starting point is an inventory: how many machines have functional TPMs, how many run secure boot, and how many are on a supported operating system version. That exercise takes a week and produces a number that will determine whether attestation-based policy is a next-quarter project or a next-year one.
It is also worth being clear about what this does not defend against, because vendors in this category tend to imply more than they deliver. Hardware attestation proves boot integrity and configuration state. It says nothing about a user who is phished into approving a malicious action, nothing about a browser session hijacked through a compromised extension, and nothing about an insider acting deliberately from a perfectly healthy machine. It closes a specific hole that software posture left open, and the organizations that treat it as a complete device trust story will be surprised by the next incident.
Skarvonix will keep following this beat with reporting grounded in how systems behave outside the launch keynote.
- Zero Trust
