Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

VMware vSphere 6.5 Virtual Machine Security Technical Implementation Guide

V2R1 · · · Released 27 Oct 2021 · 39 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V1R2 · 25 Oct 2019 +39 −39

Comparison against the immediately-prior release (V1R2). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Added rules 39

  • V-237065 Low Copy operations must be disabled on the virtual machine.
  • V-237066 Low Drag and drop operations must be disabled on the virtual machine.
  • V-237067 Low GUI functionality for copy/paste operations must be disabled on the virtual machine.
  • V-237068 Low Paste operations must be disabled on the virtual machine.
  • V-237069 Medium Virtual disk shrinking must be disabled on the virtual machine.
  • V-237070 Medium Virtual disk erasure must be disabled on the virtual machine.
  • V-237071 Medium Independent, non-persistent disks must be not be used on the virtual machine.
  • V-237072 Medium HGFS file transfers must be disabled on the virtual machine.
  • V-237073 Low The unexposed feature keyword isolation.tools.ghi.autologon.disable must be set on the virtual machine.
  • V-237074 Low The unexposed feature keyword isolation.tools.ghi.launchmenu.change must be set on the virtual machine.
  • V-237075 Low The unexposed feature keyword isolation.tools.memSchedFakeSampleStats.disable must be set on the virtual machine.
  • V-237076 Low The unexposed feature keyword isolation.tools.ghi.protocolhandler.info.disable must be set on the virtual machine.
  • V-237077 Low The unexposed feature keyword isolation.ghi.host.shellAction.disable must be set on the virtual machine.
  • V-237078 Low The unexposed feature keyword isolation.tools.ghi.trayicon.disable must be set on the virtual machine.
  • V-237079 Low The unexposed feature keyword isolation.tools.unity.disable must be set on the virtual machine.
  • V-237080 Low The unexposed feature keyword isolation.tools.unityInterlockOperation.disable must be set on the virtual machine.
  • V-237081 Low The unexposed feature keyword isolation.tools.unity.push.update.disable must be set on the virtual machine.
  • V-237082 Low The unexposed feature keyword isolation.tools.unity.taskbar.disable must be set on the virtual machine.
  • V-237083 Low The unexposed feature keyword isolation.tools.unityActive.disable must be set on the virtual machine.
  • V-237084 Low The unexposed feature keyword isolation.tools.unity.windowContents.disable must be set on the virtual machine.
  • V-237085 Low The unexposed feature keyword isolation.tools.vmxDnDVersionGet.disable must be set on the virtual machine.
  • V-237086 Low The unexposed feature keyword isolation.tools.guestDnDVersionSet.disable must be set on the virtual machine.
  • V-237087 Medium Unauthorized floppy devices must be disconnected on the virtual machine.
  • V-237088 Low Unauthorized CD/DVD devices must be disconnected on the virtual machine.
  • V-237089 Medium Unauthorized parallel devices must be disconnected on the virtual machine.
  • V-237090 Medium Unauthorized serial devices must be disconnected on the virtual machine.
  • V-237091 Medium Unauthorized USB devices must be disconnected on the virtual machine.
  • V-237092 Medium Console connection sharing must be limited on the virtual machine.
  • V-237093 Medium Console access through the VNC protocol must be disabled on the virtual machine.
  • V-237094 Low Informational messages from the virtual machine to the VMX file must be limited on the virtual machine.
  • V-237095 Medium Unauthorized removal, connection and modification of devices must be prevented on the virtual machine.
  • V-237096 Medium The virtual machine must not be able to obtain host information from the hypervisor.
  • V-237097 Low Shared salt values must be disabled on the virtual machine.
  • V-237098 Low Access to virtual machines through the dvfilter network APIs must be controlled.
  • V-237099 Low System administrators must use templates to deploy virtual machines whenever possible.
  • V-237100 Medium Use of the virtual machine console must be minimized.
  • V-237101 Medium The virtual machine guest operating system must be locked when the last console connection is closed.
  • V-237102 Low 3D features on the virtual machine must be disabled when not required.
  • V-237103 Medium Encryption must be enabled for vMotion on the virtual machine.

