II - Mission Support Classified
Rules and Groups employed by this XCCDF Profile
-
SRG-OS-000106
<GroupDescription></GroupDescription>Group -
The VMM must use multifactor authentication for network access to non-privileged accounts.
<VulnDiscussion>To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to ...Rule Medium Severity -
SRG-OS-000107
<GroupDescription></GroupDescription>Group -
The VMM must use multifactor authentication for local access to privileged accounts.
<VulnDiscussion>To assure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prev...Rule Medium Severity -
SRG-OS-000108
<GroupDescription></GroupDescription>Group -
The VMM must use multifactor authentication for local access to non-privileged accounts.
<VulnDiscussion> To assure accountability, prevent unauthenticated access, and prevent misuse of the system, privileged users must utilize mu...Rule Medium Severity -
SRG-OS-000109
<GroupDescription></GroupDescription>Group -
The VMM must require individuals to be authenticated with an individual authenticator prior to using a group authenticator.
<VulnDiscussion> To assure individual accountability and prevent unauthorized access, organizational users shall be individually identified a...Rule Medium Severity -
SRG-OS-000112
<GroupDescription></GroupDescription>Group -
The VMM must implement replay-resistant authentication mechanisms for network access to privileged accounts.
<VulnDiscussion>A replay attack may enable an unauthorized user to gain access to the VMM. Authentication sessions between the authenticator ...Rule Medium Severity -
SRG-OS-000113
<GroupDescription></GroupDescription>Group -
The VMM must implement replay-resistant authentication mechanisms for network access to non-privileged accounts.
<VulnDiscussion>A replay attack may enable an unauthorized user to gain access to the VMM. Authentication sessions between the authenticator ...Rule Medium Severity -
SRG-OS-000114
<GroupDescription></GroupDescription>Group -
The VMM must uniquely identify peripherals before establishing a connection.
<VulnDiscussion>Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Per...Rule Medium Severity -
SRG-OS-000118
<GroupDescription></GroupDescription>Group -
The VMM must disable local account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.
<VulnDiscussion>Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potenti...Rule Medium Severity -
SRG-OS-000120
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be r...Rule Medium Severity -
SRG-OS-000122
<GroupDescription></GroupDescription>Group -
The VMM must support an audit reduction capability that supports on-demand reporting requirements.
<VulnDiscussion>The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly faci...Rule Medium Severity -
SRG-OS-000123
<GroupDescription></GroupDescription>Group -
The VMM must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.
<VulnDiscussion>Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid ac...Rule Medium Severity -
SRG-OS-000125
<GroupDescription></GroupDescription>Group -
The VMM must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.
<VulnDiscussion>If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the syst...Rule Medium Severity -
SRG-OS-000126
<GroupDescription></GroupDescription>Group -
The VMM must terminate all sessions and network connections when nonlocal maintenance is completed.
<VulnDiscussion>If a maintenance session or connection remains open after maintenance is completed, it may be hijacked by an attacker and use...Rule Medium Severity -
SRG-OS-000132
<GroupDescription></GroupDescription>Group -
The VMM must separate user functionality (including user interface services) from VMM management functionality.
<VulnDiscussion>VMM management functionality includes functions necessary for administration and requires privileged user access. Allowing no...Rule Medium Severity -
SRG-OS-000134
<GroupDescription></GroupDescription>Group -
The VMM must isolate security functions from non-security functions.
<VulnDiscussion>An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform...Rule Medium Severity -
SRG-OS-000138
<GroupDescription></GroupDescription>Group -
The VMM must prevent unauthorized and unintended information transfer via shared system resources.
<VulnDiscussion> Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of info...Rule Medium Severity -
SRG-OS-000142
<GroupDescription></GroupDescription>Group -
The VMM must manage excess capacity, bandwidth, or other redundancy to limit the effects of information-flooding types of Denial of Service (DoS) attacks.
<VulnDiscussion>DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot ac...Rule Medium Severity -
SRG-OS-000163
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take c...Rule Medium Severity -
SRG-OS-000184
<GroupDescription></GroupDescription>Group -
The VMM must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
<VulnDiscussion>Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized acces...Rule Medium Severity -
SRG-OS-000185
<GroupDescription></GroupDescription>Group -
The VMM must protect the confidentiality and integrity of all information at rest.
<VulnDiscussion>Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and...Rule Medium Severity -
SRG-OS-000191
<GroupDescription></GroupDescription>Group -
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).
<VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the VMM or other sy...Rule Medium Severity -
SRG-OS-000203
<GroupDescription></GroupDescription>Group -
The VMM must check the validity of all data inputs except those specifically identified by the organization.
<VulnDiscussion>Invalid user input occurs when a user inserts data or characters into data entry fields and the VMM is unprepared to process ...Rule Medium Severity -
SRG-OS-000205
<GroupDescription></GroupDescription>Group -
The VMM must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
<VulnDiscussion>Any VMM providing too much information in error messages risks compromising the data and security of the structure, and conte...Rule Medium Severity -
SRG-OS-000206
<GroupDescription></GroupDescription>Group -
The VMM must reveal system error messages only to authorized users.
<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an orga...Rule Medium Severity -
SRG-OS-000221
<GroupDescription></GroupDescription>Group -
All interactions among guest VMs must be mediated by the VMM or its service VMs to support proper function.
<VulnDiscussion>Mechanisms to detect and prevent unauthorized communication flow must be configured or provided as part of the VMM design. If...Rule Medium Severity
Node 2
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.