The VMM must use multifactor authentication for local access to privileged accounts.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-207389 | SRG-OS-000107-VMM-000530 | SV-207389r984206_rule | CCI-000765 | medium |
| Description | ||||
| To assure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication is defined as using two or more factors to achieve authentication. Factors include: (i) Something you know (e.g., password/PIN); (ii) Something you have (e.g., cryptographic identification device, token); or (iii) Something you are (e.g., biometric). A privileged account is defined as a VMM account with authorizations of a privileged user. Local access is defined as access to an organizational VMM by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. The DOD CAC with DOD-approved PKI is an example of multifactor authentication. | ||||
| STIG | Date | |||
| Virtual Machine Manager Security Requirements Guide | 2024-12-06 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
IA-2(1)
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.5.3
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000765
1.00
- DISA · 2 · disa_xccdf · related
Details
Check Text (C-207389r984206_chk)
Verify the VMM uses multifactor authentication for local access to privileged accounts.
If it does not, this is a finding.
Fix Text (F-7646r365578_fix)
Configure the VMM to use multifactor authentication for local access to privileged accounts.