The Juniper BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-217052 | SRG-NET-000230-RTR-000002 | JUNI-RT-000470 | SV-217052r945862_rule | 2024-12-05 | 3 |
| Description |
|---|
| If the same keys are used between eBGP neighbors, the chance of a hacker compromising any of the BGP sessions increases. It is possible that a malicious user exists 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. |
| ℹ️ Check |
|---|
| Review the BGP configuration to determine if it is peering with multiple autonomous systems. Interview the ISSM and router administrator to determine if unique keys are being used. protocols { bgp { group AS44 { type external; peer-as 44; neighbor x.x.x.x { authentication-key "$8$tBga0ORx7VsYoIEgJ"; ## SECRET-DATA } } group AS66 { type external; peer-as 66; neighbor x.x.x.x { authentication-key "$8$Q4953nCrlMLX-9A7V"; ## SECRET-DATA } } } If unique keys are not being used, this is a finding. |
| ✔️ Fix |
|---|
| Configure the router to use unique keys for each AS that it peers with as shown in the example below. [edit protocols bgp] set group GROUP_AS66 authentication-key abc123 set group GROUP_AS44 authentication-key xyz123 |