OpenControls Logo

STIG Viewer

STIGViewer Support

The Edge SWG must authenticate Network Time Protocol sources using authentication that is cryptographically based.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279269SYME-ND-000720SV-279269r1170698_ruleCCI-001967medium
Description
If Network Time Protocol is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source. Satisfies: SRG-APP-000395-NDM-000347, SRG-APP-000920-NDM-000320, SRG-APP-000925-NDM-000330
STIGDate
Symantec Edge SWG NDM Security Technical Implementation Guide2026-02-25

Related Frameworks

1 mapping across 4 frameworks
SCF0 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.

IAC-04Identification & Authentication for Devices
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (49) 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.

AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-18(1)Authentication and Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-4(17)Domain Authentication
1.00
AC-7Unsuccessful Logon Attempts
1.00
AU-8Time Stamps
1.00

+39 more (top 10 by confidence shown)

CCI1 mapping
CCI-001967
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (3) 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.

PR.AA-01
0.50
PR.AA-03
0.50
PR.AA-05
0.50

Details

Check Text (C-279269r1170698_chk)

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Enter "show ntp". If NTP is not enabled, this is a finding. If there are not two NTP servers in use, this is a finding. If the two NTP servers are not using SHA1 preshared keys for authentication, this is a finding.

Fix Text (F-83724r1170567_fix)

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Enter "ntp enable". 4. Enter "ntp server <NTP SERVER IP/HOSTNAME> <KEY ID> sha1". Note: The key ID must be a number and match the NTP server. 5. When prompted with "key:", enter the hexadecimal SHA preshared key. 6. Repeat these steps for the site's second NTP server.