OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia Border Gateway Protocol (BGP) router must be configured to reject inbound route advertisements from a customer edge (CE) router for prefixes that are not allocated to that customer.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283900NOKI-RT-000890SV-283900r1203949_ruleCCI-001368medium
Description
As a best practice, a service provider should only accept customer prefixes that have been assigned to that customer and any peering autonomous systems. A multihomed customer with BGP speaking routers connected to the internet or other external networks could be breached and used to launch a prefix deaggregation attack. Without ingress route filtering of customers, the effectiveness of such an attack could impact the entire IP core and its customers.
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

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-283900r1203949_chk)

Review the BGP router configuration to verify routing policies are defined to only accept routes for prefixes that belong to each specific customer. Verify the prefix-list, policy-statement, and import policy are applied to the eBGP group using the commands below: - show router policy prefix-list "Customer Prefix" prefix 192.168.100.0/24 prefix-length-range 24-32 - show router policy "Import Customer Prefix" entry 10 from prefix-list "Customer Prefix" exit action accept exit exit default-action drop exit - show router bgp group "eBGP" detail | match "Import Policy" Import Policy : Import Customer Prefix If the router is not configured to reject inbound route advertisements from each CE router for prefixes that are not allocated to that customer, this is a finding.

Fix Text (F-88370r1203948_fix)

Configure all eBGP routers to reject inbound route advertisements from a CE router for prefixes that are not allocated to that customer using the example below: Create a prefix list: - configure router policy-options - config>router>policy-options# begin - config>router>policy-options# prefix-list "Customer Prefix" - config>router>policy-options>prefix-list$ prefix 192.168.100.0/24 prefix-length-range 24-32 - config>router>policy-options>prefix-list# exit Create a policy statement: - config>router>policy-options# policy-statement "Import Customer Prefix" - config>router>policy-options>policy-statement$ entry 10 - config>router>policy-options>policy-statement>entry$ from prefix-list "Customer Prefix" - config>router>policy-options>policy-statement>entry$ action accept - config>router>policy-options>policy-statement>entry>action$ exit - config>router>policy-options>policy-statement>entry$ exit - config>router>policy-options>policy-statement$ default-action drop - config>router>policy-options>policy-statement>default-action$ exit - config>router>policy-options>policy-statement$ exit - config>router>policy-options# commit - config>router>policy-options# exit all Apply the import policy to the BGP group: - configure router bgp group "eBGP" import "Import Customer Prefix"