Removed rules 39

  • V-94563 Low Copy operations must be disabled on the virtual machine.
  • V-94565 Low Drag and drop operations must be disabled on the virtual machine.
  • V-94567 Low GUI functionality for copy/paste operations must be disabled on the virtual machine.
  • V-94569 Low Paste operations must be disabled on the virtual machine.
  • V-94571 Medium Virtual disk shrinking must be disabled on the virtual machine.
  • V-94573 Medium Virtual disk erasure must be disabled on the virtual machine.
  • V-94575 Medium Independent, non-persistent disks must be not be used on the virtual machine.
  • V-94577 Medium HGFS file transfers must be disabled on the virtual machine.
  • V-94579 Low The unexposed feature keyword isolation.tools.ghi.autologon.disable must be set on the virtual machine.
  • V-94581 Low The unexposed feature keyword isolation.tools.ghi.launchmenu.change must be set on the virtual machine.
  • V-94583 Low The unexposed feature keyword isolation.tools.memSchedFakeSampleStats.disable must be set on the virtual machine.
  • V-94585 Low The unexposed feature keyword isolation.tools.ghi.protocolhandler.info.disable must be set on the virtual machine.
  • V-94593 Low The unexposed feature keyword isolation.ghi.host.shellAction.disable must be set on the virtual machine.
  • V-94595 Low The unexposed feature keyword isolation.tools.ghi.trayicon.disable must be set on the virtual machine.
  • V-94597 Low The unexposed feature keyword isolation.tools.unity.disable must be set on the virtual machine.
  • V-94599 Low The unexposed feature keyword isolation.tools.unityInterlockOperation.disable must be set on the virtual machine.
  • V-94601 Low The unexposed feature keyword isolation.tools.unity.push.update.disable must be set on the virtual machine.
  • V-94603 Low The unexposed feature keyword isolation.tools.unity.taskbar.disable must be set on the virtual machine.
  • V-94605 Low The unexposed feature keyword isolation.tools.unityActive.disable must be set on the virtual machine.
  • V-94607 Low The unexposed feature keyword isolation.tools.unity.windowContents.disable must be set on the virtual machine.
  • V-94609 Low The unexposed feature keyword isolation.tools.vmxDnDVersionGet.disable must be set on the virtual machine.
  • V-94611 Low The unexposed feature keyword isolation.tools.guestDnDVersionSet.disable must be set on the virtual machine.
  • V-94613 Medium Unauthorized floppy devices must be disconnected on the virtual machine.
  • V-94615 Low Unauthorized CD/DVD devices must be disconnected on the virtual machine.
  • V-94617 Medium Unauthorized parallel devices must be disconnected on the virtual machine.
  • V-94619 Medium Unauthorized serial devices must be disconnected on the virtual machine.
  • V-94621 Medium Unauthorized USB devices must be disconnected on the virtual machine.
  • V-94623 Medium Console connection sharing must be limited on the virtual machine.
  • V-94625 Medium Console access through the VNC protocol must be disabled on the virtual machine.
  • V-94627 Low Informational messages from the virtual machine to the VMX file must be limited on the virtual machine.
  • V-94629 Medium Unauthorized removal, connection and modification of devices must be prevented on the virtual machine.
  • V-94631 Medium The virtual machine must not be able to obtain host information from the hypervisor.
  • V-94633 Low Shared salt values must be disabled on the virtual machine.
  • V-94635 Low Access to virtual machines through the dvfilter network APIs must be controlled.
  • V-94637 Low System administrators must use templates to deploy virtual machines whenever possible.
  • V-94639 Medium Use of the virtual machine console must be minimized.
  • V-94647 Medium The virtual machine guest operating system must be locked when the last console connection is closed.
  • V-94649 Low 3D features on the virtual machine must be disabled when not required.
  • V-94651 Medium Encryption must be enabled for vMotion on the virtual machine.
Sort by
a
Copy operations must be disabled on the virtual machine.
CM-6 - Low - CCI-000366 - V-237065 - SV-237065r640032_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000001
Vuln IDs
  • V-237065
  • V-94563
Rule IDs
  • SV-237065r640032_rule
  • SV-104393
Copy and paste operations are disabled by default; however, by explicitly disabling this feature it will enable audit controls to check that this setting is correct. Copy, paste, drag and drop, or GUI copy/paste operations between the guest OS and the remote console could provide the means for an attacker to compromise the VM.
Checks: C-40284r640030_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.copy.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.copy.disable If the virtual machine advanced setting isolation.tools.copy.disable does not exist or is not set to true, this is a finding.

Fix: F-40247r640031_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.copy.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.copy.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.copy.disable | Set-AdvancedSetting -Value true

a
Drag and drop operations must be disabled on the virtual machine.
CM-6 - Low - CCI-000366 - V-237066 - SV-237066r640035_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000002
Vuln IDs
  • V-237066
  • V-94565
Rule IDs
  • SV-237066r640035_rule
  • SV-104395
Copy and paste operations are disabled by default; however, by explicitly disabling this feature it will enable audit controls to check that this setting is correct. Copy, paste, drag and drop, or GUI copy/paste operations between the guest OS and the remote console could provide the means for an attacker to compromise the VM.
Checks: C-40285r640033_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.dnd.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.dnd.disable If the virtual machine advanced setting isolation.tools.dnd.disable does not exist or is not set to true, this is a finding.

Fix: F-40248r640034_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.dnd.disable value is set to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.dnd.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.dnd.disable | Set-AdvancedSetting -Value true

a
GUI functionality for copy/paste operations must be disabled on the virtual machine.
CM-6 - Low - CCI-000366 - V-237067 - SV-237067r640038_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000003
Vuln IDs
  • V-237067
  • V-94567
Rule IDs
  • SV-237067r640038_rule
  • SV-104397
Copy and paste operations are disabled by default; however, by explicitly disabling this feature it will enable audit controls to check that this setting is correct. Copy, paste, drag and drop, or GUI copy/paste operations between the guest OS and the remote console could provide the means for an attacker to compromise the VM.
Checks: C-40286r640036_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.setGUIOptions.enable value is set to false. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.setGUIOptions.enable If the virtual machine advanced setting isolation.tools.setGUIOptions.enable does not exist or is not set to false, this is a finding.

Fix: F-40249r640037_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.setGUIOptions.enable value and set it to false. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.setGUIOptions.enable -Value false If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.setGUIOptions.enable | Set-AdvancedSetting -Value false

a
Paste operations must be disabled on the virtual machine.
CM-6 - Low - CCI-000366 - V-237068 - SV-237068r640041_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000004
Vuln IDs
  • V-237068
  • V-94569
