6.2.2 (L1) Host must ensure all datastores have unique names


Ensuring unique naming for datastores is crucial to avoid potential errors that could affect the integrity and availability of data. A descriptive and unique name for each datastore facilitates better identification and management. Although there's no specific parameter to enforce this, manual or automated naming conventions should be adhered to.

Unique and descriptive naming for datastores minimizes the risk of errors, improves manageability, and aids in quicker identification, especially in environments with numerous datastores. It's a proactive measure to maintain order and avoid issues that arise from the default names given to VMFS and vSAN datastores.

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



Not adhering to a unique naming convention can lead to confusion, misconfiguration, or incorrect data access. While renaming datastores could have downstream effects on systems like automation, monitoring, and backup, the benefits of unique naming conventions outweigh the potential negatives.

See Also


Item Details


References: 800-53|SC-4, CSCv7|14.7

Plugin: VMware

Control ID: 7340667b6c84e1623fde993f98f050bce8849806e20c0917045cd726ea7f97dc