OpenControls Logo

STIG Viewer

STIGViewer Support

The RUCKUS ICX device must authenticate Network Time Protocol sources using authentication that is cryptographically based.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-273826RCKS-NDM-000740SV-273826r1110846_ruleCCI-001967medium
Description
If Network Time Protocol (NTP) 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.
STIGDate
RUCKUS ICX NDM Security Technical Implementation Guide2025-05-28

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-273826r1110846_chk)

View NTP configuration: SSH@ICX# show running-config | begin ntp ntp disable authenticate md5 authenticate authentication-key key-id 1 sha1 2 $VWlkRGkt server x.x.x.x key 1 server y.y.y.y key 1 If the NTP servers are not configured for authentication that is cryptographically based, this is a finding.

Fix Text (F-77822r1110658_fix)

Configure NTP for authentication using SHA1: SSH@ICX(config)# ntp SSH@ICX(config-ntp)# disable authenticate md5 SSH@ICX(config-ntp)# authenticate SSH@ICX(config-ntp)# authentication-key key-id 1 sha1 [password]