JUNI-ND-000530 - The Juniper router must be configured to implement replay-resistant authentication mechanisms for network access to privileged accounts - ssh v2

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version


A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack.

An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.

Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.


Configure SSH to use FIPS-140-2 compliant HMACs as shown in the example below.

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

Note: An SSH configuration enables a server and client to authorize the negotiation of only those algorithms that are configured from the allowed list. If a user tries to negotiate using an algorithm that is not part of the allowed list, the request is rejected and the session is not established.

See Also


Item Details

References: CAT|II, CCI|CCI-001941, Rule-ID|SV-217322r855871_rule, STIG-ID|JUNI-ND-000530, STIG-Legacy|SV-101229, STIG-Legacy|V-91129, Vuln-ID|V-217322

Plugin: Juniper

Control ID: ba17b12e18d05a26c9b3330b2fab49067d43bd2a631fa48dbf4b785474a409fc