The VMM must implement replay-resistant authentication mechanisms for network access to privileged accounts.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-207392	SRG-OS-000112	SRG-OS-000112-VMM-000560	SV-207392r958494_rule	2024-12-06	2

Description
A replay attack may enable an unauthorized user to gain access to the VMM. Authentication sessions between the authenticator and the VMM 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. A privileged account is any VMM account with authorizations of a privileged user. 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.

Description

A replay attack may enable an unauthorized user to gain access to the VMM. Authentication sessions between the authenticator and the VMM 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. A privileged account is any VMM account with authorizations of a privileged user. 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.

ℹ️ Check
Verify the VMM implements replay-resistant authentication mechanisms for network access to privileged accounts. If it does not, this is a finding.

✔️ Fix
Configure the VMM to implement replay-resistant authentication mechanisms for network access to privileged accounts.