OpenControls Logo

STIG Viewer

STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-217055JUNI-RT-000500SV-217055r604135_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 multi-homed customer with BGP speaking routers connected to the Internet or other external networks could be breached and used to launch a prefix de-aggregation attack. Without ingress route filtering of customers, the effectiveness of such an attack could impact the entire IP core and its customers.
STIGDate
Juniper Router RTR Security Technical Implementation Guide2024-12-05

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-217055r604135_chk)

Review the router configuration to verify that there are filters defined to only accept routes for prefixes that belong to specific customers. Verify prefix list has been configured containing prefixes belonging to each customer as shown in the example below. policy-options { … … … prefix-list CUST1_PREFIXES { x.x.x.x/24; x.x.x.x/24; } prefix-list CUST2_PREFIXES { x.x.x.x/24; } Verify that a policy has been configured to only accept routes belonging to the customer. policy-options { … … … policy-statement FILTER_CUST1_ROUTES { term ACCEPT-ROUTES { from { prefix-list CUST1_PREFIXES; } then accept; } term REJECT_OTHER { then reject; } } policy-statement FILTER_CUST2_ROUTES { term ACCEPT_ROUTES { from { prefix-list CUST2_PREFIXES; } then accept; } term REJECT_OTHER { then reject; } } } Verify that the configured policy to filter customer prefixes has been applied to customer BGP peers as shown in the example below. protocols { bgp { … … … } group CUST1 { type external; import FILTER_CUST1_ROUTES; peer-as 55; neighbor x.x.x.x; neighbor x.x.x.x; } group CUST2 { type external; import FILTER_CUST2_ROUTES; peer-as 44; neighbor x.x.x.x; neighbor x.x.x.x; } } … … … } Note: Routes to PE-CE links within a VPN are needed for troubleshooting end-to-end connectivity across the MPLS/IP backbone. Hence, these prefixes are an exception to this requirement. 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-18282r297034_fix)

Configure the router to reject inbound route advertisements from a CE router for prefixes that are not allocated to that customer. Configure a prefix list containing prefixes belonging to the customers. [edit policy-options] set prefix-list CUST1_PREFIXES x.x.x.x/24 set prefix-list CUST1_PREFIXES x.x.x.x/24 set prefix-list CUST2_PREFIXES x.x.x.x/24 set prefix-list CUST2_PREFIXES x.x.x.x/24 Configure a policy-statement to filter customer routes. set policy-statement FILTER_CUST1_ROUTES term ACCEPT_ROUTES from prefix-list CUST1_PREFIXES set policy-statement FILTER_CUST1_ROUTES term then accept set policy-statement FILTER_CUST1_ROUTES term REJECT_OTHER then reject set policy-statement FILTER_CUST2_ROUTES term ACCEPT_ROUTES from prefix-list CUST2_PREFIXES set policy-statement FILTER_CUST2_ROUTES term then accept set policy-statement FILTER_CUST2_ROUTES term REJECT_OTHER then reject Apply the import policy to filter received routes for each customer group. [edit protocols bgp group CUST1] set import FILTER_CUST1_ROUTES [edit protocols bgp group CUST2] set import FILTER_CUST2_ROUTES