Infisical argues Active Directory cannot govern cloud machine identities
Original title: The Active Directory Era Is Finally Over
The vendor blog says auto-joined short-lived cloud workloads break AD’s human-approval model, citing Kubernetes tokens and Entra ID.
Infisical’s blog argues Active Directory, an LDAP directory plus Kerberos, still tracks many human identities but cannot reliably catalog ephemeral cloud machines. Domain joins once required a human; automated admin tokens now enroll short-lived resources without real attestation. The post contrasts that with Kubernetes service-account tokens and Azure Entra ID tokens issued through the instance metadata service.
Unconfirmed: The exposed Lambda is an unverified anecdote from a conference conversation, not a confirmed incident.
- A conference anecdote describes a defense organization’s public Lambda with an iam:* policy.
- Domain join creates a machine account, updates DNS, issues certificates, and grants Kerberos tickets.
- The author says automated admin tokens negate human approval of each trusted device.
- Kubernetes pods and Azure IMDS are cited as systems that let machines self-serve identity.
From the original article
7 min read at infisical.com
“Life was simpler on Active Directory, at least I could manage every identity”. I made that quote up, but there is nostalgia for a golden age of corporate IT that’s never coming back: Many enterprises still (try to) track identities in Active Directory (AD), a service that’s old enough to drink and crumbles at the scale of modern cloud computing.
By FinnLobsien · infisical.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.