The storage system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-237823	HP3P-32-001400	SV-237823r647878_rule	CCI-001891	low
Description
Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).
STIG			Date
HPE 3PAR StoreServ 3.2.x Security Technical Implementation Guide			2021-11-23

Related Frameworks

1 mapping across 3 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.

AU-8Time Stamps

1.00

DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)2intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

AU-8(1)Synchronization with Authoritative Time Source

1.00

DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

CM-6Configuration Settings

1.00

DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
DISA STIG Benchmark (XCCDF)V3R3our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)V3R3intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

SC-45System Time Synchronization

1.00

DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)2intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

SC-45(1)Synchronization with Authoritative Time Source

1.00

DISA STIG Benchmark (XCCDF)V2R1intersects(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)V2R1intersects(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)

CCI1 mapping

CCI-001891

1.00

DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)

Details

Check Text (C-237823r647878_chk)

Verify NTP is operational by entering the following command: cli% shownet < multiple lines of heading, and node network information> NTP server : <ip address of ntp server> If one of the lines of the output does not show the correct NTP server IP address, this is a finding.

Fix Text (F-40992r647877_fix)

Enable NTP on the system by entering the following command: cli% setnet ntp <server_addr>