Rule IDs
  • SV-237068r640041_rule
  • SV-104399
Copy and paste operations are disabled by default; however, by explicitly disabling this feature it will enable audit controls to check that this setting is correct. Copy, paste, drag and drop, or GUI copy/paste operations between the guest OS and the remote console could provide the means for an attacker to compromise the VM.
Checks: C-40287r640039_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.paste.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.paste.disable If the virtual machine advanced setting isolation.tools.paste.disable does not exist or is not set to true, this is a finding.

Fix: F-40250r640040_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.paste.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.paste.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.paste.disable | Set-AdvancedSetting -Value true

b
Virtual disk shrinking must be disabled on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237069 - SV-237069r640044_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000005
Vuln IDs
  • V-237069
  • V-94571
Rule IDs
  • SV-237069r640044_rule
  • SV-104401
Shrinking a virtual disk reclaims unused space in it. If there is empty space in the disk, this process reduces the amount of space the virtual disk occupies on the host drive. Normal users and processes-that is, users and processes without root or administrator privileges-within virtual machines have the capability to invoke this procedure. However, if this is done repeatedly, the virtual disk can become unavailable while this shrinking is being performed, effectively causing a denial-of-service. In most datacenter environments, disk shrinking is not done, so this feature must be disabled. Repeated disk shrinking can make a virtual disk unavailable. The capability to shrink is available to non-administrative users operating within the VMs guest OS.
Checks: C-40288r640042_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.diskShrink.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.diskShrink.disable If the virtual machine advanced setting isolation.tools.diskShrink.disable does not exist or is not set to true, this is a finding.

Fix: F-40251r640043_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.diskShrink.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.diskShrink.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.diskShrink.disable | Set-AdvancedSetting -Value true

b
Virtual disk erasure must be disabled on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237070 - SV-237070r640047_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000006
Vuln IDs
  • V-237070
  • V-94573
Rule IDs
  • SV-237070r640047_rule
  • SV-104403
Shrinking and wiping (erasing) a virtual disk reclaims unused space in it. If there is empty space in the disk, this process reduces the amount of space the virtual disk occupies on the host drive. Normal users and processes - that is, users and processes without root or administrator privileges - within virtual machines have the capability to invoke this procedure. However, if this is done repeatedly, the virtual disk can become unavailable while this shrinking is being performed, effectively causing a denial-of-service. In most datacenter environments, disk shrinking is not done, so this feature must be disabled. Repeated disk shrinking can make a virtual disk unavailable. The capability to wipe (erase) is available to non-administrative users operating within the VMs guest OS.
Checks: C-40289r640045_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.diskWiper.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.diskWiper.disable If the virtual machine advanced setting isolation.tools.diskWiper.disable does not exist or is not set to true, this is a finding.

Fix: F-40252r640046_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.diskWiper.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.diskWiper.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.diskWiper.disable | Set-AdvancedSetting -Value true

b
Independent, non-persistent disks must be not be used on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237071 - SV-237071r640050_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000007
Vuln IDs
  • V-237071
  • V-94575
Rule IDs
  • SV-237071r640050_rule
  • SV-104405
The security issue with nonpersistent disk mode is that successful attackers, with a simple shutdown or reboot, might undo or remove any traces that they were ever on the machine. To safeguard against this risk, production virtual machines should be set to use persistent disk mode; additionally, make sure that activity within the VM is logged remotely on a separate server, such as a syslog server or equivalent Windows-based event collector. Without a persistent record of activity on a VM, administrators might never know whether they have been attacked or hacked. There can be valid use cases for these types of disks such as with an application presentation solution where read only disks are desired and such cases should be identified and documented.
Checks: C-40290r640048_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Review the attached hard disks and verify they are not configured as independent nonpersistent disks. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-HardDisk | Select Parent, Name, Filename, DiskType, Persistence | FT -AutoSize If the virtual machine has attached disks that are in independent nonpersistent mode and are not documented, this is a finding.

Fix: F-40253r640049_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Select the target hard disk and change the mode to persistent or uncheck Independent. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-HardDisk | Set-HardDisk -Persistence IndependentPersistent or Get-VM "VM Name" | Get-HardDisk | Set-HardDisk -Persistence Persistent

b
HGFS file transfers must be disabled on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237072 - SV-237072r640053_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000008
Vuln IDs
  • V-237072
  • V-94577
Rule IDs
  • SV-237072r640053_rule
  • SV-104407
Setting isolation.tools.hgfsServerSet.disable to true disables registration of the guest's HGFS server with the host. APIs that use HGFS to transfer files to and from the guest operating system, such as some VIX commands, will not function. An attacker could potentially use this to transfer files inside the guest OS.
Checks: C-40291r640051_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.hgfsServerSet.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.hgfsServerSet.disable If the virtual machine advanced setting isolation.tools.hgfsServerSet.disable does not exist or is not set to true, this is a finding.

Fix: F-40254r640052_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.hgfsServerSet.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.hgfsServerSet.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.hgfsServerSet.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.ghi.autologon.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237073 - SV-237073r640056_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000009
Vuln IDs
  • V-237073
  • V-94579
Rule IDs
  • SV-237073r640056_rule
  • SV-104409
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40292r640054_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.ghi.autologon.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.autologon.disable If the virtual machine advanced setting isolation.tools.ghi.autologon.disable does not exist or is not set to true, this is a finding.

