Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Virtual Machine Manager Security Requirements Guide

V1R3 · · · Released 25 Oct 2023 · 190 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Sort by
b
The VMM must provide automated mechanisms for supporting account management functions.
AC-2 - Medium - CCI-000015 - V-207338 - SV-207338r378478_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000015
Version
SRG-OS-000001-VMM-000010
Vuln IDs
  • V-207338
  • V-56553
Rule IDs
  • SV-207338r378478_rule
  • SV-70813
Enterprise environments make account management challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. A comprehensive account management process that includes automation helps to ensure accounts designated as requiring attention are consistently and promptly addressed. Examples include, but are not limited to, using automation to take action on multiple accounts designated as inactive, suspended, or terminated or by disabling accounts located in non-centralized account stores such as multiple servers. This requirement applies to all account types, including individual/user, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. The automated mechanisms may reside within the VMM itself or may be offered by other infrastructure providing automated account management capabilities. Automated mechanisms may be composed of differing technologies that, when placed together, contain an overall automated mechanism supporting an organization's automated account management requirements. Account management functions include: assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the VMM to monitor account usage; and using automated telephonic notification to report atypical system account usage.
Checks: C-7595r365424_chk

Verify the VMM provides automated mechanisms for supporting account management functions. If it does not, this is a finding.

Fix: F-7595r365425_fix

Configure the VMM to provide automated mechanisms for supporting account management functions.

b
The VMM must automatically remove or disable local temporary user accounts after 72 hours.
AC-2 - Medium - CCI-000016 - V-207339 - SV-207339r378481_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000016
Version
SRG-OS-000002-VMM-000020
Vuln IDs
  • V-207339
  • V-56819
Rule IDs
  • SV-207339r378481_rule
  • SV-71079
If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. If temporary accounts are used, the VMM must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. To address access requirements, many VMMs may be integrated with enterprise level authentication/access mechanisms that meet or exceed access control policy requirements.
Checks: C-7596r365427_chk

Verify the VMM automatically removes or disables local temporary user accounts after 72 hours. If it does not, this is a finding.

Fix: F-7596r365428_fix

Configure the VMM to automatically remove or disable local temporary user accounts after 72 hours.

b
The VMM must automatically disable local accounts after a 35-day period of account inactivity.
AC-2 - Medium - CCI-000017 - V-207340 - SV-207340r378484_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000017
Version
SRG-OS-000003-VMM-000030
Vuln IDs
  • V-207340
  • V-56821
Rule IDs
  • SV-207340r378484_rule
  • SV-71081
Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. VMMs need to track periods of user inactivity and disable accounts after 35 days of inactivity. Such a process greatly reduces the risk that accounts will be hijacked, leading to a data compromise. This policy does not apply to either emergency accounts or infrequently used accounts. Infrequently used accounts are local logon administrator accounts used by the system administrator when network or normal logon/access is not available. Emergency accounts are accounts created in response to crisis situations.
Checks: C-7597r365430_chk

Verify the VMM automatically disables local accounts after a 35-day period of account inactivity. If it does not, this is a finding.

Fix: F-7597r365431_fix

Configure the VMM to automatically disable local accounts after a 35-day period of account inactivity.

b
The VMM must automatically audit account creation.
AC-2 - Medium - CCI-000018 - V-207341 - SV-207341r378487_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000018
Version
SRG-OS-000004-VMM-000040
Vuln IDs
  • V-207341
  • V-56825
Rule IDs
  • SV-207341r378487_rule
  • SV-71085
Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes. To address access requirements, many VMMs may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7598r365433_chk

Verify the VMM automatically audits account creation. If it does not, this is a finding.

Fix: F-7598r365434_fix

Configure the VMM to automatically audit account creation.

b
The VMM must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
AC-7 - Medium - CCI-000044 - V-207342 - SV-207342r378517_rule
RMF Control
AC-7
Severity
M
CCI
CCI-000044
Version
SRG-OS-000021-VMM-000050
Vuln IDs
  • V-207342
  • V-56833
Rule IDs
  • SV-207342r378517_rule
  • SV-71093
By limiting the number of failed login attempts, the risk of unauthorized VMM access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. This restriction may be relaxed for administrative accounts to avoid potential Denial of Service.
Checks: C-7599r365436_chk

Verify the VMM enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding.

Fix: F-7599r365437_fix

Configure the VMM to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period, by locking the account.

b
The VMM must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
AC-8 - Medium - CCI-000048 - V-207343 - SV-207343r378520_rule
RMF Control
AC-8
Severity
M
CCI
CCI-000048
Version
SRG-OS-000023-VMM-000060
Vuln IDs
  • V-207343
  • V-56839
Rule IDs
  • SV-207343r378520_rule
  • SV-71099
Display of a standardized and approved use notification before granting access to the VMM ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for a VMM that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) VMM (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for VMMs that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."
Checks: C-7600r365439_chk

Verify the VMM displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. If it does not, this is a finding. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for a VMM that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) VMM (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for VMMs that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

Fix: F-7600r365440_fix

Configure the VMM to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for a VMM that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) VMM (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for VMMs that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

b
The VMM must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.
AC-8 - Medium - CCI-000050 - V-207344 - SV-207344r378523_rule
RMF Control
AC-8
Severity
M
CCI
CCI-000050
Version
SRG-OS-000024-VMM-000070
Vuln IDs
  • V-207344
  • V-56847
Rule IDs
  • SV-207344r378523_rule
  • SV-71107
The banner must be acknowledged by the user prior to allowing the user access to the VMM. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. To establish acceptance of the application usage policy, a click-through banner at system logon is required. The system must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK".
Checks: C-7601r365442_chk

Verify the VMM retains the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access. If it does not, this is a finding.

Fix: F-7601r365443_fix

Configure the VMM to retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.

b
The VMM must limit the number of concurrent sessions to ten for all accounts and/or account types.
AC-10 - Medium - CCI-000054 - V-207345 - SV-207345r378532_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
SRG-OS-000027-VMM-000080
Vuln IDs
  • V-207345
  • V-56855
Rule IDs
  • SV-207345r378532_rule
  • SV-71115
VMM management includes the ability to control the number of users and user sessions that utilize the VMM. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks. This requirement addresses concurrent sessions for VMM accounts and does not address concurrent sessions by single users via multiple VMM accounts. If the concurrent-session limitation of ten is insufficient to support operational requirements, it may be set to a higher value, but it must not be unlimited.
Checks: C-7602r365445_chk

Verify the VMM limits the number of concurrent sessions to ten for all accounts and/or account types. If it does not, this is a finding.

Fix: F-7602r365446_fix

Configure the VMM to limit the number of concurrent sessions to ten for all accounts and/or account types.

b
The VMM must retain the session lock until the user reestablishes access using established identification and authentication procedures.
AC-11 - Medium - CCI-000056 - V-207346 - SV-207346r378535_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000056
Version
SRG-OS-000028-VMM-000090
Vuln IDs
  • V-207346
  • V-56857
Rule IDs
  • SV-207346r378535_rule
  • SV-71117
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the VMM but does not want to log out because of the temporary nature of the absence. The session lock is implemented at the point where session activity can be determined. Regardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates. No other activity aside from re-authentication shall unlock the VMM session.
Checks: C-7603r365448_chk

Verify the VMM retains the session lock until the user reestablishes access using established identification and authentication procedures. If it does not, this is a finding.

Fix: F-7603r365449_fix

Configure the VMM to retain the session lock until the user reestablishes access using established identification and authentication procedures.

b
The VMM must initiate a session lock after a 15-minute period of inactivity.
AC-11 - Medium - CCI-000057 - V-207347 - SV-207347r378598_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000057
Version
SRG-OS-000029-VMM-000100
Vuln IDs
  • V-207347
  • V-56859
Rule IDs
  • SV-207347r378598_rule
  • SV-71119
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the VMM but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their VMM session prior to vacating the vicinity, VMMs need to be able to identify when a user's session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled.
Checks: C-7604r365451_chk

Verify the VMM initiates a session lock after a 15-minute period of inactivity. If it does not, this is a finding.

Fix: F-7604r365452_fix

Configure the VMM to initiate a session lock after a 15-minute period of inactivity.

b
The VMM must provide the capability for users to directly initiate a session lock.
AC-11 - Medium - CCI-000058 - V-207348 - SV-207348r378601_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000058
Version
SRG-OS-000030-VMM-000110
Vuln IDs
  • V-207348
  • V-56863
Rule IDs
  • SV-207348r378601_rule
  • SV-71123
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the VMM but does not want to log out because of the temporary nature of the absence. The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, VMMs need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity.
Checks: C-7605r365454_chk

Verify the VMM provides the capability for users to directly initiate a session lock. If it does not, this is a finding.

Fix: F-7605r365455_fix

Configure the VMM to provide the capability for users to directly initiate a session lock.

b
The VMM must conceal, via the session lock, information previously visible on the display with a publicly viewable image.
AC-11 - Medium - CCI-000060 - V-207349 - SV-207349r378604_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000060
Version
SRG-OS-000031-VMM-000120
Vuln IDs
  • V-207349
  • V-56867
Rule IDs
  • SV-207349r378604_rule
  • SV-71127
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the VMM but does not log out because of the temporary nature of the absence. The session lock is implemented at the point where session activity can be determined. The VMM session lock event must include an obfuscation of the display screen to prevent other users from reading what was previously displayed. Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, or a blank screen, with the additional caveat that none of the images convey sensitive information.
Checks: C-7606r365457_chk

Verify the VMM conceals, via the session lock, information previously visible on the display with a publicly viewable image. If it does not, this is a finding.

Fix: F-7606r365458_fix

Configure the VMM to conceal, via the session lock, information previously visible on the display with a publicly viewable image.

b
The VMM must monitor remote access methods automatically.
AC-17 - Medium - CCI-000067 - V-207350 - SV-207350r378607_rule
RMF Control
AC-17
Severity
M
CCI
CCI-000067
Version
SRG-OS-000032-VMM-000130
Vuln IDs
  • V-207350
  • V-56871
Rule IDs
  • SV-207350r378607_rule
  • SV-71131
Remote access services, such as those providing remote access to network devices and VMMs, which lack automated capabilities, increase risk and make remote user access management difficult at best. Remote access is access to DoD VMMs by an authorized user (or another VMM) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Automated monitoring of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of VMM components.
Checks: C-7607r365460_chk

Verify the VMM monitors remote access methods automatically. If it does not, this is a finding.

Fix: F-7607r365461_fix

Configure the VMM to monitor remote access methods automatically.

b
The VMM must use DoD-approved encryption to protect the confidentiality of remote access sessions.
AC-17 - Medium - CCI-000068 - V-207351 - SV-207351r378610_rule
RMF Control
AC-17
Severity
M
CCI
CCI-000068
Version
SRG-OS-000033-VMM-000140
Vuln IDs
  • V-207351
  • V-56873
Rule IDs
  • SV-207351r378610_rule
  • SV-71133
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DoD non-public VMMs by an authorized user (or another VMM) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of mechanism is selected based on the security categorization of the information.
Checks: C-7608r365463_chk

Verify the VMM uses DoD-approved encryption to protect the confidentiality of remote access sessions. If it does not, this is a finding.

Fix: F-7608r365464_fix

Configure the VMM to use DoD-approved encryption to protect the confidentiality of remote access sessions.

b
The VMM must produce audit records containing information to establish what type of events occurred.
AU-3 - Medium - CCI-000130 - V-207352 - SV-207352r378616_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000130
Version
SRG-OS-000037-VMM-000150
Vuln IDs
  • V-207352
  • V-56875
Rule IDs
  • SV-207352r378616_rule
  • SV-71135
Without establishing what types of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process/VM identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the VMM audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured VMM.
Checks: C-7609r365466_chk

Verify the VMM produces audit records containing information to establish what type of events occurred. If it does not, this is a finding.

Fix: F-7609r365467_fix

Configure the VMM to produce audit records containing information to establish what type of events occurred.

b
The VMM must produce audit records containing information to establish when (date and time) the events occurred.
AU-3 - Medium - CCI-000131 - V-207353 - SV-207353r378619_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000131
Version
SRG-OS-000038-VMM-000160
Vuln IDs
  • V-207353
  • V-56879
Rule IDs
  • SV-207353r378619_rule
  • SV-71139
Without establishing when events occurred, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time). Associating event types with detected events in the VMM audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured VMM.
Checks: C-7610r365469_chk

Verify the VMM produces audit records containing information to establish when (date and time) the events occurred. If it does not, this is a finding.

Fix: F-7610r365470_fix

Configure the VMM to produce audit records containing information to establish when (date and time) the events occurred.

b
The VMM must produce audit records containing information to establish where the events occurred.
AU-3 - Medium - CCI-000132 - V-207354 - SV-207354r378622_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000132
Version
SRG-OS-000039-VMM-000170
Vuln IDs
  • V-207354
  • V-56881
Rule IDs
  • SV-207354r378622_rule
  • SV-71141
Without establishing where events occurred, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as VMM components, guest VMs, modules, device identifiers, node names, file names, and functionality. Associating information about where the event occurred within the VMM provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured VMM.
Checks: C-7611r365472_chk

Verify the VMM produces audit records containing information to establish where the events occurred. If it does not, this is a finding.

Fix: F-7611r365473_fix

Configure the VMM to produce audit records containing information to establish where the events occurred.

b
The VMM must produce audit records containing information to establish the source of the events.
AU-3 - Medium - CCI-000133 - V-207355 - SV-207355r378625_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000133
Version
SRG-OS-000040-VMM-000180
Vuln IDs
  • V-207355
  • V-56885
Rule IDs
  • SV-207355r378625_rule
  • SV-71145
Without establishing the source of an event, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack. In addition to logging where events occur within the VMM, the VMM must also generate audit records that identify sources of events. Sources of VMM events include, but are not limited to, guest VMs, processes and services. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know the source of the event.
Checks: C-7612r365475_chk

Verify the VMM produces audit records containing information to establish the source of the events. If it does not, this is a finding.

Fix: F-7612r365476_fix

Configure the VMM to produce audit records containing information to establish the source of the events.

b
The VMM must produce audit records containing information to establish the outcome of the events.
AU-3 - Medium - CCI-000134 - V-207356 - SV-207356r378628_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000134
Version
SRG-OS-000041-VMM-000190
Vuln IDs
  • V-207356
  • V-56889
Rule IDs
  • SV-207356r378628_rule
  • SV-71149
Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the VMM after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.
Checks: C-7613r365478_chk

Verify the VMM produces audit records containing information to establish the outcome of the events. If it does not, this is a finding.

Fix: F-7613r365479_fix

Configure the VMM to produce audit records containing information to establish the outcome of the events.

b
The VMM must generate audit records containing the full-text recording of privileged commands or the individual identities of group account users.
AU-3 - Medium - CCI-000135 - V-207357 - SV-207357r378631_rule
RMF Control
AU-3
Severity
M
CCI
CCI-000135
Version
SRG-OS-000042-VMM-000200
Vuln IDs
  • V-207357
  • V-56891
Rule IDs
  • SV-207357r378631_rule
  • SV-71151
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations should consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. The additional information required is dependent on the type of information (i.e., sensitivity of the data and the environment within which it resides). At a minimum, the organization must audit either full-text recording of privileged commands or the individual identities of group users, or both. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. In addition, the VMM must have the capability to include organization-defined additional (more detailed) information in the audit records for audit events.
Checks: C-7614r365481_chk

Verify the VMM generates audit records containing the full-text recording of privileged commands or the individual identities of group account users. If it does not, this is a finding.

Fix: F-7614r365482_fix

Configure the VMM to generate audit records containing the full-text recording of privileged commands or the individual identities of group account users.

b
The VMM must alert the ISSO and SA (at a minimum) in the event of an audit processing failure.
AU-5 - Medium - CCI-000139 - V-207358 - SV-207358r378634_rule
RMF Control
AU-5
Severity
M
CCI
CCI-000139
Version
SRG-OS-000046-VMM-000210
Vuln IDs
  • V-207358
  • V-56893
Rule IDs
  • SV-207358r378634_rule
  • SV-71153
