JUNI-ND-001190 - The Juniper router must be configured to use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of remote maintenance sessions.


Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.

Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network.

Currently, HMAC is the only FIPS-approved algorithm for generating and verifying message/data authentication codes in accordance with FIPS 198-1. Products that are FIPS 140-2 validated will have an HMAC that meets specification; however, the option must be configured for use as the only message authentication code used for authentication to cryptographic modules.

Separate requirements for configuring applications and protocols used by each application (e.g., SNMPv3, SSHv2, NTP, HTTPS, and other protocols and applications that require server/client authentication) are required to implement this requirement. Where SSH is used, the SSHv2 protocol suite is required because it includes Layer 7 protocols such as SCP and SFTP, which can be used for secure file transfers.


Configure SSH to use FIPS-validated HMAC for remote maintenance sessions as shown in the following example:

[edit system services]
set ssh protocol-version v2
set ssh macs hmac-sha2-256

See Also


Item Details


References: 800-53|MA-4(6), CAT|I, CCI|CCI-002890, Rule-ID|SV-217340r879784_rule, STIG-ID|JUNI-ND-001190, STIG-Legacy|SV-101269, STIG-Legacy|V-91169, Vuln-ID|V-217340

Plugin: Juniper

Control ID: 4c217d4f08a755e06be55b2678ea1a1aa3fa8b11c5d7343b2f271b8ac707766e