The vCenter Server must have new Key Encryption Keys (KEKs) reissued at regular intervals for vSAN encrypted datastore(s).
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-258954 | VCSA-80-000287 | SV-258954r1003610_rule | CCI-000366 | medium |
| Description | ||||
| 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. | ||||
| STIG | Date | |||
| VMware vSphere 8.0 vCenter Security Technical Implementation Guide | 2025-06-09 | |||
Related Frameworks
4 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-6
1.00
- DISA · V2R3 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
- DISA · V2R3 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
- DISA · V2R3 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
- DISA · V2R3 · disa_xccdf · related
Details
Check Text (C-258954r1003610_chk)
If vSAN is not in use, this is not applicable.
Interview the system administrator (SA) to determine that a procedure has been put in place to perform a shallow rekey of all vSAN encrypted datastores at regular, site-defined intervals.
VMware recommends a 60-day rekey task, but this interval must be defined by the SA and the ISSO.
If vSAN encryption is not in use, this is not a finding.
If vSAN encryption is in use and a regular rekey procedure is not in place, this is a finding.
Fix Text (F-62603r1003609_fix)
If vSAN encryption is in use, ensure a regular rekey procedure is in place.
To generate new encryption keys for vSAN, do the following:
From the vSphere Client, go to Host and Clusters.
Select the vCenter Server >> Select the cluster >> Configure >> vSAN >> Services >> Data Services.
Select "Generate New Encryption Keys" and optionally generate new DEKs and click "Generate".