It is critical for the appropriate personnel to be aware if a VMM is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and VMM operation may be adversely affected. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. This requirement applies to each audit data storage repository (i.e., distinct VMM component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.
Checks: C-7615r365484_chk

Verify the VMM alerts the ISSO and SA (at a minimum) in the event of an audit processing failure. If it does not, this is a finding.

Fix: F-7615r365485_fix

Configure the VMM to alert the ISSO and SA (at a minimum) in the event of an audit processing failure.

b
The VMM must shut down by default upon audit failure (unless availability is an overriding concern).
AU-5 - Medium - CCI-000140 - V-207359 - SV-207359r378637_rule
RMF Control
AU-5
Severity
M
CCI
CCI-000140
Version
SRG-OS-000047-VMM-000220
Vuln IDs
  • V-207359
  • V-56895
Rule IDs
  • SV-207359r378637_rule
  • SV-71155
It is critical that when the VMM is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. When availability is an overriding concern, other approved actions in response to an audit failure are as follows: (i) If the failure was caused by the lack of audit record storage capacity, the VMM must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner. (ii) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the VMM must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.
Checks: C-7616r365487_chk

Verify the VMM shuts down by default upon audit failure (unless availability is an overriding concern). If it does not, this is a finding.

Fix: F-7616r365488_fix

Configure the VMM to shut down by default upon audit failure (unless availability is an overriding concern).

b
The VMM must support the capability to centrally review and analyze audit records from multiple components within the system.
AU-6 - Medium - CCI-000154 - V-207360 - SV-207360r378640_rule
RMF Control
AU-6
Severity
M
CCI
CCI-000154
Version
SRG-OS-000051-VMM-000230
Vuln IDs
  • V-207360
  • V-56897
Rule IDs
  • SV-207360r378640_rule
  • SV-71157
Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the VMM does not provide the ability to centrally review the VMM logs, forensic analysis is negatively impacted. Segregation of logging data to multiple disparate computer systems is counterproductive and makes log analysis and log event alarming difficult to implement and manage, particularly when the system has multiple logging components writing to different locations or systems. To support the centralized capability, the VMM must be able to provide the information in a format that can be extracted and used, allowing the application performing the centralization of the log records to meet this requirement.
Checks: C-7617r365490_chk

Verify the VMM supports the capability to centrally review and analyze audit records from multiple components within the system. If it does not, this is a finding.

Fix: F-7617r365491_fix

Configure the VMM to support the capability to centrally review and analyze audit records from multiple components within the system.

b
The VMM must support the capability to filter audit records for events of interest based upon all audit fields within audit records.
AU-7 - Medium - CCI-000158 - V-207361 - SV-207361r378643_rule
RMF Control
AU-7
Severity
M
CCI
CCI-000158
Version
SRG-OS-000054-VMM-000240
Vuln IDs
  • V-207361
  • V-56899
Rule IDs
  • SV-207361r378643_rule
  • SV-71159
The ability to specify the event criteria that are of interest provides the individuals reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation. Without this capability, forensic investigations are impeded. Events of interest can be identified by the content of specific audit record fields, including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations use all audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific VMM component. This requires VMMs to provide the capability to customize audit record reports based on all available criteria.
Checks: C-7618r365493_chk

Verify the VMM supports the capability to filter audit records for events of interest based upon all audit fields within audit records. If it does not, this is a finding.

Fix: F-7618r365494_fix

Configure the VMM to support the capability to filter audit records for events of interest based upon all audit fields within audit records.

b
The VMM must use internal system clocks to generate time stamps for audit records.
AU-8 - Medium - CCI-000159 - V-207362 - SV-207362r378646_rule
RMF Control
AU-8
Severity
M
CCI
CCI-000159
Version
SRG-OS-000055-VMM-000250
Vuln IDs
  • V-207362
  • V-56901
Rule IDs
  • SV-207362r378646_rule
  • SV-71161
Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a VMM is critical when conducting forensic analysis and investigating system events. If the internal clock is not used, the VMM may not be able to provide time stamps for log messages. Additionally, externally generated time stamps may not be accurate.
Checks: C-7619r365496_chk

Verify the VMM uses internal system clocks to generate time stamps for audit records. If it does not, this is a finding.

Fix: F-7619r365497_fix

Configure the VMM to use internal system clocks to generate time stamps for audit records.

b
The VMM must protect audit information from unauthorized read access.
AU-9 - Medium - CCI-000162 - V-207363 - SV-207363r378649_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000162
Version
SRG-OS-000057-VMM-000260
Vuln IDs
  • V-207363
  • V-56905
Rule IDs
  • SV-207363r378649_rule
  • SV-71165
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult to achieve. To ensure the confidentiality of audit data, the VMM must protect audit information from unauthorized access. This requirement can be achieved through multiple methods which will depend upon system architecture and design. Commonly employed methods for protecting audit information include least privilege permissions as well as restricting the location and number of log file repositories. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit VMM activity.
Checks: C-7620r365499_chk

Verify the VMM protects audit information from unauthorized read access. If it does not, this is a finding.

Fix: F-7620r365500_fix

Configure the VMM to protect audit information from unauthorized read access.

b
The VMM must protect audit information from unauthorized modification.
AU-9 - Medium - CCI-000163 - V-207364 - SV-207364r378652_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000163
Version
SRG-OS-000058-VMM-000270
Vuln IDs
  • V-207364
  • V-56907
Rule IDs
  • SV-207364r378652_rule
  • SV-71167
If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the VMM must protect audit information from unauthorized modification. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit VMM activity.
Checks: C-7621r365502_chk

Verify the VMM protects audit information from unauthorized modification. If it does not, this is a finding.

Fix: F-7621r365503_fix

Configure the VMM to protect audit information from unauthorized modification.

b
The VMM must protect audit information from unauthorized deletion.
AU-9 - Medium - CCI-000164 - V-207365 - SV-207365r378655_rule
RMF Control
AU-9
Severity
M
CCI
CCI-000164
Version
SRG-OS-000059-VMM-000280
Vuln IDs
  • V-207365
  • V-56911
Rule IDs
  • SV-207365r378655_rule
  • SV-71171
If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the VMM must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit VMM activity.
Checks: C-7622r365505_chk

Verify the VMM protects audit information from unauthorized deletion. If it does not, this is a finding.

Fix: F-7622r365506_fix

Configure the VMM to protect audit information from unauthorized deletion.

b
The VMM must provide audit record generation capability for DoD-defined auditable events for all VMM components.
AU-12 - Medium - CCI-000169 - V-207366 - SV-207366r378721_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
SRG-OS-000062-VMM-000300
Vuln IDs
  • V-207366
  • V-56915
Rule IDs
  • SV-207366r378721_rule
  • SV-71175
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter). The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. DoD has defined the list of events for which the VMM will provide an audit record generation capability as the following: (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the VMM; (iii) All account creations, modifications, disabling, and terminations; and (iv) All kernel module load, unload, and restart actions.
Checks: C-7623r365508_chk

Verify the VMM provides audit record generation capability for DoD-defined auditable events for all VMM components. If it does not, this is a finding. DoD has defined the list of events for which the VMM will provide an audit record generation capability as the following: (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the VMM; (iii) All account creations, modifications, disabling, and terminations; and (iv) All kernel module load, unload, and restart actions.

Fix: F-7623r365509_fix

Configure the VMM to provide audit record generation capability for DoD-defined auditable events for all VMM components. DoD has defined the list of events for which the VMM will provide an audit record generation capability as the following: (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the VMM; (iii) All account creations, modifications, disabling, and terminations; and (iv) All kernel module load, unload, and restart actions.

b
The VMM must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
AU-12 - Medium - CCI-000171 - V-207367 - SV-207367r378724_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000171
Version
SRG-OS-000063-VMM-000310
Vuln IDs
  • V-207367
  • V-56919
Rule IDs
  • SV-207367r378724_rule
  • SV-71179
Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the VMM's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Checks: C-7624r365511_chk

Verify the VMM allows only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. If it does not, this is a finding.

Fix: F-7624r365512_fix

Configure the VMM to allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.

b
The VMM must generate audit records when successful/unsuccessful attempts to access privileges occur.
AU-12 - Medium - CCI-000172 - V-207368 - SV-207368r378727_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000064-VMM-000320
Vuln IDs
  • V-207368
  • V-56923
Rule IDs
  • SV-207368r378727_rule
  • SV-71183
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., guest VM, module, or policy filter).
Checks: C-7625r365514_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding.

Fix: F-7625r365515_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to access privileges occur.

b
The VMM, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.
IA-5 - Medium - CCI-000185 - V-207369 - SV-207369r378730_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000185
Version
SRG-OS-000066-VMM-000330
Vuln IDs
  • V-207369
  • V-56925
Rule IDs
  • SV-207369r378730_rule
  • SV-71185
Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. This requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.
Checks: C-7626r365517_chk

Verify the VMM, for PKI-based authentication, validates certificates by constructing a certification path (which includes status information) to an accepted trust anchor. If it does not, this is a finding.

Fix: F-7626r365518_fix

Configure the VMM, for PKI-based authentication, to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.

b
The VMM, for PKI-based authentication, must enforce authorized access to the corresponding private key.
IA-5 - Medium - CCI-000186 - V-207370 - SV-207370r378733_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000186
Version
SRG-OS-000067-VMM-000340
Vuln IDs
  • V-207370
  • V-56927
Rule IDs
  • SV-207370r378733_rule
  • SV-71187
If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.
Checks: C-7627r365520_chk

Verify the VMM, for PKI-based authentication, enforces authorized access to the corresponding private key. If it does not, this is a finding.

Fix: F-7627r365521_fix

Configure the VMM, for PKI-based authentication, to enforce authorized access to the corresponding private key.

b
The VMM must map the authenticated identity to the user or group account for PKI-based authentication.
IA-5 - Medium - CCI-000187 - V-207371 - SV-207371r378736_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000187
Version
SRG-OS-000068-VMM-000350
Vuln IDs
  • V-207371
  • V-56929
Rule IDs
  • SV-207371r378736_rule
  • SV-71189
Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.
Checks: C-7628r365523_chk

Verify the VMM maps the authenticated identity to the user or group account for PKI-based authentication. If it does not, this is a finding.

Fix: F-7628r365524_fix

Configure the VMM to map the authenticated identity to the user or group account for PKI-based authentication.

b
The VMM must enforce password complexity by requiring that at least one upper-case character be used.
IA-5 - Medium - CCI-000192 - V-207372 - SV-207372r378739_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000192
Version
SRG-OS-000069-VMM-000360
Vuln IDs
  • V-207372
  • V-56931
Rule IDs
  • SV-207372r378739_rule
  • SV-71191
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-7629r365526_chk

Verify the VMM enforces password complexity by requiring that at least one upper-case character be used. If it does not, this is a finding.

Fix: F-7629r365527_fix

Configure the VMM to enforce password complexity by requiring that at least one upper-case character be used.

b
The VMM must enforce password complexity by requiring that at least one lower-case character be used.
IA-5 - Medium - CCI-000193 - V-207373 - SV-207373r378742_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000193
Version
SRG-OS-000070-VMM-000370
Vuln IDs
  • V-207373
  • V-56933
Rule IDs
  • SV-207373r378742_rule
  • SV-71193
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-7630r365529_chk

Verify the VMM enforces password complexity by requiring that at least one lower-case character be used. If it does not, this is a finding.

Fix: F-7630r365530_fix

Configure the VMM to enforce password complexity by requiring that at least one lower-case character be used.

b
The VMM must enforce password complexity by requiring that at least one numeric character be used.
IA-5 - Medium - CCI-000194 - V-207374 - SV-207374r378745_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000194
Version
SRG-OS-000071-VMM-000380
Vuln IDs
  • V-207374
  • V-56969
Rule IDs
  • SV-207374r378745_rule
  • SV-71229
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-7631r365532_chk

Verify the VMM enforces password complexity by requiring that at least one numeric character be used. If it does not, this is a finding.

Fix: F-7631r365533_fix

Configure the VMM to enforce password complexity by requiring that at least one numeric character be used.

b
The VMM must require the change of at least 8 of the total number of characters when passwords are changed.
IA-5 - Medium - CCI-000195 - V-207375 - SV-207375r378748_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000195
Version
SRG-OS-000072-VMM-000390
Vuln IDs
  • V-207375
  • V-56971
Rule IDs
  • SV-207375r378748_rule
  • SV-71231
If the VMM allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks. The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different.
Checks: C-7632r365535_chk

Verify the VMM requires the change of at least 8 of the total number of characters when passwords are changed. If it does not, this is a finding.

Fix: F-7632r365536_fix

Configure the VMM to require the change of at least 8 of the total number of characters when passwords are changed.

b
The VMM must store only encrypted representations of passwords.
IA-5 - Medium - CCI-000196 - V-207376 - SV-207376r378751_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000196
Version
SRG-OS-000073-VMM-000400
Vuln IDs
  • V-207376
  • V-56943
Rule IDs
  • SV-207376r378751_rule
  • SV-71203
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.
Checks: C-7633r365538_chk

Verify the VMM stores only encrypted representations of passwords. If it does not, this is a finding.

Fix: F-7633r365539_fix

Configure the VMM to store only encrypted representations of passwords.

b
The VMM must transmit only encrypted representations of passwords.
IA-5 - Medium - CCI-000197 - V-207377 - SV-207377r378754_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000197
Version
SRG-OS-000074-VMM-000410
Vuln IDs
  • V-207377
  • V-56945
Rule IDs
  • SV-207377r378754_rule
  • SV-71205
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.
Checks: C-7634r365541_chk

Verify the VMM transmits only encrypted representations of passwords. If it does not, this is a finding.

Fix: F-7634r365542_fix

Configure the VMM to transmit only encrypted representations of passwords.

b
The VMM must enforce 24 hours/1 day as the minimum password lifetime.
IA-5 - Medium - CCI-000198 - V-207378 - SV-207378r378757_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000198
Version
SRG-OS-000075-VMM-000420
Vuln IDs
  • V-207378
  • V-56947
Rule IDs
  • SV-207378r378757_rule
  • SV-71207
Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.
Checks: C-7635r365544_chk

Verify the VMM enforces 24 hours/1 day as the minimum password lifetime. If it does not, this is a finding.

Fix: F-7635r365545_fix

Configure the VMM to enforce 24 hours/1 day as the minimum password lifetime.

b
The VMM must enforce a 60-day maximum password lifetime restriction.
IA-5 - Medium - CCI-000199 - V-207379 - SV-207379r378760_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000199
Version
SRG-OS-000076-VMM-000430
Vuln IDs
  • V-207379
  • V-56949
Rule IDs
  • SV-207379r378760_rule
  • SV-71209
Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the VMM does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the VMM passwords could be compromised.
Checks: C-7636r365547_chk

Verify the VMM enforces a 60-day maximum password lifetime restriction. If it does not, this is a finding.

Fix: F-7636r365548_fix

Configure the VMM to enforce a 60-day maximum password lifetime restriction.

b
The VMM must prohibit password reuse for a minimum of five generations.
IA-5 - Medium - CCI-000200 - V-207380 - SV-207380r378763_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000200
Version
SRG-OS-000077-VMM-000440
Vuln IDs
  • V-207380
  • V-56951
Rule IDs
  • SV-207380r378763_rule
  • SV-71211
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the VMM or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.
Checks: C-7637r365550_chk

Verify the VMM prohibits password reuse for a minimum of five generations. If it does not, this is a finding.

Fix: F-7637r365551_fix

Configure the VMM to prohibit password reuse for a minimum of five generations.

b
The VMM must enforce a minimum 15-character password length.
IA-5 - Medium - CCI-000205 - V-207381 - SV-207381r378766_rule
RMF Control
IA-5
Severity
M
CCI
CCI-000205
Version
SRG-OS-000078-VMM-000450
Vuln IDs
  • V-207381
  • V-56953
Rule IDs
  • SV-207381r378766_rule
  • SV-71213
The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.
Checks: C-7638r365553_chk

Verify the VMM enforces a minimum 15-character password length. If it does not, this is a finding.

Fix: F-7638r365554_fix

Configure the VMM to enforce a minimum 15-character password length.

b
The VMM must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
IA-6 - Medium - CCI-000206 - V-207382 - SV-207382r378769_rule
RMF Control
IA-6
Severity
M
CCI
CCI-000206
Version
SRG-OS-000079-VMM-000460
Vuln IDs
  • V-207382
  • V-56955
Rule IDs
  • SV-207382r378769_rule
  • SV-71215
To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback from the VMM shall not provide any information allowing an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided information that is typed into the system is a method used when addressing this risk. For example, displaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.
Checks: C-7639r365556_chk

Verify the VMM obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. If it does not, this is a finding.

Fix: F-7639r365557_fix

Configure the VMM to obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

b
The VMM must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
AC-3 - Medium - CCI-000213 - V-207383 - SV-207383r378772_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
SRG-OS-000080-VMM-000470
Vuln IDs
  • V-207383
  • V-56957
Rule IDs
  • SV-207383r378772_rule
  • SV-71217
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., networks, web servers, and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. VMMs use access control policies and enforcement mechanisms to implement this requirement. Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the VMM.
Checks: C-7640r365559_chk

Verify the VMM enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding.

Fix: F-7640r365560_fix

Configure the VMM to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

b
The VMM must be configured to disable non-essential capabilities.
CM-7 - Medium - CCI-000381 - V-207384 - SV-207384r378841_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
SRG-OS-000095-VMM-000480
Vuln IDs
  • V-207384
  • V-56959
Rule IDs
  • SV-207384r378841_rule
  • SV-71219
It is detrimental for VMMs to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. VMMs are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
Checks: C-7641r365562_chk

Verify the VMM is configured to disable non-essential capabilities. If it is not, this is a finding.

Fix: F-7641r365563_fix

Configure the VMM to disable non-essential capabilities.

b
The VMM must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
CM-7 - Medium - CCI-000382 - V-207385 - SV-207385r378844_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000382
Version
SRG-OS-000096-VMM-000490
Vuln IDs
  • V-207385
  • V-56961
Rule IDs
  • SV-207385r378844_rule
  • SV-71221
In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on VMMs. VMMs are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the VMM must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.
Checks: C-7642r365565_chk

Verify the VMM is configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. If it is not, this is a finding.

Fix: F-7642r365566_fix

Configure the VMM to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

b
The VMM must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users).
IA-2 - Medium - CCI-000764 - V-207386 - SV-207386r378847_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
SRG-OS-000104-VMM-000500
Vuln IDs
  • V-207386
  • V-56963
Rule IDs
  • SV-207386r378847_rule
  • SV-71223
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have the equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except for the following: (i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the VMM without identification or authentication; and (ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.
Checks: C-7643r365568_chk

Verify the VMM uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users). If it does not, this is a finding.

Fix: F-7643r365569_fix

Configure the VMM to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

b
The VMM must use multifactor authentication for network access to privileged accounts.
IA-2 - Medium - CCI-000765 - V-207387 - SV-207387r378850_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000765
Version
SRG-OS-000105-VMM-000510
Vuln IDs
  • V-207387
  • V-56965
Rule IDs
  • SV-207387r378850_rule
  • SV-71225
Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has (e.g., cryptographic identification device, token); or (iii) something a user is (e.g., biometric). A privileged account is defined as a VMM account with authorizations of a privileged user. Network access is defined as access to a VMM by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the Internet). The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
Checks: C-7644r365571_chk

Verify the VMM uses multifactor authentication for network access to privileged accounts. If it does not, this is a finding.

Fix: F-7644r365572_fix

Configure the VMM to use multifactor authentication for network access to privileged accounts.

b
The VMM must use multifactor authentication for network access to non-privileged accounts.
IA-2 - Medium - CCI-000766 - V-207388 - SV-207388r378853_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000766
Version
SRG-OS-000106-VMM-000520
Vuln IDs
  • V-207388
  • V-56977
Rule IDs
  • SV-207388r378853_rule
  • SV-71237
To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication uses 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 non-privileged account is any VMM account with authorizations of a non-privileged user. Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection. The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
Checks: C-7645r365574_chk

Verify the VMM uses multifactor authentication for network access to non-privileged accounts. If it does not, this is a finding.

Fix: F-7645r365575_fix

Configure the VMM to use multifactor authentication for network access to non-privileged accounts.

b
The VMM must use multifactor authentication for local access to privileged accounts.
IA-2 - Medium - CCI-000767 - V-207389 - SV-207389r378856_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000767
Version
SRG-OS-000107-VMM-000530
Vuln IDs
  • V-207389
  • V-56979
Rule IDs
  • SV-207389r378856_rule
  • SV-71239
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.
Checks: C-7646r365577_chk

Verify the VMM uses multifactor authentication for local access to privileged accounts. If it does not, this is a finding.

Fix: F-7646r365578_fix

Configure the VMM to use multifactor authentication for local access to privileged accounts.

b
The VMM must use multifactor authentication for local access to non-privileged accounts.
IA-2 - Medium - CCI-000768 - V-207390 - SV-207390r378859_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000768
Version
SRG-OS-000108-VMM-000540
Vuln IDs
  • V-207390
  • V-56981
Rule IDs
  • SV-207390r378859_rule
  • SV-71241
To assure accountability, prevent unauthenticated access, and prevent misuse of the system, privileged users must utilize multifactor authentication for local access. 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 or token); or (iii) Something you are (e.g., biometric). A non-privileged account is defined as a VMM account with authorizations of a regular or non-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.
Checks: C-7647r365580_chk

