AI
The Client Identity Blind Spot
Twenty years of HTTPS solved server identity. TLS, certificates, transparency logs — the server knows exactly who it is. The client side never got the same treatment. A server sees a header, a token, a string. If the string looks right, the server accepts it. Attackers don’t break cryptography. They grab a working credential — an API token off disk, a certificate from a container image — and use the system as designed. That is impersonation, not intrusion.
TPM: Roots of Trust and Non-Exportable Keys
The Trusted Platform Module is a secure processor that protects keys, measures boot state, and enforces policy in hardware. Keys are derived from internal seeds — the TPM can create them but cannot export them. Endorsement Key (EK) establishes manufacturing identity. Attestation Key (AK) signs evidence. Application keys live under the owner hierarchy. Platform Configuration Registers (PCRs) accumulate cryptographic hashes of the boot chain. Sealing binds key usage to acceptable PCR values. The key is only usable when the system is in a measured, trusted state.
Apple Secure Enclave and Android StrongBox
Apple’s Secure Enclave is a coprocessor with its own microkernel and memory. Keys are non-exportable by design. Applications request signing or decryption; the enclave returns only the result. Identity is per-app and per-device — if an app is deleted, the key is gone. Android uses the Keystore system backed by TrustZone (secure execution mode) or StrongBox (discrete hardware security module). Guarantees vary by device class and OS version. Attestation includes boot state, patch level, and StrongBox support. Servers must inspect attestation claims and define policy tiers — StrongBox required for high trust, weaker devices get reduced privileges.
Attestation: Turning Hardware Facts into Verifiable Evidence
Attestation combines evidence and a signature. The device says, “Here are my claims.” The hardware signs them. A verifier checks the signature and evaluates the claims — key provenance, non-exportability, platform state. On TPM, this is a quote over selected PCRs plus a nonce for freshness. On Android, attestation includes verified boot state, bootloader lock status, and OS patch level. Two phases: cryptographic verification of the certificate chain, then policy evaluation against your requirements. Without a nonce, evidence could be replayed. Attestation does not prove the application is bug-free; it proves the hardware and platform state are as expected.
Production Lifecycle: Enrollment, Rotation, Revocation
Enrollment starts with key generation inside hardware. The device attests; the backend verifies before registering the public key. Credentials — OAuth tokens, mTLS certificates — are issued only after proof of possession. Hardware key becomes the root; everything else derives from it. Do not rotate the hardware key routinely. Rotate derived credentials. Revocation becomes device-scoped: invalidate the certificate, add the key fingerprint to a deny list. The user account survives, the device identity does not. If attestation claims change (bootloader unlock, firmware downgrade), flag the device and reduce privileges. Hardware identity continuity breaks by design — a new motherboard means a new enrollment event. That break is a signal, not a bug.
What Hardware-Backed Identity Stops
Stolen credentials no longer scale. Stealing a token without the device holding the non-exportable key is useless. Cloned workloads cannot copy the private key sealed inside a secure processor. Replay is defeated by freshness — nonces and timestamps bound evidence in time. Shadow clients lack the hardware anchor and fail policy. Cryptography did not get stronger. Attackers did not get less capable. What changed is scale: one compromised identity cannot multiply across infrastructure. Incident response shifts from resetting a shared secret to revoking a device identity. Containment becomes precise, not global. The question moves from “Is this credential valid?” to “What physical thing produced this proof?”
Notable Quotes
But that isn’t identity. That’s copyable possession. Victor Lyuboslavsky · ▶ Watch (3:50)
If identity fits in a clipboard, it’s not really identity. Victor Lyuboslavsky · ▶ Watch (3:55)
With hardware backed keys, you can use the key, but you cannot read it. Victor Lyuboslavsky · ▶ Watch (7:43)
Attestation is not about secrecy, it is about proof. Victor Lyuboslavsky · ▶ Watch (35:19)
Identity moves from software to physics. Victor Lyuboslavsky · ▶ Watch (39:05)
Key Takeaways
- Stolen API tokens no longer grant access without the originating hardware device.
- Attestation turns internal hardware facts into externally verifiable, non-replayable evidence.
- Revocation scopes to a single machine rather than a shared credential.
About the Speaker
Victor Lyuboslavsky is a software engineering leader and author with over 25 years of experience building products and leading teams. He has co-founded startups, held technical leadership roles at AMD, and now architects secure, scalable systems for enterprise IT at Fleet Device Management. His work bridges hands-on technical execution with strategic leadership. Drawing on experience in startups and open source communities, Victor focuses on clarity, transparency, and evolutionary design. These principles help teams scale architectures, adopt AI responsibly, and build resilient systems without creating chaos.