Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-239326 | ESXI-67-000074 | SV-239326r674907_rule | High |
Description |
---|
TLS 1.0 and 1.1 are deprecated protocols with well-published shortcomings and vulnerabilities. TLS 1.2 should be enabled on all interfaces and SSLv3, TL 1.1, and 1.0 disabled where supported. Mandating TLS 1.2 may break third-party integrations and add-ons to vSphere. Test these integrations carefully after implementing TLS 1.2 and roll back where appropriate. On interfaces where required functionality is broken with TLS 1.2 this finding is not applicable until the third-party software supports TLS 1.2. Be sure to modify TLS settings in the following order: 1. Platform Services Controllers (if applicable) 2. vCenter 3. ESXi |
STIG | Date |
---|---|
VMware vSphere 6.7 ESXi Security Technical Implementation Guide | 2022-01-05 |
Check Text ( C-42559r674905_chk ) |
---|
From the vSphere Web Client, select the host and click Configure >> System >> Advanced System Settings. Find the "UserVars.ESXiVPsDisabledProtocols" value and verify that it is set to the following: tlsv1,tlsv1.1,sslv3 If the value is not set as above or it does not exist, this is a finding. or From a PowerCLI command prompt while connected to the ESXi host, run the following command: Get-VMHost | Get-AdvancedSetting -Name UserVars.ESXiVPsDisabledProtocols If the value returned is not "tlsv1,tlsv1.1,sslv3" or the setting does not exist, this is a finding. |
Fix Text (F-42518r674906_fix) |
---|
From the vSphere Web Client, select the host and click Configure >> System >> Advanced System Settings. Find the "UserVars.ESXiVPsDisabledProtocols" value and set it to the following: tlsv1,tlsv1.1,sslv3 or From a PowerCLI command prompt while connected to the ESXi host, run the following command: Get-VMHost | Get-AdvancedSetting -Name UserVars.ESXiVPsDisabledProtocols | Set-AdvancedSetting -Value "tlsv1,tlsv1.1,sslv3" A host reboot is required for changes to take effect. |