Verify the VMM uses multifactor authentication for local access to non-privileged accounts. If it does not, this is a finding.

Fix: F-7647r365581_fix

Configure the VMM to use multifactor authentication for local access to non-privileged accounts.

b
The VMM must require individuals to be authenticated with an individual authenticator prior to using a group authenticator.
IA-2 - Medium - CCI-000770 - V-207391 - SV-207391r378862_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000770
Version
SRG-OS-000109-VMM-000550
Vuln IDs
  • V-207391
  • V-56983
Rule IDs
  • SV-207391r378862_rule
  • SV-71243
To assure individual accountability and prevent unauthorized access, organizational users shall be individually identified and authenticated. A group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the UNIX OS "Root" user account, the Windows "Administrator" account, the "sa" account, or a "helpdesk" account. For example, the UNIX and Windows VMMs offer a 'switch user' capability allowing users to authenticate with their individual credentials and, when needed, 'switch' to the administrator role. This method provides for unique individual authentication prior to using a group authenticator. Users (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization which outlines specific user actions that can be performed on the VMM without identification or authentication. Requiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.
Checks: C-7648r365583_chk

Verify the VMM requires individuals to be authenticated with an individual authenticator prior to using a group authenticator. If it does not, this is a finding.

Fix: F-7648r365584_fix

Configure the VMM to require individuals to be authenticated with an individual authenticator prior to using a group authenticator.

b
The VMM must implement replay-resistant authentication mechanisms for network access to privileged accounts.
IA-2 - Medium - CCI-001941 - V-207392 - SV-207392r854604_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001941
Version
SRG-OS-000112-VMM-000560
Vuln IDs
  • V-207392
  • V-56985
Rule IDs
  • SV-207392r854604_rule
  • SV-71245
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.
Checks: C-7649r365586_chk

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

Fix: F-7649r365587_fix

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

b
The VMM must implement replay-resistant authentication mechanisms for network access to non-privileged accounts.
IA-2 - Medium - CCI-001942 - V-207393 - SV-207393r854605_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001942
Version
SRG-OS-000113-VMM-000570
Vuln IDs
  • V-207393
  • V-56987
Rule IDs
  • SV-207393r854605_rule
  • SV-71247
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 non-privileged account is any VMM account with authorizations of a non-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.
Checks: C-7650r365589_chk

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

Fix: F-7650r365590_fix

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

b
The VMM must uniquely identify peripherals before establishing a connection.
IA-3 - Medium - CCI-000778 - V-207394 - SV-207394r378877_rule
RMF Control
IA-3
Severity
M
CCI
CCI-000778
Version
SRG-OS-000114-VMM-000580
Vuln IDs
  • V-207394
  • V-56989
Rule IDs
  • SV-207394r378877_rule
  • SV-71249
Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers, whether physical or virtual.
Checks: C-7651r365592_chk

Verify the VMM uniquely identifies peripherals before establishing a connection. If it does not, this is a finding.

Fix: F-7651r365593_fix

Configure the VMM to uniquely identify peripherals before establishing a connection.

b
The VMM must disable local account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.
IA-4 - Medium - CCI-000795 - V-207395 - SV-207395r378880_rule
RMF Control
IA-4
Severity
M
CCI
CCI-000795
Version
SRG-OS-000118-VMM-000590
Vuln IDs
  • V-207395
  • V-56991
Rule IDs
  • SV-207395r378880_rule
  • SV-71251
Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. VMMs need to track periods of inactivity and disable local account identifiers after 35 days of inactivity.
Checks: C-7652r365595_chk

Verify the VMM disables local account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. If it does not, this is a finding.

Fix: F-7652r365596_fix

Configure the VMM to disable local account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.

b
The VMM must use mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.
IA-7 - Medium - CCI-000803 - V-207396 - SV-207396r378886_rule
RMF Control
IA-7
Severity
M
CCI
CCI-000803
Version
SRG-OS-000120-VMM-000600
Vuln IDs
  • V-207396
  • V-56993
Rule IDs
  • SV-207396r378886_rule
  • SV-71253
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. VMMs utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements.
Checks: C-7653r365598_chk

Verify the VMM uses mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding.

Fix: F-7653r365599_fix

Configure the VMM to use mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.

b
The VMM must support an audit reduction capability that supports on-demand reporting requirements.
AU-7 - Medium - CCI-001876 - V-207397 - SV-207397r854606_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001876
Version
SRG-OS-000122-VMM-000610
Vuln IDs
  • V-207397
  • V-56995
Rule IDs
  • SV-207397r854606_rule
  • SV-71255
The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. The report generation capability provided by the application must support on-demand (i.e., customizable, ad-hoc, and as-needed) reports.
Checks: C-7654r365601_chk

Verify the VMM supports an audit reduction capability that supports on-demand reporting requirements. If it does not, this is a finding.

Fix: F-7654r365602_fix

Configure the VMM to support an audit reduction capability that supports on-demand reporting requirements.

b
The VMM must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.
AC-2 - Medium - CCI-001682 - V-207398 - SV-207398r378895_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001682
Version
SRG-OS-000123-VMM-000620
Vuln IDs
  • V-207398
  • V-56997
Rule IDs
  • SV-207398r378895_rule
  • SV-71257
Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. Emergency accounts are different from infrequently used accounts (i.e., local logon accounts used by the organization's system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.
Checks: C-7655r365604_chk

Verify the VMM is configured such that emergency administrator accounts are automatically removed or disabled after the crisis is resolved or 72 hours. If it is not, this is a finding.

Fix: F-7655r365605_fix

Configure the VMM such that emergency administrator accounts are automatically removed or disabled after the crisis is resolved or 72 hours.

b
The VMM must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.
MA-4 - Medium - CCI-000877 - V-207399 - SV-207399r378958_rule
RMF Control
MA-4
Severity
M
CCI
CCI-000877
Version
SRG-OS-000125-VMM-000630
Vuln IDs
  • V-207399
  • V-56999
Rule IDs
  • SV-207399r378958_rule
  • SV-71259
If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive VMM information, such as system configuration details, diagnostic information, user information, and potentially sensitive application data. Some maintenance and test tools are either standalone devices with their own VMMs or are applications bundled with a VMM. 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. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the VMM or VMM component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric.
Checks: C-7656r365607_chk

Verify the VMM employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. If it does not, this is a finding.

Fix: F-7656r365608_fix

Configure the VMM to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.

b
The VMM must terminate all sessions and network connections when nonlocal maintenance is completed.
MA-4 - Medium - CCI-000879 - V-207400 - SV-207400r378961_rule
RMF Control
MA-4
Severity
M
CCI
CCI-000879
Version
SRG-OS-000126-VMM-000640
Vuln IDs
  • V-207400
  • V-57001
Rule IDs
  • SV-207400r378961_rule
  • SV-71261
If a maintenance session or connection remains open after maintenance is completed, it may be hijacked by an attacker and used to compromise or damage the system. Some maintenance and test tools are either standalone devices with their own VMMs or are applications bundled with a VMM. 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. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the VMM or VMM component and not communicating across a network connection.
Checks: C-7657r365610_chk

Verify the VMM terminates all sessions and network connections when nonlocal maintenance is completed. If it does not, this is a finding.

Fix: F-7657r365611_fix

Configure the VMM to terminate all sessions and network connections when nonlocal maintenance is completed.

b
The VMM must separate user functionality (including user interface services) from VMM management functionality.
SC-2 - Medium - CCI-001082 - V-207401 - SV-207401r378967_rule
RMF Control
SC-2
Severity
M
CCI
CCI-001082
Version
SRG-OS-000132-VMM-000650
Vuln IDs
  • V-207401
  • V-57003
Rule IDs
  • SV-207401r378967_rule
  • SV-71263
VMM management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access VMM management functionality capabilities increases the risk that non-privileged users may obtain elevated privileges. VMM management functionality includes functions necessary to administer console, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from VMM management functionality is either physical or logical and is accomplished by using different guest VMs, different computers, different central processing units, different instances of the VMM, different network addresses, different TCP/UDP ports, other virtualization techniques, combinations of these methods, or other methods, as appropriate.
Checks: C-7658r365613_chk

Verify the VMM separates user functionality (including user interface services) from VMM management functionality. If it does not, this is a finding.

Fix: F-7658r365614_fix

Configure the VMM to separate user functionality (including user interface services) from VMM management functionality.

b
The VMM must isolate security functions from non-security functions.
SC-3 - Medium - CCI-001084 - V-207402 - SV-207402r378973_rule
RMF Control
SC-3
Severity
M
CCI
CCI-001084
Version
SRG-OS-000134-VMM-000660
Vuln IDs
  • V-207402
  • V-57005
Rule IDs
  • SV-207402r378973_rule
  • SV-71265
An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, and/or firmware of the VMM responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. VMMs implement code separation (i.e., separation of security functions from non-security functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code. Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of guest VMs, memory space, and libraries. VMMs restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.
Checks: C-7659r365616_chk

Verify the VMM isolates security functions from non-security functions. If it does not, this is a finding.

Fix: F-7659r365617_fix

Configure the VMM to isolate security functions from non-security functions.

b
The VMM must prevent unauthorized and unintended information transfer via shared system resources.
SC-4 - Medium - CCI-001090 - V-207403 - SV-207403r378982_rule
RMF Control
SC-4
Severity
M
CCI
CCI-001090
Version
SRG-OS-000138-VMM-000670
Vuln IDs
  • V-207403
  • V-57007
Rule IDs
  • SV-207403r378982_rule
  • SV-71267
Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to the VMM. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular VMM components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies. There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific VMM components.
Checks: C-7660r365619_chk

Verify the VMM prevents unauthorized and unintended information transfer via shared system resources. If it does not, this is a finding.

Fix: F-7660r365620_fix

Configure the VMM to prevent unauthorized and unintended information transfer via shared system resources.

b
The VMM must manage excess capacity, bandwidth, or other redundancy to limit the effects of information-flooding types of Denial of Service (DoS) attacks.
SC-5 - Medium - CCI-001095 - V-207404 - SV-207404r378988_rule
RMF Control
SC-5
Severity
M
CCI
CCI-001095
Version
SRG-OS-000142-VMM-000690
Vuln IDs
  • V-207404
  • V-57009
Rule IDs
  • SV-207404r378988_rule
  • SV-71269
DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning.
Checks: C-7661r365622_chk

Verify the VMM manages excess capacity, bandwidth, or other redundancy to limit the effects of information-flooding types of Denial of Service (DoS) attacks. If it does not, this is a finding.

Fix: F-7661r365623_fix

Configure the VMM to manage excess capacity, bandwidth, or other redundancy to limit the effects of information-flooding types of Denial of Service (DoS) attacks.

b
The VMM must terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements.
SC-10 - Medium - CCI-001133 - V-207405 - SV-207405r878140_rule
RMF Control
SC-10
Severity
M
CCI
CCI-001133
Version
SRG-OS-000163-VMM-000700
Vuln IDs
  • V-207405
  • V-57011
Rule IDs
  • SV-207405r878140_rule
  • SV-71271
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the VMM. Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the VMM level, and de-allocating networking assignments at the application level if multiple application sessions are using a single, VMM-level network connection. This does not mean that the VMM terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
Checks: C-7662r365625_chk

Verify the VMM terminates all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements. If it does not, this is a finding.

Fix: F-7662r365626_fix

Configure the VMM to terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements.

b
The VMM must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
SC-24 - Medium - CCI-001190 - V-207406 - SV-207406r379081_rule
RMF Control
SC-24
Severity
M
CCI
CCI-001190
Version
SRG-OS-000184-VMM-000710
Vuln IDs
  • V-207406
  • V-57013
Rule IDs
  • SV-207406r379081_rule
  • SV-71273
Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. VMMs that fail suddenly and with no incorporated failure state planning may leave the system available but with a reduced security protection capability. Preserving VMM state information also facilitates system restart and return to the operational mode of the organization with less disruption to mission-essential processes. Abort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations.
Checks: C-7663r365628_chk

Verify the VMM fails to a secure state if system initialization fails, shutdown fails, or aborts fail. If it does not, this is a finding.

Fix: F-7663r365629_fix

Configure the VMM to fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

b
The VMM must protect the confidentiality and integrity of all information at rest.
SC-28 - Medium - CCI-001199 - V-207407 - SV-207407r379084_rule
RMF Control
SC-28
Severity
M
CCI
CCI-001199
Version
SRG-OS-000185-VMM-000720
Vuln IDs
  • V-207407
  • V-57015
Rule IDs
  • SV-207407r379084_rule
  • SV-71275
Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within a VMM. This requirement addresses protection of user-generated data, as well as VMM-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.
Checks: C-7664r365631_chk

Verify the VMM protects the confidentiality and integrity of all information at rest. If it does not, this is a finding.

Fix: F-7664r365632_fix

Configure the VMM to protect the confidentiality and integrity of all information at rest.

b
The VMM must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).
SI-2 - Medium - CCI-001233 - V-207408 - SV-207408r878139_rule
RMF Control
SI-2
Severity
M
CCI
CCI-001233
Version
SRG-OS-000191-VMM-000730
Vuln IDs
  • V-207408
  • V-57017
Rule IDs
  • SV-207408r878139_rule
  • SV-71277
Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the VMM or other system components may remain vulnerable to the exploits presented by undetected software flaws. To support this requirement, the VMM may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools, as specified in the requirement.
Checks: C-7665r365634_chk

Verify the VMM employs automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). If it does not, this is a finding.

Fix: F-7665r365635_fix

Configure the VMM to employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).

