Skip to content

Virtual Machine Manager Security Requirements Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-OS-000001

    Group
  • The VMM must provide automated mechanisms for supporting account management functions.

    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 a...
    Rule Medium Severity
  • SRG-OS-000002

    Group
  • The VMM must automatically remove or disable local temporary user accounts after 72 hours.

    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 al...
    Rule Medium Severity
  • SRG-OS-000003

    Group
  • SRG-OS-000004

    Group
  • The VMM must automatically audit account creation.

    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...
    Rule Medium Severity
  • SRG-OS-000021

    Group
  • The VMM must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.

    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 acco...
    Rule Medium Severity
  • SRG-OS-000023

    Group
  • The VMM must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.

    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, Executi...
    Rule Medium Severity
  • SRG-OS-000024

    Group
  • SRG-OS-000027

    Group
  • The VMM must limit the number of concurrent sessions to ten for all accounts and/or account types.

    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 r...
    Rule Medium Severity
  • SRG-OS-000028

    Group
  • The VMM must retain the session lock until the user reestablishes access using established identification and authentication procedures.

    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...
    Rule Medium Severity
  • SRG-OS-000029

    Group
  • The VMM must initiate a session lock after a 15-minute period of inactivity.

    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...
    Rule Medium Severity
  • SRG-OS-000030

    Group
  • The VMM must provide the capability for users to directly initiate a session lock.

    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 ...
    Rule Medium Severity
  • SRG-OS-000031

    Group
  • SRG-OS-000032

    Group
  • The VMM must monitor remote access methods automatically.

    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....
    Rule Medium Severity
  • SRG-OS-000033

    Group
  • The VMM must use DoD-approved encryption to protect the confidentiality of remote access sessions.

    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 a...
    Rule Medium Severity
  • SRG-OS-000037

    Group
  • The VMM must produce audit records containing information to establish what type of events occurred.

    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 n...
    Rule Medium Severity
  • SRG-OS-000038

    Group
  • The VMM must produce audit records containing information to establish when (date and time) the events occurred.

    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 an...
    Rule Medium Severity
  • SRG-OS-000039

    Group
  • SRG-OS-000040

    Group
  • The VMM must produce audit records containing information to establish the source of the events.

    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...
    Rule Medium Severity
  • SRG-OS-000041

    Group
  • The VMM must produce audit records containing information to establish the outcome of the events.

    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 sy...
    Rule Medium Severity
  • SRG-OS-000042

    Group
  • SRG-OS-000046

    Group
  • The VMM must alert the ISSO and SA (at a minimum) in the event of an audit processing failure.

    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 im...
    Rule Medium Severity
  • SRG-OS-000051

    Group
  • SRG-OS-000054

    Group
  • The VMM must support the capability to filter audit records for events of interest based upon all audit fields within audit records.

    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 ent...
    Rule Medium Severity
  • SRG-OS-000055

    Group
  • The VMM must use internal system clocks to generate time stamps for audit records.

    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 ti...
    Rule Medium Severity
  • SRG-OS-000057

    Group
  • The VMM must protect audit information from unauthorized read access.

    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 confide...
    Rule Medium Severity
  • SRG-OS-000058

    Group
  • The VMM must protect audit information from unauthorized modification.

    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 audi...
    Rule Medium Severity
  • SRG-OS-000059

    Group
  • SRG-OS-000062

    Group
  • The VMM must provide audit record generation capability for DoD-defined auditable events for all VMM components.

    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 re...
    Rule Medium Severity
  • SRG-OS-000063

    Group

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules