Identity and Access Management for VMware Cloud Foundation
Provides detailed design, implementation, configuration, and operation guidance on use of Active Directory as an identity provider and authentication source, and on use of role-based access control (RBAC) in SDDC Manager, vCenter Server, ESXi, and NSX. Also covers password management, password policies, and account lockout policies across these components.
Key Components: NSX, SDDC Manager, vCenter, ESXi
External dependencies: None (Active Directory and Microsoft CA are external services)
48 design decisions. The Quality column is the Academy's assessment for defence practice; the VVS documents do not classify decisions by design quality (D133).
| DD-ID | Decision | Quality (Academy view) |
|---|---|---|
| IAM-VCF-SEC-001 | Limit the use of local accounts for both interactive or API access and solution integration. | SecurityManageability |
Decision: Limit the use of local accounts for both interactive or API access and solution integration. Rationale: Local accounts are not specific to user identity and do not offer complete auditing from an endpoint back to the user identity. Implication: You must define and manage service accounts, security groups, group membership, and security controls in Active Directory. Component: VCF | ||
| IAM-VCF-SEC-002 | Limit the scope and privileges for accounts used for both interactive or API access and solution… | SecurityManageability |
Decision: Limit the scope and privileges for accounts used for both interactive or API access and solution integration. Rationale: The principle of least privilege is a critical aspect of access management and must be part of a comprehensive defense-indepth security strategy. Implication: You must define and manage custom roles and security controls to limit the scope and privileges used for interactive access or solution integration. Component: VCF | ||
| IAM-VCF-SEC-003 | Assign Active Directory user accounts to security groups following your organization's access… | Security |
Decision: Assign Active Directory user accounts to security groups following your organization's access policies. Rationale: Allows Active Directory security groups to be assigned to roles in SDDC components for streamlined management of access and administrative privileges. Implication: You must define and manage security groups, group membership, and security controls in Active Directory. Component: VCF | ||
| IAM-VCF-SEC-004 | Assign Active Directory security groups to default or custom roles, as applicable, for interactive… | AvailabilitySecurityManageability |
Decision: Assign Active Directory security groups to default or custom roles, as applicable, for interactive or API access to solution components based on your organization's business and security requirements: SDDC Manager, ESXi (as applicable), vCenter Servers, NSX Managers. Rationale: Using Active Directory security group membership provides greater flexibility in granting access to roles across solution components. Ensuring that users log in with a unique Active Directory user account provides greater visibility for auditing. • Evaluate the needs for additional role separation in your organization and implement mapping from Active Directory users to Active Directory security groups and default or custom roles. Implication: • You must manage privileges assigned to custom roles. • You must manage the assignment and scope of custom roles based on the business and security requirements. • Additional Active Directory security groups must be created in advance to assigning roles. • You must maintain the life cycle and availability of Active Directory security groups outside of the SDDC stack. • The principle of least privilege is only one aspect of access management and must be part of a comprehensive defensein-depth security strategy aligned with organization personas. Component: VCF | ||
| IAM-ESXI-SEC-001 | Configure the password expiration policy for each ESXi host. | Security |
Decision: Configure the password expiration policy for each ESXi host. Rationale: • You configure the password expiration for ESXi hosts to align with the requirements of your organization which might be based on industry compliance standards. • The password expiration policy is applicable to the following default accounts for a commissioned ESXi host: – root account – SERVICE account • The policy is applicable only to the local ESXi host users. Implication: You must manage the local user password expiration policy on each ESXi host by using the advanced system settings in the vSphere Client or the Host Client. Component: ESXI | ||
| IAM-ESXI-SEC-002 | Configure the password complexity policy for each ESXi host. | Security |
Decision: Configure the password complexity policy for each ESXi host. Rationale: • You configure the password complexity policy for ESXi hosts to align with the requirements of your organization which might be based on industry compliance standards. • The password complexity policy is applicable only to the local ESXi host users. Implication: You must manage the local user password complexity policy on each ESXi host by using the advanced system settings in the vSphere Client or the Host Client. Component: ESXI | ||
| IAM-ESXI-SEC-003 | Configure the account lockout policy for each ESXi host. | Security |
Decision: Configure the account lockout policy for each ESXi host. Rationale: • You configure the account lockout policy for ESXi hosts to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local ESXi host users. Implication: You must manage the local user account lockout policy on each ESXi host by using the advanced system settings in the vSphere Client or the Host Client. Component: ESXI | ||
| IAM-ESXI-SEC-004 | Change the root user password for each ESXi host on a recurring or event-initiated schedule by… | Security |
Decision: Change the root user password for each ESXi host on a recurring or event-initiated schedule by using SDDC Manager. Rationale: • The password for the ESXi host's root user does not expire based on the default password expiration policy. • SDDC Manager manages each ESXi host in the system. The ESXi root user password must be known and managed by SDDC Manager. Implication: • You must manage the password update or password rotation for the root account by using SDDC Manager. • An automated password rotation schedule can not be activated for ESXi hosts in SDDC Manager. Component: ESXI | ||
| IAM-ESXI-SEC-005 | Rotate the SERVICE account password for each ESXi host on a recurring or event-initiated schedule… | Security |
Decision: Rotate the SERVICE account password for each ESXi host on a recurring or event-initiated schedule by using SDDC Manager. Rationale: SDDC Manager creates a SERVICE account on each ESXi host to provide the access to the ESXi host over SSH in the context of an exception user in normal lock down mode. The password for the ESXi host's SERVICE account does not expire based on the default password expiration policy. SDDC Manager manages each ESXi host in the system. The ESXi root user password must be known and managed by SDDC Manager. Implication: • You must manage the password rotation for the SERVICE account by using SDDC Manager. • An automated password rotation schedule can not be activated for ESXi hosts in SDDC Manager. Component: ESXI | ||
| IAM-VCS-SEC-001 | Configure the vCenter Server instances to use Active Directory over LDAP with SSL (LDAPS) as the… | SecurityManageability |
Decision: Configure the vCenter Server instances to use Active Directory over LDAP with SSL (LDAPS) as the identity source. Rationale: • Provides the ability for vCenter Server to connect to an Active Directory using LDAP. • Ensures that LDAP traffic between a vCenter Server instance and the Active Directory is encrypted. Microsoft recommends a hardened configuration for LDAP channel binding and LDAP signing on Active Directory domain controllers. For more information, see Microsoft Security Advisory ADV190023. Implication: • In a multi-domain forest, where the vCenter Server instance connects to a child domain, Active Directory security groups must have global scope. Therefore members added to the Active Directory global security group and user accounts for solution integration must reside within the same Active Directory domain. • If multiple VMware Cloud Foundation instances are deployed to separate Active Directory domains (for example, child domains in a multidomain forest), the instances can not be in enhanced linked-mode. • A certificate is required to establish trust for the Active Directory LDAPS endpoints. You must obtain a CA-signed certificate that can be used for server authentication. • You must remove and reconfigure the integration between the identity provider and vCenter Server when replacing the certificates used by Active Directory over LDAP with SSL. Component: VCS | ||
| IAM-VCS-SEC-002 | Use an Active Directory user account with minimum read-only access as Base DN for users and groups… | SecurityManageability |
Decision: Use an Active Directory user account with minimum read-only access as Base DN for users and groups to serve as the service account for the Active Directory bind. Rationale: Provides the following access control features: • Each vCenter Server instance connects to the Active Directory domain with the minimum permissions to bind and query the directory. • Improves the visibility in tracking request-response interactions between the vCenter Server instances and Active Directory. Implication: You must manage the password life cycle of this Active Directory user account. Component: VCS | ||
| IAM-VCS-SEC-003 | Assign the default Administrator role in vCenter Server to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the default Administrator role in vCenter Server to an Active Directory security group. Rationale: By assigning the Administrator role to an Active Directory security group, you can simplify and manage user access with administrative rights in vCenter Server based on your organization's personas. Implication: • An Active Directory security group must be created in advance to assigning a role. • You must maintain the life cycle and availability of the security group in Active Directory. Component: VCS | ||
| IAM-VCS-SEC-004 | Assign vCenter Server global permissions for the Active Directory security groups assigned the… | Security |
Decision: Assign vCenter Server global permissions for the Active Directory security groups assigned the Administrator role. Rationale: By assigning the global permissions to an Active Directory security group with the Administrator role, you can manage user access with administrative rights across all management and workload domain vCenter Servers instances which participate in enhanced linked-mode and use the same identity provider. Implication: None. Component: VCS | ||
| IAM-VCS-SEC-005 | Assign the default ReadOnly role in vCenter Server to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the default ReadOnly role in vCenter Server to an Active Directory security group. Rationale: By assigning the Read-only role to an Active Directory security group, you can simplify and manage user access with read-only rights in vCenter Server based on your organization's personas. Implication: An Active Directory security group must be created in advance to assigning a role. You must maintain the life cycle and availability of the security group in Active Directory. Component: VCS | ||
| IAM-VCS-SEC-006 | Assign vCenter Server global permissions for the Active Directory security groups assigned the… | Security |
Decision: Assign vCenter Server global permissions for the Active Directory security groups assigned the ReadOnly role. Rationale: By assigning global permissions to an Active Directory security group with the Read-only role, you can manage user access with read-only privileges across all management and workload domain vCenter Servers instances which participate in enhanced linked-mode and use the same identity provider. Implication: None. Component: VCS | ||
| IAM-VCS-SEC-007 | Add an Active Directory security group as a member of the vCenter Single SignOn Administrators… | AvailabilitySecurityManageability |
Decision: Add an Active Directory security group as a member of the vCenter Single SignOn Administrators group. Rationale: By adding an Active Directory security group as a member of the Administrators group, you can manage user access with administrative rights to the vCenter Single Sign-On built-in identity provider based on your organization's personas. Implication: • An Active Directory security group must be created in advance to assigning a role. • You must maintain the life cycle and availability of the security group in Active Directory. Component: VCS | ||
| IAM-VCS-SEC-008 | Configure the global password expiration policy for each vCenter Server instance. | Security |
Decision: Configure the global password expiration policy for each vCenter Server instance. Rationale: You configure the global password expiration policy for each vCenter Server instance to align with the requirements of your organization which might be based on industry compliance standards. Implication: You must manage the password expiration policy on each vCenter Server instance by using the vCenter Server Management Interface. Component: VCS | ||
| IAM-VCS-SEC-009 | Configure the local user password expiration policy for each vCenter Server instance. | Security |
Decision: Configure the local user password expiration policy for each vCenter Server instance. Rationale: • You configure the local user password expiration policy for each vCenter Server instance to align with the requirements of your organization which might be based on industry compliance standards. • The local user password expiration policy is applicable to the root account for the vCenter Server virtual appliance. Implication: You must manage the local user password expiration settings on each vCenter Server instance by using both the vCenter Server Management Interface and the virtual appliance console. Component: VCS | ||
| IAM-VCS-SEC-010 | Configure the local user password complexity policy for each vCenter Server instance. | Security |
Decision: Configure the local user password complexity policy for each vCenter Server instance. Rationale: • You configure the local user password complexity policy for each vCenter Server instance to align with the requirements of your organization which might be based on industry compliance standards. • The local user password complexity policy is applicable only to the local vCenter Server virtual appliance users. Implication: • You must manage the local user password complexity settings on each vCenter Server instance by using the virtual appliance console. • If the password complexity policy sets the minimum password length to a value greater than 20, password rotation in SDDC Manager cannot be performed for a managed account. Passwords must be updated or remediated. Component: VCS | ||
| IAM-VCS-SEC-011 | Configure the local user account lockout policy for each vCenter Server instance. | Security |
Decision: Configure the local user account lockout policy for each vCenter Server instance. Rationale: • You configure the local user account lockout policy for each vCenter Server instance to align with the requirements of your organization which might be based on industry compliance standards. • The local user account lockout policy is applicable only to the local vCenter Server virtual appliance users. Implication: You must manage the local user account lockout settings on each vCenter Server instance by using the virtual appliance console. Component: VCS | ||
| IAM-VCS-SEC-012 | Configure the password expiration policy for the vCenter Single Sign-On built-in identity provider. | Security |
Decision: Configure the password expiration policy for the vCenter Single Sign-On built-in identity provider. Rationale: • You configure the password expiration policy for the vCenter Single Sign-On built-in identity provider to align with the requirements of your organization which might be based on industry compliance standards. • The password expiration policy is applicable to the built-in identity provider users only and does not impact your organization's directory services or the root account for the vCenter Server virtual appliance. • The password for the Administrator account of the vCenter Single Sign-On built-in identity provider does not expire based on the default vCenter Server Single-Sign-On password expiration policy configuration. Implication: You must manage the password expiration policy for the vCenter Single Sign-On built-in identity provider by using the vSphere Client. Component: VCS | ||
| IAM-VCS-SEC-013 | Configure the password complexity policy for the vCenter Single Sign-On built-in identity provider. | Security |
Decision: Configure the password complexity policy for the vCenter Single Sign-On built-in identity provider. Rationale: • You configure the password complexity policy for the vCenter Single Sign-On built-in identity provider to align with the requirements of your organization which might be based on industry compliance standards. • The password complexity policy is applicable to the built-in identity provider users only and does not impact your organization's directory services or the root account for the vCenter Server virtual appliance. Implication: You must manage the password expiration policy for the vCenter Single Sign-On built-in identity provider using the vSphere Client. If the password complexity policy sets the minimum password length to a value greater than 20, password rotation in SDDC Manager cannot be performed for a managed account. Passwords must be updated or remediated. Component: VCS | ||
| IAM-VCS-SEC-014 | Configure the account lockout policy for the vCenter Single Sign-On built-in identity provider. | Security |
Decision: Configure the account lockout policy for the vCenter Single Sign-On built-in identity provider. Rationale: • You configure the account lockout policy for the vCenter Single Sign-On domain to align with the requirements of your organization which might be based on industry compliance standards. • The account lockout policy is applicable to the built-in identity provider users only and does not impact your organization's directory services or the root account for the vCenter Server virtual appliance. • The password for the vCenter Single Sign-On built-in identity providerAdministrator account does not lock out based on the vCenter Server Single-Sign-On account lockout policy configuration. Implication: You must manage the password expiration policy for the vCenter Single Sign-On built-in identity provider by using the vSphere Client. Component: VCS | ||
| IAM-VCS-SEC-015 | For each vCenter Server instance, change the vCenter Server virtual appliance root account password… | Security |
Decision: For each vCenter Server instance, change the vCenter Server virtual appliance root account password on a recurring or event-initiated schedule by using SDDC Manager. Rationale: • The password for the vCenter Server root user account expires based on the default password expiration settings. By default, SDDC Manager is configured to automate a password rotation for the root account every 90 days. • SDDC Manager manages each vCenter Server instance in the system. The vCenter Server virtual appliance root account password must be known and managed by SDDC Manager. Implication: You must manage the password update or an automated password rotation schedule (default) for the root account by using SDDC Manager. Component: VCS | ||
| IAM-VCS-SEC-016 | Change the vCenter Single Sign-On domain administrator SYSTEM account (for example… | Security |
Decision: Change the vCenter Single Sign-On domain administrator SYSTEM account (for example, administrator@vsphere.local) password in the vCenter Single Sign-On built-in identity provider on a recurring or event-initiated schedule by using SDDC Manager. Rationale: • The password for the vCenter Single Sign-On domain administrator SYSTEM account does not expire based on the default vCenter Server Single Sign-On password expiration settings. • SDDC Manager manages each vCenter Server instance in the system. The vCenter Single Sign-On domain administrator SYSTEM account password must be known and managed by SDDC Manager. Implication: You must manage the password update or an automated password rotation schedule for the SYSTEM account by using SDDC Manager. Component: VCS | ||
| IAM-VCS-SEC-017 | Rotate the passwords for • SDDC Manager SERVICE account types in the vCenter Single Sign-On… | AvailabilitySecurity |
Decision: Rotate the passwords for • SDDC Manager SERVICE account types in the vCenter Single Sign-On built-in identity provider on a recurring or event-initiated schedule by using SDDC Manager. Rationale: The password for each vCenter Single SignOn SERVICE account expires based on the vCenter Server Single Sign-On password expiration settings. By default, SDDC Manager is configured to automate a password rotation for the account every 90 days. A vCenter Server instance is registered as a compute manager with its NSX Local Manager cluster during workload domain creation. This SERVICE account password must be known and managed by SDDC Manager.The passwords for the SERVICE accounts are randomly generated by SDDC Manager and cannot be manually set. Implication: You must manage the password rotation or an automated password rotation schedule for the SERVICE account by using SDDC Manager. Component: VCS | ||
| IAM-NSX-SEC-001 | Configure Active Directory over LDAP as the authentication source for the NSX Local Managers. | SecurityManageability |
Decision: Configure Active Directory over LDAP as the authentication source for the NSX Local Managers. Rationale: Provides integration with Active Directory for rolebased access control. You can introduce authorization policies by assigning roles to Active Directory security groups. Implication: None. Component: NSX | ||
| IAM-NSX-SEC-002 | Assign the default Enterprise Admin role in NSX Manager to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the default Enterprise Admin role in NSX Manager to an Active Directory security group. Rationale: By assigning the Enterprise • Admin role to an Active Directory security group, you can simplify and manage user access to NSX by using the enterprise administrative access controls in Active Directory. Implication: An Active Directory security group must be created before assigning a role. You must maintain the life cycle and availability of the security group in Active Directory. Component: NSX | ||
| IAM-NSX-SEC-003 | Assign the default Network Admin role in NSX Manager to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the default Network Admin role in NSX Manager to an Active Directory security group. Rationale: By assigning the Network Admin role to an Active Directory security group, you can simplify and manage user access to NSX by using the enterprise administrative access controls in Active Directory. Implication: An Active Directory security group must be created before assigning a role. You must maintain the life cycle and availability of the security group in Active Directory. Component: NSX | ||
| IAM-NSX-SEC-004 | Assign the default Auditor role in NSX Manager to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the default Auditor role in NSX Manager to an Active Directory security group. Rationale: By assigning the Auditor role to an Active Directory security group, you can simplify and manage user access to NSX by using the enterprise administrative access controls in Active Directory. Implication: • An Active Directory security group must be created before assigning a role. • You must maintain the life cycle and availability of the security group in Active Directory. Component: NSX | ||
| IAM-NSX-SEC-005 | Configure the password expiration policy for each NSX Local Manager cluster. | AvailabilitySecurity |
Decision: Configure the password expiration policy for each NSX Local Manager cluster. Rationale: • You configure the password expiration policy for NSX Local Manager cluster to align with the requirements of your organization which might be based on industry compliance standards. • The password expiration policy is applicable to the following default active accounts for the NSX Local Manager cluster nodes: – root account – admin account – audit account Implication: You must manage the password expiration policy on each NSX Local Manager cluster using the CLI or an API. Component: NSX | ||
| IAM-NSX-SEC-006 | Configure the password complexity policy for each NSX Local Manager cluster node. | AvailabilitySecurity |
Decision: Configure the password complexity policy for each NSX Local Manager cluster node. Rationale: You configure the password complexity policy for each NSX Local Manager cluster node to align with the requirements of your organization which might be based on industry compliance standards. Implication: • You must manage the password complexity policy on each NSX Local Manager cluster node using the virtual appliance console. • If the password complexity policy sets the minimum password length to a value greater than 20, automatic password rotation in SDDC Manager cannot be performed. Passwords must be updated or remediated. Component: NSX | ||
| IAM-NSX-SEC-007 | Configure the account lockout policy on each NSX Local Manager cluster to configure the account… | AvailabilitySecurity |
Decision: Configure the account lockout policy on each NSX Local Manager cluster to configure the account lockout policy and set the lockout behavior for the API, CLI, and user interface. Rationale: You configure the account lockout policy for each NSX Local Manager cluster to align with the requirements of your organization which might be based on industry compliance standards. Implication: You must manage the account lockout policy on each NSX Local Manager cluster by using the virtual appliance console. Component: NSX | ||
| IAM-NSX-SEC-008 | Configure the password expiration policy for each NSX Edge node. | Security |
Decision: Configure the password expiration policy for each NSX Edge node. Rationale: • You configure the password expiration policy for NSX Edge nodes to align with the requirements of your organization which might be based on industry compliance standards. • The password expiration policy is applicable to the following default active accounts for the NSX Edge nodes: – root account – admin account – audit account Implication: You must manage the password expiration policy on each NSX Edge node by using the virtual appliance console. Component: NSX | ||
| IAM-NSX-SEC-009 | Configure the password complexity policy for each NSX Edge node. | Security |
Decision: Configure the password complexity policy for each NSX Edge node. Rationale: You configure the password complexity policy for NSX Edge nodes to align with the requirements of your organization which might be based on industry compliance standards. Implication: • You must manage the password complexity policy on each NSX Edge node by using the virtual appliance console. • If the password complexity policy sets the minimum password length to a value greater than 20, automatic password rotation in SDDC Manager cannot be performed. Passwords must be updated or remediated. Component: NSX | ||
| IAM-NSX-SEC-010 | Configure the account lockout policy on each NSX Edge node to configure the account lockout policy… | Security |
Decision: Configure the account lockout policy on each NSX Edge node to configure the account lockout policy and set the lockout behavior for the CLI. Rationale: You configure the account lockout policy for NSX Edge nodes to align with the requirements of your organization which might be based on industry compliance standards. Implication: You must manage the account lockout policy on each NSX Edge node by using the virtual appliance console. Component: NSX | ||
| IAM-NSX-SEC-011 | • For VMware Cloud • Foundation 5.1 and later, for each NSX Local Manager cluster, change the root… | AvailabilitySecurity |
Decision: • For VMware Cloud • Foundation 5.1 and later, for each NSX Local Manager cluster, change the root, admin, and audit account passwords on a recurring or event-initiated schedule by using SDDC Manager. • For VMware Cloud Foundation 5.0 and earlier, for the management domain NSX Local Manager cluster, change the root,a dmin, and audit account passwords on a recurring or event-initiated schedule by using SDDC Manager. Rationale: The passwords for the accounts for the management domain NSX Local Manager cluster expire based on the password expiration settings for each account. • SDDC Manager manages the management domain NSX Local Manager cluster in the system. The accounts passwords must be known and managed by SDDC Manager. Implication: • For VMware Cloud Foundation 5.1 and later, SDDC Manager supports the rotation of the audit account for each NSX Local Manager cluster, regardless of the domain type. • You must manage the password change or an automated password rotation schedule for the root, admin, and audit accounts by using SDDC Manager. Component: NSX | ||
| IAM-NSX-SEC-012 | For VMware Cloud Foundation 5.0 and earlier, for each VI workload domain NSX Local Manager cluster… | AvailabilitySecurity |
Decision: For VMware Cloud Foundation 5.0 and earlier, for each VI workload domain NSX Local Manager cluster, change the root and the admin account passwords on a recurring or event-initiated schedule by using SDDC Manager. Rationale: • The passwords for the accounts for each VI workload domain NSX Local Manager cluster expire based on the password expiration settings for each account. • SDDC Manager manages each VI workload domain NSX Local Manager cluster in the system. The accounts passwords must be known and managed by SDDC Manager. Implication: • You must manage the password change or an automated password rotation schedule for the accounts by using SDDC Manager • If the authentication policy sets the minimum password length to a value greater than 20, automatic password rotation in SDDC Manager cannot be performed. Passwords must be updated or remediated. Component: NSX | ||
| IAM-NSX-SEC-013 | For VMware Cloud • Foundation 5.0 and earlier, for each VI workload domain NSX Local Manager… | AvailabilitySecurityManageability |
Decision: For VMware Cloud • Foundation 5.0 and earlier, for each VI workload domain NSX Local Manager cluster, change the audit account password on a recurring or event-initiated schedule by using the API or CLI. Rationale: The password for the account for each VI workload domain NSX Local Manager cluster expires based on the password expiration settings the account. SDDC Manager does not manage the workload domain NSX Local Manager cluster audit account password. Implication: • You must manage the password change for the account by using the API or CLI. • You must monitor the password expiration of the account. Component: NSX | ||
| IAM-NSX-SEC-014 | For each NSX Edge cluster deployed and managed by SDDC Manager, change the root, admin, and audit… | AvailabilitySecurity |
Decision: For each NSX Edge cluster deployed and managed by SDDC Manager, change the root, admin, and audit account passwords for each NSX Edge node on a recurring or event-initiated schedule by using SDDC Manager. Rationale: The passwords for the accounts for each NSX Edge node in an NSX Edge cluster managed by SDDC Manager expire based on the password expiration settings for each account. • For each NSX Edge node in an NSX Edge cluster managed by SDDC Manager, the accounts passwords must be known and managed by SDDC Manager. Implication: • You must manage the password change for the accounts by using SDDC Manager. • If the authentication policy sets the minimum password length to a value greater than 20, automatic password rotation in SDDC Manager cannot be performed. Passwords must be updated or remediated. Component: NSX | ||
| IAM-SDDC-SEC-001 | Assign the Admin role in SDDC Manager to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the Admin role in SDDC Manager to an Active Directory security group. Rationale: By assigning the Admin role to an Active Directory security group, you can simplify and manage user access with administrative rights to SDDC Manager. Implication: • An Active Directory security group must be created before assigning a role. • You must maintain the life cycle and availability of the security group in Active Directory. Component: SDDC | ||
| IAM-SDDC-SEC-002 | Assign the Operator role in SDDC Manager to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the Operator role in SDDC Manager to an Active Directory security group. Rationale: By assigning the Operator role to an Active Directory security group, you can simplify and manage user access with operative rights to SDDC Manager. Implication: • An Active Directory security group must be created before assigning a role. • You must maintain the life cycle and availability of the security group in Active Directory. Component: SDDC | ||
| IAM-SDDC-SEC-003 | Assign the Viewer role in SDDC Manager to an Active Directory security group. | AvailabilitySecurityManageability |
Decision: Assign the Viewer role in SDDC Manager to an Active Directory security group. Rationale: By assigning the Viewer role to an Active Directory security group, you can create user accounts that have read-only rights in SDDC Manager. Implication: • An Active Directory security group must be created before assigning a role. • You must maintain the life cycle and availability of the security group in Active Directory. Component: SDDC | ||
| IAM-SDDC-SEC-004 | Configure the password expiration policy for the SDDC Manager appliance. | RecoverabilitySecurity |
Decision: Configure the password expiration policy for the SDDC Manager appliance. Rationale: • You configure the password expiration policy for the SDDC Manager appliance to align with the requirements of your organization which might be based on industry compliance standards. • The password expiration policy is applicable only to the following accounts for the SDDC Manager appliance: – root account – vcf account – backup account Implication: You must manage the password expiration policy on the SDDC Manager appliance by using the virtual appliance console. Component: SDDC | ||
| IAM-SDDC-SEC-005 | Configure the password complexity policy for the SDDC Manager appliance. | Security |
Decision: Configure the password complexity policy for the SDDC Manager appliance. Rationale: • You configure the password complexity policy for SDDC Manager to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local SDDC Manager users. Implication: You must manage the password complexity policy on the SDDC Manager appliance by using the virtual appliance console. Component: SDDC | ||
| IAM-SDDC-SEC-006 | Configure the account lockout policy for the SDDC Manager appliance. | Security |
Decision: Configure the account lockout policy for the SDDC Manager appliance. Rationale: • You configure the account lockout policy for SDDC Manager to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local SDDC Manager users. Implication: You must manage the account lockout policy on the SDDC Manager appliance by using the virtual appliance console. Component: SDDC | ||
| IAM-SDDC-SEC-007 | Change the SDDC Manager virtual appliance root,vcf, and backup account passwords on a recurring or… | RecoverabilitySecurityManageability |
Decision: Change the SDDC Manager virtual appliance root,vcf, and backup account passwords on a recurring or event-initiated schedule by using the appliance shell. Rationale: • The passwords for the root,vcf, and backup accounts for the SDDC Manager virtual appliance expire based on the password expiration settings for each account. • You cannot update the SDDC Manager virtual appliance account passwords through the SDDC Manager user interface or API. Implication: • You must manage the password change for the virtual appliance root,vcf, and backup accounts by using the SDDC Manager virtual appliance console. • You must monitor the password expiration of the accounts. Component: SDDC | ||
| IAM-SDDC-SEC-008 | Change the SDDC Manager local administrative admin@local account password on a recurring or… | Security |
Decision: Change the SDDC Manager local administrative admin@local account password on a recurring or event-initiated schedule by using the API. Rationale: The password for the SDDC Manager local administrative admin@local account does not expire. Implication: You must routinely perform the password change for the admin@local account by using the API. Component: SDDC | ||
Prerequisites
- VCF version listed in Support Matrix (5.1.0, 5.1.1, 5.2.0, 5.2.1)
- Environment configured per Before You Apply This Guidance
- Captured all parameters for Identity and Access Management tab of VCF Planning and Preparation Workbook
- VCF instance healthy and fully operational
- DNS forward/reverse records for relevant components
- AD Domain Controllers available
- Required AD service accounts created
- Required AD security groups created
- Microsoft Certificate Authority available
- OpenSSL 3.0 or later installed on PowerShell host
- PowerShell 7.2 or later for automation
- PowerShell modules: VMware.PowerCLI >= 13.2.1
- PowerShell modules: VMware.vSphere.SsoAdmin >= 1.3.9
- PowerShell modules: ImportExcel >= 7.8.5
- PowerShell modules: PowerVCF >= 2.4.0
- PowerShell modules: PowerValidatedSolutions >= 2.11.0
- PowerShell modules: VMware.CloudFoundation.PasswordManagement >= 1.8.1 (password policies)
Implementation Procedure
PowerShell automation workflow
- Install/import modules; run Test-PowerValidatedSolutionsPrereq to verify
- Create folder structure (generatedJsons, certificates, binaries, validatedSolutions)
- Populate VCF Planning and Preparation Workbook (e.g. instanceA-pnpWorkbook.xlsx)
- Run Start-ValidatedSolutionMenu with jsonPath/certificatePath/binaryPath/protectedWorkbook/logPath
- From the main menu, enter 04. (IAM) Identity and Access Management, then run sub-options 01. Generate JSON Specification File, 02. Verify Prerequisites, 03. Request Root Certificate for the Microsoft AD Domain and 05. End-to-End Deployment
UI implementation outline
- vCenter: Administration > Single Sign On > Configuration > Identity Sources > Add (Active Directory over LDAP) with LDAPS URI, Base DN for users, Base DN for groups, Bind DN, Bind password, and LDAPS certificate chain
Personas
| Persona | Responsibility | Component role or group |
|---|---|---|
| Cloud Admin | vSphere infrastructure and solution environments | vCenter SSO Administrator; vCenter Server Administrator; NSX Enterprise Admin; SDDC Manager Administrator |
| VI Admin | vSphere infrastructure level environments | vCenter Server Administrator; NSX Network Engineer; SDDC Manager Operator |
| Network Admin | Network level environments | NSX Enterprise Admin |
| Compliance Officer | Read-only access for auditing and compliance review | vCenter Server Read Only; NSX Auditor; SDDC Manager Viewer |
Day-2 Operations Tasks
Operational verification — vCenter Server
After installation, identity changes or outageLog in to each vCenter with the local system account (administrator@vsphere.local), then with an AD account from the Administrator group (IAM-VCS-SEC-003) and confirm the expected permission scope; repeat per vCenter instance.
Operational verification — NSX
After installation or identity changesLog in to each NSX Local Manager with an AD account in the groups mapped to Enterprise Admin, Network Engineer or Auditor and browse the UI for the expected menus; repeat for every Local Manager (and Global Manager where present). Troubleshooting: AD connectivity, NSX AD integration, group membership, account not locked (p.73).
Operational verification — SDDC Manager
After installation or identity changesLog in to SDDC Manager with AD accounts in the Admin, Operator and Viewer groups (IAM-SDDC-SEC-001..003) and confirm the role scope.
Password policies
Per policy; detect drift regularlyConfigure expiration, complexity and lockout for ESXi (IAM-ESXI-SEC-001..003), vCenter appliance and SSO (IAM-VCS-SEC-008..014), NSX Local Managers and Edges (IAM-NSX-SEC-005..010) and SDDC Manager (IAM-SDDC-SEC-004..006); use PowerValidatedSolutions Invoke-PasswordPolicyManager to apply and to report drift (Lab 2).
Password rotation
Recurring or event-initiatedESXi root and SERVICE accounts via SDDC Manager (IAM-ESXI-SEC-004/005, no automated schedule for ESXi); vCenter root and SSO administrator via SDDC Manager (IAM-VCS-SEC-015/016); NSX Local Manager and Edge root/admin/audit via SDDC Manager (IAM-NSX-SEC-011/014; 5.0 and earlier: audit via API/CLI, IAM-NSX-SEC-012/013); SDDC Manager root/vcf/backup via appliance shell and admin@local via API (IAM-SDDC-SEC-007/008).
Certificate management for LDAPS
When AD domain-controller certificates rotateUpdate the trusted CA certificate on the vCenter identity source and the NSX LDAP source so LDAPS binds keep working (IAM-VCS-SEC-001, IAM-NSX-SEC-001).
Authentication transition
One-off, then as identity providers changeMigrate NSX from Workspace ONE Access to AD over LDAP (Lab 3) and verify role mapping with the persona accounts.
Monitoring Points
- ProcVerify authentication using administrator@vsphere.local
- Verify ELM active for all vCenters (all instances visible in Hosts & Clusters)
- ProcVerify authentication using AD user account
- Verify menu access matches expected role
- Verify menu access
- Verify role-appropriate menu access
- Browse and verify menu access
- ProcVerify AD LDAP connection
- Click Check Status on LDAP domain row
- Verify Status = Success
Troubleshooting
Likely Panelist Questions
Q: Why AD over LDAPS rather than Integrated Windows Authentication or WS1 Access?
IAM-VCS-SEC-001 and IAM-NSX-SEC-001: LDAPS is the validated identity source for vCenter and NSX; it encrypts the bind, needs only a read-only bind account (IAM-VCS-SEC-002) and avoids the WS1 Access dependency; multi-domain forests need the right group scope.
Q: How do you keep administrator@vsphere.local out of daily use?
IAM-VCF-SEC-001..003: AD groups mapped to roles per component, local accounts limited to break-glass and rotated by SDDC Manager (IAM-VCS-SEC-016).
Q: What does SDDC Manager rotate and what does it not?
ESXi root/SERVICE, vCenter root/SSO administrator, NSX Local Manager and Edge root/admin/audit (5.1+) are rotated by SDDC Manager; SDDC Manager's own root/vcf/backup use the appliance shell and admin@local the API (IAM-SDDC-SEC-007/008); NSX Global Managers are out of scope.
Failure Scenarios
Trade-off Analysis
vCenter built-in identity provider with AD over LDAPS vs external IdP federation
Chosen: AD over LDAPS (IAM-VCS-SEC-001)
Justification: Validated, simple, no extra appliances; no MFA or SAML federation without an external IdP.
Shared SSO across instances vs dedicated identity per instance
Chosen: Per-instance SSO with the same AD groups
Justification: Keeps instances independent for DR while roles stay consistent through AD.
administrator@vsphere.local for daily operations vs AD groups
Chosen: AD groups; local account rotated and reserved
Justification: Auditability and least privilege (IAM-VCF-SEC-001/003).
Quiz — Identity & Access Management
- SAML 2.0 federation
- OpenLDAP
- Active Directory over LDAP with SSL (LDAPS)
- Active Directory (Integrated Windows Authentication)
- Never, SDDC Manager prohibits it
- Always, to enforce AD-based logins
- Only when using NFS v4.1 with Kerberos supplemental storage
- Only when Enhanced Linked Mode is active
- 5
- 99999
- 3
- 10
- vcf
- backup
- admin@local
- root
- PowerVCF
- VMware.CloudFoundation.PasswordManagement
- VMware.PowerCLI
- PowerValidatedSolutions
- Only Administrators group works
- They cannot participate in ELM
- They can use ELM only if Bind DN is in root domain
- They can still use ELM with global groups
- 14
- 12
- 8
- 6
- Security Operator
- Enterprise Admin
- Network Admin
- Auditor
- Per local user, 90 days
- Per built-in IdP domain (e.g. vsphere.local), 90 days
- Global across ELM, 60 days
- Per vCenter instance, 365 days
- Account Operators group with Join Computers to Domain delegation
- Schema Admins
- Enterprise Admins
- Domain Admins
- 3
- 10
- 5
- 15
- 636
- 389
- 3269
- 3268
- Viewer
- Administrator
- Auditor
- Operator
- Edit LDAP domain server and paste new certificate, then Apply & Save
- Run SDDC Manager certificate rotation
- Delete and re-create the AD identity source
- Restart NSX Manager
- Generating random passwords
- Forcing AD password reset
- Synchronizing SDDC Manager inventory with externally-set password and (optionally) rotating it
- Resetting vCenter SSO administrator password
Flashcards — Identity & Access Management
Labs
Lab 1: Configure AD over LDAPS as IdP for vCenter and Assign Role to AD Security Group
Configure vCenter SSO to use AD over LDAPS and assign an AD group to the Administrator role with global permissions.
Starting State: VCF 5.2 management domain operational; AD DCs with LDAPS CA-signed certificate available; AD security group gg-vc-admins created; administrator@vsphere.local access.
- Export AD root CA certificate in Base-64 PEM
- Log in to management vCenter as administrator@vsphere.local
- Administration > Single Sign On > Configuration > Identity Provider > Identity Sources > Add
- Select 'Active Directory over LDAP'; provide Name, Base DN for users, Base DN for groups, Domain name, Domain alias, Primary server URL (ldaps://dc01.sfo.rainpole.io:636), Bind DN, Bind password, upload CA certificate chain
- Test and Save identity source
- Administration > Access Control > Global Permissions > Add
- Select AD domain, search gg-vc-admins, assign Administrator role, check 'Propagate to children'
- Sign out and log back in as an AD member of gg-vc-admins to verify access
Log in to the vSphere Client as a member of the Active Directory group assigned the Administrator role (e.g. gg-vc-admins); Administration > Single Sign On > Configuration shows the AD over LDAPS identity source, and Administration > Global Permissions shows the group with Administrator (IAM-VCS-SEC-001/003/004).
Lab 2: Configure Password Policy and Detect Drift Across VCF Using PowerShell
Generate baseline password policy JSON, modify to match org standards, run drift report, apply changes.
Starting State: Windows/Linux workstation with PowerShell 7.2+, VMware.PowerCLI, PowerVCF, PowerValidatedSolutions, VMware.CloudFoundation.PasswordManagement installed; SDDC Manager accessible.
- Import-Module VMware.CloudFoundation.PasswordManagement
- Get-PasswordPolicyDefault -generateJson -jsonFile passwordPolicyConfig.json
- Edit passwordPolicyConfig.json to set ESXi Security.PasswordMaxDays=90, deny=5; SSO max-lifetime=60; SDDC Manager minlen=12
- Invoke-PasswordPolicyManager -sddcManagerFqdn $sddcManagerFqdn -sddcManagerUser administrator@vsphere.local -sddcManagerPass <pw> -sddcRootPass <root-pw> -reportPath F:\Reporting -allDomains -drift -policyFile passwordPolicyConfig.json
- Review HTML drift report; examine mismatches per component
- Start-PasswordPolicyConfig -sddcManagerFqdn ... -policyFile passwordPolicyConfig.json
- Re-run drift report to validate zero-drift state
Invoke-PasswordPolicyManager drift report shows 0 mismatches against the configured password expiration, complexity and lockout policies for ESXi, vCenter SSO, NSX and SDDC Manager (IAM-*-SEC password-policy rows).
Lab 3: Authentication Transition — Migrate NSX from Workspace ONE Access to AD over LDAP
Reconfigure NSX to use AD over LDAP natively, removing Workspace ONE Access integration, and reassigning roles.
Starting State: VCF with NSX configured to use standalone Workspace ONE Access as authentication provider; AD security groups gg-nsx-enterprise-admins, gg-nsx-network-admins, gg-nsx-auditors exist.
- Start PowerShell and connect to NSX Manager via PowerValidatedSolutions
- Undo-NsxtVidmRole -server $sddcManagerFqdn -user ... -domain $sddcDomainName -principal gg-nsx-enterprise-admins@sfo.rainpole.io
- Repeat Undo-NsxtVidmRole for network-admins and auditors groups
- UI: NSX System > Settings > User Management > Authentication Providers > VMware Identity Manager > Edit > toggle Off > Save
- Configure LDAP identity source: LDAP tab > Add domain (sfo.rainpole.io); add LDAP server (ldaps://dc01... :636) with Bind DN and CA cert; Save
- Click Check Status — expect Success
- Assign NSX roles: Enterprise Admin to gg-nsx-enterprise-admins (IAM-NSX-SEC-002); Network Admin to gg-nsx-network-admins (IAM-NSX-SEC-003; the VVS persona table and PowerShell variable label this group Network Engineer); Auditor to gg-nsx-auditors (IAM-NSX-SEC-004)
- Repeat for each NSX Local Manager in each workload domain and all NSX Global Managers
- Verify by logging in as AD user and confirming role-appropriate access
NSX Manager > System > Users and Roles shows the AD over LDAP identity source and the Active Directory groups mapped to Enterprise Admin, Network Admin and Auditor (IAM-NSX-SEC-001..004); Check Status reports Success and Workspace ONE Access is no longer the identity source.