I - Mission Critical Classified
Rules and Groups employed by this XCCDF Profile
-
SRG-OS-000106
<GroupDescription></GroupDescription>Group -
The operating system 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 operating system 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 operating system must use multifactor authentication for local access to non-privileged accounts.
<VulnDiscussion>To assure accountability, prevent unauthenticated access, and prevent misuse of the system, non-privileged users must utilize...Rule Medium Severity -
SRG-OS-000109
<GroupDescription></GroupDescription>Group -
The operating system 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 must be individually identified and...Rule Medium Severity -
SRG-OS-000112
<GroupDescription></GroupDescription>Group -
The operating system 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 operating system. Authentication sessions between the a...Rule Medium Severity -
SRG-OS-000113
<GroupDescription></GroupDescription>Group -
The operating system 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 operating system. Authentication sessions between the a...Rule Medium Severity -
SRG-OS-000114
<GroupDescription></GroupDescription>Group -
The operating system 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 operating system must disable 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 operating system 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-000121
<GroupDescription></GroupDescription>Group -
The operating system must uniquely identify and must authenticate non-organizational users (or processes acting on behalf of non-organizational users).
<VulnDiscussion>Lack of authentication and identification enables non-organizational users to gain access to the application or possibly othe...Rule Medium Severity -
SRG-OS-000122
<GroupDescription></GroupDescription>Group -
The operating system must provide 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 information system 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 acc...Rule Medium Severity -
SRG-OS-000125
<GroupDescription></GroupDescription>Group -
The operating system 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 High Severity -
SRG-OS-000126
<GroupDescription></GroupDescription>Group -
The operating system must terminate all sessions and network connections related to nonlocal maintenance 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 us...Rule Medium Severity -
SRG-OS-000132
<GroupDescription></GroupDescription>Group -
The operating system must separate user functionality (including user interface services) from operating system management functionality.
<VulnDiscussion>Operating system management functionality includes functions necessary for administration and requires privileged user access...Rule Medium Severity -
SRG-OS-000134
<GroupDescription></GroupDescription>Group -
The operating system must isolate security functions from nonsecurity 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 -
Operating systems 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 infor...Rule Medium Severity -
SRG-OS-000142
<GroupDescription></GroupDescription>Group -
The operating system 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 operating system 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 operating system 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 operating system 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 operating system must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, 30 days, 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 operating syste...Rule Medium Severity -
SRG-OS-000205
<GroupDescription></GroupDescription>Group -
The operating system must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
<VulnDiscussion> Any operating system providing too much information in error messages risks compromising the data and security of the struct...Rule Medium Severity -
SRG-OS-000206
<GroupDescription></GroupDescription>Group -
The operating system must reveal 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-000228
<GroupDescription></GroupDescription>Group -
Any publically accessible connection to the operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
<VulnDiscussion>Display of a standardized and approved use notification before granting access to the publicly accessible operating system en...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.