Skip to content
ATO Pathways
  Log In

General Purpose Operating System Security Requirements Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • The operating system must enforce a minimum 15-character password length.

    <VulnDiscussion>The shorter the password, the lower the number of possible combinations that need to be tested before the password is comprom...
    Rule Medium Severity
    Show

  • SRG-OS-000079

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

    &lt;VulnDiscussion&gt;To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback fr...
    Rule Medium Severity
    Show

  • SRG-OS-000080

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

    &lt;VulnDiscussion&gt;To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-ap...
    Rule Medium Severity
    Show

  • SRG-OS-000095

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must be configured to disable non-essential capabilities.

    &lt;VulnDiscussion&gt;It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission ob...
    Rule Medium Severity
    Show

  • SRG-OS-000096

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system 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.

    &lt;VulnDiscussion&gt;In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e....
    Rule Medium Severity
    Show

  • The operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users).

    &lt;VulnDiscussion&gt;To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to pre...
    Rule Medium Severity
    Show

  • SRG-OS-000105

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must use multifactor authentication for network access to privileged accounts.

    &lt;VulnDiscussion&gt;Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor ...
    Rule Medium Severity
    Show

  • SRG-OS-000106

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must use multifactor authentication for network access to non-privileged accounts.

    &lt;VulnDiscussion&gt;To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to ...
    Rule Medium Severity
    Show

  • SRG-OS-000107

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must use multifactor authentication for local access to privileged accounts.

    &lt;VulnDiscussion&gt;To ensure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prev...
    Rule Medium Severity
    Show

  • SRG-OS-000108

    <GroupDescription></GroupDescription>
    Group
    Show

  • SRG-OS-000240

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must use multifactor authentication for local access to nonprivileged accounts.

    &lt;VulnDiscussion&gt;To ensure accountability, prevent unauthenticated access, and prevent misuse of the system, nonprivileged users must utilize ...
    Rule Medium Severity
    Show

  • SRG-OS-000109

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must require individuals to be authenticated with an individual authenticator prior to using a group authenticator.

    &lt;VulnDiscussion&gt;To ensure individual accountability and prevent unauthorized access, organizational users must be individually identified and...
    Rule Medium Severity
    Show

  • SRG-OS-000112

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must implement replay-resistant authentication mechanisms for network access to privileged accounts.

    &lt;VulnDiscussion&gt;A replay attack may enable an unauthorized user to gain access to the operating system. Authentication sessions between the a...
    Rule Medium Severity
    Show

  • SRG-OS-000113

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must implement replay-resistant authentication mechanisms for network access to nonprivileged accounts.

    &lt;VulnDiscussion&gt;A replay attack may enable an unauthorized user to gain access to the operating system. Authentication sessions between the a...
    Rule Medium Severity
    Show

  • SRG-OS-000114

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must uniquely identify peripherals before establishing a connection.

    &lt;VulnDiscussion&gt;Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Per...
    Rule Medium Severity
    Show

  • SRG-OS-000118

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.

    &lt;VulnDiscussion&gt;Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potenti...
    Rule Medium Severity
    Show

  • SRG-OS-000120

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be r...
    Rule Medium Severity
    Show

  • SRG-OS-000121

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must uniquely identify and must authenticate non-organizational users (or processes acting on behalf of non-organizational users).

    &lt;VulnDiscussion&gt;Lack of authentication and identification enables non-organizational users to gain access to the application or possibly othe...
    Rule Medium Severity
    Show

  • SRG-OS-000122

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must provide an audit reduction capability that supports on-demand reporting requirements.

    &lt;VulnDiscussion&gt;The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly faci...
    Rule Medium Severity
    Show

  • SRG-OS-000123

    <GroupDescription></GroupDescription>
    Group
    Show

  • The information system must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.

    &lt;VulnDiscussion&gt;Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid acc...
    Rule Medium Severity
    Show

  • SRG-OS-000125

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.

    &lt;VulnDiscussion&gt;If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the syst...
    Rule High Severity
    Show

  • SRG-OS-000132

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must separate user functionality (including user interface services) from operating system management functionality.

    &lt;VulnDiscussion&gt;Operating system management functionality includes functions necessary for administration and requires privileged user access...
    Rule Medium Severity
    Show

  • SRG-OS-000134

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

    &lt;VulnDiscussion&gt;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
    Show

  • SRG-OS-000185

    <GroupDescription></GroupDescription>
    Group
    Show

  • SRG-OS-000278

    <GroupDescription></GroupDescription>
    Group
    Show

  • The operating system must isolate security functions from nonsecurity functions.

    &lt;VulnDiscussion&gt;An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform...
    Rule Medium Severity
    Show

  • SRG-OS-000138

    <GroupDescription></GroupDescription>
    Group
    Show

  • Operating systems must prevent unauthorized and unintended information transfer via shared system resources.

    &lt;VulnDiscussion&gt;Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of infor...
    Rule Medium Severity
    Show

  • SRG-OS-000142

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot ac...
    Rule Medium Severity
    Show

Node 2

siemur/test-space

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