b
The VMM must check the validity of all data inputs except those specifically identified by the organization.
SI-10 - Medium - CCI-001310 - V-207409 - SV-207409r379102_rule
RMF Control
SI-10
Severity
M
CCI
CCI-001310
Version
SRG-OS-000203-VMM-000750
Vuln IDs
  • V-207409
  • V-57019
Rule IDs
  • SV-207409r379102_rule
  • SV-71279
Invalid user input occurs when a user inserts data or characters into data entry fields and the VMM is unprepared to process that data. This results in unanticipated VMM behavior, potentially leading to a compromise. Invalid input is one of the primary methods employed when attempting to compromise a VMM. Checking the valid syntax and semantics of VMM inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software typically follows well-defined protocols that use structured messages (i.e., commands or queries) to communicate among guest VMs, software modules, or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If the VMM uses attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the guest VM, module, or component that receives the tainted output will perform the wrong operations or otherwise interpret the data incorrectly. Pre-screening inputs prior to passing to interpreters prevents the content from being unintentionally interpreted as commands. Input validation helps to ensure accurate and correct inputs and prevent attacks.
Checks: C-7666r365637_chk

Verify the VMM checks the validity of all data inputs except those specifically identified by the organization. If it does not, this is a finding.

Fix: F-7666r365638_fix

Configure the VMM to check the validity of all data inputs except those specifically identified by the organization.

b
The VMM must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
SI-11 - Medium - CCI-001312 - V-207410 - SV-207410r379105_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001312
Version
SRG-OS-000205-VMM-000760
Vuln IDs
  • V-207410
  • V-57021
Rule IDs
  • SV-207410r379105_rule
  • SV-71281
Any VMM providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization. Organizations carefully consider the structure/content of error messages. The extent to which VMMs are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers.
Checks: C-7667r365640_chk

Verify the VMM generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. If it does not, this is a finding.

Fix: F-7667r365641_fix

Configure the VMM to generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

b
The VMM must reveal system error messages only to authorized users.
SI-11 - Medium - CCI-001314 - V-207411 - SV-207411r379108_rule
RMF Control
SI-11
Severity
M
CCI
CCI-001314
Version
SRG-OS-000206-VMM-000770
Vuln IDs
  • V-207411
  • V-57023
Rule IDs
  • SV-207411r379108_rule
  • SV-71283
Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the VMM or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the VMM is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Checks: C-7668r365643_chk

Verify the VMM reveals system error messages only to authorized users. If it does not, this is a finding.

Fix: F-7668r365644_fix

Configure the VMM to reveal system error messages only to authorized users.

b
All interactions among guest VMs must be mediated by the VMM or its service VMs to support proper function.
AC-4 - Medium - CCI-001368 - V-207412 - SV-207412r379126_rule
RMF Control
AC-4
Severity
M
CCI
CCI-001368
Version
SRG-OS-000221-VMM-000800
Vuln IDs
  • V-207412
  • V-57025
Rule IDs
  • SV-207412r379126_rule
  • SV-71285
Mechanisms to detect and prevent unauthorized communication flow must be configured or provided as part of the VMM design. If information flow control is not enforced based on proper functioning of the VMM and its service, helper, and guest VMs, the VMM may become compromised. Information flow control regulates where information is allowed to travel within a VMM. The flow of all system information must be monitored and controlled so it does not introduce any unacceptable risk to the VMM, its guest VMs, or data.
Checks: C-7669r365646_chk

Verify all interactions among guest VMs are mediated by the VMM or its service VMs to support proper function. If they are not, this is a finding.

Fix: F-7669r365647_fix

Configure all interactions among guest VMs to be mediated by the VMM or its service VMs to support proper function.

b
The VMM must automatically audit account modification.
AC-2 - Medium - CCI-001403 - V-207413 - SV-207413r379204_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001403
Version
SRG-OS-000239-VMM-000810
Vuln IDs
  • V-207413
  • V-57027
Rule IDs
  • SV-207413r379204_rule
  • SV-71287
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify an existing account. Auditing account modification actions provides logging that can be used for forensic purposes. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7670r365649_chk

Verify the VMM automatically audits account modification. If it does not, this is a finding.

Fix: F-7670r365650_fix

Configure the VMM to automatically audit account modification.

b
The VMM must automatically audit account disabling actions.
AC-2 - Medium - CCI-001404 - V-207414 - SV-207414r379207_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001404
Version
SRG-OS-000240-VMM-000820
Vuln IDs
  • V-207414
  • V-57029
Rule IDs
  • SV-207414r379207_rule
  • SV-71289
When VMM accounts are disabled, user accessibility is affected. Once an attacker establishes access to a system, the attacker often attempts to disable authorized accounts to disrupt services or prevent the implementation of countermeasures. Auditing account disabling actions provides logging that can be used for forensic purposes. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7671r365652_chk

Verify the VMM automatically audits account disabling actions. If it does not, this is a finding.

Fix: F-7671r365653_fix

Configure the VMM to automatically audit account disabling actions.

b
The VMM must automatically audit account removal actions.
AC-2 - Medium - CCI-001405 - V-207415 - SV-207415r379210_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001405
Version
SRG-OS-000241-VMM-000830
Vuln IDs
  • V-207415
  • V-57031
Rule IDs
  • SV-207415r379210_rule
  • SV-71291
When VMM accounts are removed, user accessibility is affected. Once an attacker establishes access to a system, the attacker often attempts to disable authorized accounts to disrupt services or prevent the implementation of countermeasures. Auditing account removal actions provides logging that can be used for forensic purposes. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7672r365655_chk

Verify the VMM automatically audits account removal actions. If it does not, this is a finding.

Fix: F-7672r365656_fix

Configure the VMM to automatically audit account removal actions.

b
All guest VM network communications must be implemented through use of virtual network devices provisioned by the VMM.
AC-4 - Medium - CCI-001414 - V-207416 - SV-207416r379213_rule
RMF Control
AC-4
Severity
M
CCI
CCI-001414
Version
SRG-OS-000242-VMM-000840
Vuln IDs
  • V-207416
  • V-57033
Rule IDs
  • SV-207416r379213_rule
  • SV-71293
Mechanisms to detect and prevent unauthorized communication flow must be configured or provided as part of the VMM design. If information flow control is not enforced based on proper functioning of the VMM and its service, helper, and guest VMs, the VMM may become compromised. Information flow control regulates where information is allowed to travel between a VMM (and its guest VMs) and external systems. In some cases, the VMM may delegate interface device management to a service VM, but the VMM still maintains control of all information flows. The flow of all system information must be monitored and controlled so it does not introduce any unacceptable risk to the VMM, its guest VMs, or data.
Checks: C-7673r365658_chk

Verify all guest VM network communications are implemented through use of virtual network devices provisioned by the VMM. If they are not, this is a finding.

Fix: F-7673r365659_fix

Configure all guest VM network communications to be implemented through use of virtual network devices provisioned by the VMM.

b
All interactions between guest VMs and external systems, via other interface devices, must be mediated by the VMM or its service VMs.
AC-4 - Medium - CCI-001414 - V-207417 - SV-207417r379213_rule
RMF Control
AC-4
Severity
M
CCI
CCI-001414
Version
SRG-OS-000242-VMM-000850
Vuln IDs
  • V-207417
  • V-57035
Rule IDs
  • SV-207417r379213_rule
  • SV-71295
Mechanisms to detect and prevent unauthorized communication flow must be configured or provided as part of the VMM design. If information flow control is not enforced based on proper functioning of the VMM and its service and helper VMs, the VMM may become compromised. Information flow control regulates where information is allowed to travel between a VMM (and its guest VMs) and external systems. In some cases, the VMM may delegate interface device management to a service VM, but the VMM still maintains control of all information flows. The flow of all system information must be monitored and controlled so it does not introduce any unacceptable risk to the VMM, its guest VMs, or data.
Checks: C-7674r365661_chk

Verify all interactions between guest VMs and external systems, via other interface devices, are mediated by the VMM or its service VMs. If they are not, this is a finding.

Fix: F-7674r365662_fix

Configure all interactions between guest VMs and external systems, via other interface devices, are mediated by the VMM or its service VMs.

b
The VMM must implement cryptography to protect the integrity of remote access sessions.
AC-17 - Medium - CCI-001453 - V-207418 - SV-207418r379225_rule
RMF Control
AC-17
Severity
M
CCI
CCI-001453
Version
SRG-OS-000250-VMM-000860
Vuln IDs
  • V-207418
  • V-57037
Rule IDs
  • SV-207418r379225_rule
  • SV-71297
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Remote access (e.g., RDP) is access to DoD nonpublic VMMs by an authorized user (or another VMM) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.
Checks: C-7675r365664_chk

Verify the VMM implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding.

Fix: F-7675r365665_fix

Configure the VMM to implement cryptography to protect the integrity of remote access sessions.

b
The VMM must initiate session audits at system startup.
AU-14 - Medium - CCI-001464 - V-207419 - SV-207419r379231_rule
RMF Control
AU-14
Severity
M
CCI
CCI-001464
Version
SRG-OS-000254-VMM-000880
Vuln IDs
  • V-207419
  • V-57039
Rule IDs
  • SV-207419r379231_rule
  • SV-71299
If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.
Checks: C-7676r365667_chk

Verify the VMM initiates session audits at system startup. If it does not, this is a finding.

Fix: F-7676r365668_fix

Configure the VMM to initiate session audits at system startup.

b
The VMM must produce audit records containing information to establish the identity of any individual or process associated with the event.
AU-3 - Medium - CCI-001487 - V-207420 - SV-207420r379234_rule
RMF Control
AU-3
Severity
M
CCI
CCI-001487
Version
SRG-OS-000255-VMM-000890
Vuln IDs
  • V-207420
  • V-57041
Rule IDs
  • SV-207420r379234_rule
  • SV-71301
Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event.
Checks: C-7677r365670_chk

Verify the VMM produces audit records containing information to establish the identity of any individual or process associated with the event. If it does not, this is a finding.

Fix: F-7677r365671_fix

Configure the VMM to produce audit records containing information to establish the identity of any individual or process associated with the event.

b
The VMM must protect audit tools from unauthorized access.
AU-9 - Medium - CCI-001493 - V-207421 - SV-207421r379237_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001493
Version
SRG-OS-000256-VMM-000900
Vuln IDs
  • V-207421
  • V-57043
Rule IDs
  • SV-207421r379237_rule
  • SV-71303
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. VMMs providing tools to interface with audit data will leverage roles identifying the user accessing the tools and permissions identifying the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit VMM activity and records. Audit tools include custom queries and report generators.
Checks: C-7678r365673_chk

Verify the VMM protects audit tools from unauthorized access. If it does not, this is a finding.

Fix: F-7678r365674_fix

Configure the VMM to protect audit tools from unauthorized access.

b
The VMM must protect audit tools from unauthorized modification.
AU-9 - Medium - CCI-001494 - V-207422 - SV-207422r379240_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001494
Version
SRG-OS-000257-VMM-000910
Vuln IDs
  • V-207422
  • V-57045
Rule IDs
  • SV-207422r379240_rule
  • SV-71305
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. VMMs providing tools to interface with audit data will leverage roles identifying the user accessing the tools and permissions identifying the corresponding rights the user is assigned in order to make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit VMM activity and records. Audit tools include custom queries and report generators.
Checks: C-7679r365676_chk

Verify the VMM protects audit tools from unauthorized modification. If it does not, this is a finding.

Fix: F-7679r365677_fix

Configure the VMM to protect audit tools from unauthorized modification.

b
The VMM must protect audit tools from unauthorized deletion.
AU-9 - Medium - CCI-001495 - V-207423 - SV-207423r379243_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001495
Version
SRG-OS-000258-VMM-000920
Vuln IDs
  • V-207423
  • V-57047
Rule IDs
  • SV-207423r379243_rule
  • SV-71307
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. VMMs providing tools to interface with audit data will leverage roles identifying the user accessing the tools and permissions identifying the corresponding rights the user is assigned in order to make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit VMM activity and records. Audit tools include custom queries and report generators.
Checks: C-7680r365679_chk

Verify the VMM protects audits tools from unauthorized deletion. If it does not, this is a finding.

Fix: F-7680r365680_fix

Configure the VMM to protect audit tools from unauthorized deletion.

b
The VMM must limit privileges to change software resident within software libraries.
CM-5 - Medium - CCI-001499 - V-207424 - SV-207424r379246_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
SRG-OS-000259-VMM-000930
Vuln IDs
  • V-207424
  • V-57049
Rule IDs
  • SV-207424r379246_rule
  • SV-71309
If the VMM were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. This requirement applies to VMMs with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to VMM components for the purpose of initiating changes, including upgrades and modifications.
Checks: C-7681r365682_chk

Verify the VMM limits privileges to change software resident within software libraries. If it does not, this is a finding.

Fix: F-7681r365683_fix

Configure the VMM to limit privileges to change software resident within software libraries.

b
The VMM must enforce password complexity by requiring that at least one special character be used.
IA-5 - Medium - CCI-001619 - V-207425 - SV-207425r379249_rule
RMF Control
IA-5
Severity
M
CCI
CCI-001619
Version
SRG-OS-000266-VMM-000940
Vuln IDs
  • V-207425
  • V-57051
Rule IDs
  • SV-207425r379249_rule
  • SV-71311
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Special characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.
Checks: C-7682r365685_chk

Verify the VMM enforces password complexity by requiring that at least one special character be used. If it does not, this is a finding.

Fix: F-7682r365686_fix

Configure the VMM to enforce password complexity by requiring that at least one special character be used.

b
In the event of a system failure, the VMM must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
SC-24 - Medium - CCI-001665 - V-207426 - SV-207426r379318_rule
RMF Control
SC-24
Severity
M
CCI
CCI-001665
Version
SRG-OS-000269-VMM-000950
Vuln IDs
  • V-207426
  • V-57053
Rule IDs
  • SV-207426r379318_rule
  • SV-71313
Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the VMM or a component of the system. Preserving VMM state information helps to facilitate VMM restart and return to the operational mode of the organization with less disruption of mission/business processes.
Checks: C-7683r365688_chk

Verify the VMM preserves any information necessary, in the event of a system failure, to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. If it does not, this is a finding.

Fix: F-7683r365689_fix

Configure the VMM to preserve any information necessary, in the event of a system failure, to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.

b
The VMM must notify system administrators and ISSOs when accounts are created.
AC-2 - Medium - CCI-001683 - V-207427 - SV-207427r379321_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001683
Version
SRG-OS-000274-VMM-000960
Vuln IDs
  • V-207427
  • V-57055
Rule IDs
  • SV-207427r379321_rule
  • SV-71315
Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the creation of VMM user accounts and notifies the system administrator and ISSO that it exists. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7684r365691_chk

Verify the VMM notifies system administrators and ISSOs when accounts are created. If it does not, this is a finding.

Fix: F-7684r365692_fix

Configure the VMM to notify system administrators and ISSOs when accounts are created.

b
The VMM must notify the system administrator and ISSO when accounts are modified.
AC-2 - Medium - CCI-001684 - V-207428 - SV-207428r379324_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001684
Version
SRG-OS-000275-VMM-000970
Vuln IDs
  • V-207428
  • V-57057
Rule IDs
  • SV-207428r379324_rule
  • SV-71317
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply modify an existing account. Notification of account modification is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail that documents the creation of VMM user accounts and notifies the system administrator and ISSO that it exists. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7685r365694_chk

Verify the VMM notifies the system administrator and ISSO when accounts are modified. If it does not, this is a finding.

Fix: F-7685r365695_fix

Configure the VMM to notify the system administrator and ISSO when accounts are modified.

b
The VMM must notify the system administrator and ISSO when accounts are disabled.
AC-2 - Medium - CCI-001685 - V-207429 - SV-207429r379327_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001685
Version
SRG-OS-000276-VMM-000980
Vuln IDs
  • V-207429
  • V-57059
Rule IDs
  • SV-207429r379327_rule
  • SV-71319
When VMM accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual VMM users or for identifying the VMM processes themselves. Sending notification of account disabling events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that VMM accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7686r365697_chk

Verify the VMM notifies the system administrator and ISSO when accounts are disabled. If it does not, this is a finding.

Fix: F-7686r365698_fix

Configure the VMM to notify the system administrator and ISSO when accounts are disabled.

b
The VMM must notify the system administrator and ISSO when accounts are removed.
AC-2 - Medium - CCI-001686 - V-207430 - SV-207430r379330_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001686
Version
SRG-OS-000277-VMM-000990
Vuln IDs
  • V-207430
  • V-57061
Rule IDs
  • SV-207430r379330_rule
  • SV-71321
When VMM accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual VMM users or for identifying the VMM processes themselves. Sending notification of account removal events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that VMM accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7687r365700_chk

Verify the VMM notifies the system administrator and ISSO when accounts are removed. If it does not, this is a finding.

Fix: F-7687r365701_fix

