STIGQter: STIG Summary: VMware ESXi Version 5 Virtual Machine Security Technical Implementation Guide Version: 1 Release: 7 Benchmark Date: 28 Jul 2017: The system must disable VM Monitor Control during normal operation. STIGQter: STIG Summary: VMware ESXi Version 5 Virtual Machine Security Technical Implementation Guide Version: 1 Release: 7 Benchmark Date: 28 Jul 2017: The system must disable VM Monitor Control during normal operation.SV-51312r1_rule
V-39454
ESXi5-212
ESXI5-VM-000013
CAT II
10
Configure the VM with the correct "<keyword> = <keyval>" pair.
To edit a powered-down virtual machine's .vmx file, first remove it from vCenter Server's inventory. Manual additions to the .vmx file from ESXi will be overwritten by any registered entries stored in the vCenter Server database. Make a backup copy of the .vmx file. If the edit breaks the virtual machine, it can be rolled back to the original version of the file.
Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Storage.
Right-click on the appropriate datastore and click Browse Datastore.
Navigate to the folder named after the virtual machine, and locate the <virtual machine>.vmx file.
Right-click the .vmx file and click Remove from inventory.
Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client.
Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Software, Security Profile, Services, Properties, ESXi Shell, and Options, respectively.
Start the ESXi Shell service, where/as required.
As root, log in to the ESXi host and locate the VM's vmx file.
# find / | grep vmx
Add the following to the VM's vmx file.
keyword = "keyval"
Where:
keyword = isolation.monitor.control.disable
keyval = TRUE
Re-enable Lockdown Mode on the host.
Re-register the VM with the vCenter Server:
Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Storage.
Right-click on the appropriate datastore and click Browse Datastore.
Navigate to the folder named after the virtual machine, and locate the <virtual machine>.vmx file.
Right-click the .vmx file and click Add to inventory. The Add to Inventory wizard opens.
Continue to follow the wizard to add the virtual machine.
Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client.
Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Software, Security Profile, Services, Properties, ESXi Shell, and Options, respectively.
Start the ESXi Shell service, where/as required.
As root, log in to the ESXi Shell and locate the VM's vmx file.
# find / | grep vmx
Check the VM's ".vmx" file for the correct "<keyword> = <keyval>" pair.
keyword = isolation.monitor.control.disable
keyval = TRUE
# grep "^<keyword>" <the VM's vmx file>
If the above command return is either empty or does not reflect the above keyword and keyval value(s), this is a finding.
Re-enable Lockdown Mode on the host.
V-39454
False
ESXI5-VM-000013
Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client.
Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Software, Security Profile, Services, Properties, ESXi Shell, and Options, respectively.
Start the ESXi Shell service, where/as required.
As root, log in to the ESXi Shell and locate the VM's vmx file.
# find / | grep vmx
Check the VM's ".vmx" file for the correct "<keyword> = <keyval>" pair.
keyword = isolation.monitor.control.disable
keyval = TRUE
# grep "^<keyword>" <the VM's vmx file>
If the above command return is either empty or does not reflect the above keyword and keyval value(s), this is a finding.
Re-enable Lockdown Mode on the host.
M
2438