Details

VSAN Datastore name by default is ‘vsanDatastore’. If more than one VSAN cluster is present in vCenter both datastores will have the same name by default potentially leading to confusion and manually misplaced workloads.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

From the vSphere Web Client go to Host and Clusters > Select a Cluster > Related Objects > Datastores. Right click on the datastore named ‘vsanDatastore’ and select ‘Rename’. Rename the datastore based on operational naming standards.

or

From a PowerCLI command prompt while connected to the vCenter server run the following command:

If($(Get-Cluster | where {$_.VsanEnabled} | Measure).Count -gt 0){
Write-Host ‘VSAN Enabled Cluster found’
$Clusters = Get-Cluster | where {$_.VsanEnabled}
Foreach ($clus in $clusters){
$clus | Get-Datastore | where {$_.type -match ‘vsan’} | Set-Datastore -Name $(($clus.name) + ‘_VSAN_Datastore’)
}
}
else{
Write-Host ‘VSAN is not enabled, this finding is not applicable’
}

Supportive Information

The following resource is also helpful.

• http://iasecontent.disa.mil/stigs/zip/U_VMware_vSphere_6-0_vCenter_Server_for_Windows_V1R4_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system VMware.

References

• 800-53|CM-6b.
• CAT|III
• CCI|CCI-000366
• Group-ID|V-73143
• Rule-ID|SV-87795r1_rule
• STIG-ID|VCWN-06-000054
• Vuln-ID|V-73143

Source

• Tenable.com/audits