OpenControls Logo

STIG Viewer

STIGViewer Support

The RUCKUS ICX device must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-273825RCKS-NDM-000730SV-273825r1110845_ruleCCI-001967medium
Description
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, internet). A remote connection is any connection with a device communicating through an external network (e.g., the internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.
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-273825r1110845_chk)

View SNMP users: SSH@ICX# show snmp user username = admin1 acl name = <none> group = lab security model = v3 group acl name = <none> group ipv6 acl name = <none> authtype = sha authkey = 6e3e368283194dffcdabde95c9c44e795de911c2 privtype = aes privkey = c8b94fccfc1c845ed8a0d7b172405feb engine ID= 80 0 7c7 3d4c19e609a58 If any users are not configured for authtype sha, this is a finding.

Fix Text (F-77821r1110655_fix)

Delete any SNMP users not configured for SHA/AES. Configure SNMP user account for SHA/AES. SSH@ICX(config)#snmp-server user test_admin test_group v3 auth sha256 [security-string] priv aes [security-key]