Virtual machines (VMs) must enable encryption for Fault Tolerance.
An XCCDF Rule
Description
<VulnDiscussion>Fault Tolerance log traffic can be encrypted. This could contain sensitive data from the protected machine's memory or CPU instructions. vSphere Fault Tolerance performs frequent checks between a primary VM and secondary VM so the secondary VM can quickly resume from the last successful checkpoint. The checkpoint contains the VM state that has been modified since the previous checkpoint. When Fault Tolerance is turned on, FT encryption is set to "Opportunistic" by default, which means it enables encryption only if both the primary and secondary host are capable of encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-258717r933212_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
For each virtual machine do the following:
From the vSphere Client, right-click the Virtual Machine and go to Edit Settings >> VM Options >> Encryption.
For "Encrypted FT" set the value to "Opportunistic" or "Required". Click "OK".