OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia Border Gateway Protocol (BGP) router must be configured to use a unique key for each autonomous system (AS) that it peers with.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283884NOKI-RT-000670SV-283884r1203901_ruleCCI-001184medium
Description
If the same keys are used between eBGP neighbors, the chance of a hacker compromising any of the BGP sessions increases. A malicious user could exist in one autonomous system who would know the key used for the eBGP session. This user would then be able to hijack BGP sessions with other trusted neighbors.
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 (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.

NET-09Session Integrity
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (30) 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(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
AU-9(3)Cryptographic Protection
1.00
CM-14Signed Components
1.00
CM-5(3)Signed Components
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(1)Multi-factor Authentication to Privileged Accounts
1.00
IA-2(12)Acceptance of PIV Credentials
1.00

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

3.13.15
1.00
CCI1 mapping
CCI-001184
1.00

Details

Check Text (C-283884r1203901_chk)

Interview the information system security manager (ISSM) and router administrator to determine if unique keys are being used. Verify the key-chain is enabled for the BGP protocol 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 NOTE: Nokia router is limited to MD5, HMAC-sha-1-96, and AES-128-CMAC-96 for BGP authentication. Configure the router with AES-128-CMAC-96, which will be FIPS compliant once SP 800-224 is finalized. Until then, this is a finding because it is not FIPS compliant but may be downgraded to a CAT III. If the key-chain is not enabled for the BGP protocol, this is a finding.

Fix Text (F-88354r1203900_fix)

Configure all eBGP routers with unique keys for each eBGP neighbor that it peers with, as shown in the example below: Configure a 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"