开发者生态
morning
Active Directory 时代终于结束
2026-11-17
1 阅读
约10分钟阅读
FinnLobsien
字号:
“Active Directory 上的生活更简单,至少我可以管理每个身份”。 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. It held up because the architecture is simple enough: Active Directory is an LDAP directory to store identities and a Kerberos implementation to let them authenticate, wrapped in decent UX and with continued updates. AD 实现了身份管理的目标:一种了解所有身份、谁为这些身份提供担保以及这些身份在哪里有效的方法。它在一个统一的目录中回答了三个问题:存在哪些身份?有了目录,里面记录了每一个用户和机器,用什么来保证身份呢?使用根据管理员凭据批准身份验证的域控制器 身份在哪里有效?通过反映公司基础设施的 AD 域架构,如果您无法回答其中任何一项,安全策略就毫无意义。 I spent many hours keeping our Active Directory catalog accurate so it could answer these questions, because everything downstream depended on it: issuing certificates automatically with Certificate Services , applying settings at scale with Group Policies, and more. There were always some compromises: databases with local users, Linux servers requiring workarounds (Thank you SSSD!), but most users and machines in my network had an identity in Active Directory, and I knew which didn’t.但对于现代云架构来说,统一 Active Directory(或任何一个目录)中的每个身份几乎是不可能的。 There’s an AD ecosystem of security products, password rotations, and sync plugins that modernizes it, but nothing can undo architecture choices from a bygone era. Active Directory 是新的大型机:在当时非常有用,但您永远不会选择从头开始。取代它是不可能的,因为它是如此根深蒂固。 Active Directory 可以通过一些集成和插件准确反映人类身份,但机器身份几乎是不可能的。也许这是有争议的。 You can come to me with torches, pitchforks, and architectural diagrams about Kubernetes pod identity attestation in AD, but Active Directory is still a piece of infrastructure built for a bygone era. Visibility and attestation: Unified machine identity is nearly impossible in Active Directory Most organizations are creating grave security risks because they don’t understand modern machine identity.我曾经在一次会议上与某人交谈,他告诉我他们最近发现了一个公开暴露的 Lambda 函数。 Bad enough, but that function’s policy was iam:* meaning it could take any IAM action, including crowning any attacker the organization’s superadmin.哦,顺便说一句,这是一个防御组织。如果具有高安全要求的组织犯了这些错误,您就不会想知道其他组织会发生什么。 This problem isn’t specific to AD, but it is a symptom of organizations not figuring out how to correctly attest machine identity in modern software development.要理解为什么没有组织可以解释 AD 中的所有计算机身份,我们需要了解计算机如何进入域。域是共享安全规则的管理边界。实际上,这通常是一个组织。 When a new machine joins your domain, three main events happen: An object is created inside the directory (often called a machine account) DNS is updated, certificates are issued (assuming you have AD Certificate Services autoenrollment) Kerberos tickets are issued so the machine can assert its identity When that machine logs in, it authenticates to a Domain Controller (the server running Active Directory for the domain), which trusts it because the machine is in its directory.但机器必须先进入该目录。当构建 Active Directory 时,这意味着需要人工手动添加它。 “机器”是物理服务器,被运送到办公室,安装在服务器地下城房间中,并由人类管理员注册。人工审批无法扩展到
这篇文章对您有帮助吗?
订阅66必读
每日精选科技资讯,直达你的邮箱