General Purpose Operating System Security Requirements Guide
Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]
Details
Version / Release: V2R5
Published: 2022-11-21
Updated At: 2023-01-25 00:40:47
Compare/View Releases
Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Actions
Download
Filter
Findings
| Severity | Open | Not Reviewed | Not Applicable | Not a Finding |
|---|---|---|---|---|
| Overall | 0 | 0 | 0 | 0 |
| Low | 0 | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 | 0 |
| High | 0 | 0 | 0 | 0 |
Drop CKL or SCAP (XCCDF) results here.
| Vuln | Rule | Version | CCI | Severity | Title | Description | Status | Finding Details | Comments |
|---|---|---|---|---|---|---|---|---|---|
| SV-203591r557031_rule | SRG-OS-000001-GPOS-00001 | CCI-000015 | MEDIUM | The operating system 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 errors. A comprehensive account management process that includes automation helps t | ||||
| SV-203592r557034_rule | SRG-OS-000002-GPOS-00002 | CCI-000016 | MEDIUM | The operating system must automatically remove or disable 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 all temporary accounts must be set upon account creation. T | ||||
| SV-203593r557037_rule | SRG-OS-000004-GPOS-00004 | CCI-000018 | MEDIUM | The operating system must audit all account creations. | 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 an account. Auditing account creation actions provides logging th | ||||
| SV-203594r557040_rule | SRG-OS-000021-GPOS-00005 | CCI-000044 | MEDIUM | The operating system 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 logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. | ||||
| SV-203595r557043_rule | SRG-OS-000023-GPOS-00006 | CCI-000048 | MEDIUM | The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, | ||||
| SV-203596r557046_rule | SRG-OS-000024-GPOS-00007 | CCI-000050 | MEDIUM | The operating system must display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access. | The banner must be acknowledged by the user prior to allowing the user access to the operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user | ||||
| SV-203597r877399_rule | SRG-OS-000027-GPOS-00008 | CCI-000054 | LOW | 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 helpful in reducing the risks related to DoS attacks. This r | ||||
| SV-203598r557052_rule | SRG-OS-000028-GPOS-00009 | CCI-000056 | MEDIUM | 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 nature of the absence. The session lock is implemented a | ||||
| SV-203599r557055_rule | SRG-OS-000029-GPOS-00010 | CCI-000057 | MEDIUM | The operating system must initiate a session lock after a 15-minute period of inactivity for all connection types. | 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 information system but does not log out because of the temporary nature of the absence. Rather than relying on the user t | ||||
| SV-203600r557058_rule | SRG-OS-000030-GPOS-00011 | CCI-000058 | MEDIUM | The operating system must provide the capability for users to directly initiate a session lock for all connection types. | 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 nature of the absence. The session lock is implemented a | ||||
| SV-203601r557061_rule | SRG-OS-000031-GPOS-00012 | CCI-000060 | MEDIUM | The operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image. | 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 log out because of the temporary nature of the absence. The session lock is implemented at the po | ||||
| SV-203602r557064_rule | SRG-OS-000032-GPOS-00013 | CCI-000067 | MEDIUM | 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 management difficult at best. Remote access is access to DoD | ||||
| SV-203603r877398_rule | SRG-OS-000033-GPOS-00014 | CCI-000068 | HIGH | The operating system must implement 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 nonpublic information systems by an authorized user (or an information system) co | ||||
| SV-203604r557070_rule | SRG-OS-000037-GPOS-00015 | CCI-000130 | MEDIUM | 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 necessary to satisfy this requirement includes, for example, | ||||
| SV-203605r557073_rule | SRG-OS-000038-GPOS-00016 | CCI-000131 | MEDIUM | The operating system must produce audit records containing information to establish when (date and time) the events occurred. | Without establishing when 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 and provide forensic analysis, it is essential for security | ||||
| SV-203606r557076_rule | SRG-OS-000039-GPOS-00017 | CCI-000132 | MEDIUM | 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 and provide forensic analysis, it is essential for securit | ||||
| SV-203607r557079_rule | SRG-OS-000040-GPOS-00018 | CCI-000133 | MEDIUM | The operating system must produce audit records containing information to establish the source of the events. | Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In addition to logging where events occur within the operating system, the operating system must also ge | ||||
| SV-203608r557082_rule | SRG-OS-000041-GPOS-00019 | CCI-000134 | MEDIUM | 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 system. Event outcomes can include indicators of event succ | ||||
| SV-203609r557085_rule | SRG-OS-000042-GPOS-00020 | CCI-000135 | MEDIUM | The operating system must generate audit records containing the full-text recording of privileged commands. | 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 full-text recording of privileged commands. The organization must maintain audit trail | ||||
| SV-203610r557088_rule | SRG-OS-000042-GPOS-00021 | CCI-000135 | MEDIUM | 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 group users. The organization must maintain audit trails in s | ||||
| SV-203611r557091_rule | SRG-OS-000046-GPOS-00022 | CCI-000139 | MEDIUM | The operating system 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 system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system oper | ||||
| SV-203612r557094_rule | SRG-OS-000047-GPOS-00023 | CCI-000140 | MEDIUM | The operating system must shut down by default upon audit failure (unless availability is an overriding concern). | It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and au | ||||
| SV-203613r557097_rule | SRG-OS-000051-GPOS-00024 | CCI-000154 | MEDIUM | 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 proficient manner. If the operating system does not provide the abi | ||||
| SV-203614r557100_rule | SRG-OS-000054-GPOS-00025 | CCI-000158 | MEDIUM | 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 entries that are of little or no consequence to the investiga | ||||
| SV-203615r557103_rule | SRG-OS-000055-GPOS-00026 | CCI-000159 | MEDIUM | The operating system 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 time a particular event occurred on a system is critical when | ||||
| SV-203616r557574_rule | SRG-OS-000057-GPOS-00027 | CCI-000162 | MEDIUM | 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 records, audit settings, audit reports) needed to successfully | ||||
| SV-203617r557577_rule | SRG-OS-000058-GPOS-00028 | CCI-000163 | MEDIUM | The operating system must protect audit information from unauthorized modification. | If audit information 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 audit information, the operating system must protect aud | ||||
| SV-203618r557580_rule | SRG-OS-000059-GPOS-00029 | CCI-000164 | MEDIUM | The operating system must protect audit information from unauthorized deletion. | If audit information 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 audit information, the operating system must protect aud | ||||
| SV-203619r557583_rule | SRG-OS-000062-GPOS-00031 | CCI-000169 | MEDIUM | 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 records can be generated from various components within the i | ||||
| SV-203620r557586_rule | SRG-OS-000063-GPOS-00032 | CCI-000171 | MEDIUM | The operating system must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming th | ||||
| SV-203621r557589_rule | SRG-OS-000064-GPOS-00033 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203622r557592_rule | SRG-OS-000066-GPOS-00034 | CCI-000185 | MEDIUM | The operating system, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. | Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is | ||||
| SV-203623r557595_rule | SRG-OS-000067-GPOS-00035 | CCI-000186 | MEDIUM | 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 used to encrypt or digitally sign information. If the priva | ||||
| SV-203624r557598_rule | SRG-OS-000068-GPOS-00036 | CCI-000187 | MEDIUM | The operating system must map the authenticated identity to the user or group account for PKI-based authentication. | Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. | ||||
| SV-203625r557601_rule | SRG-OS-000069-GPOS-00037 | CCI-000192 | MEDIUM | The operating system must enforce password complexity by requiring that at least one upper-case 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 resisting attempts at guessing and brute-force attacks. Password | ||||
| SV-203626r557604_rule | SRG-OS-000070-GPOS-00038 | CCI-000193 | MEDIUM | The operating system must enforce password complexity by requiring that at least one lower-case 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 resisting attempts at guessing and brute-force attacks. Password | ||||
| SV-203627r557607_rule | SRG-OS-000071-GPOS-00039 | CCI-000194 | MEDIUM | The operating system must enforce password complexity by requiring that at least one numeric 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 resisting attempts at guessing and brute-force attacks. Password | ||||
| SV-203628r557610_rule | SRG-OS-000072-GPOS-00040 | CCI-000195 | MEDIUM | The operating system must require the change of at least 50% 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 attempts at guessing and brute-force attacks. The number of cha | ||||
| SV-203629r877397_rule | SRG-OS-000073-GPOS-00041 | CCI-000196 | HIGH | The operating system must store 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 compromised. | ||||
| SV-203630r877396_rule | SRG-OS-000074-GPOS-00042 | CCI-000197 | HIGH | 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 compromised. | ||||
| SV-203631r557619_rule | SRG-OS-000075-GPOS-00043 | CCI-000198 | MEDIUM | Operating systems must enforce 24 hours/1 day as the minimum password lifetime. | Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, then the password could be repeate | ||||
| SV-203632r557622_rule | SRG-OS-000076-GPOS-00044 | CCI-000199 | MEDIUM | 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 users to change their passwords, there is the risk that the op | ||||
| SV-203633r557625_rule | SRG-OS-000077-GPOS-00045 | CCI-000200 | MEDIUM | The operating system must prohibit password reuse for a minimum of five generations. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password | ||||
| SV-203634r557628_rule | SRG-OS-000078-GPOS-00046 | CCI-000205 | MEDIUM | The operating system must enforce a minimum 15-character password length. | The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and bru | ||||
| SV-203635r557631_rule | SRG-OS-000079-GPOS-00047 | CCI-000206 | MEDIUM | 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 unauthorized user to compromise the authentication mechanism | ||||
| SV-203636r557634_rule | SRG-OS-000080-GPOS-00048 | CCI-000213 | MEDIUM | The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. | To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods | ||||
| SV-203637r557638_rule | SRG-OS-000095-GPOS-00049 | CCI-000381 | MEDIUM | 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 overlooked and therefore may remain unsecured. They increase the ri | ||||
| SV-203638r557642_rule | SRG-OS-000096-GPOS-00050 | CCI-000382 | MEDIUM | 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 or restrict unused or unnecessary physical and logical po | ||||
| SV-203639r557645_rule | SRG-OS-000104-GPOS-00051 | CCI-000764 | MEDIUM | 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 users include organizational employees or individuals the orga | ||||
| SV-203640r557648_rule | SRG-OS-000105-GPOS-00052 | CCI-000765 | MEDIUM | The operating system must use multifactor authentication for network access to privileged accounts. | Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: 1) something a user knows (e.g., p | ||||
| SV-203641r557170_rule | SRG-OS-000106-GPOS-00053 | CCI-000766 | MEDIUM | 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 authentication uses two or more factors to achieve authenticat | ||||
| SV-203642r557173_rule | SRG-OS-000107-GPOS-00054 | CCI-000767 | MEDIUM | The operating system must use multifactor authentication for local access to privileged accounts. | To assure accountability and prevent unauthenticated access, privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication is defined as using two or more factors to achieve | ||||
| SV-203643r557176_rule | SRG-OS-000108-GPOS-00055 | CCI-000768 | MEDIUM | The operating system must use multifactor authentication for local access to non-privileged accounts. | To assure accountability, prevent unauthenticated access, and prevent misuse of the system, non-privileged users must utilize multifactor authentication for local access. Multifactor authentication is defined as using two or more factors to achieve authe | ||||
| SV-203644r557179_rule | SRG-OS-000109-GPOS-00056 | CCI-000770 | MEDIUM | The operating system must require individuals to be authenticated with an individual authenticator prior to using a group authenticator. | To assure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated. A group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does | ||||
| SV-203645r851748_rule | SRG-OS-000112-GPOS-00057 | CCI-001941 | MEDIUM | 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 must not be vulnerable to a replay attack. An authenticatio | ||||
| SV-203646r851749_rule | SRG-OS-000113-GPOS-00058 | CCI-001942 | MEDIUM | The operating system must implement replay-resistant authentication mechanisms for network access to non-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 must not be vulnerable to a replay attack. An authenticatio | ||||
| SV-203647r557188_rule | SRG-OS-000114-GPOS-00059 | CCI-000778 | MEDIUM | 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, external storage, and printers. | ||||
| SV-203648r557191_rule | SRG-OS-000118-GPOS-00060 | CCI-000795 | MEDIUM | The operating system must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user acco | ||||
| SV-203649r832978_rule | SRG-OS-000120-GPOS-00061 | CCI-000803 | MEDIUM | 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 compromised. Operating systems utilizing encryption are r | ||||
| SV-203650r557197_rule | SRG-OS-000121-GPOS-00062 | CCI-000804 | MEDIUM | 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 compromise resources within the application or information syst | ||||
| SV-203651r851750_rule | SRG-OS-000122-GPOS-00063 | CCI-001876 | MEDIUM | 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 needed to better handle larger-scale or more complex security i | ||||
| SV-203652r557203_rule | SRG-OS-000123-GPOS-00064 | CCI-001682 | MEDIUM | 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 bypass normal account authorization processes. If these a | ||||
| SV-203653r877395_rule | SRG-OS-000125-GPOS-00065 | CCI-000877 | HIGH | The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. | If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as system | ||||
| SV-203654r557209_rule | SRG-OS-000126-GPOS-00066 | CCI-000879 | MEDIUM | The operating system must terminate all sessions and network connections related to nonlocal maintenance when nonlocal maintenance is completed. | If a maintenance session or connection remains open after maintenance is completed, it may be hijacked by an attacker and used to compromise or damage the system. Some maintenance and test tools are either standalone devices with their own operating sys | ||||
| SV-203655r557212_rule | SRG-OS-000132-GPOS-00067 | CCI-001082 | MEDIUM | 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 functionality capabilities increases the risk that non-privi | ||||
| SV-203656r557215_rule | SRG-OS-000134-GPOS-00068 | CCI-001084 | MEDIUM | The operating system must isolate security functions from nonsecurity functions. | An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, and/or firmware of the information system responsible for enf | ||||
| SV-203657r557218_rule | SRG-OS-000138-GPOS-00069 | CCI-001090 | MEDIUM | Operating systems must prevent unauthorized and unintended information transfer via shared system resources. | Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from bein | ||||
| SV-203658r557221_rule | SRG-OS-000142-GPOS-00071 | CCI-001095 | MEDIUM | 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 excess capacity ensures that sufficient capacity is availabl | ||||
| SV-203659r793162_rule | SRG-OS-000163-GPOS-00072 | CCI-001133 | MEDIUM | 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. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminat | ||||
| SV-203660r557227_rule | SRG-OS-000184-GPOS-00078 | CCI-001190 | MEDIUM | The operating system must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. | Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Operating systems that fail suddenly and with no incorporated failure state planning may leave the system a | ||||
| SV-203661r557230_rule | SRG-OS-000185-GPOS-00079 | CCI-001199 | MEDIUM | The operating system must protect the confidentiality and integrity of all information at rest. | Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system. This requirement addresses protection of user-generated data, as | ||||
| SV-203662r804662_rule | SRG-OS-000191-GPOS-00080 | CCI-001233 | MEDIUM | The operating system must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Endpoint Security Solution (ESS) is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). | Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. To support this requir | ||||
| SV-203663r557236_rule | SRG-OS-000205-GPOS-00083 | CCI-001312 | MEDIUM | 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 the organization. Organizations carefully consider the str | ||||
| SV-203664r557239_rule | SRG-OS-000206-GPOS-00084 | CCI-001314 | MEDIUM | The operating system must reveal error messages only to authorized users. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally Identifiable Information ( | ||||
| SV-203665r557242_rule | SRG-OS-000228-GPOS-00088 | CCI-001384 | MEDIUM | 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 applicable federal laws, Executive Orders, directives, po | ||||
| SV-203666r379204_rule | SRG-OS-000239-GPOS-00089 | CCI-001403 | MEDIUM | 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 existing account. Auditing account modification actions prov | ||||
| SV-203667r379207_rule | SRG-OS-000240-GPOS-00090 | CCI-001404 | MEDIUM | 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 order to detect and respond to events affecting user acces | ||||
| SV-203668r379210_rule | SRG-OS-000241-GPOS-00091 | CCI-001405 | MEDIUM | The operating system must audit all account removal actions. | When operating system accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user access | ||||
| SV-203669r877394_rule | SRG-OS-000250-GPOS-00093 | CCI-001453 | HIGH | The operating system must implement cryptography to protect the integrity of remote access sessions. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating throu | ||||
| SV-203670r379231_rule | SRG-OS-000254-GPOS-00095 | CCI-001464 | MEDIUM | The operating system must initiate session audits at system start-up. | If auditing is enabled late in the start-up process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created. | ||||
| SV-203671r379234_rule | SRG-OS-000255-GPOS-00096 | CCI-001487 | MEDIUM | 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 for the potentially harmful event. | ||||
| SV-203672r379237_rule | SRG-OS-000256-GPOS-00097 | CCI-001493 | MEDIUM | 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 operation on audit information. Operating systems providing tools | ||||
| SV-203673r379240_rule | SRG-OS-000257-GPOS-00098 | CCI-001494 | MEDIUM | 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 operation on audit information. Operating systems providing tools | ||||
| SV-203674r379243_rule | SRG-OS-000258-GPOS-00099 | CCI-001495 | MEDIUM | The operating system must protect audit tools from unauthorized deletion. | 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 operation on audit information. Operating systems providing tools | ||||
| SV-203675r379246_rule | SRG-OS-000259-GPOS-00100 | CCI-001499 | MEDIUM | The operating system must limit privileges to change software resident within software libraries. | If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. This requirement | ||||
| SV-203676r379249_rule | SRG-OS-000266-GPOS-00101 | CCI-001619 | MEDIUM | The operating system must enforce password complexity by requiring that at least one special 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 resisting attempts at guessing and brute-force attacks. Password co | ||||
| SV-203677r379318_rule | SRG-OS-000269-GPOS-00103 | CCI-001665 | MEDIUM | 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, integrity, or availability in the event of a failure of the | ||||
| SV-203678r379321_rule | SRG-OS-000274-GPOS-00104 | CCI-001683 | MEDIUM | 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 account. Notification of account creation is one method f | ||||
| SV-203679r379324_rule | SRG-OS-000275-GPOS-00105 | CCI-001684 | MEDIUM | 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 existing account. Notification of account modification is one | ||||
| SV-203680r379327_rule | SRG-OS-000276-GPOS-00106 | CCI-001685 | MEDIUM | 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 processes themselves. Sending notification of account disabling e | ||||
| SV-203681r379330_rule | SRG-OS-000277-GPOS-00107 | CCI-001686 | MEDIUM | 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 themselves. Sending notification of account removal event | ||||
| SV-203682r877393_rule | SRG-OS-000278-GPOS-00108 | CCI-001496 | HIGH | 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 records, audit settings, and audit reports) needed to successfu | ||||
| SV-203683r851751_rule | SRG-OS-000279-GPOS-00109 | CCI-002361 | MEDIUM | 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.e., network disconnect). A logical session (for local, net | ||||
| SV-203684r851752_rule | SRG-OS-000280-GPOS-00110 | CCI-002363 | MEDIUM | 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 users gain access via authentication include, for example, l | ||||
| SV-203685r851753_rule | SRG-OS-000281-GPOS-00111 | CCI-002364 | MEDIUM | The operating system must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions. | 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. Users need to be aware of whether or not the session has been terminated. Information resou | ||||
| SV-203686r851754_rule | SRG-OS-000297-GPOS-00115 | CCI-002314 | MEDIUM | 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 management difficult at best. Remote access is access to DoD no | ||||
| SV-203687r851755_rule | SRG-OS-000298-GPOS-00116 | CCI-002322 | MEDIUM | The operating system must provide the capability to immediately disconnect or disable remote access to the operating system. | Without the ability to immediately disconnect or disable remote access, an attack or other compromise taking place would not be immediately stopped. Operating system remote access functionality must have the capability to immediately disconnect current u | ||||
| SV-203688r379456_rule | SRG-OS-000299-GPOS-00117 | CCI-001444 | MEDIUM | 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 intercepted, it is necessary to use encryption to protect th | ||||
| SV-203689r379459_rule | SRG-OS-000300-GPOS-00118 | CCI-001443 | MEDIUM | The operating system must protect wireless access to the system using authentication of users and/or devices. | Allowing devices and users to connect to the system without first authenticating them allows untrusted access and can lead to a compromise or attack. Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. W | ||||
| SV-203690r851756_rule | SRG-OS-000303-GPOS-00120 | CCI-002130 | MEDIUM | The operating system must audit all 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 a new or disabled account. Auditing account modification action | ||||
| SV-203691r851757_rule | SRG-OS-000304-GPOS-00121 | CCI-002132 | MEDIUM | The operating system must notify system administrators and 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 existing disabled account. Sending notification of account e | ||||
| SV-203692r851758_rule | SRG-OS-000312-GPOS-00122 | CCI-002165 | MEDIUM | 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 mode (e.g., read or write). Ownership is usually acquired | ||||
| SV-203693r851759_rule | SRG-OS-000312-GPOS-00123 | CCI-002165 | MEDIUM | The operating system must allow operating system admins to grant their privileges to other operating system admins. | 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 mode (e.g., read or write). Ownership is usually acquired | ||||
| SV-203694r851760_rule | SRG-OS-000312-GPOS-00124 | CCI-002165 | MEDIUM | The operating system must allow operating system admins to change security attributes on users, the operating system, or the operating systems components. | 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 mode (e.g., read or write). Ownership is usually acquired | ||||
| SV-203695r877392_rule | SRG-OS-000324-GPOS-00125 | CCI-002235 | HIGH | The operating system must prevent nonprivileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileged functions include, for example, establishing accounts, | ||||
| SV-203696r851762_rule | SRG-OS-000326-GPOS-00126 | CCI-002233 | MEDIUM | The operating system must prevent all software from executing at higher privilege levels than users executing the software. | In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invo | ||||
| SV-203697r851763_rule | SRG-OS-000327-GPOS-00127 | CCI-002234 | MEDIUM | The operating system must audit the execution of privileged functions. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts | ||||
| SV-203698r851764_rule | SRG-OS-000329-GPOS-00128 | CCI-002238 | MEDIUM | The operating system must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes occur. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. | ||||
| SV-203699r877036_rule | SRG-OS-000337-GPOS-00129 | CCI-001914 | MEDIUM | The operating system must provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all operating system components, based on all selectable event criteria in near real time. | If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost. This requirement enable | ||||
| SV-203700r877391_rule | SRG-OS-000341-GPOS-00132 | CCI-001849 | LOW | The operating system must allocate audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility. | In order to ensure operating systems have a sufficient storage capacity in which to write the audit logs, operating systems need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually perform | ||||
| SV-203701r877390_rule | SRG-OS-000342-GPOS-00133 | CCI-001851 | LOW | The operating system must offload audit records onto a different system or media from the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. | ||||
| SV-203702r877389_rule | SRG-OS-000343-GPOS-00134 | CCI-001855 | LOW | The operating system must immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. | If security personnel are not notified immediately when storage volume reaches 75% utilization, they are unable to plan for audit record storage capacity expansion. | ||||
| SV-203703r851770_rule | SRG-OS-000344-GPOS-00135 | CCI-001858 | MEDIUM | The operating system must provide an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability and system operation | ||||
| SV-203704r877388_rule | SRG-OS-000348-GPOS-00136 | CCI-001875 | LOW | The operating system must provide an audit reduction capability that supports on-demand audit review and analysis. | The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports, as needed, to better handle larger-scale or more | ||||
| SV-203705r877387_rule | SRG-OS-000349-GPOS-00137 | CCI-001877 | LOW | The operating system must provide an audit reduction capability that supports after-the-fact investigations of security incidents. | If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required t | ||||
| SV-203706r877386_rule | SRG-OS-000350-GPOS-00138 | CCI-001878 | LOW | The operating system must provide a report generation capability that supports on-demand audit review and analysis. | The report generation capability must support on-demand review and analysis in order to facilitate the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents. Report generation mus | ||||
| SV-203707r877385_rule | SRG-OS-000351-GPOS-00139 | CCI-001879 | LOW | The operating system must provide a report generation capability that supports on-demand reporting requirements. | The report generation capability must support on-demand reporting in order to facilitate the organization's ability to generate incident reports, as needed, to better handle larger-scale or more complex security incidents. Report generation must be capab | ||||
| SV-203708r877384_rule | SRG-OS-000352-GPOS-00140 | CCI-001880 | LOW | The operating system must provide a report generation capability that supports after-the-fact investigations of security incidents. | If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack or identify those responses for one. This capability is also required | ||||
| SV-203709r851776_rule | SRG-OS-000353-GPOS-00141 | CCI-001881 | MEDIUM | The operating system must not alter original content or time ordering of audit records when it provides an audit reduction capability. | If the audit reduction capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Audit reduction is a process that manipulates collected | ||||
| SV-203710r851777_rule | SRG-OS-000354-GPOS-00142 | CCI-001882 | MEDIUM | The operating system must not alter original content or time ordering of audit records when it provides a report generation capability. | If the report generation capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronological organizatio | ||||
| SV-203711r877963_rule | SRG-OS-000355-GPOS-00143 | CCI-001891 | MEDIUM | The operating system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. S | ||||
| SV-203712r851781_rule | SRG-OS-000356-GPOS-00144 | CCI-002046 | MEDIUM | The operating system must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second. | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. | ||||
| SV-203713r851782_rule | SRG-OS-000358-GPOS-00145 | CCI-001889 | MEDIUM | The operating system must record time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. | Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the operating system include date and time. Granularity of time measurements refers to the degree of sy | ||||
| SV-203714r877383_rule | SRG-OS-000359-GPOS-00146 | CCI-001890 | LOW | The operating system must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the operating system include date and time. Time is commonly expressed in Coordinated Universal Time | ||||
| SV-203715r851784_rule | SRG-OS-000360-GPOS-00147 | CCI-000366 | MEDIUM | The operating system must enforce dual authorization for movement and/or deletion of all audit information, when such movement or deletion is not part of an authorized automatic process. | An authorized user may intentionally or accidentally move or delete audit records without those specific actions being authorized. All bulk manipulation of audit information must be authorized via automatic processes. Any manual manipulation of audit inf | ||||
| SV-203716r851785_rule | SRG-OS-000362-GPOS-00149 | CCI-001812 | MEDIUM | The operating system must prohibit user installation of system software without explicit privileged status. | Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular use | ||||
| SV-203717r851786_rule | SRG-OS-000363-GPOS-00150 | CCI-001744 | MEDIUM | The operating system must notify designated personnel if baseline configurations are changed in an unauthorized manner. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be | ||||
| SV-203718r851787_rule | SRG-OS-000364-GPOS-00151 | CCI-001813 | MEDIUM | The operating system must enforce access restrictions. | Failure to provide logical access restrictions associated with changes to system configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted that | ||||
| SV-203719r851788_rule | SRG-OS-000365-GPOS-00152 | CCI-001814 | MEDIUM | The operating system must audit the enforcement actions used to restrict access associated with changes to the system. | Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation for after-the-fact actions. E | ||||
| SV-203720r877463_rule | SRG-OS-000366-GPOS-00153 | CCI-001749 | HIGH | The operating system must prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor. Accordingly, patches, ser | ||||
| SV-203721r851792_rule | SRG-OS-000368-GPOS-00154 | CCI-001764 | MEDIUM | The operating system must prevent program execution in accordance with local policies regarding software program usage and restrictions and/or rules authorizing the terms and conditions of software program usage. | Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This i | ||||
| SV-203722r851793_rule | SRG-OS-000370-GPOS-00155 | CCI-001774 | MEDIUM | The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. | Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. The organization must identify aut | ||||
| SV-203723r851794_rule | SRG-OS-000373-GPOS-00156 | CCI-002038 | MEDIUM | The operating system must require users to re-authenticate for privilege escalation. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate. | ||||
| SV-203724r851795_rule | SRG-OS-000373-GPOS-00157 | CCI-002038 | MEDIUM | The operating system must require users to re-authenticate when changing roles. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When operating systems provide the capability to change security roles, it is critical the user re-authenticate. | ||||
| SV-203725r851796_rule | SRG-OS-000373-GPOS-00158 | CCI-002038 | MEDIUM | The operating system must require users to re-authenticate when changing authenticators. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When operating systems provide the capability to change user authenticators, it is critical the user re-authenticate. | ||||
| SV-203726r851797_rule | SRG-OS-000374-GPOS-00159 | CCI-002039 | MEDIUM | The operating system must require devices to re-authenticate when changing authenticators. | Without re-authentication, devices may access resources or perform tasks for which they do not have authorization. When operating systems provide the capability to change device authenticators, it is critical the device re-authenticate. | ||||
| SV-203727r851798_rule | SRG-OS-000375-GPOS-00160 | CCI-001948 | MEDIUM | The operating system must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. | Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device. Multifactor | ||||
| SV-203728r851799_rule | SRG-OS-000376-GPOS-00161 | CCI-001953 | MEDIUM | The operating system must accept Personal Identity Verification (PIV) credentials. | The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Di | ||||
| SV-203729r851800_rule | SRG-OS-000377-GPOS-00162 | CCI-001954 | MEDIUM | The operating system must electronically verify Personal Identity Verification (PIV) credentials. | The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Di | ||||
| SV-203730r851801_rule | SRG-OS-000378-GPOS-00163 | CCI-001958 | MEDIUM | The operating system must authenticate peripherals before establishing a connection. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers. | ||||
| SV-203731r877039_rule | SRG-OS-000379-GPOS-00164 | CCI-001967 | MEDIUM | The operating system must authenticate all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of gre | ||||
| SV-203732r851803_rule | SRG-OS-000380-GPOS-00165 | CCI-002041 | MEDIUM | The operating system must allow the use of a temporary password for system logons with an immediate change to a permanent password. | Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial logon. Temporary passwords are typicall | ||||
| SV-203733r851804_rule | SRG-OS-000383-GPOS-00166 | CCI-002007 | MEDIUM | The operating system must prohibit the use of cached authenticators after one day. | If cached authentication information is out-of-date, the validity of the authentication information may be questionable. | ||||
| SV-203734r851805_rule | SRG-OS-000384-GPOS-00167 | CCI-001991 | MEDIUM | The operating system, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. | Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). | ||||
| SV-203735r851806_rule | SRG-OS-000392-GPOS-00172 | CCI-002884 | MEDIUM | The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions. | If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available. This requirement addresses auditing-related issues associated with maintenance to | ||||
| SV-203736r877382_rule | SRG-OS-000393-GPOS-00173 | CCI-002890 | HIGH | The operating system must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. | Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms, such as a hash function or digital signature, to protect integri | ||||
| SV-203737r877381_rule | SRG-OS-000394-GPOS-00174 | CCI-003123 | HIGH | The operating system must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. | Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms such as encryption to protect confidentiality. Nonlocal maintena | ||||
| SV-203738r851809_rule | SRG-OS-000395-GPOS-00175 | CCI-002891 | MEDIUM | The operating system must verify remote disconnection at the termination of nonlocal maintenance and diagnostic sessions, when used for nonlocal maintenance sessions. | If the remote connection is not closed and verified as closed, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Remote connections must be disconnected and verified as disconnected when nonlocal mainten | ||||
| SV-203739r877380_rule | SRG-OS-000396-GPOS-00176 | CCI-002450 | HIGH | The operating system must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provide | ||||
| SV-203744r851811_rule | SRG-OS-000403-GPOS-00182 | CCI-002470 | MEDIUM | The operating system must only allow the use of DoD PKI-established certificate authorities for authentication in the establishment of protected sessions to the operating system. | Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate | ||||
| SV-203745r877379_rule | SRG-OS-000404-GPOS-00183 | CCI-002475 | HIGH | The operating system must implement cryptographic mechanisms to prevent unauthorized modification of all information at rest on all operating system components. | Operating systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a cryptographic mechanism is based on the need to prote | ||||
| SV-203746r877378_rule | SRG-OS-000405-GPOS-00184 | CCI-002476 | HIGH | The operating system must implement cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all operating system components. | Operating systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a cryptographic mechanism is based on the need to prote | ||||
| SV-203747r851814_rule | SRG-OS-000420-GPOS-00186 | CCI-002385 | MEDIUM | The operating system must protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces. | 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. This requirement addresses the configuration of the operating system t | ||||
| SV-203748r851815_rule | SRG-OS-000423-GPOS-00187 | CCI-002418 | MEDIUM | The operating system must protect the confidentiality and integrity of transmitted information. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. This requirement applies to both internal and external networks and all | ||||
| SV-203749r877465_rule | SRG-OS-000424-GPOS-00188 | CCI-002421 | HIGH | The operating system must implement cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission unless otherwise protected by alternative physical safeguards, such as, at a minimum, a Protected Distribution System (PDS). | Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions which have common applicat | ||||
| SV-203750r851819_rule | SRG-OS-000425-GPOS-00189 | CCI-002420 | MEDIUM | The operating system must maintain the confidentiality and integrity of information during preparation for transmission. | Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modific | ||||
| SV-203751r851820_rule | SRG-OS-000426-GPOS-00190 | CCI-002422 | MEDIUM | The operating system must maintain the confidentiality and integrity of information during reception. | Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications c | ||||
| SV-203752r851821_rule | SRG-OS-000432-GPOS-00191 | CCI-002754 | MEDIUM | The operating system must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. | A common vulnerability of operating system is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input | ||||
| SV-203753r851822_rule | SRG-OS-000433-GPOS-00192 | CCI-002824 | MEDIUM | The operating system must implement non-executable data to protect its memory from unauthorized code execution. | Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address sp | ||||
| SV-203754r851823_rule | SRG-OS-000433-GPOS-00193 | CCI-002824 | MEDIUM | The operating system must implement address space layout randomization to protect its memory from unauthorized code execution. | Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address sp | ||||
| SV-203755r851824_rule | SRG-OS-000437-GPOS-00194 | CCI-002617 | MEDIUM | The operating system must remove all software components after updated versions have been installed. | Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the | ||||
| SV-203756r851825_rule | SRG-OS-000445-GPOS-00199 | CCI-002696 | MEDIUM | The operating system must verify correct operation of all security functions. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the | ||||
| SV-203757r851826_rule | SRG-OS-000446-GPOS-00200 | CCI-002699 | MEDIUM | The operating system must perform verification of the correct operation of security functions: upon system start-up and/or restart; upon command by a user with privileged access; and/or every 30 days. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the | ||||
| SV-203758r851827_rule | SRG-OS-000447-GPOS-00201 | CCI-002702 | MEDIUM | The operating system must shut down the information system, restart the information system, and/or notify the system administrator when anomalies in the operation of any security functions are discovered. | If anomalies are not acted upon, security functions may fail to secure the system. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the | ||||
| SV-203759r380329_rule | SRG-OS-000458-GPOS-00203 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203760r380335_rule | SRG-OS-000461-GPOS-00205 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203761r381448_rule | SRG-OS-000462-GPOS-00206 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203762r381451_rule | SRG-OS-000463-GPOS-00207 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203763r381457_rule | SRG-OS-000465-GPOS-00209 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203764r381460_rule | SRG-OS-000466-GPOS-00210 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203765r381463_rule | SRG-OS-000467-GPOS-00211 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to delete security levels occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203766r381466_rule | SRG-OS-000468-GPOS-00212 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203767r381472_rule | SRG-OS-000470-GPOS-00214 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful logon attempts occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203768r381475_rule | SRG-OS-000471-GPOS-00215 | CCI-000172 | MEDIUM | The operating system must generate audit records for privileged activities or other system-level access. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203769r381475_rule | SRG-OS-000471-GPOS-00216 | CCI-000172 | MEDIUM | The audit system must be configured to audit the loading and unloading of dynamic kernel modules. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit reco | ||||
| SV-203770r381478_rule | SRG-OS-000472-GPOS-00217 | CCI-000172 | MEDIUM | The operating system must generate audit records showing starting and ending time for user access to the system. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203771r381481_rule | SRG-OS-000473-GPOS-00218 | CCI-000172 | MEDIUM | The operating system must generate audit records when concurrent logons to the same account occur from different sources. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203772r381484_rule | SRG-OS-000474-GPOS-00219 | CCI-000172 | MEDIUM | The operating system must generate audit records when successful/unsuccessful accesses to objects occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203773r381487_rule | SRG-OS-000475-GPOS-00220 | CCI-000172 | MEDIUM | The operating system must generate audit records for all direct access to the information system. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203774r381490_rule | SRG-OS-000476-GPOS-00221 | CCI-000172 | MEDIUM | The operating system must generate audit records for all account creations, modifications, disabling, and termination events. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203775r381493_rule | SRG-OS-000477-GPOS-00222 | CCI-000172 | MEDIUM | The operating system must generate audit records for all kernel module load, unload, and restart actions, and also for all program initiations. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor | ||||
| SV-203776r877466_rule | SRG-OS-000478-GPOS-00223 | CCI-002450 | HIGH | The operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provide | ||||
| SV-203777r851831_rule | SRG-OS-000479-GPOS-00224 | CCI-001851 | MEDIUM | The operating system must, at a minimum, off-load audit data from interconnected systems in real time and off-load audit data from standalone systems weekly. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. | ||||
| SV-203778r388482_rule | SRG-OS-000480-GPOS-00225 | CCI-000366 | MEDIUM | The operating system must prevent the use of dictionary words for passwords. | If the operating system allows the user to select passwords based on dictionary words, then this increases the chances of password compromise by increasing the opportunity for successful guesses and brute-force attacks. | ||||
| SV-203779r388482_rule | SRG-OS-000480-GPOS-00226 | CCI-000366 | MEDIUM | The operating system must enforce a delay of at least 4 seconds between logon prompts following a failed logon attempt. | Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account. | ||||
| SV-203780r388482_rule | SRG-OS-000480-GPOS-00227 | CCI-000366 | MEDIUM | The operating system must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. | Configuring the operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive secur | ||||
| SV-203781r388482_rule | SRG-OS-000480-GPOS-00228 | CCI-000366 | MEDIUM | The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. | Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access. | ||||
| SV-203782r877377_rule | SRG-OS-000480-GPOS-00229 | CCI-000366 | HIGH | The operating system must not allow an unattended or automatic logon to the system. | Failure to restrict system access to authenticated users negatively impacts operating system security. | ||||
| SV-203783r388482_rule | SRG-OS-000480-GPOS-00230 | CCI-000366 | MEDIUM | The operating system must limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. | Users' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with an SA through shared resources. | ||||
| SV-203784r388482_rule | SRG-OS-000480-GPOS-00232 | CCI-000366 | MEDIUM | The operating system must enable an application firewall, if available. | Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network. | ||||
| SV-252688r851832_rule | SRG-OS-000481-GPOS-00481 | CCI-002418 | MEDIUM | The operating system must protect the confidentiality and integrity of communications with wireless peripherals. | Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the operating system. This requirement | ||||