Configure the VMM to notify the system administrator and ISSO when accounts are removed.

b
The VMM must use cryptographic mechanisms to protect the integrity of audit tools.
AU-9 - Medium - CCI-001496 - V-207431 - SV-207431r379333_rule
RMF Control
AU-9
Severity
M
CCI
CCI-001496
Version
SRG-OS-000278-VMM-001000
Vuln IDs
  • V-207431
  • V-57063
Rule IDs
  • SV-207431r379333_rule
  • SV-71323
Protecting the integrity of the tools used for auditing purposes is a critical step towards ensuring the integrity of audit data. Audit data includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit VMM activity. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit VMM activity and records. Audit tools include custom queries and report generators. It is not uncommon for attackers to replace the audit tools or inject code into the existing tools for the purpose of providing the capability to hide or erase system activity from the audit logs. To address this risk, audit tools must be cryptographically signed in order to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files.
Checks: C-7688r365703_chk

Verify the VMM uses cryptographic mechanisms to protect the integrity of audit tools. If it does not, this is a finding.

Fix: F-7688r365704_fix

Configure the VMM to use cryptographic mechanisms to protect the integrity of audit tools.

b
The VMM must automatically terminate a user session after inactivity timeouts have expired or at shutdown.
AC-12 - Medium - CCI-002361 - V-207432 - SV-207432r854607_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002361
Version
SRG-OS-000279-VMM-001010
Vuln IDs
  • V-207432
  • V-57065
Rule IDs
  • SV-207432r854607_rule
  • SV-71325
Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses a VMM. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated.
Checks: C-7689r365706_chk

Verify the VMM automatically terminates a user session after inactivity timeouts have expired or at shutdown. If it does not, this is a finding.

Fix: F-7689r365707_fix

Configure the VMM to automatically terminate a user session after inactivity timeouts have expired or at shutdown.

b
VMMs requiring user access authentication must provide a logout capability for user-initiated communications sessions.
AC-12 - Medium - CCI-002363 - V-207433 - SV-207433r854608_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002363
Version
SRG-OS-000280-VMM-001020
Vuln IDs
  • V-207433
  • V-57067
Rule IDs
  • SV-207433r854608_rule
  • SV-71327
If a user cannot explicitly end a VMM session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Information resources to which users gain access via authentication include, for example, local workstations and remote services. For some types of interactive sessions, including, for example, remote login, VMMs typically send logout messages as final messages prior to terminating sessions.
Checks: C-7690r365709_chk

Verify VMMs requiring user access authentication provide a logout capability for user-initiated communications sessions. If they do not, this is a finding.

Fix: F-7690r365710_fix

Configure VMMs requiring user access authentication to provide a logout capability for user-initiated communications sessions.

b
The VMM must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions.
AC-12 - Medium - CCI-002364 - V-207434 - SV-207434r854609_rule
RMF Control
AC-12
Severity
M
CCI
CCI-002364
Version
SRG-OS-000281-VMM-001030
Vuln IDs
  • V-207434
  • V-57069
Rule IDs
  • SV-207434r854609_rule
  • SV-71329
If a user cannot explicitly end a VMM session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Users need to be aware of whether or not the session has been terminated. Information resources to which users gain access via authentication include, for example, local workstations and remote services. Logout messages can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions, including, for example, remote login, VMMs typically send logout messages as final messages prior to terminating sessions.
Checks: C-7691r365712_chk

Verify the VMM displays an explicit logout message to users indicating the reliable termination of authenticated communications sessions. If it does not, this is a finding.

Fix: F-7691r365713_fix

Configure the VMM to display an explicit logout message to users indicating the reliable termination of authenticated communications sessions.

b
The VMM must control remote access methods.
AC-17 - Medium - CCI-002314 - V-207435 - SV-207435r854610_rule
RMF Control
AC-17
Severity
M
CCI
CCI-002314
Version
SRG-OS-000297-VMM-001040
Vuln IDs
  • V-207435
  • V-57071
Rule IDs
  • SV-207435r854610_rule
  • SV-71331
Remote access services, such as those providing remote access to network devices and VMMs, which lack automated control capabilities, increase risk and make remote user access management difficult at best. Remote access is access to DoD nonpublic VMMs by an authorized user (or another VMM) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. VMM functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of VMM components (e.g., servers, workstations, notebook computers, smart phones, and tablets).
Checks: C-7692r365715_chk

Verify the VMM controls remote access methods. If it does not, this is a finding.

Fix: F-7692r365716_fix

Configure the VMM to control remote access methods.

b
The VMM must provide the capability to immediately disconnect or disable remote access to the information system.
AC-17 - Medium - CCI-002322 - V-207436 - SV-207436r854611_rule
RMF Control
AC-17
Severity
M
CCI
CCI-002322
Version
SRG-OS-000298-VMM-001050
Vuln IDs
  • V-207436
  • V-57073
Rule IDs
  • SV-207436r854611_rule
  • SV-71333
Without the ability to immediately disconnect or disable remote access, an attack or other compromise taking place would not be immediately stopped. VMM remote access functionality must have the capability to immediately disconnect current users remotely accessing the VMM and/or disable further remote access. The speed of disconnect or disablement varies based on the criticality of missions functions and the need to eliminate immediate or future remote access to organizational VMMs. The remote access functionality (e.g., RDP) may implement features, such as automatic disconnect (or user-initiated disconnect), in case of adverse information based on an indicator of compromise or attack.
Checks: C-7693r365718_chk

Verify the VMM provides the capability to immediately disconnect or disable remote access to the information system. If it does not, this is a finding.

Fix: F-7693r365719_fix

Configure the VMM to provide the capability to immediately disconnect or disable remote access to the information system.

b
The VMM must protect wireless access to the system using encryption.
AC-18 - Medium - CCI-001444 - V-207437 - SV-207437r379456_rule
RMF Control
AC-18
Severity
M
CCI
CCI-001444
Version
SRG-OS-000299-VMM-001060
Vuln IDs
  • V-207437
  • V-57075
Rule IDs
  • SV-207437r379456_rule
  • SV-71335
Allowing devices and users to connect to the system without first authenticating them allows untrusted access and can lead to a compromise or attack. Since wireless communications can be intercepted, it is necessary to use encryption to protect the confidentiality of information in transit. Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication. This requirement applies to those VMMs that control wireless devices.
Checks: C-7694r365721_chk

Verify the VMM protects wireless access to the system using encryption. If it does not, this is a finding.

Fix: F-7694r365722_fix

Configure the VMM to protect wireless access to the system using encryption.

b
The VMM must protect wireless access to the system using authentication of users and/or devices.
AC-18 - Medium - CCI-001443 - V-207438 - SV-207438r379459_rule
RMF Control
AC-18
Severity
M
CCI
CCI-001443
Version
SRG-OS-000300-VMM-001070
Vuln IDs
  • V-207438
  • V-57077
Rule IDs
  • SV-207438r379459_rule
  • SV-71337
Allowing devices and users to connect to the system without first authenticating them allows untrusted access and can lead to a compromise or attack. Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication. This requirement applies to those VMMs that control wireless devices.
Checks: C-7695r365724_chk

Verify the VMM protects wireless access to the system using authentication of users and/or devices. If it does not, this is a finding.

Fix: F-7695r365725_fix

Configure the VMM to protect wireless access to the system using authentication of users and/or devices.

b
The VMM must automatically audit account enabling actions.
AC-2 - Medium - CCI-002130 - V-207439 - SV-207439r854612_rule
RMF Control
AC-2
Severity
M
CCI
CCI-002130
Version
SRG-OS-000303-VMM-001090
Vuln IDs
  • V-207439
  • V-57079
Rule IDs
  • SV-207439r854612_rule
  • SV-71339
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account enabling is one method for mitigating this risk. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7696r365727_chk

Verify the VMM automatically audits account enabling actions. If it does not, this is a finding.

Fix: F-7696r365728_fix

Configure the VMM to automatically audit account enabling actions.

b
The VMM must notify the system administrator and ISSO of account enabling actions.
AC-2 - Medium - CCI-002132 - V-207440 - SV-207440r854613_rule
RMF Control
AC-2
Severity
M
CCI
CCI-002132
Version
SRG-OS-000304-VMM-001100
Vuln IDs
  • V-207440
  • V-57081
Rule IDs
  • SV-207440r854613_rule
  • SV-71341
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Sending notification of account enabling events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that VMM accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. In order to detect and respond to events that affect user accessibility and application processing, VMMs must audit account enabling actions and, as required, notify the appropriate individuals so they can investigate the event. To address access requirements, many VMMs can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-7697r365730_chk

Verify the VMM notifies the system administrator and ISSO of account enabling actions. If it does not, this is a finding.

Fix: F-7697r365731_fix

Configure the VMM to notify the system administrator and ISSO of account enabling actions.

b
The VMM must implement discretionary access controls to allow VMM admins to pass information to any other VMM admin, user, or guest VM.
AC-3 - Medium - CCI-002165 - V-207441 - SV-207441r854614_rule
RMF Control
AC-3
Severity
M
CCI
CCI-002165
Version
SRG-OS-000312-VMM-001110
Vuln IDs
  • V-207441
  • V-57083
Rule IDs
  • SV-207441r854614_rule
  • SV-71343
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the VMM boundary. Once the information is passed outside of the control of the VMM, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
Checks: C-7698r365733_chk

Verify the VMM implements discretionary access controls to allow VMM admins to pass information to any other VMM admin, user, or guest VM. If it does not, this is a finding.

Fix: F-7698r365734_fix

Configure the VMM to implement discretionary access controls to allow VMM admins to pass information to any other VMM admin, user, or guest VM.

b
The VMM must implement discretionary access controls to allow VMM admins to grant their privileges to other VMM admins.
AC-3 - Medium - CCI-002165 - V-207442 - SV-207442r854615_rule
RMF Control
AC-3
Severity
M
CCI
CCI-002165
Version
SRG-OS-000312-VMM-001120
Vuln IDs
  • V-207442
  • V-57085
Rule IDs
  • SV-207442r854615_rule
  • SV-71345
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the VMM boundary. Once the information is passed outside of the control of the VMM, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
Checks: C-7699r365736_chk

Verify the VMM implements discretionary access controls to allow VMM admins to grant their privileges to other VMM admins. If it does not, this is a finding.

Fix: F-7699r365737_fix

Configure the VMM to implement discretionary access controls to allow VMM admins to grant their privileges to other VMM admins.

b
The VMM must implement discretionary access controls to allow VMM admins to change security attributes on users, guest VMs, the VMM, or the VMMs components.
AC-3 - Medium - CCI-002165 - V-207443 - SV-207443r854616_rule
RMF Control
AC-3
Severity
M
CCI
CCI-002165
Version
SRG-OS-000312-VMM-001130
Vuln IDs
  • V-207443
  • V-57087
Rule IDs
  • SV-207443r854616_rule
  • SV-71347
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the VMM boundary. Once the information is passed outside of the control of the VMM, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
Checks: C-7700r365739_chk

Verify the VMM implements discretionary access controls to allow VMM admins to change security attributes on users, guest VMs, the VMM, or the VMM's components. If it does not, this is a finding.

Fix: F-7700r365740_fix

Configure the VMM to implement discretionary access controls to allow VMM admins to change security attributes on users, guest VMs, the VMM, or the VMM's components.

b
The VMM must implement discretionary access controls to allow VMM admins to choose the security attributes to be associated with newly created or revised guest VMs.
AC-3 - Medium - CCI-002165 - V-207444 - SV-207444r854617_rule
RMF Control
AC-3
Severity
M
CCI
CCI-002165
Version
SRG-OS-000312-VMM-001140
Vuln IDs
  • V-207444
  • V-57089
Rule IDs
  • SV-207444r854617_rule
  • SV-71349
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the VMM boundary. Once the information is passed outside of the control of the VMM, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
Checks: C-7701r365742_chk

Verify the VMM implements discretionary access controls to allow VMM admins to choose the security attributes to be associated with newly created or revised guest VMs. If it does not, this is a finding.

Fix: F-7701r365743_fix

Configure the VMM to implement discretionary access controls to allow VMM admins to choose the security attributes to be associated with newly created or revised guest VMs.

b
The VMM must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
AC-6 - Medium - CCI-002235 - V-207445 - SV-207445r854618_rule
RMF Control
AC-6
Severity
M
CCI
CCI-002235
Version
SRG-OS-000324-VMM-001150
Vuln IDs
  • V-207445
  • V-57091
Rule IDs
  • SV-207445r854618_rule
  • SV-71351
Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.
Checks: C-7702r365745_chk

Verify the VMM prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding.

Fix: F-7702r365746_fix

Configure the VMM to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.

b
The VMM must prevent all software from executing at higher privilege levels than users executing the software.
AC-6 - Medium - CCI-002233 - V-207446 - SV-207446r854619_rule
RMF Control
AC-6
Severity
M
CCI
CCI-002233
Version
SRG-OS-000326-VMM-001160
Vuln IDs
  • V-207446
  • V-57093
Rule IDs
  • SV-207446r854619_rule
  • SV-71353
In certain situations, guest VMs, applications, and programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to VMM users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. Some guest VMs, applications, programs, and processes are required to operate at a higher privilege level and therefore should be excluded from this restriction after review.
Checks: C-7703r365748_chk

Verify the VMM prevents all software from executing at higher privilege levels than users executing the software. If it does not, this is a finding.

Fix: F-7703r365749_fix

Configure the VMM to prevent all software from executing at higher privilege levels than users executing the software.

b
The VMM must audit the execution of privileged functions.
AC-6 - Medium - CCI-002234 - V-207447 - SV-207447r854620_rule
RMF Control
AC-6
Severity
M
CCI
CCI-002234
Version
SRG-OS-000327-VMM-001170
Vuln IDs
  • V-207447
  • V-57095
Rule IDs
  • SV-207447r854620_rule
  • SV-71355
Misuse of privileged functions, either intentionally or unintentionally, by authorized users, or by unauthorized external entities that have compromised VMM accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.
Checks: C-7704r365751_chk

Verify the VMM audits the execution of privileged functions. If it does not, this is a finding.

Fix: F-7704r365752_fix

Configure the VMM to audit the execution of privileged functions.

b
The VMM must automatically lock an account until the locked account is released by an administrator, when three unsuccessful logon attempts in 15 minutes are made.
AC-7 - Medium - CCI-002238 - V-207448 - SV-207448r854621_rule
RMF Control
AC-7
Severity
M
CCI
CCI-002238
Version
SRG-OS-000329-VMM-001180
Vuln IDs
  • V-207448
  • V-57097
Rule IDs
  • SV-207448r854621_rule
  • SV-71357
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.
Checks: C-7705r365754_chk

Verify the VMM automatically locks an account until the locked account is released by an administrator, when three unsuccessful logon attempts in 15 minutes are made. If it does not, this is a finding.

Fix: F-7705r365755_fix

Configure the VMM to automatically lock an account until the locked account is released by an administrator, when three unsuccessful logon attempts in 15 minutes are made.

b
The VMM must provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all VMM components, based on all selectable event criteria in near real time.
AU-12 - Medium - CCI-001914 - V-207449 - SV-207449r877036_rule
RMF Control
AU-12
Severity
M
CCI
CCI-001914
Version
SRG-OS-000337-VMM-001190
Vuln IDs
  • V-207449
  • V-57099
Rule IDs
  • SV-207449r877036_rule
  • SV-71359
If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost. This requirement enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve VMM resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting.
Checks: C-7706r365757_chk

Verify the VMM provides the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all VMM components, based on all selectable event criteria in near real time. If it does not, this is a finding.

Fix: F-7706r365758_fix

Configure the VMM to provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all VMM components, based on all selectable event criteria in near real time.

b
The VMM must allocate audit record storage capacity to store at least one weeks worth of audit records when audit records are not immediately sent to a central audit record storage facility.
AU-4 - Medium - CCI-001849 - V-207452 - SV-207452r854623_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001849
Version
SRG-OS-000341-VMM-001220
Vuln IDs
  • V-207452
  • V-57105
Rule IDs
  • SV-207452r854623_rule
  • SV-71365
In order to ensure VMMs have a sufficient storage capacity in which to write the audit logs, VMMs need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial installation of the VMM and should be based upon anticipated audit record volume. If a central audit record storage facility is available, the local storage capacity should be sufficient to hold audit records that would accumulate during anticipated interruptions in delivery of records to the facility.
Checks: C-7709r365760_chk

Verify the VMM allocates audit record storage capacity to store at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility. If it does not, this is a finding.

Fix: F-7709r365761_fix

Configure the VMM to allocate audit record storage capacity to store at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility.

b
The VMM must off-load audit records onto a different system or media than the system being audited.
AU-4 - Medium - CCI-001851 - V-207453 - SV-207453r854624_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001851
Version
SRG-OS-000342-VMM-001230
Vuln IDs
  • V-207453
  • V-57107
Rule IDs
  • SV-207453r854624_rule
  • SV-71367
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in VMMs with limited audit storage capacity.
Checks: C-7710r365763_chk