Fix: F-40255r640055_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.ghi.autologon.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.ghi.autologon.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.autologon.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.ghi.launchmenu.change must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237074 - SV-237074r640059_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000012
Vuln IDs
  • V-237074
  • V-94581
Rule IDs
  • SV-237074r640059_rule
  • SV-104411
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40293r640057_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.ghi.launchmenu.change value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.launchmenu.change If the virtual machine advanced setting isolation.tools.ghi.launchmenu.change does not exist or is not set to true, this is a finding.

Fix: F-40256r640058_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.ghi.launchmenu.change value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.ghi.launchmenu.change -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.launchmenu.change | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.memSchedFakeSampleStats.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237075 - SV-237075r640062_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000013
Vuln IDs
  • V-237075
  • V-94583
Rule IDs
  • SV-237075r640062_rule
  • SV-104413
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40294r640060_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.memSchedFakeSampleStats.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.memSchedFakeSampleStats.disable If the virtual machine advanced setting isolation.tools.memSchedFakeSampleStats.disable does not exist or is not set to true, this is a finding.

Fix: F-40257r640061_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.memSchedFakeSampleStats.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.memSchedFakeSampleStats.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.memSchedFakeSampleStats.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.ghi.protocolhandler.info.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237076 - SV-237076r640065_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000014
Vuln IDs
  • V-237076
  • V-94585
Rule IDs
  • SV-237076r640065_rule
  • SV-104415
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40295r640063_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.ghi.protocolhandler.info.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.protocolhandler.info.disable If the virtual machine advanced setting isolation.tools.ghi.protocolhandler.info.disable does not exist or is not set to true, this is a finding.

Fix: F-40258r640064_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.ghi.protocolhandler.info.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.ghi.protocolhandler.info.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.protocolhandler.info.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.ghi.host.shellAction.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237077 - SV-237077r640068_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000015
Vuln IDs
  • V-237077
  • V-94593
Rule IDs
  • SV-237077r640068_rule
  • SV-104423
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40296r640066_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.ghi.host.shellAction.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.ghi.host.shellAction.disable If the virtual machine advanced setting isolation.ghi.host.shellAction.disable does not exist or is not set to true, this is a finding.

Fix: F-40259r640067_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.ghi.host.shellAction.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.ghi.host.shellAction.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.ghi.host.shellAction.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.ghi.trayicon.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237078 - SV-237078r640071_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000018
Vuln IDs
  • V-237078
  • V-94595
Rule IDs
  • SV-237078r640071_rule
  • SV-104425
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40297r640069_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.ghi.trayicon.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.trayicon.disable If the virtual machine advanced setting isolation.tools.ghi.trayicon.disable does not exist or is not set to true, this is a finding.

Fix: F-40260r640070_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.ghi.trayicon.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.ghi.trayicon.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.ghi.trayicon.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.unity.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237079 - SV-237079r640074_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000019
Vuln IDs
  • V-237079
  • V-94597
Rule IDs
  • SV-237079r640074_rule
  • SV-104427
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40298r640072_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.unity.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.disable If the virtual machine advanced setting isolation.tools.unity.disable does not exist or is not set to true, this is a finding

Fix: F-40261r640073_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.unity.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.unity.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.unityInterlockOperation.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237080 - SV-237080r640077_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000020
Vuln IDs
  • V-237080
  • V-94599
Rule IDs
  • SV-237080r640077_rule
  • SV-104429
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40299r640075_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.unityInterlockOperation.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unityInterlockOperation.disable If the virtual machine advanced setting isolation.tools.unityInterlockOperation.disable does not exist or is not set to true, this is a finding.

Fix: F-40262r640076_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.unityInterlockOperation.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.unityInterlockOperation.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unityInterlockOperation.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.unity.push.update.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237081 - SV-237081r640080_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000021
Vuln IDs
  • V-237081
  • V-94601
Rule IDs
  • SV-237081r640080_rule
  • SV-104431
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40300r640078_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.unity.push.update.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.push.update.disable If the virtual machine advanced setting isolation.tools.unity.push.update.disable does not exist or is not set to true, this is a finding.

Fix: F-40263r640079_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.unity.push.update.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.unity.push.update.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.push.update.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.unity.taskbar.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237082 - SV-237082r640083_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000022
Vuln IDs
  • V-237082
  • V-94603
Rule IDs
  • SV-237082r640083_rule
  • SV-104433
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40301r640081_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.unity.taskbar.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.taskbar.disable If the virtual machine advanced setting isolation.tools.unity.taskbar.disable does not exist or is not set to true, this is a finding.

Fix: F-40264r640082_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.unity.taskbar.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.unity.taskbar.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.taskbar.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.unityActive.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237083 - SV-237083r640086_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000023
Vuln IDs
  • V-237083
  • V-94605
Rule IDs
  • SV-237083r640086_rule
  • SV-104435
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40302r640084_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.unityActive.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unityActive.disable If the virtual machine advanced setting isolation.tools.unityActive.disable does not exist or is not set to true, this is a finding.

Fix: F-40265r640085_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.unityActive.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.unityActive.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unityActive.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.unity.windowContents.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237084 - SV-237084r640089_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000024
Vuln IDs
  • V-237084
  • V-94607
