6.0.3

Table Of Contents
Security in the vSphere Environment 1
The components of a vSphere environment are secured out of the box by a number of features such as
certicates, authorization, a rewall on each ESXi, limited access, and so on. You can modify the default
setup in many ways - for example, you can set permissions on vCenter objects, open rewall ports, or
change the default certicates. This results in maximum exibility in securing vCenter Server systems, ESXi
hosts, and virtual machines.
A high level overview of dierent areas of vSphere that require aention helps you plan your security
strategy. You also benet from additional vSphere Security resources on the VMware website.
This chapter includes the following topics:
n
“Securing the ESXi Hypervisor,” on page 11
n
“Securing vCenter Server Systems and Associated Services,” on page 13
n
“Securing Virtual Machines,” on page 14
n
“Securing the Virtual Networking Layer,” on page 14
n
“Passwords in Your vSphere Environment,” on page 16
n
“Security Best Practices and Resources,” on page 17
Securing the ESXi Hypervisor
The ESXi hypervisor is secured out of the box. You can further protect ESXi hosts by using lockdown mode,
and other built-in features. If you set up a reference host and make changes to all hosts based on that host's
host proles, or if you perform scripted management, you further protect your environment by assuring
changes apply to all hosts.
Use the following features, discussed in detail in this guide, to enhance protection of ESXi hosts that are
managed by vCenter Server. See also the Security of the VMware vSphere Hypervisor white paper.
Limit ESXi Access
By default, the ESXi Shell and SSH services are not running and only the root
user can log in to the Direct Console User Interface (DCUI). If you decide to
enable ESXi or SSH access, you can set timeouts to limit the risk of
unauthorized access.
VMware, Inc. 11