The ESXi host must synchronize internal information system clocks to an authoritative time source.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-258745 | ESXI-80-000124 | SV-258745r933296_rule | CCI-001891 | medium |
| Description | ||||
| To ensure the accuracy of the system clock, it must be synchronized with an authoritative time source within DOD. Many system functions, including time-based logon and activity restrictions, automated reports, system logs, and audit records, depend on an accurate system clock. If there is no confidence in the correctness of the system clock, time-based functions may not operate as intended and records may be of diminished value. Satisfies: SRG-OS-000355-VMM-001330, SRG-OS-000356-VMM-001340 | ||||
| STIG | Date | |||
| VMware vSphere 8.0 ESXi Security Technical Implementation Guide | 2023-10-11 | |||
Related Frameworks
2 mappings across 3 frameworks
Related Frameworks
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (5) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V3R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V3R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA STIG Benchmark (XCCDF)3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
NIST 800-1710 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
3.3.7
1.00
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- NIST SP 800-171 Rev 2, Appendix DRev 2 (Feb 2020, errata Jan 2021)equal to(normalised)
CCI2 mappings
CCI-001891
1.00
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
CCI-002046
1.00
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
Details
Check Text (C-258745r933296_chk)
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Time Configuration.
Verify NTP or PTP are configured, and one or more authoritative time sources are listed.
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Services.
Verify the NTP or PTP service is running and configured to start and stop with the host.
or
From a PowerCLI command prompt while connected to the ESXi host, run the following commands:
Get-VMHost | Get-VMHostNTPServer
Get-VMHost | Get-VMHostService | Where {$_.Label -eq "NTP Daemon" -or $_.Label -eq "PTP Daemon"}
If the NTP service is not configured with authoritative DOD time sources or the service is not configured to start and stop with the host ("Policy" of "on" in PowerCLI) or is stopped, this is a finding.
If PTP is used instead of NTP, this is not a finding.
Fix Text (F-62394r933295_fix)
To configure NTP, perform the following:
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Time Configuration.
Click "Add Service" and select "Network Time Protocol".
Enter or update the NTP servers listed with a comma-separated list of authoritative time servers. Click "OK".
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Services.
Select the "NTP Daemon" service and click "Edit Startup Policy".
Select "Start and stop with host". Click "OK".
or
From a PowerCLI command prompt while connected to the ESXi host, run the following commands:
$NTPServers = "ntpserver1","ntpserver2"
Get-VMHost | Add-VMHostNTPServer $NTPServers
Get-VMHost | Get-VMHostService | Where {$_.Label -eq "NTP Daemon"} | Set-VMHostService -Policy On
Get-VMHost | Get-VMHostService | Where {$_.Label -eq "NTP Daemon"} | Start-VMHostService
To configure PTP, perform the following:
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Time Configuration.
Click "Add Service" and select "Precision Time Protocol".
Select the network adapter that can receive the PTP traffic.
If NTP servers are available, select "Enable fallback" and enter or update the NTP servers listed with a comma separate list of authoritative time servers. Click "OK".
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Services.
Select the "PTP Daemon" service and click "Edit Startup Policy".
Select "Start and stop with host". Click "OK".