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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-283912	NOKI-RT-001010	SV-283912r1203985_rule	CCI-001184	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. This requirement applies to all IPv4 and IPv6 protocols that are used to exchange routing or packet forwarding information. This includes Border Gateway Protocol (BGP), Routing Information Protocol (RIP), Open Shortest Path First (OSPF), Enhanced Interior Gateway Routing Protocol (EIGRP), Intermediate System to Intermediate System (IS-IS), and Label Distribution Protocol (LDP). Satisfies: SRG-NET-000230-RTR-000001, SRG-NET-000168-RTR-000077
STIG			Date
Nokia Service Router OS 25.x Router Security Technical Implementation Guide			2026-06-15

Details

Check Text (C-283912r1203985_chk)

Review the router configuration. For every protocol that affects the routing or forwarding tables (where information is exchanged between neighbors), verify neighbor router authentication is enabled using the command below: - 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 authentication is not enabled, this is a finding.

Fix Text (F-88382r1203984_fix)

Configure authentication to be enabled for every protocol that affects the routing or forwarding tables using the example below: Configure key chain: - 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 Apply the key chain to the BGP neighbor: - configure router bgp group "eBGP" auth-keychain "test"