Rule IDs
  • SV-237084r640089_rule
  • SV-104437
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40303r640087_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.unity.windowContents.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.windowContents.disable If the virtual machine advanced setting isolation.tools.unity.windowContents.disable does not exist or is not set to true, this is a finding.

Fix: F-40266r640088_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.unity.windowContents.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.unity.windowContents.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.unity.windowContents.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.vmxDnDVersionGet.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237085 - SV-237085r640092_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000025
Vuln IDs
  • V-237085
  • V-94609
Rule IDs
  • SV-237085r640092_rule
  • SV-104439
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40304r640090_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.vmxDnDVersionGet.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.vmxDnDVersionGet.disable If the virtual machine advanced setting isolation.tools.vmxDnDVersionGet.disable does not exist or is not set to true, this is a finding.

Fix: F-40267r640091_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.vmxDnDVersionGet.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.vmxDnDVersionGet.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.vmxDnDVersionGet.disable | Set-AdvancedSetting -Value true

a
The unexposed feature keyword isolation.tools.guestDnDVersionSet.disable must be set on the virtual machine.
CM-6 - Low - CCI-000366 - V-237086 - SV-237086r640095_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000026
Vuln IDs
  • V-237086
  • V-94611
Rule IDs
  • SV-237086r640095_rule
  • SV-104441
Some virtual machine advanced settings parameters do not apply on vSphere because VMware virtual machines work on both vSphere and hosted virtualization platforms such as Workstation and Fusion. Explicitly disabling these features reduces the potential for vulnerabilities because it reduces the number of ways in which a guest can affect the host.
Checks: C-40305r640093_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.tools.guestDnDVersionSet.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.guestDnDVersionSet.disable If the virtual machine advanced setting isolation.tools.guestDnDVersionSet.disable does not exist or is not set to true, this is a finding.

Fix: F-40268r640094_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.tools.guestDnDVersionSet.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.tools.guestDnDVersionSet.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.tools.guestDnDVersionSet.disable | Set-AdvancedSetting -Value true

b
Unauthorized floppy devices must be disconnected on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237087 - SV-237087r640098_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000028
Vuln IDs
  • V-237087
  • V-94613
Rule IDs
  • SV-237087r640098_rule
  • SV-104443
Ensure that no device is connected to a virtual machine if it is not required. For example, floppy, serial and parallel ports are rarely used for virtual machines in a datacenter environment, and CD/DVD drives are usually connected only temporarily during software installation.
Checks: C-40306r640096_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Review the VMs hardware and verify no floppy device is connected. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM | Get-FloppyDrive | Select Parent, Name, ConnectionState If a virtual machine has a floppy drive connected, this is a finding.

Fix: F-40269r640097_fix

If the floppy drive is required to be present, then from the vSphere Client right-click the Virtual Machine and go to Edit Settings, make sure the drive is not connected and will not "Connect at power on". If the floppy drive is not required, then from the vSphere Client power off the virtual machine, right-click the Virtual Machine and go to Edit Settings, select the floppy drive and click the circle-x to remove then OK. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-FloppyDrive | Remove-FloppyDrive

a
Unauthorized CD/DVD devices must be disconnected on the virtual machine.
CM-6 - Low - CCI-000366 - V-237088 - SV-237088r640101_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000029
Vuln IDs
  • V-237088
  • V-94615
Rule IDs
  • SV-237088r640101_rule
  • SV-104445
Ensure that no device is connected to a virtual machine if it is not required. For example, floppy, serial and parallel ports are rarely used for virtual machines in a datacenter environment, and CD/DVD drives are usually connected only temporarily during software installation.
Checks: C-40307r640099_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Review the VMs hardware and verify no CD/DVD drives are connected. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM | Get-CDDrive | Where {$_.extensiondata.connectable.connected -eq $true} | Select Parent,Name If a virtual machine has a CD/DVD drive connected other than temporarily, this is a finding.

Fix: F-40270r640100_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Select the CD/DVD drive and uncheck "Connected" and "Connect at power on" and remove any attached ISOs. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-CDDrive | Set-CDDrive -NoMedia

b
Unauthorized parallel devices must be disconnected on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237089 - SV-237089r640104_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000030
Vuln IDs
  • V-237089
  • V-94617
Rule IDs
  • SV-237089r640104_rule
  • SV-104447
Ensure that no device is connected to a virtual machine if it is not required. For example, floppy, serial and parallel ports are rarely used for virtual machines in a datacenter environment, and CD/DVD drives are usually connected only temporarily during software installation.
Checks: C-40308r640102_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Review the VMs hardware and verify no parallel devices exist. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM | Where {$_.ExtensionData.Config.Hardware.Device.DeviceInfo.Label -match "parallel"} If a virtual machine has a parallel device present, this is a finding.

Fix: F-40271r640103_fix

The VM must be powered off in order to remove a parallel device. From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Select the parallel device and click the circle-x to remove then OK.

b
Unauthorized serial devices must be disconnected on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237090 - SV-237090r640107_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000031
Vuln IDs
  • V-237090
  • V-94619
Rule IDs
  • SV-237090r640107_rule
  • SV-104449
Ensure that no device is connected to a virtual machine if it is not required. For example, floppy, serial and parallel ports are rarely used for virtual machines in a datacenter environment, and CD/DVD drives are usually connected only temporarily during software installation.
Checks: C-40309r640105_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Review the VMs hardware and verify no serial devices exist. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM | Where {$_.ExtensionData.Config.Hardware.Device.DeviceInfo.Label -match "serial"} If a virtual machine has a serial device present, this is a finding.