Verify the VMM off-loads audit records onto a different system or media than the system being audited. If it does not, this is a finding.

Fix: F-7710r365764_fix

Configure the VMM to off-load audit records onto a different system or media than the system being audited.

b
The VMM must provide an immediate warning to the SA and ISSO, at a minimum, when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.
AU-5 - Medium - CCI-001855 - V-207454 - SV-207454r854625_rule
RMF Control
AU-5
Severity
M
CCI
CCI-001855
Version
SRG-OS-000343-VMM-001240
Vuln IDs
  • V-207454
  • V-57109
Rule IDs
  • SV-207454r854625_rule
  • SV-71369
If security personnel are not notified immediately when storage volume reaches 75%, they are unable to plan for audit record storage capacity expansion.
Checks: C-7711r365766_chk

Verify the VMM provides an immediate warning to the SA and ISSO, at a minimum, when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity. If it does not, this is a finding.

Fix: F-7711r365767_fix

Configure the VMM to provide an immediate warning to the SA and ISSO, at a minimum, when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity.

b
The VMM must provide an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts.
AU-5 - Medium - CCI-001858 - V-207455 - SV-207455r854626_rule
RMF Control
AU-5
Severity
M
CCI
CCI-001858
Version
SRG-OS-000344-VMM-001250
Vuln IDs
  • V-207455
  • V-57111
Rule IDs
  • SV-207455r854626_rule
  • SV-71371
It is critical for the appropriate personnel to be aware if a VMM is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less).
Checks: C-7712r365769_chk

Verify the VMM provides an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts. If it does not, this is a finding.

Fix: F-7712r365770_fix

Configure the VMM to provide an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts.

b
The VMM must provide an audit reduction capability that supports on-demand audit review and analysis.
AU-7 - Medium - CCI-001875 - V-207456 - SV-207456r854627_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001875
Version
SRG-OS-000348-VMM-001260
Vuln IDs
  • V-207456
  • V-57113
Rule IDs
  • SV-207456r854627_rule
  • SV-71373
The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Audit reduction is a technique used to reduce the volume of audit records in order to facilitate a manual review. Audit reduction does not alter original audit records. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports.
Checks: C-7713r365772_chk

Verify the VMM provides an audit reduction capability that supports on-demand audit review and analysis. If it does not, this is a finding.

Fix: F-7713r365773_fix

Configure the VMM to provide an audit reduction capability that supports on-demand audit review and analysis.

b
The VMM must provide an audit reduction capability that supports after-the-fact investigations of security incidents.
AU-7 - Medium - CCI-001877 - V-207457 - SV-207457r854628_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001877
Version
SRG-OS-000349-VMM-001270
Vuln IDs
  • V-207457
  • V-57115
Rule IDs
  • SV-207457r854628_rule
  • SV-71375
If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies. Audit reduction capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools This requirement is specific to VMMs with audit reduction capabilities
Checks: C-7714r365775_chk

Verify the VMM provides an audit reduction capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding.

Fix: F-7714r365776_fix

Configure the VMM to provide an audit reduction capability that supports after-the-fact investigations of security incidents.

b
The VMM must provide a report generation capability that supports on-demand audit review and analysis.
AU-7 - Medium - CCI-001878 - V-207458 - SV-207458r854629_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001878
Version
SRG-OS-000350-VMM-001280
Vuln IDs
  • V-207458
  • V-57117
Rule IDs
  • SV-207458r854629_rule
  • SV-71377
The report generation capability must support on-demand review and analysis in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Report generation must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective.
Checks: C-7715r365778_chk

Verify the VMM provides a report generation capability that supports on-demand audit review and analysis. If it does not, this is a finding.

Fix: F-7715r365779_fix

Ensure the VMM provides a report generation capability that supports on-demand audit review and analysis.

b
The VMM must provide a report generation capability that supports on-demand reporting requirements.
AU-7 - Medium - CCI-001879 - V-207459 - SV-207459r854630_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001879
Version
SRG-OS-000351-VMM-001290
Vuln IDs
  • V-207459
  • V-57119
Rule IDs
  • SV-207459r854630_rule
  • SV-71379
The report generation capability must support on-demand reporting in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Report generation must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective.
Checks: C-7716r365781_chk

Verify the VMM provides a report generation capability that supports on-demand reporting requirements. If it does not, this is a finding.

Fix: F-7716r365782_fix

Ensure the VMM provides a report generation capability that supports on-demand reporting requirements.

b
The VMM must provide a report generation capability that supports after-the-fact investigations of security incidents.
AU-7 - Medium - CCI-001880 - V-207460 - SV-207460r854631_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001880
Version
SRG-OS-000352-VMM-001300
Vuln IDs
  • V-207460
  • V-57121
Rule IDs
  • SV-207460r854631_rule
  • SV-71381
If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required to comply with applicable Federal laws and DoD policies. The report generation capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools.
Checks: C-7717r365784_chk

Verify the VMM provides a report generation capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding.

Fix: F-7717r365785_fix

Ensure the VMM provides a report generation capability that supports after-the-fact investigations of security incidents.

b
The VMM that provides an audit reduction capability must not alter original content or time ordering of audit records.
AU-7 - Medium - CCI-001881 - V-207461 - SV-207461r854632_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001881
Version
SRG-OS-000353-VMM-001310
Vuln IDs
  • V-207461
  • V-57123
Rule IDs
  • SV-207461r854632_rule
  • SV-71383
If the audit reduction capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this. This requirement is specific to VMMs providing audit reduction capabilities. The audit reduction capability can be met either natively or through the use of third-party tools.
Checks: C-7718r365787_chk

Verify the VMM that provides an audit reduction capability does not alter original content or time ordering of audit records. If it does not, this is a finding.

Fix: F-7718r365788_fix

Configure the VMM that provides an audit reduction capability so that it does not alter original content or time ordering of audit records.

b
The VMM that provides a report generation capability must not alter original content or time ordering of audit records.
AU-7 - Medium - CCI-001882 - V-207462 - SV-207462r854633_rule
RMF Control
AU-7
Severity
M
CCI
CCI-001882
Version
SRG-OS-000354-VMM-001320
Vuln IDs
  • V-207462
  • V-57125
Rule IDs
  • SV-207462r854633_rule
  • SV-71385
If the report generation capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this. This requirement is specific to VMMs providing report generation capabilities. The report generation capability can be met either natively or through the use of third-party tools.
Checks: C-7719r365790_chk

Verify the VMM that provides a report generation capability does not alter original content or time ordering of audit records. If it does not, this is a finding.

Fix: F-7719r365791_fix

Configure the VMM that provides a report generation capability so that it does not alter original content or time ordering of audit records.

b
The VMM must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).
AU-8 - Medium - CCI-001891 - V-207463 - SV-207463r878143_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001891
Version
SRG-OS-000355-VMM-001330
Vuln IDs
  • V-207463
  • V-57127
Rule IDs
  • SV-207463r878143_rule
  • SV-71387
Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside of the configured acceptable allowance (drift) may be inaccurate. Synchronizing internal VMM clocks provides uniformity of time stamps for VMMs with multiple system clocks and systems connected over a network. Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).
Checks: C-7720r878141_chk

Verify the VMM, for networked systems, compares internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). If it does not, this is a finding.

Fix: F-7720r878142_fix

Configure the VMM, for networked systems, to compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

b
The VMM must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.
AU-8 - Medium - CCI-002046 - V-207464 - SV-207464r854637_rule
RMF Control
AU-8
Severity
M
CCI
CCI-002046
Version
SRG-OS-000356-VMM-001340
Vuln IDs
  • V-207464
  • V-57129
Rule IDs
  • SV-207464r854637_rule
  • SV-71389
Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Synchronizing internal VMM clocks provides uniformity of time stamps for VMMs with multiple system clocks and systems connected over a network.
Checks: C-7721r365796_chk

Verify the VMM synchronizes internal information system clocks to the authoritative time source when the time difference is greater than one second. If it does not, this is a finding.

Fix: F-7721r365797_fix

Configure the VMM to synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.

b
The VMM must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.
AU-8 - Medium - CCI-001889 - V-207465 - SV-207465r854638_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001889
Version
SRG-OS-000358-VMM-001350
Vuln IDs
  • V-207465
  • V-57131
Rule IDs
  • SV-207465r854638_rule
  • SV-71391
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the VMM include date and time. Granularity of time measurements refers to the degree of synchronization between VMM clocks and reference clocks.
Checks: C-7722r365799_chk

Verify the VMM records time stamps for audit records that meet a granularity of one second for a minimum degree of precision. If it does not, this is a finding.

Fix: F-7722r365800_fix

Configure the VMM to record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.

b
The VMM must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
AU-8 - Medium - CCI-001890 - V-207466 - SV-207466r854639_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001890
Version
SRG-OS-000359-VMM-001360
Vuln IDs
  • V-207466
  • V-57133
Rule IDs
  • SV-207466r854639_rule
  • SV-71393
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the VMM include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.
Checks: C-7723r365802_chk

Verify the VMM records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). If it does not, this is a finding.

Fix: F-7723r365803_fix

Configure the VMM to record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).

b
The VMM must enforce dual authorization for movement and/or deletion of all audit information, when such movement or deletion is not part of an authorized automatic process.
CM-6 - Medium - CCI-000366 - V-207467 - SV-207467r854640_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-OS-000360-VMM-001370
Vuln IDs
  • V-207467
  • V-57135
Rule IDs
  • SV-207467r854640_rule
  • SV-71395
An authorized user may intentionally or accidentally move or delete audit records without those specific actions being authorized. All bulk manipulation of audit information must be via authorized automatic processes. Any manual manipulation of audit information must require dual authorization. Dual authorization mechanisms require the approval of two authorized individuals in order to execute.
Checks: C-7724r365805_chk

Verify the VMM enforces dual authorization for movement and/or deletion of all audit information, when such movement or deletion is not part of an authorized automatic process. If it does not, this is a finding.

Fix: F-7724r365806_fix

Configure the VMM to enforce dual authorization for movement and/or deletion of all audit information, when such movement or deletion is not part of an authorized automatic process.

b
The VMM must prohibit user installation of software without explicit privileged status.
CM-11 - Medium - CCI-001812 - V-207468 - SV-207468r854641_rule
RMF Control
CM-11
Severity
M
CCI
CCI-001812
Version
SRG-OS-000362-VMM-001390
Vuln IDs
  • V-207468
  • V-57137
Rule IDs
  • SV-207468r854641_rule
  • SV-71397
Allowing regular users to install software or guest VMs, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the VMM. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceeds the rights of a regular user. VMM functionality will vary, and while users are not permitted to install unapproved software or guest VMs, there may be instances when the organization allows the user to install approved software packages such as from an approved software repository. The VMM or software configuration management utility must enforce control of software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization.
Checks: C-7725r365808_chk

Verify the VMM prohibits user installation of software or guest VMs without explicit privileged status. If it does not, this is a finding.

Fix: F-7725r365809_fix

Configure the VMM to prohibit user installation of software or guest VMs without explicit privileged status.

b
The VMM must notify designated personnel if baseline configurations are changed in an unauthorized manner.
CM-3 - Medium - CCI-001744 - V-207469 - SV-207469r854642_rule
RMF Control
CM-3
Severity
M
CCI
CCI-001744
Version
SRG-OS-000363-VMM-001400
Vuln IDs
  • V-207469
  • V-57139
Rule IDs
  • SV-207469r854642_rule
  • SV-71399
Unauthorized changes to the baseline configuration could make the VMM vulnerable to various attacks or allow unauthorized access to the VMM. Changes to VMM configurations can have unintended side effects, some of which may be relevant to security. Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the VMM. The VMM's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.
Checks: C-7726r365811_chk

Verify the VMM notifies designated personnel if baseline configurations are changed in an unauthorized manner. If it does not, this is a finding.

Fix: F-7726r365812_fix

Configure the VMM to notify designated personnel if baseline configurations are changed in an unauthorized manner.

b
The VMM must enforce access restrictions associated with changes to the system.
CM-5 - Medium - CCI-001813 - V-207470 - SV-207470r854643_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001813
Version
SRG-OS-000364-VMM-001410
Vuln IDs
  • V-207470
  • V-57141
Rule IDs
  • SV-207470r854643_rule
  • SV-71401
Failure to provide logical access restrictions associated with changes to system configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the VMM can potentially have significant effects on the overall security of the system. Accordingly, only qualified and authorized individuals should be allowed to obtain access to VMM components for the purposes of initiating changes, including upgrades and modifications. Logical access restrictions include, for example, controls that restrict access to guest VMs, workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into VMMs), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover).
Checks: C-7727r365814_chk

Verify the VMM enforces access restrictions associated with changes to the system. If it does not, this is a finding.

Fix: F-7727r365815_fix

Configure the VMM to enforce access restrictions associated with changes to the system.

b
The VMM must audit the enforcement actions used to restrict access associated with changes to the system.
CM-5 - Medium - CCI-001814 - V-207471 - SV-207471r854644_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001814
Version
SRG-OS-000365-VMM-001420
Vuln IDs
  • V-207471
  • V-57143
Rule IDs
  • SV-207471r854644_rule
  • SV-71403
Without auditing the enforcement of access restrictions against changes to the VMM configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available for forensic investigation for after-the-fact actions. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.
Checks: C-7728r365817_chk

Verify the VMM audits the enforcement actions used to restrict access associated with changes to the system. If it does not, this is a finding.

Fix: F-7728r365818_fix

Configure the VMM to audit the enforcement actions used to restrict access associated with changes to the system.

b
The VMM must prevent the installation of guest VMs, patches, service packs, device drivers, or VMM components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.
CM-5 - Medium - CCI-001749 - V-207472 - SV-207472r878138_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001749
Version
SRG-OS-000366-VMM-001430
Vuln IDs
  • V-207472
  • V-57145
Rule IDs
  • SV-207472r878138_rule
  • SV-71405
Changes to any software components can have significant effects on the overall security of the VMM. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor. Accordingly, guest VMs, patches, service packs, device drivers, or VMM components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The VMM should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.
Checks: C-7729r878137_chk

Verify the VMM prevents the installation of guest VMs, patches, service packs, device drivers, or VMM components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. If it does not, this is a finding.

Fix: F-7729r365821_fix

Configure the VMM to prevent the installation of guest VMs, patches, service packs, device drivers, or VMM components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.

b
The VMM must prevent use of service and helper VMs not required to support proper VMM function.
CM-7 - Medium - CCI-001764 - V-207473 - SV-207473r854647_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001764
Version
SRG-OS-000368-VMM-001440
Vuln IDs
  • V-207473
  • V-57147
Rule IDs
  • SV-207473r854647_rule
  • SV-71407
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some VMMs may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the VMM level. Some of the service and helper VMs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of such VMs is not always possible; therefore, establishing a method of preventing VM activation is critical to maintaining a secure system baseline. Methods for complying with this requirement include restricting execution of VMs in certain environments, while preventing execution in other environments; or limiting execution of certain VM functionality based on organizationally defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).
Checks: C-7730r365823_chk

Verify the VMM prevents use of service and helper VMs not required to support proper VMM function. If it does not, this is a finding.

Fix: F-7730r365824_fix

Configure the VMM to prevent use of service and helper VMs not required to support proper VMM function.

b
The VMM must prevent inappropriate use of redundant guest VMs.
CM-7 - Medium - CCI-001764 - V-207474 - SV-207474r854648_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001764
Version
SRG-OS-000368-VMM-001450
Vuln IDs
  • V-207474
  • V-57149
Rule IDs
  • SV-207474r854648_rule
  • SV-71409
Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some VMMs may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the VMM level. Some of the guest VMs, set up for redundancy, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions) at the present time. Removal of such VMs is not always possible; therefore, establishing a method of preventing VM activation is critical to maintaining a secure system baseline. Methods for complying with this requirement include restricting execution of VMs in certain environments, while preventing execution in other environments; or limiting execution of certain VM functionality based on organizationally defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).
Checks: C-7731r365826_chk

Verify the VMM prevents inappropriate use of redundant guest VMs. If it does not, this is a finding.

Fix: F-7731r365827_fix

Configure the VMM to prevent inappropriate use of redundant guest VMs.

b
The VMM must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and guest VMs.
CM-7 - Medium - CCI-001774 - V-207475 - SV-207475r854649_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001774
Version
SRG-OS-000370-VMM-001460
Vuln IDs
  • V-207475
  • V-57151
Rule IDs
  • SV-207475r854649_rule
  • SV-71411
Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software and guest VMs. Using only authorized software decreases risk by limiting the number of potential vulnerabilities and by preventing the execution of malware. The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs and guest VMs that are authorized to execute on organizational VMMs is commonly referred to as whitelisting. Verification of white-listed software and guest VMs can occur either prior to execution or at system startup.
Checks: C-7732r365829_chk

Verify the VMM employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs and guest VMs. If it does not, this is a finding.

Fix: F-7732r365830_fix

Configure the VMM to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and guest VMs.

