OpenControls Logo

STIG Viewer

STIGViewer Support

The RUCKUS ICX BGP router must be configured to reject outbound route advertisements for any prefixes that do not belong to any customer or the local autonomous system (AS).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-273573RCKS-RTR-000050SV-273573r1111031_ruleCCI-001368medium
Description
Advertisement of routes by an autonomous system for networks that do not belong to any of its customers pulls traffic away from the authorized network. This causes a denial of service (DoS) on the network that allocated the block of addresses and may cause a DoS on the network that is inadvertently advertising it as the originator. It is also possible that a misconfigured or compromised router within the GIG IP core could redistribute IGP routes into BGP, thereby leaking internal routes.
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 (17) 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.

AST-04Network Diagrams & Data Flow Diagrams (DFDs)
1.00
AST-04.2Control Applicability Boundary Graphical Representation
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
DCH-19Geographic Location of Data
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
IAC-21Least Privilege
1.00

+7 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (42) 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-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00
AC-6(9)Log Use of Privileged Functions
1.00

+32 more (top 10 by confidence shown)

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.1.3
1.00
CCI1 mapping
CCI-001368
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) 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-09
1.00
ID.AM-03
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

18 NICE work roles and 10 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-273573r1111031_chk)

Review the router configuration to verify there is a filter defined to only advertise routes for prefixes that belong to any customers or the local AS. This requirement is not applicable for the DODIN Backbone. 1. Verify a prefix-list is configured for routes belonging to the local AS. ICX# show ip prefix-lists ip prefix-list local-AS: 2 entries seq 5 permit x.1.1.0/24 seq 10 permit x.1.2.0/24 2. Verify the prefix-list is applied to outbound routes to neighbors. ICX# show ip bgp config Current BGP configuration: router bgp local-as 1000 neighbor x.x.x.x remote-as 1001 neighbor x.x.x.x prefix-list local-AS out If the router does not filter out prefix advertisements that do not belong on the local AS, this is a finding.

Fix Text (F-77569r1111030_fix)

Configure a prefix-list representing prefixes that belong to the local-AS and apply them to BGP neighbors similar to what is shown below: ip prefix-list mylist seq 10 permit x.1.1.0/24 ip prefix-list mylist seq 10 permit x.1.2.0/24 ip prefix-list mylist seq 15 deny 0.0.0.0/0 ge 8 router bgp local-as 1000 neighbor x.x.x.x remote-as 1001 neighbor x.x.x.x prefix-list local-AS out