6.0.3

Table Of Contents
Securing vCenter Server Systems 6
Securing vCenter Server includes ensuring security of the host where vCenter Server is running, following
best practices for assigning privileges and roles, and verifying the integrity of the clients that connect to
vCenter Server.
This chapter includes the following topics:
n
“vCenter Server Security Best Practices,” on page 209
n
“Verify Thumbprints for Legacy ESXi Hosts,” on page 213
n
“Verify that SSL Certicate Validation Over Network File Copy Is Enabled,” on page 214
n
“vCenter Server TCP and UDP Ports,” on page 215
n
“Control CIM-Based Hardware Monitoring Tool Access,” on page 216
vCenter Server Security Best Practices
Following vCenter Server security best practices helps you ensure the integrity of your vSphere
environment.
Best Practices for vCenter Server Access Control
Strictly control access to dierent vCenter Server components to increase security for the system.
The following guidelines help ensure security of your environment.
Use Named Accounts
n
If the local Windows administrator account currently has full administrative rights to vCenter Server,
remove those access rights and grant those rights to one or more named vCenter Server administrator
accounts. Grant full administrative rights only to those administrators who are required to have it. Do
not grant this privilege to any group whose membership is not strictly controlled.
N Starting with vSphere 6.0, the local administrator no longer has full administrative rights to
vCenter Server by default. Using local operating system users is not recommended.
n
Install vCenter Server using a service account instead of a Windows account. The service account must
be an administrator on the local machine.
n
Make sure that applications use unique service accounts when connecting to a vCenter Server system.
VMware, Inc.
209