b
The VMM must require users to re-authenticate for privilege escalation.
IA-11 - Medium - CCI-002038 - V-207476 - SV-207476r854650_rule
RMF Control
IA-11
Severity
M
CCI
CCI-002038
Version
SRG-OS-000373-VMM-001470
Vuln IDs
  • V-207476
  • V-57153
Rule IDs
  • SV-207476r854650_rule
  • SV-71413
Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When VMMs provide the capability to escalate a functional capability, it is critical the user re-authenticate.
Checks: C-7733r365832_chk

Verify the VMM requires users to re-authenticate for privilege escalation. If it does not, this is a finding.

Fix: F-7733r365833_fix

Configure the VMM to require users to re-authenticate for privilege escalation.

b
The VMM must require users to re-authenticate when changing roles.
IA-11 - Medium - CCI-002038 - V-207477 - SV-207477r854651_rule
RMF Control
IA-11
Severity
M
CCI
CCI-002038
Version
SRG-OS-000373-VMM-001480
Vuln IDs
  • V-207477
  • V-57155
Rule IDs
  • SV-207477r854651_rule
  • SV-71415
Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When VMMs provide the capability to change security roles, it is critical the user re-authenticate.
Checks: C-7734r365835_chk

Verify the VMM requires users to re-authenticate when changing roles. If it does not, this is a finding.

Fix: F-7734r365836_fix

Configure the VMM to require users to re-authenticate when changing roles.

b
The VMM must require users to re-authenticate when changing authenticators.
IA-11 - Medium - CCI-002038 - V-207478 - SV-207478r854652_rule
RMF Control
IA-11
Severity
M
CCI
CCI-002038
Version
SRG-OS-000373-VMM-001490
Vuln IDs
  • V-207478
  • V-57157
Rule IDs
  • SV-207478r854652_rule
  • SV-71417
Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When VMMs provide the capability to change user authenticators, it is critical the user re-authenticate.
Checks: C-7735r365838_chk

Verify the VMM requires users to re-authenticate when changing authenticators. If it does not, this is a finding.

Fix: F-7735r365839_fix

Configure the VMM to require users to re-authenticate when changing authenticators.

b
The VMM must require devices to re-authenticate when changing authenticators.
IA-11 - Medium - CCI-002039 - V-207479 - SV-207479r854653_rule
RMF Control
IA-11
Severity
M
CCI
CCI-002039
Version
SRG-OS-000374-VMM-001500
Vuln IDs
  • V-207479
  • V-57159
Rule IDs
  • SV-207479r854653_rule
  • SV-71419
Without re-authentication, devices may access resources or perform tasks for which they do not have authorization. When VMMs provide the capability to change device authenticators, it is critical the device re-authenticate. This requirement is applicable to devices capable of authentication.
Checks: C-7736r365841_chk

Verify the VMM requires devices to re-authenticate when changing authenticators. If it does not, this is a finding.

Fix: F-7736r365842_fix

Configure the VMM to require devices to re-authenticate when changing authenticators.

b
The VMM must implement multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access.
IA-2 - Medium - CCI-001948 - V-207480 - SV-207480r854654_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001948
Version
SRG-OS-000375-VMM-001510
Vuln IDs
  • V-207480
  • V-57161
Rule IDs
  • SV-207480r854654_rule
  • SV-71421
Using an authentication device, such as a CAC or token that is separate from the VMM, ensures that even if the VMM is compromised, that compromise will not affect credentials stored on the authentication device. Multifactor solutions that require devices separate from VMMs gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card. A privileged account is defined as a VMM account with authorizations of a privileged user. Remote access is access to DoD non-public VMMs by an authorized user (or a VMM) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Checks: C-7737r365844_chk

Verify the VMM implements multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access. If it does not, this is a finding.

Fix: F-7737r365845_fix

Configure the VMM to implement multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access.

b
The VMM must accept Personal Identity Verification (PIV) credentials.
IA-2 - Medium - CCI-001953 - V-207481 - SV-207481r854655_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001953
Version
SRG-OS-000376-VMM-001520
Vuln IDs
  • V-207481
  • V-57163
Rule IDs
  • SV-207481r854655_rule
  • SV-71423
The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12 and as a primary component of layered protection for national security systems.
Checks: C-7738r365847_chk

Verify the VMM accepts Personal Identity Verification (PIV) credentials. If it does not, this is a finding.

Fix: F-7738r365848_fix

Configure the VMM to accept Personal Identity Verification (PIV) credentials.

b
The VMM must electronically verify Personal Identity Verification (PIV) credentials.
IA-2 - Medium - CCI-001954 - V-207482 - SV-207482r854656_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001954
Version
SRG-OS-000377-VMM-001530
Vuln IDs
  • V-207482
  • V-57165
Rule IDs
  • SV-207482r854656_rule
  • SV-71425
The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12 and as a primary component of layered protection for national security systems.
Checks: C-7739r365850_chk

Verify the VMM electronically verifies Personal Identity Verification (PIV) credentials. If it does not, this is a finding.

Fix: F-7739r365851_fix

Configure the VMM to electronically verify Personal Identity Verification (PIV) credentials.

b
The VMM must authenticate peripherals before establishing a connection.
IA-3 - Medium - CCI-001958 - V-207483 - SV-207483r854657_rule
RMF Control
IA-3
Severity
M
CCI
CCI-001958
Version
SRG-OS-000378-VMM-001540
Vuln IDs
  • V-207483
  • V-57167
Rule IDs
  • SV-207483r854657_rule
  • SV-71427
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers. This requirement is applicable to devices capable of authentication.
Checks: C-7740r365853_chk

Verify the VMM authenticates peripherals before establishing a connection. If it does not, this is a finding.

Fix: F-7740r365854_fix

Configure the VMM to authenticate peripherals before establishing a connection.

b
The VMM must authenticate all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based.
IA-3 - Medium - CCI-001967 - V-207484 - SV-207484r877039_rule
RMF Control
IA-3
Severity
M
CCI
CCI-001967
Version
SRG-OS-000379-VMM-001550
Vuln IDs
  • V-207484
  • V-57269
Rule IDs
  • SV-207484r877039_rule
  • SV-71529
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. Bidirectional authentication solutions include, but are not limited, to IEEE 802.1x and Extensible Authentication Protocol [EAP], Radius server with EAP-Transport Layer Security [TLS] authentication, Kerberos, and SSL mutual authentication. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area network, wide area network, or the Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply this requirement to those limited number (and type) of devices that truly need to support this capability.
Checks: C-7741r365856_chk

Verify the VMM authenticates all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based. If it does not, this is a finding.

Fix: F-7741r365857_fix

Configure the VMM to authenticate all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based.

b
The VMM must allow the use of a temporary password for system logons with an immediate change to a permanent password.
IA-5 - Medium - CCI-002041 - V-207485 - SV-207485r854659_rule
RMF Control
IA-5
Severity
M
CCI
CCI-002041
Version
SRG-OS-000380-VMM-001560
Vuln IDs
  • V-207485
  • V-57271
Rule IDs
  • SV-207485r854659_rule
  • SV-71531
Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial login. Temporary passwords are typically used to allow access when new accounts are created or passwords are changed. It is common practice for administrators to create temporary passwords for user accounts which allow the users to log in, yet force them to change the password once they have successfully authenticated.
Checks: C-7742r365859_chk

Verify the VMM allows the use of a temporary password for system logons with an immediate change to a permanent password. If it does not, this is a finding.

Fix: F-7742r365860_fix

Configure the VMM to allow the use of a temporary password for system logons with an immediate change to a permanent password.

b
The VMM must prohibit the use of cached authenticators after one day.
IA-5 - Medium - CCI-002007 - V-207486 - SV-207486r854660_rule
RMF Control
IA-5
Severity
M
CCI
CCI-002007
Version
SRG-OS-000383-VMM-001570
Vuln IDs
  • V-207486
  • V-57273
Rule IDs
  • SV-207486r854660_rule
  • SV-71533
If cached authentication information is out of date, the validity of the authentication information may be questionable.
Checks: C-7743r365862_chk

Verify the VMM prohibits the use of cached authenticators after one day. If it does not, this is a finding.

Fix: F-7743r365863_fix

Configure the VMM to prohibit the use of cached authenticators after one day.

b
The VMM, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network.
IA-5 - Medium - CCI-001991 - V-207487 - SV-207487r854661_rule
RMF Control
IA-5
Severity
M
CCI
CCI-001991
Version
SRG-OS-000384-VMM-001580
Vuln IDs
  • V-207487
  • V-57275
Rule IDs
  • SV-207487r854661_rule
  • SV-71535
Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates).
Checks: C-7744r365865_chk

Verify the VMM, for PKI-based authentication, implements a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. If it does not, this is a finding.

Fix: F-7744r365866_fix

Configure the VMM, for PKI-based authentication, to implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network.

b
The VMM must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.
SC-13 - Medium - CCI-002450 - V-207488 - SV-207488r854662_rule
RMF Control
SC-13
Severity
M
CCI
CCI-002450
Version
SRG-OS-000396-VMM-001590
Vuln IDs
  • V-207488
  • V-57277
Rule IDs
  • SV-207488r854662_rule
  • SV-71537
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The VMM must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
Checks: C-7745r365868_chk

Verify the VMM implements NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. If it does not, this is a finding.

Fix: F-7745r365869_fix

Configure the VMM to implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

b
The VMM must request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002465 - V-207489 - SV-207489r854663_rule
RMF Control
SC-21
Severity
M
CCI
CCI-002465
Version
SRG-OS-000399-VMM-001600
Vuln IDs
  • V-207489
  • V-57279
Rule IDs
  • SV-207489r854663_rule
  • SV-71539
If data origin authentication and data integrity verification is not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or DoS. Data origin authentication must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own, or has authenticated channels to trusted validation providers. VMMs that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. VMMs that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity of response data. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-7746r365871_chk

Verify the VMM requests data origin authentication verification on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-7746r365872_fix

Configure the VMM to request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.

b
The VMM must request data integrity verification on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002466 - V-207490 - SV-207490r854664_rule
RMF Control
SC-21
Severity
M
CCI
CCI-002466
Version
SRG-OS-000400-VMM-001610
Vuln IDs
  • V-207490
  • V-57281
Rule IDs
  • SV-207490r854664_rule
  • SV-71541
If data origin authentication and data integrity verification is not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed that would result in query failure or denial of service. Data integrity verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. VMMs that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-7747r365874_chk

Verify the VMM requests data integrity verification on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-7747r365875_fix

Configure the VMM to request data integrity verification on the name/address resolution responses the system receives from authoritative sources.

b
The VMM must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002467 - V-207491 - SV-207491r854665_rule
RMF Control
SC-21
Severity
M
CCI
CCI-002467
Version
SRG-OS-000401-VMM-001620
Vuln IDs
  • V-207491
  • V-57283
Rule IDs
  • SV-207491r854665_rule
  • SV-71543
If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data integrity verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own, or has authenticated channels to trusted validation providers. VMMs that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-7748r365877_chk

Verify the VMM performs data integrity verification on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-7748r365878_fix

Configure the VMM to perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.

b
The VMM must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002468 - V-207492 - SV-207492r854666_rule
RMF Control
SC-21
Severity
M
CCI
CCI-002468
Version
SRG-OS-000402-VMM-001630
Vuln IDs
  • V-207492
  • V-57285
Rule IDs
  • SV-207492r854666_rule
  • SV-71545
If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data origin authentication verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. VMMs that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-7749r365880_chk

Verify the VMM performs data origin verification authentication on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-7749r365881_fix

Configure the VMM to perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.

b
The VMM must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.
SC-23 - Medium - CCI-002470 - V-207493 - SV-207493r854667_rule
RMF Control
SC-23
Severity
M
CCI
CCI-002470
Version
SRG-OS-000403-VMM-001640
Vuln IDs
  • V-207493
  • V-57287
Rule IDs
  • SV-207493r854667_rule
  • SV-71547
Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DoD-approved CA, trust of this CA has not been established. The DoD will only accept PKI certificates obtained from a DoD-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of SSL/TLS certificates. This requirement is not applicable to VMM-internal sessions between components not identified as "Key Terrain" for "Non-Person Entities" per DoD policy.
Checks: C-7750r365883_chk

Verify the VMM only allows the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions. If it does not, this is a finding.

Fix: F-7750r365884_fix

Configure the VMM to only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.

b
The VMM must implement cryptographic mechanisms to prevent unauthorized modification of all information at rest on all VMM components.
SC-28 - Medium - CCI-002475 - V-207494 - SV-207494r854668_rule
RMF Control
SC-28
Severity
M
CCI
CCI-002475
Version
SRG-OS-000404-VMM-001650
Vuln IDs
  • V-207494
  • V-57289
Rule IDs
  • SV-207494r854668_rule
  • SV-71549
VMMs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized modification of the information at rest. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information.
Checks: C-7751r365886_chk

Verify the VMM implements cryptographic mechanisms to prevent unauthorized modification of all information at rest on all VMM components. If it does not, this is a finding.

Fix: F-7751r365887_fix

Configure the VMM to implement cryptographic mechanisms to prevent unauthorized modification of all information at rest on all VMM components.

b
The VMM must implement cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all VMM components.
SC-28 - Medium - CCI-002476 - V-207495 - SV-207495r854669_rule
RMF Control
SC-28
Severity
M
CCI
CCI-002476
Version
SRG-OS-000405-VMM-001660
Vuln IDs
  • V-207495
  • V-57291
Rule IDs
  • SV-207495r854669_rule
  • SV-71551
VMMs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure of the information at rest. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information.
Checks: C-7752r365889_chk

Verify the VMM implements cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all VMM components. If it does not, this is a finding.

Fix: F-7752r365890_fix

Configure the VMM to implement cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all VMM components.

b
The VMM must maintain a separate execution domain for each executing process.
SC-39 - Medium - CCI-002530 - V-207496 - SV-207496r854670_rule
RMF Control
SC-39
Severity
M
CCI
CCI-002530
Version
SRG-OS-000408-VMM-001670
Vuln IDs
  • V-207496
  • V-57293
Rule IDs
  • SV-207496r854670_rule
  • SV-71553
VMMs can maintain separate execution domains for each executing process by assigning each process a separate address space. Each VMM process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. This capability is available in most commercial VMMs that employ multistate processor technologies.
Checks: C-7753r365892_chk

Verify the VMM maintains a separate execution domain for each executing process. If it does not, this is a finding.

Fix: F-7753r365893_fix

Configure the VMM to maintain a separate execution domain for each executing process.

b
The VMM must maintain a separate execution domain for each guest VM.
SC-39 - Medium - CCI-002530 - V-207497 - SV-207497r854671_rule
RMF Control
SC-39
Severity
M
CCI
CCI-002530
Version
SRG-OS-000408-VMM-001680
Vuln IDs
  • V-207497
  • V-57295
Rule IDs
  • SV-207497r854671_rule
  • SV-71555
VMMs can maintain separate execution domains for each executing guest VM by assigning each guest VM a separate address space. Each VMM guest VM has a distinct address space so that communication between guest VMs is performed in a manner controlled through the security functions of the VMM, and one guest VM cannot modify the executing code of another guest VM. This capability is available in most commercial VMMs that employ virtualization processor technologies.
Checks: C-7754r365895_chk

Verify the VMM maintains a separate execution domain for each guest VM. If it does not, this is a finding.

Fix: F-7754r365896_fix

Configure the VMM to maintain a separate execution domain for each guest VM.

b
The VMM must protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the VMM is implementing rate-limiting measures on impacted network interfaces.
SC-5 - Medium - CCI-002385 - V-207498 - SV-207498r854672_rule
RMF Control
SC-5
Severity
M
CCI
CCI-002385
Version
SRG-OS-000420-VMM-001690
Vuln IDs
  • V-207498
  • V-57297
Rule IDs
  • SV-207498r854672_rule
  • SV-71557
DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of the VMM to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks, though they may also exacerbate the problem.
Checks: C-7755r365898_chk

Verify the VMM protects against or limit the effects of Denial of Service (DoS) attacks by ensuring the VMM is implementing rate-limiting measures on impacted network interfaces. If it does not, this is a finding.

Fix: F-7755r365899_fix

Configure the VMM to protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the VMM is implementing rate-limiting measures on impacted network interfaces.

b
The VMM must protect the confidentiality and integrity of transmitted information.
SC-8 - Medium - CCI-002418 - V-207499 - SV-207499r854673_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
SRG-OS-000423-VMM-001700
Vuln IDs
  • V-207499
  • V-57299
Rule IDs
  • SV-207499r854673_rule
  • SV-71559
