STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to HPE Nimble Storage Array NDM Security Technical Implementation Guide

V-252202

CAT II (Medium)

The HPE Nimble must be configured to synchronize internal information system clocks using an authoritative time source.

Rule ID

SV-252202r1001011_rule

STIG

HPE Nimble Storage Array NDM Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-000366CCI-004928CCI-004922

Discussion

The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other functions. Multiple time sources provide redundancy by including a secondary source. Time synchronization is usually a hierarchy; clients synchronize time to a local source while that source synchronizes its time to a more accurate source. The network device must utilize an authoritative time server and/or be configured to use redundant authoritative time sources. This requirement is related to the comparison done in CCI-001891. DOD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DOD network (NIPRNet/SIPRNet); United States Naval Observatory (USNO) time servers; and/or the Global Positioning System (GPS). The secondary time source must be located in a different geographic region than the primary time source.

Check Content

To Determine if the HPE Nimble Array is configured to synchronize internal information system clocks with the primary NTP server:
 
ArrayA:/# ntpq
ntpq> sysinfo
associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
system peer: cxo-nmbldc-01.nimblestorage.com:123
system peer mode: client
leap indicator: 00
stratum: 4
log2 precision: -24
root delay: 37.321
root dispersion: 265.639
reference ID: 10.157.24.95
reference time: e509b178.9f897118 Thu, Oct 7 2021 11:48:40.623
system jitter: 0.000000
clock jitter: 0.673
clock wander: 0.003
broadcast delay: -50.000
symm. auth. delay: 0.000

If the HPE Storage Array is not configured to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions using redundant authoritative time sources, this is a finding.

Fix Text

Configure the HPE Nimble Array to synchronize internal information system clocks with the primary time source:
 
ArrayA:/# group --edit --ntpserver <ip_address_of_ntp_server>
  
There would be a finding here given we only support primary ntp source.