Fix: F-40272r640106_fix

The VM must be powered off in order to remove a serial device. From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Select the serial device and click the circle-x to remove then OK.

b
Unauthorized USB devices must be disconnected on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237091 - SV-237091r640110_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000032
Vuln IDs
  • V-237091
  • V-94621
Rule IDs
  • SV-237091r640110_rule
  • SV-104451
Ensure that no device is connected to a virtual machine if it is not required. For example, floppy, serial and parallel ports are rarely used for virtual machines in a datacenter environment, and CD/DVD drives are usually connected only temporarily during software installation.
Checks: C-40310r640108_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Review the VMs hardware and verify no USB devices exist. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following commands: Get-VM | Where {$_.ExtensionData.Config.Hardware.Device.DeviceInfo.Label -match "usb"} Get-VM | Get-UsbDevice If a virtual machine has any USB devices or USB controllers present, this is a finding. If USB smart card readers are used to pass smart cards through the VM console to a VM then the use of a USB controller and USB devices for that purpose is not a finding.

Fix: F-40273r640109_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings. Select the USB controller and click the circle-x to remove then OK. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-USBDevice | Remove-USBDevice Note: This will not remove the USB controller just any connected devices.

b
Console connection sharing must be limited on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237092 - SV-237092r640113_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000033
Vuln IDs
  • V-237092
  • V-94623
Rule IDs
  • SV-237092r640113_rule
  • SV-104453
By default, remote console sessions can be connected to by more than one user at a time. When multiple sessions are activated, each terminal window gets a notification about the new session. If an administrator in the VM logs in using a VMware remote console during their session, a non-administrator in the VM might connect to the console and observe the administrator's actions. Also, this could result in an administrator losing console access to a virtual machine. For example, if a jump box is being used for an open console session and the admin loses connection to that box, then the console session remains open. Allowing two console sessions permits debugging via a shared session. For highest security, only one remote console session at a time should be allowed.
Checks: C-40311r640111_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the RemoteDisplay.maxConnections value is set to 1. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name RemoteDisplay.maxConnections If the virtual machine advanced setting RemoteDisplay.maxConnections does not exist or is not set to 1, this is a finding.

Fix: F-40274r640112_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the RemoteDisplay.maxConnections value and set it to 1. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name RemoteDisplay.maxConnections -Value 1 If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name RemoteDisplay.maxConnections | Set-AdvancedSetting -Value 1

b
Console access through the VNC protocol must be disabled on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237093 - SV-237093r640116_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000034
Vuln IDs
  • V-237093
  • V-94625
Rule IDs
  • SV-237093r640116_rule
  • SV-104455
The VM console enables you to connect to the console of a virtual machine, in effect seeing what a monitor on a physical server would show. This console is also available via the VNC protocol and should be disabled.
Checks: C-40312r640114_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the RemoteDisplay.vnc.enabled value is set to false. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name RemoteDisplay.vnc.enabled If the virtual machine advanced setting RemoteDisplay.vnc.enabled does not exist or is not set to false, this is a finding.

Fix: F-40275r640115_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the RemoteDisplay.vnc.enabled value and set it to false. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name RemoteDisplay.vnc.enabled -Value false If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name RemoteDisplay.vnc.enabled | Set-AdvancedSetting -Value false

a
Informational messages from the virtual machine to the VMX file must be limited on the virtual machine.
CM-6 - Low - CCI-000366 - V-237094 - SV-237094r640119_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000036
Vuln IDs
  • V-237094
  • V-94627
Rule IDs
  • SV-237094r640119_rule
  • SV-104457
The configuration file containing these name-value pairs is limited to a size of 1MB. If not limited, VMware tools in the guest OS are capable of sending a large and continuous data stream to the host. This 1MB capacity should be sufficient for most cases, but this value can change if necessary. The value can be increased if large amounts of custom information are being stored in the configuration file. The default limit is 1MB.
Checks: C-40313r640117_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the tools.setinfo.sizeLimit value is set to 1048576. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.setinfo.sizeLimit If the virtual machine advanced setting tools.setinfo.sizeLimit does not exist or is not set to 1048576, this is a finding.

Fix: F-40276r640118_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the tools.setinfo.sizeLimit value and set it to 1048576. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name tools.setinfo.sizeLimit -Value 1048576 If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.setinfo.sizeLimit | Set-AdvancedSetting -Value 1048576

b
Unauthorized removal, connection and modification of devices must be prevented on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237095 - SV-237095r640122_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000037
Vuln IDs
  • V-237095
  • V-94629
Rule IDs
  • SV-237095r640122_rule
  • SV-104459
In a virtual machine, users and processes without root or administrator privileges can connect or disconnect devices, such as network adaptors and CD-ROM drives, and can modify device settings. Use the virtual machine settings editor or configuration editor to remove unneeded or unused hardware devices. If you want to use the device again, you can prevent a user or running process in the virtual machine from connecting, disconnecting, or modifying a device from within the guest operating system. By default, a rogue user with nonadministrator privileges in a virtual machine can: 1. Connect a disconnected CD-ROM drive and access sensitive information on the media left in the drive 2. Disconnect a network adaptor to isolate the virtual machine from its network, which is a denial of service 3. Modify settings on a device
Checks: C-40314r640120_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the isolation.device.connectable.disable value is set to true. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.device.connectable.disable If the virtual machine advanced setting isolation.device.connectable.disable does not exist or is not set to true, this is a finding.

