STIGQter: STIG Summary: Juniper EX Series Switches Router Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 24 Jul 2024:

The Juniper router must be configured to use encryption for routing protocol authentication.

DISA Rule

SV-254001r844036_rule

Vulnerability Number

V-254001

Group Title

SRG-NET-000168-RTR-000077

Rule Version

JUEX-RT-000290

Severity

CAT II

CCI(s)

• CCI-000803 - Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.

Weight

10

Fix Recommendation

Configure routing protocol authentication to encrypt the authentication key.

set protocols ospf area <area number> interface <interface name>.<logical unit> authentication md5 <key ID> key "<PSK>"
-or-
set protocols ospf area <area number> interface <interface name>.<logical unit> ipsec-sa <SA name>

set protocols ospf3 area <area number> interface <interface name>.<logical unit> ipsec-sa <SA name>

set security ipsec security-association <SA name> mode transport
set security ipsec security-association <SA name> manual direction bidirectional protocol (ah | esp | bundle)
set security ipsec security-association <SA name> manual direction bidirectional spi <manually configured SPI (256..16639)>
set security ipsec security-association <SA name> manual direction bidirectional encryption algorithm (hmac-sha1-96 | hmac-sha-256-128)
set security ipsec security-association <SA name> manual direction bidirectional authentication key hexadecimal "<appropriate PSK>"
Note: Encryption keys can also be entered as ASCII with the keyword 'ascii-text' replacing 'hexadecimal'. Regardless of key type, the PSK is hashed in the configuration.

Check Contents

Review the router configuration.

For every protocol that affects the routing or forwarding tables (where information is exchanged between neighbors), verify that neighbor router authentication is encrypting the authentication key.

[edit protocols]
ospf {
area <area number> {
interface <interface name>.<logical unit> {
authentication {
md5 1 key "$8$aes256-gcm$hmac-sha2-256$100$hvt9Fpk6EEU$I2FKFJNrdKHpp1xesMB0aA$l9BsHxOYO4+B8f7erRj8Hw$A9PYzx53Ius"; ## SECRET-DATA
}
}
interface <interface name>.<logical unit> {
ipsec-sa <SA name>;
}
}
}
ospf3 {
area <area number> {
interface <interface name>.<logical unit> {
ipsec-sa <SA name>;
}
}
}

Note: OSPFv3 only supports IPsec SA authentication; OSPFv2 supports both IPsec SA and MD5 authentication. MD5 authentication is only included to support devices that do not support IPsec SA authentication.

Verify the OSPFv3 SA.
[edit security ipsec]
security-association <SA name> {
mode transport;
manual {
direction bidirectional {
protocol (ah | esp | bundle);
spi (256..16639); <<< The SPI is an integer value that must match the peer
encryption {
algorithm (hmac-sha1-96 | hmac-sha-256-128);
key hexadecimal "$8$aes256-gcm$hmac-sha2-256$100$QAP67/2oV/s$nz+2A3zRz40fwxMJdbbA0Q$R5A/koX36OvUWBB543QwAA$tQrR3fkCL2oQ3V1O2Tw2lYl7THNuqBQ6hpyi8naLlXMaKQM0SdJYefQU41rB3zpjisVIWBwS+S8+O146luRf3Q"; ## SECRET-DATA
}
}
}
}
Note: OSPFv3 SA uses manual transport mode encapsulating security payload (ESP) associations.

If authentication is not encrypting the authentication key, this is a finding.

Vulnerability Number

V-254001

Documentable

False

Rule Version

JUEX-RT-000290

Severity Override Guidance

Review the router configuration.

For every protocol that affects the routing or forwarding tables (where information is exchanged between neighbors), verify that neighbor router authentication is encrypting the authentication key.

[edit protocols]
ospf {
area <area number> {
interface <interface name>.<logical unit> {
authentication {
md5 1 key "$8$aes256-gcm$hmac-sha2-256$100$hvt9Fpk6EEU$I2FKFJNrdKHpp1xesMB0aA$l9BsHxOYO4+B8f7erRj8Hw$A9PYzx53Ius"; ## SECRET-DATA
}
}
interface <interface name>.<logical unit> {
ipsec-sa <SA name>;
}
}
}
ospf3 {
area <area number> {
interface <interface name>.<logical unit> {
ipsec-sa <SA name>;
}
}
}

Note: OSPFv3 only supports IPsec SA authentication; OSPFv2 supports both IPsec SA and MD5 authentication. MD5 authentication is only included to support devices that do not support IPsec SA authentication.

Verify the OSPFv3 SA.
[edit security ipsec]
security-association <SA name> {
mode transport;
manual {
direction bidirectional {
protocol (ah | esp | bundle);
spi (256..16639); <<< The SPI is an integer value that must match the peer
encryption {
algorithm (hmac-sha1-96 | hmac-sha-256-128);
key hexadecimal "$8$aes256-gcm$hmac-sha2-256$100$QAP67/2oV/s$nz+2A3zRz40fwxMJdbbA0Q$R5A/koX36OvUWBB543QwAA$tQrR3fkCL2oQ3V1O2Tw2lYl7THNuqBQ6hpyi8naLlXMaKQM0SdJYefQU41rB3zpjisVIWBwS+S8+O146luRf3Q"; ## SECRET-DATA
}
}
}
}
Note: OSPFv3 SA uses manual transport mode encapsulating security payload (ESP) associations.

If authentication is not encrypting the authentication key, this is a finding.

Check Content Reference

M

Target Key

5479