STIGQter STIGQter: STIG Summary: VMware vSphere 6.7 ESXi Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 09 Mar 2021:

The ESXi host must protect the confidentiality and integrity of transmitted information by isolating vMotion traffic.

DISA Rule

SV-239303r674838_rule

Vulnerability Number

V-239303

Group Title

SRG-OS-000423-VMM-001700

Rule Version

ESXI-67-000048

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configuration of the vMotion VMkernel will be unique to each environment.

As an example, to modify the IP address and VLAN information to the correct network on a distributed switch, do the following:

From the vSphere Client, go to Networking >> Select a distributed switch >> Select a port group >> Configure >> Settings >> Edit >> VLAN.

Change the "VLAN Type" to "VLAN" and change the "VLAN ID" to a network allocated and dedicated to vMotion traffic exclusively.

Check Contents

Verify the vMotion VMKernel port group is in a dedicated VLAN, which can be on a common standard or distributed virtual switch as long as the vMotion VLAN is not shared by any other function and is not routed to anything but ESXi hosts.

For environments that do not use vCenter server to manage ESXi, this is Not Applicable.

The check for this will be unique per environment.

From the vSphere Client, select the ESXi host and go to Configuration >> Networking.

Review the VLAN associated with the vMotion VMkernel(s) and verify it is dedicated for that purpose and logically separated from other functions.

If long distance or cross-vCenter vMotion is used, the vMotion network can be routable but must be accessible to only the intended ESXi hosts.

If the vMotion port group is not on an isolated VLAN and/or is routable to systems other than ESXi hosts, this is a finding.

Vulnerability Number

V-239303

Documentable

False

Rule Version

ESXI-67-000048

Severity Override Guidance

Verify the vMotion VMKernel port group is in a dedicated VLAN, which can be on a common standard or distributed virtual switch as long as the vMotion VLAN is not shared by any other function and is not routed to anything but ESXi hosts.

For environments that do not use vCenter server to manage ESXi, this is Not Applicable.

The check for this will be unique per environment.

From the vSphere Client, select the ESXi host and go to Configuration >> Networking.

Review the VLAN associated with the vMotion VMkernel(s) and verify it is dedicated for that purpose and logically separated from other functions.

If long distance or cross-vCenter vMotion is used, the vMotion network can be routable but must be accessible to only the intended ESXi hosts.

If the vMotion port group is not on an isolated VLAN and/or is routable to systems other than ESXi hosts, this is a finding.

Check Content Reference

M

Target Key

5326

Comments