STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283912NOKI-RT-001010SV-283912r1203985_ruleCCI-001184medium
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
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

Related Frameworks

2 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (8) 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.

IAC-01.2Authenticate, Authorize and Audit (AAA)
1.00
IAC-02Identification & Authentication for Organizational Users
1.00
IAC-03Identification & Authentication for Non-Organizational Users
1.00
IAC-04Identification & Authentication for Devices
1.00
IAC-05Identification & Authentication for Third-Party Technology Assets, Applications and/or Services (TAAS)
1.00
NET-09Session Integrity
1.00
CRY-02Automated Authentication Through Cryptographic Modules
0.50
IAC-12Cryptographic Module Authentication
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (51) 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-17(1)Monitoring and Control
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-4Information Flow Enforcement
1.00
AC-4(17)Domain Authentication
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
AU-12Audit Record Generation
1.00

+41 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.

CCI2 mappings
NIST CSF 2.00 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.

Who does this work

7 NICE work roles and 5 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-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"