Deep Dive of the Day VCF Single Sign-On and the Identity Broker: keeping your admin front door apart from the domain
Kaspersky's BlackNevas write-up is a reminder that most vCenter compromises don't start with a VMware bug. Its list of entry routes is mostly about identity: Active Directory integration abuse, credentials reused from Windows systems and credentials pulled out of backup servers. Its first recommendation is to treat vCenter as a Tier 0 asset, with dedicated admin identities, phishing-resistant MFA and virtualisation admin credentials kept separate from domain and workstation ones. In VCF 9 the place you put most of that into practice is VCF Single Sign-On, so it's worth knowing exactly what it covers and what it doesn't.
VCF SSO is set up after deployment from VCF Operations, under fleet management, and the single sign-on itself is handled by the VCF Identity Broker, which Broadcom's identity post notes was formerly known as VIDB. Per the VCF 9.1 docs, it works across "all VCF components except SDDC Manager and ESX": vCenter, NSX, VCF Operations, VCF Automation, VCF Operations for networks, VCF Operations orchestrator, VCF Operations HCX and Salt RaaS. The same post points out that VCF 9.0 no longer uses Enhanced Linked Mode for SSO, so vCenters have to be reconfigured to use VCF SSO rather than inheriting it.
On the identity side you have two broad choices. You can federate to an identity provider (Okta, Ping Identity, Microsoft Entra ID, Microsoft ADFS, Symantec Identity Security Platform, or any SAML 2.0 or OIDC provider), or connect a directory, Active Directory over LDAP or OpenLDAP. Users and groups arrive by SCIM 2.0, by just-in-time provisioning at first login, or by an AD/LDAP sync of the users and groups you choose; passwords are never synced. Broadcom's post says MFA can be enforced from the corporate identity provider and then applies across the VCF stack. That's the practical answer to Kaspersky's advice: with a straight directory connection, a vCenter login is only as strong as the domain password behind it, whereas a federated identity provider can demand phishing-resistant MFA for the same login. Note that you get one identity provider per Identity Broker instance.
The Identity Broker has two deployment modes. In instance mode it's deployed as a VCF management services component in the management domain of a VCF instance, the first one in your primary instance, with optional extra brokers in other instances. In embedded mode it's configured in the management domain vCenter, which the docs describe as typically used within a single VCF instance. Broadcom's post adds that running it as a multi-node cluster protects against a single node failure, which matters once every admin login depends on it; the Identity Broker detailed design guide has the rest of the trade-offs.
A few gotchas for production. SDDC Manager and ESX sit outside VCF SSO, so their local accounts, SSH and lockdown mode are still yours to manage, which is exactly the gap the BlackNevas attackers used on the hosts. Just-in-time users aren't deleted when you remove them from the identity provider, so prefer group-based role assignments and review them, and remember that roles are granted per component (vCenter and NSX each need their own mapping). In Gibson Virtualization's walkthrough the lab binds to AD with the domain Administrator account; in production you'd want a dedicated, least-privileged bind account instead. And if you've upgraded to 9.1.1, keep an eye on the Identity Broker certificate alerts in KB 456305.
In a nested lab, embedded mode is the natural fit for a single instance, and a small lab AD with a dedicated VCF admin group, as the walkthrough uses, is enough to practise group-based roles. Whatever you build, follow Broadcom's advice from the post: test vCenter and NSX logins through the Identity Broker before you move off older or local authentication sources, and keep a documented break-glass route for SDDC Manager and ESX, since SSO won't cover them.
Based on Identity Providers and Protocols Supported for VCF Single Sign-On (VCF 9.1) Official Deployment modes for VCF Single Sign-On (VCF 9.1) Official Bringing "Out-of-the-Box" Modern Identity to Your Infrastructure with VMware Cloud Foundation 9.0 (VCF Blog) Official VCF 9: Enable and configure SSO, Part 1 (Gibson Virtualization) Ransomware at the hypervisor layer (Kaspersky Securelist) Press