The ESXi host must protect the confidentiality and integrity of transmitted information by isolating vMotion traffic.
An XCCDF Rule
Description
<VulnDiscussion>While encrypted vMotion is available, vMotion traffic should still be sequestered from other traffic to further protect it from attack. This network must only be accessible to other ESXi hosts, preventing outside access to the network. The vMotion VMkernel port group must be in a dedicated VLAN that can be on a 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-256411r886014_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
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.