Detections
Analytics
VCWN-65-000066 - The vCenter Server for Windows must have new Key Encryption Keys (KEKs) re-issued at regular intervals for vSAN encrypted datastore(s).
Information
The Key Encryption Key (KEK) for a vSAN encrypted datastore is generated by the Key Management Server (KMS) and serves as a wrapper and lock around the Disk Encryption Key (DEK). The DEK is generated by the host and is used to encrypt and decrypt the datastore. A shallow re-key is a procedure in which the KMS issues a new KEK to the ESXi host which re-wraps the DEK but does not change the DEK or any data on disk. This operation must be done on a regular, site defined interval and can be viewed as similar in criticality to changing an administrative password. Should the KMS itself somehow be compromised, a standing operational procedure to re-key will put a time limit on the usefulness of any stolen KMS data.NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
If vSAN encryption is in use, ensure that a regular re-key procedure is in place.See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_vSphere_6-5_Y23M07_STIG.zip
Item Details
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-6b., CAT|III, CCI|CCI-000366, Rule-ID|SV-216885r879887_rule, STIG-ID|VCWN-65-000066, STIG-Legacy|SV-104665, STIG-Legacy|V-94835, Vuln-ID|V-216885
Plugin: VMware
Control ID: 3b8f645904a5042af9fa7739398cd2ab865dfcb638b3b7018d3af51c8e5a924b