OpenControls Logo

STIG Viewer

STIGViewer Support

The RUCKUS ICX router must be configured to restrict traffic destined to itself.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-273605RCKS-RTR-000380SV-273605r1110875_ruleCCI-001097high
Description
The route processor handles traffic destined to the router, the key component used to build forwarding paths, and is instrumental with all network management functions. Hence, any disruption or denial-of-service (DoS) attack to the route processor can result in mission critical network outages.
STIGDate
RUCKUS ICX Router Security Technical Implementation Guide2025-06-03

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

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

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00

+8 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

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

CM-6Configuration Settings
1.00
SC-24Fail in Known State
1.00
SC-47Alternate Communications Paths
1.00
SC-5Denial-of-service Protection
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
SI-4System Monitoring
1.00
SI-4(11)Analyze Communications Traffic Anomalies
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 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.

3.13.1
1.00
3.13.2
1.00
3.13.5
1.00
CCI1 mapping
CCI-001097
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 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.

DE.CM-01
1.00
PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

15 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-273605r1110875_chk)

Review the external and internal Access Control Lists (ACLs) to verify the router is configured to only allow specific management and control plane traffic from specific sources destined to itself (addresses and protocols may vary). 1. Review the access lists. ip access-list extended EXT-ACL sequence 10 permit tcp host x.11.1.1 eq bgp host x.11.1.2 sequence 20 permit tcp host x.11.1.1 host x.11.1.2 eq bgp sequence 30 permit icmp host x.11.1.1 host x.11.1.2 echo sequence 40 permit icmp host x.11.1.1 host x.11.1.2 echo-reply sequence 50 deny ip host x.11.1.1 host x.11.1.2 log permit … … … … deny ip any any log ! ip access-list extended INT-ACL sequence 10 permit icmp any any sequence 20 permit ospf host 10.1.12.1 host 10.1.12.2 sequence 30 permit tcp 10.2.1.0 0.0.0.255 host 10.1.12.2 eq ssh sequence 40 permit tcp 10.2.1.0 0.0.0.255 host 10.1.12.2 eq radius sequence 50 permit udp 10.2.1.0 0.0.0.255 host 10.1.12.2 eq snmp sequence 60 permit udp 10.2.1.0 0.0.0.255 host 10.1.12.2 eq ntp sequence 70 deny ip any host 10.1.12.2 log permit … … … … deny ip any any log ! 2. Verify ACLs are applied to desired interfaces. interface ethernet x/x/x ip address x.11.1.2/31 ip access-group EXT-ACL in logging enable ! interface ethernet x/x/x ip address 10.1.12.2 255.255.255.0 ip access-group INT-ACL in logging enable If the router is not configured to restrict traffic destined to itself, this is a finding.

Fix Text (F-77601r1110763_fix)

Configure all routers with receive path filters to restrict traffic destined to the router. 1. Create ACLs for external and internal interfaces in accordance with site security policy (addresses and protocols may vary). ICX(config)#ip access-list ext EXT-ACL ICX(config-ext-ipacl-EXT-ACL)#permit tcp host x.11.1.1 eq bgp host x.11.1.2 ICX(config-ext-ipacl-EXT-ACL)#permit tcp host x.11.1.1 host x.11.1.2 eq bgp ICX(config-ext-ipacl-EXT-ACL)#permit icmp host x.11.1.1 host x.11.1.2 echo ICX(config-ext-ipacl-EXT-ACL)#permit icmp host x.11.1.1 host x.11.1.2 echo-reply ICX(config-ext-ipacl-EXT-ACL)#deny ip host x.11.1.1 host x.11.1.2 log ICX(config-ext-ipacl-EXT-ACL)#exit ICX(config)#ip access-list ext INT-ACL ICX(config-ext-ipacl-INT-ACL)#permit icmp any any ICX(config-ext-ipacl-INT-ACL)#permit ospf host 10.1.12.1 host 10.1.12.2 ICX(config-ext-ipacl-INT-ACL)#permit tcp 10.2.1.0/24 host 10.1.12.2 eq 22 ICX(config-ext-ipacl-INT-ACL)#permit tcp 10.2.1.0/24 host 10.1.12.2 eq radius ICX(config-ext-ipacl-INT-ACL)#permit udp 10.2.1.0/24 host 10.1.12.2 eq snmp ICX(config-ext-ipacl-INT-ACL)#permit udp 10.2.1.0/24 host 10.1.12.2 eq ntp ICX(config-ext-ipacl-INT-ACL)#deny ip any host 10.1.12.2 log 2. Apply ACLs to appropriate interfaces. ICX(config)# interface ethernet x/x/x ICX(config-if-e1000-x/x/x)#ip access-group EXT-ACL in logging enable ICX(config-if-e1000-x/x/x)# interface ethernet y/y/y ICX(config-if-e1000-y/y/y)#ip access-group INT-ACL in logging enable