Without protection of the transmitted information, confidentiality and integrity may be compromised as unprotected communications can be intercepted and either read or altered. This requirement applies to both internal and external networks and all types of VMM components from which information can be transmitted (e.g., guest VMs, servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.
Checks: C-7756r365901_chk

Verify the VMM protects the confidentiality and integrity of transmitted information. If it does not, this is a finding.

Fix: F-7756r365902_fix

Configure the VMM to protect the confidentiality and integrity of transmitted information.

b
The VMM must maintain the confidentiality and integrity of information during preparation for transmission.
SC-8 - Medium - CCI-002420 - V-207500 - SV-207500r854674_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002420
Version
SRG-OS-000425-VMM-001710
Vuln IDs
  • V-207500
  • V-57301
Rule IDs
  • SV-207500r854674_rule
  • SV-71561
Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Ensuring the confidentiality of transmitted information requires the VMM to take measures in preparing information for transmission. This can be accomplished via access control and encryption. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, VMMs need to support transmission protection mechanisms such as TLS, SSL VPNs, or IPSEC.
Checks: C-7757r365904_chk

Verify the VMM maintains the confidentiality and integrity of information during preparation for transmission. If it does not, this is a finding.

Fix: F-7757r365905_fix

Configure the VMM to maintain the confidentiality and integrity of information during preparation for transmission.

b
The VMM must maintain the confidentiality and integrity of information during reception.
SC-8 - Medium - CCI-002422 - V-207501 - SV-207501r854675_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002422
Version
SRG-OS-000426-VMM-001720
Vuln IDs
  • V-207501
  • V-57303
Rule IDs
  • SV-207501r854675_rule
  • SV-71563
Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during de-aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Ensuring the confidentiality of transmitted information requires the VMM to take measures in preparing information during reception. This can be accomplished via access control and encryption. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When receiving data, VMMs need to leverage protection mechanisms such as TLS, SSL VPNs, or IPSEC.
Checks: C-7758r365907_chk

Verify the VMM maintains the confidentiality and integrity of information during reception. If it does not, this is a finding.

Fix: F-7758r365908_fix

Configure the VMM to maintain the confidentiality and integrity of information during reception.

b
The VMM must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.
SI-10 - Medium - CCI-002754 - V-207502 - SV-207502r854676_rule
RMF Control
SI-10
Severity
M
CCI
CCI-002754
Version
SRG-OS-000432-VMM-001730
Vuln IDs
  • V-207502
  • V-57305
Rule IDs
  • SV-207502r854676_rule
  • SV-71565
A common vulnerability of VMM is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where VMM responses to the invalid input may be disruptive or cause the system to fail into an unsafe state. The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.
Checks: C-7759r365910_chk

Verify the VMM behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. If it does not, this is a finding.

Fix: F-7759r365911_fix

Ensure the VMM behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.

b
The VMM must implement non-executable data to protect its memory from unauthorized code execution.
SI-16 - Medium - CCI-002824 - V-207503 - SV-207503r854677_rule
RMF Control
SI-16
Severity
M
CCI
CCI-002824
Version
SRG-OS-000433-VMM-001740
Vuln IDs
  • V-207503
  • V-57307
Rule IDs
  • SV-207503r854677_rule
  • SV-71567
Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. Examples of attacks are buffer overflow attacks.
Checks: C-7760r365913_chk

Verify the VMM implements non-executable data to protect its memory from unauthorized code execution. If it does not, this is a finding.

Fix: F-7760r365914_fix

Configure the VMM to implement non-executable data to protect its memory from unauthorized code execution.

b
The VMM must implement address space layout randomization to protect its memory from unauthorized code execution.
SI-16 - Medium - CCI-002824 - V-207504 - SV-207504r854678_rule
RMF Control
SI-16
Severity
M
CCI
CCI-002824
Version
SRG-OS-000433-VMM-001750
Vuln IDs
  • V-207504
  • V-57309
Rule IDs
  • SV-207504r854678_rule
  • SV-71569
Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. Examples of attacks are buffer overflow attacks.
Checks: C-7761r365916_chk

Verify the VMM implements address space layout randomization to protect its memory from unauthorized code execution. If it does not, this is a finding.

Fix: F-7761r365917_fix

Configure the VMM to implement address space layout randomization to protect its memory from unauthorized code execution.

b
The VMM must remove all software components after updated versions have been installed.
SI-2 - Medium - CCI-002617 - V-207505 - SV-207505r854679_rule
RMF Control
SI-2
Severity
M
CCI
CCI-002617
Version
SRG-OS-000437-VMM-001760
Vuln IDs
  • V-207505
  • V-57311
Rule IDs
  • SV-207505r854679_rule
  • SV-71571
Previous versions of software components that are not removed from the VMM after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the VMM.
Checks: C-7762r365919_chk

Verify the VMM removes all software components after updated versions have been installed. If it does not, this is a finding.

Fix: F-7762r365920_fix

Configure the VMM to remove all software components after updated versions have been installed.

b
The VMM must verify correct operation of all security functions.
SI-6 - Medium - CCI-002696 - V-207506 - SV-207506r854680_rule
RMF Control
SI-6
Severity
M
CCI
CCI-002696
Version
SRG-OS-000445-VMM-001780
Vuln IDs
  • V-207506
  • V-57313
Rule IDs
  • SV-207506r854680_rule
  • SV-71573
Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the VMM responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters.
Checks: C-7763r365922_chk

Verify the VMM verifies correct operation of all security functions. If it does not, this is a finding.

Fix: F-7763r365923_fix

Configure the VMM to verify correct operation of all security functions.

b
The VMM must perform verification of the correct operation of security functions: upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days.
SI-6 - Medium - CCI-002699 - V-207507 - SV-207507r854681_rule
RMF Control
SI-6
Severity
M
CCI
CCI-002699
Version
SRG-OS-000446-VMM-001790
Vuln IDs
  • V-207507
  • V-57315
Rule IDs
  • SV-207507r854681_rule
  • SV-71575
Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the VMM responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Notifications provided by VMMs include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights.
Checks: C-7764r365925_chk

Verify the VMM performs verification of the correct operation of security functions: upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days. If it does not, this is a finding.

Fix: F-7764r365926_fix

Configure the VMM to perform verification of the correct operation of security functions: upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days.

b
The VMM must shut down, restart, and/or notify the system administrator when anomalies in the operation of any security functions are discovered.
SI-6 - Medium - CCI-002702 - V-207508 - SV-207508r854682_rule
RMF Control
SI-6
Severity
M
CCI
CCI-002702
Version
SRG-OS-000447-VMM-001800
Vuln IDs
  • V-207508
  • V-57317
Rule IDs
  • SV-207508r854682_rule
  • SV-71577
If anomalies are not acted upon, security functions may fail to secure the system. Security function is defined as the hardware, software, and/or firmware of the VMM responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Notifications provided by VMMs include messages to local computer consoles, hardware indications, such as lights, and/or notifying SAs via email or monitoring system traps. This capability must take into account operational requirements for availability when selecting an appropriate response. The organization may choose to shut down or restart the VMM or send notifications to SAs upon security function anomaly detection.
Checks: C-7765r365928_chk

Verify the VMM shuts down, restarts, and/or notifies the system administrator when anomalies in the operation of any security functions are discovered. If it does not, this is a finding.

Fix: F-7765r365929_fix

Configure the VMM to shut down, restart, and/or notify the system administrator when anomalies in the operation of any security functions are discovered.

b
The VMM must generate audit records when successful/unsuccessful attempts to access security objects occur.
AU-12 - Medium - CCI-000172 - V-207509 - SV-207509r380329_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000458-VMM-001810
Vuln IDs
  • V-207509
  • V-57319
Rule IDs
  • SV-207509r380329_rule
  • SV-71579
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7766r365931_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding.

Fix: F-7766r365932_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to access security objects occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to access security levels occur.
AU-12 - Medium - CCI-000172 - V-207510 - SV-207510r380332_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000460-VMM-001820
Vuln IDs
  • V-207510
  • V-57321
Rule IDs
  • SV-207510r380332_rule
  • SV-71581
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7767r365934_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to access security levels occur. If it does not, this is a finding.

Fix: F-7767r365935_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to access security levels occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur.
AU-12 - Medium - CCI-000172 - V-207511 - SV-207511r380335_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000461-VMM-001830
Vuln IDs
  • V-207511
  • V-57323
Rule IDs
  • SV-207511r380335_rule
  • SV-71583
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7768r365937_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding.

Fix: F-7768r365938_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to modify privileges occur.
AU-12 - Medium - CCI-000172 - V-207512 - SV-207512r381448_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000462-VMM-001840
Vuln IDs
  • V-207512
  • V-57325
Rule IDs
  • SV-207512r381448_rule
  • SV-71585
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7769r365940_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding.

Fix: F-7769r365941_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to modify privileges occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to modify security objects occur.
AU-12 - Medium - CCI-000172 - V-207513 - SV-207513r381451_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000463-VMM-001850
Vuln IDs
  • V-207513
  • V-57327
Rule IDs
  • SV-207513r381451_rule
  • SV-71587
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7770r365943_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding.

Fix: F-7770r365944_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to modify security objects occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to modify security levels occur.
AU-12 - Medium - CCI-000172 - V-207514 - SV-207514r381454_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000464-VMM-001860
Vuln IDs
  • V-207514
  • V-57329
Rule IDs
  • SV-207514r381454_rule
  • SV-71589
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7771r365946_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to modify security levels occur. If it does not, this is a finding.

Fix: F-7771r365947_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to modify security levels occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to delete privileges occur.
AU-12 - Medium - CCI-000172 - V-207515 - SV-207515r381460_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000466-VMM-001870
Vuln IDs
  • V-207515
  • V-57331
Rule IDs
  • SV-207515r381460_rule
  • SV-71591
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7772r365949_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding.

Fix: F-7772r365950_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to delete privileges occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to delete security levels occur.
AU-12 - Medium - CCI-000172 - V-207516 - SV-207516r381463_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000467-VMM-001880
Vuln IDs
  • V-207516
  • V-57333
Rule IDs
  • SV-207516r381463_rule
  • SV-71593
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7773r365952_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to delete security levels occur. If it does not, this is a finding.

Fix: F-7773r365953_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to delete security levels occur.

b
The VMM must generate audit records when successful/unsuccessful attempts to delete security objects occur.
AU-12 - Medium - CCI-000172 - V-207517 - SV-207517r381466_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000468-VMM-001890
Vuln IDs
  • V-207517
  • V-57335
Rule IDs
  • SV-207517r381466_rule
  • SV-71595
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7774r365955_chk

Verify the VMM generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding.

Fix: F-7774r365956_fix

Configure the VMM to generate audit records when successful/unsuccessful attempts to delete security objects occur.

b
The VMM must generate audit records when successful/unsuccessful logon attempts occur.
AU-12 - Medium - CCI-000172 - V-207518 - SV-207518r381472_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000470-VMM-001900
Vuln IDs
  • V-207518
  • V-57337
Rule IDs
  • SV-207518r381472_rule
  • SV-71597
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7775r365958_chk

Verify the VMM generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding.

Fix: F-7775r365959_fix

Configure the VMM to generate audit records when successful/unsuccessful logon attempts occur.

b
The VMM must generate audit records for privileged activities or other system-level access.
AU-12 - Medium - CCI-000172 - V-207519 - SV-207519r381475_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000471-VMM-001910
Vuln IDs
  • V-207519
  • V-57339
Rule IDs
  • SV-207519r381475_rule
  • SV-71599
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7776r365961_chk

Verify the VMM generates audit records for privileged activities or other system-level access. If it does not, this is a finding.

Fix: F-7776r365962_fix

Configure the VMM to generate audit records for privileged activities or other system-level access.

b
The VMM must generate audit records showing starting and ending time for user access to the system.
AU-12 - Medium - CCI-000172 - V-207520 - SV-207520r381478_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000472-VMM-001920
Vuln IDs
  • V-207520
  • V-57341
Rule IDs
  • SV-207520r381478_rule
  • SV-71601
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7777r365964_chk

Verify the VMM generates audit records showing starting and ending time for user access to the system. If it does not, this is a finding.

Fix: F-7777r365965_fix

Configure the VMM to generate audit records showing starting and ending time for user access to the system.

b
The VMM must generate audit records when concurrent logons from different workstations occur.
AU-12 - Medium - CCI-000172 - V-207521 - SV-207521r381481_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000473-VMM-001930
Vuln IDs
  • V-207521
  • V-57343
Rule IDs
  • SV-207521r381481_rule
  • SV-71603
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7778r365967_chk

Verify the VMM generates audit records when concurrent logons from different workstations occur. If it does not, this is a finding.

Fix: F-7778r365968_fix

Configure the VMM to generate audit records when concurrent logons from different workstations occur.

b
The VMM must generate audit records when successful/unsuccessful accesses to objects occur.
AU-12 - Medium - CCI-000172 - V-207522 - SV-207522r381484_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000474-VMM-001940
Vuln IDs
  • V-207522
  • V-57345
Rule IDs
  • SV-207522r381484_rule
  • SV-71605
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7779r365970_chk

Verify the VMM generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding.

Fix: F-7779r365971_fix

Configure the VMM to generate audit records when successful/unsuccessful accesses to objects occur.

b
The VMM must generate audit records for all direct access to the VMM.
AU-12 - Medium - CCI-000172 - V-207523 - SV-207523r381487_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000475-VMM-001950
Vuln IDs
  • V-207523
  • V-57347
Rule IDs
  • SV-207523r381487_rule
  • SV-71607
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7780r365973_chk

Verify the VMM generates audit records for all direct access to the VMM. If it does not, this is a finding.

Fix: F-7780r365974_fix

Configure the VMM to generate audit records for all direct access to the VMM.

b
The VMM must generate audit records for all account creations, modifications, disabling, and termination events.
AU-12 - Medium - CCI-000172 - V-207524 - SV-207524r381490_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000476-VMM-001960
Vuln IDs
  • V-207524
  • V-57349
Rule IDs
  • SV-207524r381490_rule
  • SV-71609
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7781r365976_chk

Verify the VMM generates audit records for all account creations, modifications, disabling, and termination events. If it does not, this is a finding.

Fix: F-7781r365977_fix

Configure the VMM to generate audit records for all account creations, modifications, disabling, and termination events.

b
The VMM must generate audit records for all module load, unload, and restart actions, and also for all program and guest VM initiations.
AU-12 - Medium - CCI-000172 - V-207525 - SV-207525r381493_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
SRG-OS-000477-VMM-001970
Vuln IDs
  • V-207525
  • V-57351
Rule IDs
  • SV-207525r381493_rule
  • SV-71611
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the VMM (e.g., module or policy filter).
Checks: C-7782r365979_chk

Verify the VMM generates audit records for all module load, unload, and restart actions, and also for all program and guest VM initiations. If it does not, this is a finding.

Fix: F-7782r365980_fix

Configure the VMM to generate audit records for all module load, unload, and restart actions, and also for all program and guest VM initiations.

b
The VMM must implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.
SC-13 - Medium - CCI-002450 - V-207526 - SV-207526r878146_rule
RMF Control
SC-13
Severity
M
CCI
CCI-002450
Version
SRG-OS-000478-VMM-001980
Vuln IDs
  • V-207526
  • V-57353
Rule IDs
  • SV-207526r878146_rule
  • SV-71613
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The VMM must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
Checks: C-7783r878144_chk

Verify the VMM implements NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. If it does not, this is a finding.

Fix: F-7783r878145_fix

Configure the VMM to implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

b
The VMM must, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly.
AU-4 - Medium - CCI-001851 - V-207527 - SV-207527r854686_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001851
Version
SRG-OS-000479-VMM-001990
Vuln IDs
  • V-207527
  • V-57355
Rule IDs
  • SV-207527r854686_rule
  • SV-71615
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in VMMs with limited audit storage capacity.
Checks: C-7784r365985_chk

Verify the VMM, at a minimum, off-loads interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding.

Fix: F-7784r365986_fix

Configure the VMM to, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly.

b
The VMM must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.
CM-6 - Medium - CCI-000366 - V-207528 - SV-207528r388482_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
SRG-OS-000480-VMM-002000
Vuln IDs
  • V-207528
  • V-57357
Rule IDs
  • SV-207528r388482_rule
  • SV-71617
Configuring the VMM to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.
Checks: C-7785r365988_chk

Verify the VMM is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it does not, this is a finding.

Fix: F-7785r365989_fix

Configure the VMM to be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.

b
The VMM must protect the confidentiality and integrity of communications with wireless peripherals.
SC-8 - Medium - CCI-002418 - V-207529 - SV-207529r916433_rule
RMF Control
SC-8
Severity
M
CCI
CCI-002418
Version
SRG-OS-000481-VMM-002010
Vuln IDs
  • V-207529
  • V-64707
Rule IDs
  • SV-207529r916433_rule
  • SV-79197
Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the VMM. This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with a VMM. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR keyboards, mice, pointing devices, and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DoD requirements for wireless data transmission and be approved for use by the AO. Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that needs to be protected, modification of communications with these wireless peripherals may be used to compromise the VMM. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required.
Checks: C-7786r365991_chk

Verify the VMM protects the confidentiality and integrity of communications with wireless peripherals. If it does not, this is a finding.

Fix: F-7786r365992_fix

Configure the VMM to protect the confidentiality and integrity of communications with wireless peripherals.