OpenControls Logo

STIG Viewer

STIGViewer Support

The Juniper BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-254015JUEX-RT-000430SV-254015r844078_ruleCCI-001097medium
Description
Outbound route advertisements belonging to the core can result in traffic either looping or being black holed, or at a minimum, using a nonoptimized path.
STIGDate
Juniper EX Series Switches Router Security Technical Implementation Guide2024-06-10

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-254015r844078_chk)

Review the BGP router configuration to verify that there is a filter defined to block route advertisements for prefixes that belong to the IP core. Verify an appropriate prefix-list containing the IP core prefixes is referenced in a policy-statement. For example: [edit policy-options] prefix-list ip-core-ipv4 { 192.0.2.0/24; } prefix-list ip-core-ipv6 { 2001:db8:2::/64; } policy-statement advertise-bgp-prefix { term exclude-ipv4-core { from { prefix-list ip-core-ipv4; } then reject; } term exclude-ipv6-core { from { prefix-list ip-core-ipv6; } then reject; } term default { then accept; } } The prefix filter must be referenced outbound on the appropriate BGP neighbor statements. For example: [edit protocols] bgp { group eBGP { type external; export advertise-bgp-prefix; neighbor 192.0.2.11 { export advertise-bgp-prefix; } } export advertise-bgp-prefix; } Note: Juniper routers support global, group, and neighbor export statements with the more specific definition taking precedence. Ensure more specific export policies (e.g., neighbor and group) do not reverse higher level export statements. If the router is not configured to reject outbound route advertisements that belong to the IP core, this is a finding.

Fix Text (F-57418r844077_fix)

Configure all eBGP routers to filter outbound route advertisements belonging to the IP core. For example: set policy-options prefix-list ip-core-ipv4 192.0.2.0/24 set policy-options prefix-list ip-core-ipv6 2001:db8:2::/64 set policy-options policy-statement advertise-bgp-prefix term exclude-ipv4-core from prefix-list ip-core-ipv4 set policy-options policy-statement advertise-bgp-prefix term exclude-ipv4-core then reject set policy-options policy-statement advertise-bgp-prefix term exclude-ipv6-core from prefix-list ip-core-ipv6 set policy-options policy-statement advertise-bgp-prefix term exclude-ipv6-core then reject set policy-options policy-statement advertise-bgp-prefix term default then accept set protocols bgp group eBGP type external set protocols bgp group eBGP export advertise-bgp-prefix set protocols bgp group eBGP neighbor 192.0.2.11 export advertise-bgp-prefix set protocols bgp export advertise-bgp-prefix