Skip to content

General Purpose Operating System Security Requirements Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

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

    Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is hel...
    Rule Low Severity
  • The operating system must retain a users session lock until that 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 information system but does not want to log out because of the temporary...
    Rule Medium Severity
  • The operating system must monitor remote access methods.

    Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access man...
    Rule Medium Severity
  • The operating system must produce audit records containing information to establish what type of events occurred.

    Without establishing what type 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 nec...
    Rule Medium Severity
  • The operating system must produce audit records containing information to establish where the events occurred.

    Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment ...
    Rule Medium Severity
  • The operating system 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
  • The operating system must produce audit records containing the individual identities of group account users.

    Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the individual identities of gro...
    Rule Medium Severity
  • The operating system must provide the capability to centrally review and analyze audit records from multiple components within the system.

    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 proficien...
    Rule Medium Severity
  • The operating system must provide 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
  • The operating system must protect audit information from unauthorized read access.

    Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. Audit information includes all information (e.g., audit recor...
    Rule Medium Severity
  • The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system 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 rec...
    Rule Medium Severity
  • The operating system, for PKI-based authentication, must enforce authorized access to the corresponding private key.

    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 us...
    Rule Medium Severity
  • The operating system must enforce password complexity by requiring that at least one lowercase character be used.

    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 resistin...
    Rule Medium Severity
  • The operating system must require the change of at least 50 percent of the total number of characters when passwords are changed.

    If the operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attemp...
    Rule Medium Severity
  • The operating system must transmit only encrypted representations of passwords.

    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 c...
    Rule High Severity
  • Operating systems must enforce a 60-day maximum password lifetime restriction.

    Any password, no matter how complex, can eventually be cracked; therefore, passwords need to be changed periodically. If the operating system does not limit the lifetime of passwords and force user...
    Rule Medium Severity
  • The operating system must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

    To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback from the operating system shall not provide any information allowing an un...
    Rule Medium Severity
  • The operating system must be configured to disable non-essential capabilities.

    It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooke...
    Rule Medium Severity
  • 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.

    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...
    Rule Medium Severity
  • The operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users).

    To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational user...
    Rule Medium Severity
  • The operating system must use multifactor authentication for network access to non-privileged accounts.

    To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor auth...
    Rule Medium Severity
  • The operating system must use multifactor authentication for local access to nonprivileged accounts.

    To ensure accountability, prevent unauthenticated access, and prevent misuse of the system, nonprivileged users must utilize multifactor authentication for local access. Multifactor authentication...
    Rule Medium Severity
  • The operating system must implement replay-resistant authentication mechanisms for network access to privileged accounts.

    A replay attack may enable an unauthorized user to gain access to the operating system. Authentication sessions between the authenticator and the operating system validating the user credentials mu...
    Rule Medium Severity
  • The operating system must implement replay-resistant authentication mechanisms for network access to nonprivileged accounts.

    A replay attack may enable an unauthorized user to gain access to the operating system. Authentication sessions between the authenticator and the operating system validating the user credentials mu...
    Rule Medium Severity
  • The operating system must uniquely identify peripherals before establishing a connection.

    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, ...
    Rule Medium Severity
  • 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.

    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 ...
    Rule Medium Severity
  • The operating system must uniquely identify and must authenticate non-organizational users (or processes acting on behalf of non-organizational users).

    Lack of authentication and identification enables non-organizational users to gain access to the application or possibly other information systems and provides an opportunity for intruders to compr...
    Rule Medium Severity
  • The operating system must provide an audit reduction capability that supports on-demand reporting requirements.

    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 neede...
    Rule Medium Severity
  • The information system must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.

    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...
    Rule Medium Severity
  • The operating system must separate user functionality (including user interface services) from operating system management functionality.

    Operating system management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access operating system management fu...
    Rule Medium Severity
  • 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.

    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 ex...
    Rule Medium Severity
  • The operating system must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

    Any operating system 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 t...
    Rule Medium Severity
  • Any publically accessible connection to the operating system 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 publicly accessible operating system ensures privacy and security notification verbiage used is consistent with...
    Rule Medium Severity
  • The operating system must audit all account modifications.

    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 exi...
    Rule Medium Severity
  • The operating system must audit all account disabling actions.

    When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In ...
    Rule Medium Severity
  • The operating system must produce audit records containing information to establish the identity of any individual or process associated with the event.

    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...
    Rule Medium Severity
  • The operating system must protect audit tools from unauthorized access.

    Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operatio...
    Rule Medium Severity
  • The operating system must protect audit tools from unauthorized modification.

    Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operatio...
    Rule Medium Severity
  • In the event of a system failure, the operating system must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.

    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, i...
    Rule Medium Severity
  • The operating system must notify system administrators and ISSOs when accounts are created.

    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 create a new ...
    Rule Medium Severity
  • The operating system must notify system administrators and ISSOs when accounts are modified.

    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 exi...
    Rule Medium Severity
  • The operating system must notify system administrators and ISSOs when accounts are disabled.

    When operating system accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual operating system users or for identifying the operating system processe...
    Rule Medium Severity
  • The operating system must notify system administrators and ISSOs when accounts are removed.

    When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual operating system users or for identifying the operating system processes...
    Rule Medium Severity
  • The operating system must use cryptographic mechanisms to protect the integrity of audit tools.

    Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit recor...
    Rule High Severity
  • The operating system must automatically terminate a user session after inactivity time-outs have expired or at shutdown.

    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....
    Rule Medium Severity
  • The operating system must provide a logoff capability for user-initiated communications sessions when requiring user access authentication.

    If a user cannot explicitly end an operating system session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Information resources to which us...
    Rule Medium Severity
  • The operating system must control remote access methods.

    Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access manage...
    Rule Medium Severity
  • The operating system must protect wireless access to and from the system using encryption.

    Allowing devices and users to connect to or from the system without first authenticating them allows untrusted access and can lead to a compromise or attack. Since wireless communications can be in...
    Rule Medium Severity
  • The operating system must notify system administrators (SAs) and information system security officers (ISSOs) of account enabling actions.

    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 enable an exis...
    Rule Medium Severity
  • The operating system must allow operating system admins to pass information to any other operating system admin or user.

    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...
    Rule Medium Severity

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