Fix: F-40277r640121_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the isolation.device.connectable.disable value and set it to true. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name isolation.device.connectable.disable -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name isolation.device.connectable.disable | Set-AdvancedSetting -Value true

b
The virtual machine must not be able to obtain host information from the hypervisor.
CM-6 - Medium - CCI-000366 - V-237096 - SV-237096r640125_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000039
Vuln IDs
  • V-237096
  • V-94631
Rule IDs
  • SV-237096r640125_rule
  • SV-104461
If enabled, a VM can obtain detailed information about the physical host. The default value for the parameter is FALSE. This setting should not be TRUE unless a particular VM requires this information for performance monitoring. An adversary potentially can use this information to inform further attacks on the host.
Checks: C-40315r640123_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the tools.guestlib.enableHostInfo value is set to false. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.guestlib.enableHostInfo If the virtual machine advanced setting tools.guestlib.enableHostInfo does not exist or is not set to false, this is a finding.

Fix: F-40278r640124_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the tools.guestlib.enableHostInfo value and set it to false. If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name tools.guestlib.enableHostInfo -Value false If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.guestlib.enableHostInfo | Set-AdvancedSetting -Value false

a
Shared salt values must be disabled on the virtual machine.
CM-6 - Low - CCI-000366 - V-237097 - SV-237097r640128_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000040
Vuln IDs
  • V-237097
  • V-94633
Rule IDs
  • SV-237097r640128_rule
  • SV-104463
When salting is enabled (Mem.ShareForceSalting=1 or 2) in order to share a page between two virtual machines both salt and the content of the page must be same. A salt value is a configurable advanced option for each virtual machine. You can manually specify the salt values in the virtual machine's advanced settings with the new option sched.mem.pshare.salt. If this option is not present in the virtual machine's advanced settings, then the value of the vc.uuid option is taken as the default value. Since the vc.uuid is unique to each virtual machine, by default TPS happens only among the pages belonging to a particular virtual machine (Intra-VM).
Checks: C-40316r640126_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the sched.mem.pshare.salt setting does not exist. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name sched.mem.pshare.salt If the virtual machine advanced setting sched.mem.pshare.salt exists, this is a finding.

Fix: F-40279r640127_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Delete the sched.mem.pshare.salt setting. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name sched.mem.pshare.salt | Remove-AdvancedSetting

a
Access to virtual machines through the dvfilter network APIs must be controlled.
CM-6 - Low - CCI-000366 - V-237098 - SV-237098r640131_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000041
Vuln IDs
  • V-237098
  • V-94635
Rule IDs
  • SV-237098r640131_rule
  • SV-104465
An attacker might compromise a VM by making use the dvFilter API. Configure only those VMs to use the API that need this access.
Checks: C-40317r640129_chk

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Look for settings with the format ethernet*.filter*.name. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name "ethernet*.filter*.name*" If the virtual machine advanced setting ethernet*.filter*.name exists and dvfilters are not in use, this is a finding. If the virtual machine advanced setting ethernet*.filter*.name exists and the value is not valid, this is a finding.

Fix: F-40280r640130_fix

From the vSphere Web Client right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Look for settings with the format ethernet*.filter*.name. Ensure only required VMs use this setting. Note: The VM must be powered off to configure the advanced settings through the vSphere Web Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name ethernetX.filterY.name | Remove-AdvancedSetting Note: Change the X and Y values to match the specific setting in your environment.

a
System administrators must use templates to deploy virtual machines whenever possible.
CM-6 - Low - CCI-000366 - V-237099 - SV-237099r640134_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000042
Vuln IDs
  • V-237099
  • V-94637
Rule IDs
  • SV-237099r640134_rule
  • SV-104467
By capturing a hardened base operating system image (with no applications installed) in a template, ensure all virtual machines are created with a known baseline level of security. Then use this template to create other, application-specific templates, or use the application template to deploy virtual machines. Manual installation of the OS and applications into a VM introduces the risk of misconfiguration due to human or process error.
Checks: C-40318r640132_chk

Ask the SA if hardened, patched templates are used for VM creation, properly configured OS deployments, including applications both dependent and non-dependent on VM-specific configurations. If hardened, patched templates are not used for VM creation, this is a finding.

Fix: F-40281r640133_fix

Create hardened virtual machine templates to use for OS deployments.

b
Use of the virtual machine console must be minimized.
CM-6 - Medium - CCI-000366 - V-237100 - SV-237100r640137_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000043
Vuln IDs
  • V-237100
  • V-94639
Rule IDs
  • SV-237100r640137_rule
  • SV-104469
The VM console enables a connection to the console of a virtual machine, in effect seeing what a monitor on a physical server would show. The VM console also provides power management and removable device connectivity controls, which might potentially allow a malicious user to bring down a virtual machine. In addition, it also has a performance impact on the service console, especially if many VM console sessions are open simultaneously.
Checks: C-40319r640135_chk

