OpenControls Logo

STIG Viewer

STIGViewer Support

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 IDVersionRule IDIA ControlsSeverity
V-283911NOKI-RT-001000SV-283911r1203982_ruleCCI-000803medium
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.
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (7) 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
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 (36) 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-12Audit Record Generation
1.00
AU-3Content of Audit Records
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00

+26 more (top 10 by confidence shown)

CCI1 mapping
CCI-000803
1.00
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.

PR.AA-01
1.00
PR.AA-03
1.00

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-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