6.0.3

Table Of Contents
Prevent Guest Operating System Processes from Sending Configuration
Messages to the Host
You can prevent guests from writing any name-value pairs to the conguration le. This is appropriate
when guest operating systems must be prevented from modifying conguration seings.
Prerequisites
Turn o the virtual machine.
Procedure
1 Find the virtual machine in the vSphere Web Client inventory.
a Select a data center, folder, cluster, resource pool, or host.
b Click the Related Objects tab and click Virtual Machines.
2 Right-click the virtual machine and click Edit .
3 Select VM Options.
4 Click Advanced and click Edit .
5 Click Add Row and type the following values in the Name and Value columns.
n
In the Name column: isolation.tools.setinfo.disable
n
In the Value column: true
6 Click OK to close the Conguration Parameters dialog box, and click OK again.
Avoid Using Independent Nonpersistent Disks
When you use independent nonpersistent disks, successful aackers can remove any evidence that the
machine was compromised by shuing down or rebooting the system. Without a persistent record of
activity on a virtual machine, administrators might be unaware of an aack. Therefore, you should avoid
using independent nonpersistent disks.
Procedure
u
Ensure that virtual machine activity is logged remotely on a separate server, such as a syslog server or
equivalent Windows-based event collector.
If remote logging of events and activity is not congured for the guest, scsiX:Y.mode should be one of
the following seings:
n
Not present
n
Not set to independent nonpersistent
When nonpersistent mode is not enabled, you cannot roll a virtual machine back to a known state when you
reboot the system.
vSphere Security
226 VMware, Inc.