Remote management services, such as terminal services and SSH, must be used to interact with virtual machines. VM console access should only be granted when remote management services are unavailable or insufficient to perform necessary management tasks. Ask the SA if a VM console is used to perform VM management tasks, other than for troubleshooting VM issues. If a VM console is used to perform VM management tasks, other than for troubleshooting VM issues, this is a finding. If SSH and/or terminal management services are exclusively used to perform management tasks, this is not a finding.

Fix: F-40282r640136_fix

Develop a policy prohibiting the use of a VM console for performing management services. This policy should include procedures for the use of SSH and Terminal Management services for VM management. Where SSH and Terminal Management services prove insufficient to troubleshoot a VM, access to the VM console may be temporarily granted.

b
The virtual machine guest operating system must be locked when the last console connection is closed.
CM-6 - Medium - CCI-000366 - V-237101 - SV-237101r640140_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000047
Vuln IDs
  • V-237101
  • V-94647
Rule IDs
  • SV-237101r640140_rule
  • SV-104477
When accessing the VM console the guest OS must be locked when the last console user disconnects, limiting the possibility of session hijacking. This setting only applies to Windows-based VMs with VMware tools installed.
Checks: C-40320r640138_chk

From the vSphere Web Client select the Virtual Machine, right click and go to Edit Settings >> VM Options Tab >> Advanced >> Configuration Parameters >> Edit Configuration. Find the "tools.guest.desktop.autolock" value and verify that it is set to "true". or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.guest.desktop.autolock If the virtual machine advanced setting "tools.guest.desktop.autolock" does not exist or is not set to "true", this is a finding. If the VM is not Windows-based, this is not a finding.

Fix: F-40283r640139_fix

From the vSphere Client select the Virtual Machine, right click and go to Edit Settings >> VM Options Tab >> Advanced >> Configuration Parameters >> Edit Configuration. Find or create the "tools.guest.desktop.autolock" value and set it to "true". Note: The VM must be powered off to modify the advanced settings through the vSphere Web Client. It is recommended to configure these settings with PowerCLI as this can be done while the VM is powered on. In this case the modified settings will not take effect until a cold boot of the VM. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name tools.guest.desktop.autolock -Value true If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.guest.desktop.autolock | Set-AdvancedSetting -Value true

a
3D features on the virtual machine must be disabled when not required.
CM-6 - Low - CCI-000366 - V-237102 - SV-237102r640143_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
VMCH-65-000048
Vuln IDs
  • V-237102
  • V-94649
Rule IDs
  • SV-237102r640143_rule
  • SV-104479
It is recommended that 3D acceleration be disabled on virtual machines that do not require 3D functionality, (e.g. most server workloads or desktops not using 3D applications).
Checks: C-40321r640141_chk

From the vSphere Web Client select the Virtual Machine, right click and go to Edit Settings >> VM Options Tab >> Advanced >> Configuration Parameters >> Edit Configuration. Find the "mks.enable3d" value and verify it is set to "false". or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name mks.enable3d If the virtual machine advanced setting "mks.enable3d" does not exist or is not set to "false", this is a finding. If a virtual machine requires 3D features, this is not a finding.

Fix: F-40284r640142_fix

From the vSphere Client select the Virtual Machine, right click and go to Edit Settings >> VM Options Tab >> Advanced >> Configuration Parameters >> Edit Configuration. Find the "mks.enable3d" value and set it to "false". Note: The VM must be powered off to modify the advanced settings through the vSphere Web Client. It is recommended to configure these settings with PowerCLI as this can be done while the VM is powered on. In this case the modified settings will not take effect until a cold boot of the VM. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name mks.enable3d -Value false If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name mks.enable3d | Set-AdvancedSetting -Value false

b
Encryption must be enabled for vMotion on the virtual machine.
CM-6 - Medium - CCI-000366 - V-237103 - SV-237103r802905_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
VMCH-65-000049
Vuln IDs
  • V-237103
  • V-94651
Rule IDs
  • SV-237103r802905_rule
  • SV-104481
vMotion migrations in vSphere 6.0 and earlier transferred working memory and CPU state information in clear text over the vMotion network. As of vSphere 6.5 this transfer can be transparently encrypted using 256bit AES-GCM with negligible performance impact. vSphere 6.5 enables encrypted vMotion by default as 'Opportunistic', meaning that encrypted channels are used where supported but the operation will continue in plain text where encryption is not supported. For example when vMotioning between two 6.5 hosts encryption will always be utilized but since 6.0 and earlier releases do not support this feature vMotion from a 6.5 host to a 6.0 host would be allowed but would not be encrypted. If this finding is set to 'Required' then vMotions to unsupported hosts will fail. This setting must be set to 'Opportunistic' or 'Required'.
Checks: C-40322r802904_chk

Note: If the system does not have vCenter installed and utilizes vMotion, then this is Not Applicable. From the vSphere Web Client, select the Virtual Machine, right-click and go to Edit Settings >> VM Options Tab >> Encryption >> Encrypted vMotion. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM | Where {($_.ExtensionData.Config.MigrateEncryption -ne "opportunistic") -and ($_.ExtensionData.Config.MigrateEncryption -ne "required")} If the setting does not have a value of "Opportunistic" or "Required", this is a finding.

Fix: F-40285r717087_fix

From the vSphere Client select the Virtual Machine, right click and go to Edit Settings >> VM Options Tab >> Encryption >> Encrypted vMotion. Set the value to "Opportunistic" or "Required".