Secure Enclave: Keys That Never Leave the Coprocessor
Apple's Secure Enclave Processor holds biometric templates and private keys in a separated world so iOS can prove 'the user is present' without exposing key material to the application processor.
Category
44 articles · 145 min of reading
Apple's Secure Enclave Processor holds biometric templates and private keys in a separated world so iOS can prove 'the user is present' without exposing key material to the application processor.
Unity Catalog centralized identities, tables, and permissions so lakehouse objects could be governed like warehouse objects instead of as raw S3 prefixes.
How Microsoft Defender uses local sensors plus cloud-side reputation and ML verdicts so a newly seen binary can be blocked without waiting for a monthly signature drop.
How Coinbase-style crypto custody treats private keys as a ceremony-backed system of HSMs, quorums, and air gaps rather than a string in a config file.
How HashiCorp Boundary brokers sessions to infrastructure so engineers get just-in-time access instead of a shared SSH key on a jump box.
How HashiCorp Vault replaced long-lived shared credentials with authenticated identities, dynamic leases, and revocation as a first-class operation.
How Zoom introduced true end-to-end meeting encryption by keeping media keys among clients instead of at the cloud mixer — and what that does to features.
CloudFront, Cloud CDN, and Azure Front Door style signatures: expiry, prefix scope, and the leak that is a URL in a log file.
TC39 ShadowRealm: a fresh global for untrusted JS, how it differs from iframes and workers, and why production isolation is still not 'just new ShadowRealm'.
Enclaves, vsock, attestation documents, and KMS Decrypt that only the enclave can call — plus the operational limits that keep this from being 'just a VM'.
How to ban unsafe-inline without breaking React and Angular, when hashes beat nonces, and the report-only rollout that does not brick production.
Simple vs preflighted requests, why Access-Control-Allow-Origin cannot be * with credentials, and what CORS never was (a server-side access control system).
How interceptors chain, where to attach auth headers and correlation IDs, and how to write a retry interceptor that does not duplicate POSTs.
SPDX/CycloneDX name ingredients; in-toto layouts name who ran which step. Together they are stronger than a lockfile screenshot.
Kocher et al. and Lipp et al.: how mispredicted paths leave traces in caches, and what isolation still means after the 2018 papers.
Kim et al. and the follow-on literature: adjacent-row bit flips, TRR's incomplete story, and why 'userspace cannot flip bits' stopped being true.
RFC 8555: account keys, HTTP-01 and DNS-01 challenges, short-lived certs, and the operational habits that keep renewals from becoming outages.
DH ratchet plus symmetric ratchet: why stealing today's session key should not decrypt last month's messages, and what you must persist carefully.
How a service with a broad role gets tricked into acting on the wrong resource, and the sts:ExternalId / source ARN patterns that stop it.
Public-key credentials scoped to RP ID, user verification, and why a fake login page cannot replay a passkey assertion.
What SLSA levels actually require, how provenance attestations fit next to SBOMs, and a realistic path from 'we tag git' to a verifiable builder.
RFC 7636: why native and SPA clients must use authorization code plus PKCE, and how a stolen redirect code becomes useless without the verifier.
AS, TGS, tickets, and clocks: how Kerberos avoids sending passwords to every service, and why skew and SPNs still page AD admins.
GitHub-hosted VMs versus autoscaled ephemeral self-hosted: dirty workspaces, credential lifetime, and when Buildkite's similar model is the same idea.