Symantec ProxySG must compare internal information system clocks at least every 24 hours with an authoritative time server.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-94671 | SYMP-NM-000100 | SV-104501r1_rule | CCI-001891 | medium |
| 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 of the configured acceptable allowance (drift) may be inaccurate. Additionally, unnecessary synchronization may have an adverse impact on system performance and may indicate malicious activity. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. | ||||
| STIG | Date | |||
| Symantec ProxySG NDM Security Technical Implementation Guide | 2019-12-20 | |||
Related Frameworks
1 mapping 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)V1R2intersects(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)V1R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(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)V1R2intersects(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)V1R2intersects(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)V1R2intersects(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)V1R2intersects(normalised)
Details
Check Text (C-104501r1_chk)
Verify the Symantec ProxySG is configured to use authoritative NTP servers (the NTP protocol itself enforces periodic checks at least every 24 hours).
1. Log on to the Web Management Console.
2. Click Configuration >> General >> Clock.
3. Confirm that the value of the "Query interval (minutes)" field is at least 1440 (24 hours in minutes).
4. Click "NTP", and confirm that the desired authoritative time servers are present.
If Symantec ProxySG does not compare internal information system clocks at least every 24 hours with an authoritative time server, this is a finding.
Fix Text (F-100789r1_fix)
Configure the Symantec ProxySG to use authoritative NTP servers (the NTP protocol itself enforces periodic checks at least every 24 hours).
1. Log on to the Web Management Console.
2. Select "Configuration", then "General", then "Clock".
3. Enter the desired time sync period into the "Query interval (minutes) field and click Apply.
4. Click "NTP", then "New", then "Add" and enter each desired authoritative time server.
5. Click "Apply".