Detections
Analytics
VCSA-70-000287 - The vCenter Server must have new Key Encryption Keys (KEKs) reissued at regular intervals for vSAN encrypted datastore(s).
Information
The 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 rekey is a procedure in which the KMS issues a new KEK to the ESXi host, which rewraps 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. If the KMS is compromised, a standing operational procedure to rekey 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 a regular rekey procedure is in place.See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_vSphere_7-0_Y24M01_STIG.zip
Item Details
Audit Name: DISA STIG VMware vSphere 7.0 vCenter v1r3
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-6b., CAT|II, CCI|CCI-000366, Rule-ID|SV-256367r885712_rule, STIG-ID|VCSA-70-000287, Vuln-ID|V-256367
Plugin: VMware
Control ID: 2e054f1d9186680b854a5f93e276d6690b889178ee2dcb6af46b16b67da03108