6.7

Table Of Contents
Evaluate the Use of Linux Clients with CLIs and SDKs
Communications between client components and a vCenter Server system or ESXi hosts are protected
by SSL-based encryption by default. Linux versions of these components do not perform certificate
validation. Consider restricting the use of these clients.
To improve security, you can replace the VMCA-signed certificates on the vCenter Server system and on
the ESXi hosts with certificates that are signed by an enterprise or third-party CA. However, certain
communications with Linux clients might still be vulnerable to man-in-the-middle attacks. The following
components are vulnerable when they run on the Linux operating system.
n
vCLI commands
n
vSphere SDK for Perl scripts
n
Programs that are written using the vSphere Web Services SDK
You can relax the restriction against using Linux clients if you enforce proper controls.
n
Restrict management network access to authorized systems only.
n
Use firewalls to ensure that only authorized hosts are allowed to access vCenter Server.
n
Use jump-box systems to ensure that Linux clients are behind the jump.
Examine vSphere Web Client Plug-Ins
vSphere Web Client extensions run at the same privilege level as the user who is logged in. A malicious
extension can masquerade as a useful plug-in and perform harmful operations such as stealing
credentials or changing the system configuration. To increase security, use a vSphere Web Client
installation that includes only authorized extensions from trusted sources.
A vCenter installation includes the vSphere Web Client extensibility framework. You can use this
framework to extend the vSphere Web Client with menu selections or toolbar icons. The extensions can
provide access to vCenter add-on components or external, Web-based functionality.
Using the extensibility framework results in a risk of introducing unintended capabilities. For example, if
an administrator installs a plug-in in an instance of the vSphere Web Client, the plug-in can execute
arbitrary commands with the privilege level of that administrator.
To protect against potential compromise of your vSphere Web Client, examine all installed plug-ins
periodically and make sure that each plug-in comes from a trusted source.
Prerequisites
You must have privileges to access the vCenter Single Sign-On service. These privileges differ from
vCenter Server privileges.
Procedure
1 Log in to the vSphere Web Client as administrator@vsphere.local or a user with vCenter Single Sign-
On privileges.
2 From the Home page, select Administration, and then select Client Plug-Ins under Solutions.
vSphere Security
VMware, Inc. 114