OpenControls Logo

STIG Viewer

STIGViewer Support

The Juniper router must be configured to implement message authentication for all control plane protocols.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-217012JUNI-RT-000020SV-217012r945861_ruleCCI-002205medium
Description
A rogue router could send a fictitious routing update to convince a site's perimeter router to send traffic to an incorrect or even a rogue destination. This diverted traffic could be analyzed to learn confidential information about the site's network or used to disrupt the network's ability to communicate with other networks. This is known as a "traffic attraction attack" and is prevented by configuring neighbor router authentication for routing updates. This requirement applies to all IPv4 and IPv6 protocols that are used to exchange routing or packet forwarding information; this includes all Interior Gateway Protocols (such as OSPF, EIGRP, and IS-IS) and Exterior Gateway Protocols (such as BGP), MPLS-related protocols (such as LDP), and multicast-related protocols.
STIGDate
Juniper Router RTR Security Technical Implementation Guide2024-12-05

Related Frameworks

2 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (9) 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-01Configuration Management Program
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
MON-01Continuous Monitoring
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
NET-04.12Cross Domain Authentication
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) 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-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3(7)Role-based Access Control
1.00
AC-3(8)Revocation of Access Authorizations
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.4.1
1.00
3.4.2
1.00
CCI2 mappings
CCI-000366
1.00
CCI-002205
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-09
1.00
PR.PS-01
1.00
PR.DS-10
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

10 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-217012r945861_chk)

Review the router configuration. Verify that neighbor router authentication is enabled for all routing protocols as shown in the example configuration below. protocols { bgp { group AS_5 { type external; peer-as 5; neighbor x.x.x.x { authentication-key "$8$tBga0ORx7VsYoIEgJ"; ## SECRET-DATA } } } ospf { area 0.0.0.0 { interface ge-0/0/0.0 { authentication { simple-password "$8$NHVb2mPQ3nCYg/t"; ## SECRET-DATA } } interface ge-0/1/0.0 { authentication { simple-password "$8$Lgb7NbHkPTQnVwF/"; ## SECRET-DATA } } interface lo0.0; interface ge-0/2/0.0 { authentication { simple-password "$8$7DdVY.mTF39s26A"; ## SECRET-DATA } } } } isis { level 1 { authentication-key "$8$n2OT9CuvMXN-wp0VY"; ## SECRET-DATA authentication-type md5; } level 2 { authentication-key "$8$8G9x7ViHm5T3dbz6"; ## SECRET-DATA authentication-type md5; } interface ge-0/0/0.0; interface ge-0/0/1.0; } ldp { interface ge-0/0/0.0; interface ge-0/0/1.0; session 10.3.3.3 { authentication-key "$8$3hus/u1ylMNVYX7qf"; ## SECRET-DATA } session 10.1.2.2 { authentication-key "$8$Qq0I3nCrlMLX-9A7V"; ## SECRET-DATA } } rip { authentication-type md5; authentication-key "$8$34fM/u1ylMNVYX7qf"; ## SECRET-DATA group RIP_GROUP { neighbor ge-1/0/1.0; } } } If authentication is not enabled for all control plane protocols, this is a finding.

Fix Text (F-18239r296905_fix)

Configure authentication to be enabled for all control plane protocols as shown in the example below. [edit protocols ospf area 0.0.0.0] set interface ge-0/0/0 authentication simple-password xxxxxxxxxxxx set interface ge-0/1/0 authentication simple-password xxxxxxxxxxxx set interface ge-0/2/0 authentication simple-password xxxxxxxxxxxx [edit protocols isis] set level 1 authentication-type md5 set level 1 authentication-key xxxxxxxx set level 2 authentication-type md5 set level 2 authentication-key xxxxxxxx [edit protocols rip] set authentication-type md5 set authentication-key xxxxxxxx [edit protocols bgp group AS_2 neighbor x.x.x.x] set authentication-key xxxxxxxxxxxxxxx [edit protocols ldp] set session 10.1.2.2 authentication-key xxxxxxxxxx