The Nokia router must be configured to authenticate all routing protocol messages using National Institute of Standards and Technology (NIST)-validated Federal Information Processing Standards (FIPS) 198-1 message authentication code algorithm.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-283911 | NOKI-RT-001000 | SV-283911r1203982_rule | CCI-000803 | medium |
| Description | ||||
| A rogue router could send a fictitious routing update to convince a site's perimeter router to send traffic to an incorrect or 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. However, using clear-text authentication provides little benefit because an attacker can intercept traffic and view the authentication key. This would allow the attacker to use the authentication key in an attack. Because MD5 is vulnerable to "birthday" attacks and may be compromised, routing protocol authentication must use FIPS 198-1-validated algorithms and modules to encrypt the authentication key. 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 Open Shortest Path First (OSPF), Enhanced Interior Gateway Routing Protocol (EIGRP), and Intermediate System to Intermediate System (IS-IS). It also includes Exterior Gateway Protocols, such as Border Gateway Protocol (BGP); Multiprotocol Label Switching (MPLS)-related protocols, such as Label Distribution Protocol (LDP); and multicast-related protocols. | ||||
| STIG | Date | |||
| Nokia Service Router OS 25.x Router Security Technical Implementation Guide | 2026-06-15 | |||
Details
Check Text (C-283911r1203982_chk)
Review the router configuration to verify it is using a NIST-validated FIPS 198-1 message authentication code algorithm to authenticate routing protocol messages.
Use the command below and verify "Algorithm" configured for each keychain is a NIST-validated algorithm:
- show system security keychain "test" detail
Key chain:test
Description : (Not Specified)
TCP-Option number send : tcp-ao Admin state : Up
TCP-Option number receive : tcp-ao Oper state : Up
Used by : BGP
Expired : No
Key entries for key chain: test
Id : 1 Direction : send-receive
Algorithm : aes-128-cmac-96 Option : none
Admin State : Up RX Valid : Yes
TX Active : Yes Tolerance : 300
Begin Time : 2025/12/28 00:00:00 Begin Time (UTC) : 2025/12/28 00:00:00
End Time : 2026/06/28 00:00:00 End Time (UTC) : 2026/06/28 00:00:00
If a NIST-validated FIPS 198-1 message authentication code algorithm is not being used to authenticate routing protocol messages, this is a finding.
Fix Text (F-88381r1203981_fix)
Configure routing protocol authentication to use a NIST-validated FIPS 198-1 message authentication code algorithm using the example below:
- configure system security keychain "test" tcp-option-number send tcp-ao
- configure system security keychain "test" tcp-option-number receive tcp-ao
- configure system security keychain "test" direction bi entry 1 key 12345678901 algorithm aes-128-cmac-96 begin-time 2025/12/28 UTC 00:00:00
- configure system security keychain "test" direction bi entry 2 key 12345678901 algorithm aes-128-cmac-96 begin-time 2026/06/28 UTC 00:00:00