Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

General Purpose Operating System SRG

  • Version/Release: V1R6
  • Published: 2019-07-01
  • Released: 2019-07-26
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

The General Purpose Operating System Security Requirements Guide (SRG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.
b
The operating system must provide automated mechanisms for supporting account management functions.
AC-2 - Medium - CCI-000015 - V-56571 - SV-70831r1_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000015
Version
SRG-OS-000001-GPOS-00001
Vuln IDs
  • V-56571
Rule IDs
  • SV-70831r1_rule
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 to ensure accounts designated as requiring attention are consistently and promptly addressed. Examples include, but are not limited to, using automation to take action on multiple accounts designated as inactive, suspended or terminated, or by disabling accounts located in non-centralized account stores such as multiple servers. This requirement applies to all account types, including individual/user, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. The automated mechanisms may reside within the operating system itself or may be offered by other infrastructure providing automated account management capabilities. Automated mechanisms may be composed of differing technologies that, when placed together, contain an overall automated mechanism supporting an organization's automated account management requirements. Account management functions include: assigning group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The use of automated mechanisms can include, for example: using email or text messaging to automatically notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using automated telephonic notification to report atypical system account usage.
Checks: C-57131r1_chk

Verify the operating system provides automated mechanisms for supporting account management functions. If it does not, this is a finding.

Fix: F-61459r1_fix

Configure the operating system to provide automated mechanisms for supporting account management functions.

b
The operating system must enable an application firewall, if available.
CM-6 - Medium - CCI-000366 - V-56573 - SV-70833r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000480-GPOS-00232
Vuln IDs
  • V-56573
Rule IDs
  • SV-70833r1_rule
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.
Checks: C-57141r1_chk

Verify the operating system enabled an application firewall, if available. If it does not, this is a finding. If the operating system does not support an application firewall, this may be downgraded to a CAT III finding.

Fix: F-61467r1_fix

Ensure the operating system's application firewall is enabled, if available.

b
The operating system must automatically remove or disable temporary user accounts after 72 hours.
AC-2 - Medium - CCI-000016 - V-56575 - SV-70835r1_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000016
Version
SRG-OS-000002-GPOS-00002
Vuln IDs
  • V-56575
Rule IDs
  • SV-70835r1_rule
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. Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.
Checks: C-57143r1_chk

Verify the operating system automatically removes or disables local temporary user accounts after 72 hours. If it does not, this is a finding.

Fix: F-61469r1_fix

Configure the operating system to automatically remove or disable local temporary user accounts after 72 hours.

b
The operating system must audit all account creations.
AC-2 - Medium - CCI-000018 - V-56577 - SV-70837r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000018
Version
SRG-OS-000004-GPOS-00004
Vuln IDs
  • V-56577
Rule IDs
  • SV-70837r2_rule
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 that can be used for forensic purposes. To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57147r1_chk

Verify the operating system automatically audits account creation. If it does not, this is a finding.

Fix: F-61473r1_fix

Configure the operating system to automatically audit account creation.

b
The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
AC-7 - Medium - CCI-000044 - V-56579 - SV-70839r1_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-000044
Version
SRG-OS-000021-GPOS-00005
Vuln IDs
  • V-56579
Rule IDs
  • SV-70839r1_rule
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.
Checks: C-57149r1_chk

Verify that the operating system enforces the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. If it does not, this is a finding.

Fix: F-61475r1_fix

Configure the operating system to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.

b
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.
CM-6 - Medium - CCI-000366 - V-56583 - SV-70843r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000480-GPOS-00230
Vuln IDs
  • V-56583
Rule IDs
  • SV-70843r1_rule
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.
Checks: C-57155r1_chk

Verify the operating system limits the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders. If it does not, this is a finding.

Fix: F-61481r1_fix

Configure the operating system to limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders.

b
The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system.
AC-8 - Medium - CCI-000048 - V-56585 - SV-70845r1_rule
RMF Control
AC-8
Severity
Medium
CCI
CCI-000048
Version
SRG-OS-000023-GPOS-00006
Vuln IDs
  • V-56585
Rule IDs
  • SV-70845r1_rule
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, standards, and guidance. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."
Checks: C-57151r3_chk

Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." If it does not, this is a finding.

Fix: F-61477r2_fix

Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." If it does not, this is a finding.

b
The operating system must not allow an unattended or automatic logon to the system.
CM-6 - Medium - CCI-000366 - V-56587 - SV-70847r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000480-GPOS-00229
Vuln IDs
  • V-56587
Rule IDs
  • SV-70847r1_rule
Failure to restrict system access to authenticated users negatively impacts operating system security.
Checks: C-57157r1_chk

If the operating system provides a public access service, such as a kiosk, this is not applicable. Verify the operating system does not allow an unattended or automatic logon to the system. If it does, this is a finding. Automatic logon as an authorized user allows access to any user with physical access to the operating system.

Fix: F-61483r1_fix

If the operating system provides a public access service, such as a kiosk, this is not applicable. Configure the operating system to not allow an unattended or automatic logon to the system. Automatic logon as an authorized user allows access to any user with physical access to the operating system.

b
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.
CM-6 - Medium - CCI-000366 - V-56589 - SV-70849r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000480-GPOS-00228
Vuln IDs
  • V-56589
Rule IDs
  • SV-70849r1_rule
Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access.
Checks: C-57159r1_chk

Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files. If it does not, this is a finding.

Fix: F-61485r1_fix

Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files.

b
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.
CM-6 - Medium - CCI-000366 - V-56591 - SV-70851r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000480-GPOS-00227
Vuln IDs
  • V-56591
Rule IDs
  • SV-70851r1_rule
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 security posture consistent with operational requirements. Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.
Checks: C-57161r1_chk

Verify the operating system is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not, this is a finding.

Fix: F-61487r1_fix

Configure the operating system in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.

b
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.
AC-8 - Medium - CCI-000050 - V-56593 - SV-70853r1_rule
RMF Control
AC-8
Severity
Medium
CCI
CCI-000050
Version
SRG-OS-000024-GPOS-00007
Vuln IDs
  • V-56593
Rule IDs
  • SV-70853r1_rule
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, DoD will not be in compliance with system use notifications required by law. To establish acceptance of the application usage policy, a click-through banner at system logon is required. The system must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK".
Checks: C-57163r1_chk

Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access. If it does not, this is a finding.

Fix: F-61489r1_fix

Configure the operating system to 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.

b
The operating system must enforce a delay of at least 4 seconds between logon prompts following a failed logon attempt.
CM-6 - Medium - CCI-000366 - V-56595 - SV-70855r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000480-GPOS-00226
Vuln IDs
  • V-56595
Rule IDs
  • SV-70855r1_rule
Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account.
Checks: C-57165r1_chk

Verify the operating system enforces a delay of at least 4 seconds between logon prompts following a failed logon attempt. If it does not, this is a finding.

Fix: F-61491r1_fix

Configure the operating system to enforce a delay of at least 4 seconds between logon prompts following a failed logon attempt.

b
The operating system must prevent the use of dictionary words for passwords.
CM-6 - Medium - CCI-000366 - V-56597 - SV-70857r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000480-GPOS-00225
Vuln IDs
  • V-56597
Rule IDs
  • SV-70857r1_rule
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.
Checks: C-57167r1_chk

Verify the operating system prevents the use of dictionary words for passwords. If it does not, this is a finding.

Fix: F-61493r1_fix

Configure the operating system to prevent the use of dictionary words for passwords.

b
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.
AU-4 - Medium - CCI-001851 - V-56599 - SV-70859r2_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001851
Version
SRG-OS-000479-GPOS-00224
Vuln IDs
  • V-56599
Rule IDs
  • SV-70859r2_rule
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.
Checks: C-57169r1_chk

Verify the operating system, at a minimum, off-loads interconnected systems in real time and off-loads standalone systems weekly. If it does not, this is a finding.

Fix: F-61495r1_fix

Configure the operating system to, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly.

b
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.
SC-13 - Medium - CCI-002450 - V-56601 - SV-70861r1_rule
RMF Control
SC-13
Severity
Medium
CCI
CCI-002450
Version
SRG-OS-000478-GPOS-00223
Vuln IDs
  • V-56601
Rule IDs
  • SV-70861r1_rule
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 provides assurance they have been tested and validated.
Checks: C-57171r1_chk

Verify the operating system implements 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. If it does not, this is a finding.

Fix: F-61497r1_fix

Configure the operating system to 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.

b
The operating system must generate audit records for all kernel module load, unload, and restart actions, and also for all program initiations.
AU-12 - Medium - CCI-000172 - V-56603 - SV-70863r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000477-GPOS-00222
Vuln IDs
  • V-56603
Rule IDs
  • SV-70863r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57173r1_chk

Verify the operating system generates audit records for all kernel module load, unload, and restart actions, and also for all program initiations. If it does not, this is a finding.

Fix: F-61499r1_fix

Configure the operating system to generate audit records for all kernel module load, unload, and restart actions, and also for all program initiations.

b
The operating system must generate audit records for all account creations, modifications, disabling, and termination events.
AU-12 - Medium - CCI-000172 - V-56605 - SV-70865r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000476-GPOS-00221
Vuln IDs
  • V-56605
Rule IDs
  • SV-70865r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57175r1_chk

Verify the operating system generates audit records for all account creations, modifications, disabling, and termination events. If it does not, this is a finding.

Fix: F-61501r1_fix

Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events.

b
The operating system must generate audit records for all direct access to the information system.
AU-12 - Medium - CCI-000172 - V-56607 - SV-70867r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000475-GPOS-00220
Vuln IDs
  • V-56607
Rule IDs
  • SV-70867r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57177r1_chk

Verify the operating system generates audit records for all direct access to the information system. If it does not, this is a finding.

Fix: F-61503r1_fix

Configure the operating system to generate audit records for all direct access to the information system.

b
The operating system must generate audit records when successful/unsuccessful accesses to objects occur.
AU-12 - Medium - CCI-000172 - V-56609 - SV-70869r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000474-GPOS-00219
Vuln IDs
  • V-56609
Rule IDs
  • SV-70869r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57179r1_chk

Verify the operating system generates audit records when successful/unsuccessful accesses to objects occur. If it does not, this is a finding.

Fix: F-61505r1_fix

Configure the operating system to generate audit records when successful/unsuccessful accesses to objects occur.

b
The operating system must generate audit records when concurrent logons to the same account occur from different sources.
AU-12 - Medium - CCI-000172 - V-56611 - SV-70871r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000473-GPOS-00218
Vuln IDs
  • V-56611
Rule IDs
  • SV-70871r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57181r1_chk

Verify the operating system generates audit records when concurrent logons to the same account occur from different sources. If it does not, this is a finding.

Fix: F-61507r1_fix

Configure the operating system to generate audit records when concurrent logons to the same account occur from different sources.

b
The operating system must generate audit records showing starting and ending time for user access to the system.
AU-12 - Medium - CCI-000172 - V-56613 - SV-70873r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000472-GPOS-00217
Vuln IDs
  • V-56613
Rule IDs
  • SV-70873r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57183r1_chk

Verify the operating system generates audit records showing starting and ending time for user access to the system. If it does not, this is a finding.

Fix: F-61509r1_fix

Configure the operating system to generate audit records showing starting and ending time for user access to the system.

b
The audit system must be configured to audit the loading and unloading of dynamic kernel modules.
AU-12 - Medium - CCI-000172 - V-56615 - SV-70875r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000471-GPOS-00216
Vuln IDs
  • V-56615
Rule IDs
  • SV-70875r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57185r1_chk

Verify the audit system is configured to audit the loading and unloading of dynamic kernel modules. If it does not, this is a finding.

Fix: F-61511r1_fix

Configure the audit system to audit the loading and unloading of dynamic kernel modules.

b
The operating system must generate audit records for privileged activities or other system-level access.
AU-12 - Medium - CCI-000172 - V-56617 - SV-70877r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000471-GPOS-00215
Vuln IDs
  • V-56617
Rule IDs
  • SV-70877r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57187r1_chk

Verify the operating system generates audit records for privileged activities or other system-level access. If it does not, this is a finding.

Fix: F-61513r1_fix

Configure the operating system to generate audit records for privileged activities or other system-level access.

b
The operating system must generate audit records when successful/unsuccessful logon attempts occur.
AU-12 - Medium - CCI-000172 - V-56619 - SV-70879r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000470-GPOS-00214
Vuln IDs
  • V-56619
Rule IDs
  • SV-70879r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57189r1_chk

Verify the operating system generates audit records when successful/unsuccessful logon attempts occur. If it does not, this is a finding.

Fix: F-61515r1_fix

Configure the operating system to generate audit records when successful/unsuccessful logon attempts occur.

b
The operating system must generate audit records when successful/unsuccessful attempts to delete security objects occur.
AU-12 - Medium - CCI-000172 - V-56621 - SV-70881r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000468-GPOS-00212
Vuln IDs
  • V-56621
Rule IDs
  • SV-70881r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57191r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to delete security objects occur. If it does not, this is a finding.

Fix: F-61517r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security objects occur.

b
The operating system must generate audit records when successful/unsuccessful attempts to delete security levels occur.
AU-12 - Medium - CCI-000172 - V-56623 - SV-70883r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000467-GPOS-00211
Vuln IDs
  • V-56623
Rule IDs
  • SV-70883r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57193r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to delete security levels occur. If it does not, this is a finding.

Fix: F-61519r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to delete security levels occur.

b
The operating system must generate audit records when successful/unsuccessful attempts to delete privileges occur.
AU-12 - Medium - CCI-000172 - V-56625 - SV-70885r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000466-GPOS-00210
Vuln IDs
  • V-56625
Rule IDs
  • SV-70885r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57195r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to delete privileges occur. If it does not, this is a finding.

Fix: F-61521r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to delete privileges occur.

b
The operating system must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur.
AU-12 - Medium - CCI-000172 - V-56627 - SV-70887r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000465-GPOS-00209
Vuln IDs
  • V-56627
Rule IDs
  • SV-70887r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57197r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. If it does not, this is a finding.

Fix: F-61523r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur.

b
The operating system must limit the number of concurrent sessions to ten for all accounts and/or account types.
AC-10 - Medium - CCI-000054 - V-56629 - SV-70889r1_rule
RMF Control
AC-10
Severity
Medium
CCI
CCI-000054
Version
SRG-OS-000027-GPOS-00008
Vuln IDs
  • V-56629
Rule IDs
  • SV-70889r1_rule
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 requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based upon mission needs and the operational environment for each system.
Checks: C-57199r1_chk

Verify the operating system limits the number of concurrent sessions to ten for all accounts and/or account types. If it does not, this is a finding.

Fix: F-61525r1_fix

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

b
The operating system must retain a users session lock until that user reestablishes access using established identification and authentication procedures.
AC-11 - Medium - CCI-000056 - V-56631 - SV-70891r1_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000056
Version
SRG-OS-000028-GPOS-00009
Vuln IDs
  • V-56631
Rule IDs
  • SV-70891r1_rule
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 at the point where session activity can be determined. Regardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates. No other activity aside from re-authentication shall unlock the system.
Checks: C-57201r1_chk

Verify the operating system retains a user's session lock until that user reestablishes access using established identification and authentication procedures. If it does not, this is a finding.

Fix: F-61527r1_fix

Configure the operating system to retain a user's session lock until that user reestablishes access using established identification and authentication procedures.

b
The operating system must initiate a session lock after a 15-minute period of inactivity for all connection types.
AC-11 - Medium - CCI-000057 - V-56633 - SV-70893r1_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000057
Version
SRG-OS-000029-GPOS-00010
Vuln IDs
  • V-56633
Rule IDs
  • SV-70893r1_rule
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 to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled.
Checks: C-57203r1_chk

Verify the operating system initiates a session lock after a 15-minute period of inactivity for all connection types. If it does not, this is a finding.

Fix: F-61529r1_fix

Configure the operating system to initiate a session lock after a 15-minute period of inactivity for all connection types.

b
The operating system must provide the capability for users to directly initiate a session lock for all connection types.
AC-11 - Medium - CCI-000058 - V-56635 - SV-70895r1_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000058
Version
SRG-OS-000030-GPOS-00011
Vuln IDs
  • V-56635
Rule IDs
  • SV-70895r1_rule
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 at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity.
Checks: C-57205r1_chk

Verify the operating system provides the capability for users to directly initiate a session lock for all connection types. If it does not, this is a finding.

Fix: F-61531r1_fix

Configure the operating system to provide the capability for users to directly initiate a session lock for all connection types.

b
The operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image.
AC-11 - Medium - CCI-000060 - V-56637 - SV-70897r1_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000060
Version
SRG-OS-000031-GPOS-00012
Vuln IDs
  • V-56637
Rule IDs
  • SV-70897r1_rule
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 point where session activity can be determined. The operating system session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed. Publicly viewable images can include static or dynamic images, for example, patterns used with screen savers, photographic images, solid colors, a clock, a battery life indicator, or a blank screen, with the additional caveat that none of the images convey sensitive information.
Checks: C-57207r1_chk

Verify the operating system conceals, via the session lock, information previously visible on the display with a publicly viewable image. If it does not, this is a finding.

Fix: F-61533r1_fix

Configure the operating system to conceal, via the session lock, information previously visible on the display with a publicly viewable image.

b
The operating system must monitor remote access methods.
AC-17 - Medium - CCI-000067 - V-56639 - SV-70899r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000067
Version
SRG-OS-000032-GPOS-00013
Vuln IDs
  • V-56639
Rule IDs
  • SV-70899r1_rule
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 nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Automated monitoring of remote access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).
Checks: C-57209r1_chk

Verify the operating system monitors remote access methods. If it does not, this is a finding.

Fix: F-61535r1_fix

Configure the operating system to monitor remote access methods.

b
The operating system must implement DoD-approved encryption to protect the confidentiality of remote access sessions.
AC-17 - Medium - CCI-000068 - V-56641 - SV-70901r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000068
Version
SRG-OS-000033-GPOS-00014
Vuln IDs
  • V-56641
Rule IDs
  • SV-70901r1_rule
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) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information.
Checks: C-57211r1_chk

Verify the operating system implements DoD-approved encryption to protect the confidentiality of remote access sessions. If it does not, this is a finding.

Fix: F-61537r1_fix

Configure the operating system to implement DoD-approved encryption to protect the confidentiality of remote access sessions.

b
The operating system must generate audit records when successful/unsuccessful attempts to modify security objects occur.
AU-12 - Medium - CCI-000172 - V-56643 - SV-70903r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000463-GPOS-00207
Vuln IDs
  • V-56643
Rule IDs
  • SV-70903r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57213r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to modify security objects occur. If it does not, this is a finding.

Fix: F-61539r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to modify security objects occur.

b
The operating system must generate audit records when successful/unsuccessful attempts to modify privileges occur.
AU-12 - Medium - CCI-000172 - V-56645 - SV-70905r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000462-GPOS-00206
Vuln IDs
  • V-56645
Rule IDs
  • SV-70905r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57215r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to modify privileges occur. If it does not, this is a finding.

Fix: F-61541r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to modify privileges occur.

b
The operating system must produce audit records containing information to establish what type of events occurred.
AU-3 - Medium - CCI-000130 - V-56647 - SV-70907r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000130
Version
SRG-OS-000037-GPOS-00015
Vuln IDs
  • V-56647
Rule IDs
  • SV-70907r1_rule
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, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.
Checks: C-57217r1_chk

Verify the operating system produces audit records containing information to establish what type of events occurred. If it does not, this is a finding.

Fix: F-61543r1_fix

Configure the operating system to produce audit records containing information to establish what type of events occurred.

b
The operating system must produce audit records containing information to establish when (date and time) the events occurred.
AU-3 - Medium - CCI-000131 - V-56649 - SV-70909r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000131
Version
SRG-OS-000038-GPOS-00016
Vuln IDs
  • V-56649
Rule IDs
  • SV-70909r1_rule
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 personnel to know when events occurred (date and time). Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.
Checks: C-57219r1_chk

Verify the operating system produces audit records containing information to establish when (date and time) the events occurred. If it does not, this is a finding.

Fix: F-61545r1_fix

Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred.

b
The operating system must produce audit records containing information to establish where the events occurred.
AU-3 - Medium - CCI-000132 - V-56651 - SV-70911r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000132
Version
SRG-OS-000039-GPOS-00017
Vuln IDs
  • V-56651
Rule IDs
  • SV-70911r1_rule
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 security personnel to know where events occurred, such as operating system components, modules, device identifiers, node names, file names, and functionality. Associating information about where the event occurred within the operating system provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.
Checks: C-57221r1_chk

Verify the operating system produces audit records containing information to establish where the events occurred. If it does not, this is a finding.

Fix: F-61547r2_fix

Configure the operating system to produce audit records containing information to establish where the events occurred.

b
The operating system must produce audit records containing information to establish the source of the events.
AU-3 - Medium - CCI-000133 - V-56653 - SV-70913r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000133
Version
SRG-OS-000040-GPOS-00018
Vuln IDs
  • V-56653
Rule IDs
  • SV-70913r1_rule
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 generate audit records that identify sources of events. Sources of operating system events include, but are not limited to, processes and services. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the source of the event.
Checks: C-57223r1_chk

Verify the operating system produces audit records containing information to establish the source of the events. If it does not, this is a finding.

Fix: F-61549r1_fix

Configure the operating system to produce audit records containing information to establish the source of the events.

b
The operating system must produce audit records containing information to establish the outcome of the events.
AU-3 - Medium - CCI-000134 - V-56655 - SV-70915r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000134
Version
SRG-OS-000041-GPOS-00019
Vuln IDs
  • V-56655
Rule IDs
  • SV-70915r1_rule
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 success or failure and event-specific results (e.g., the security state of the information system after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.
Checks: C-57225r1_chk

Verify the operating system produces audit records containing information to establish the outcome of the events. If it does not, this is a finding.

Fix: F-61551r1_fix

Configure the operating system to produce audit records containing information to establish the outcome of the events.

b
The operating system must generate audit records containing the full-text recording of privileged commands.
AU-3 - Medium - CCI-000135 - V-56657 - SV-70917r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000135
Version
SRG-OS-000042-GPOS-00020
Vuln IDs
  • V-56657
Rule IDs
  • SV-70917r1_rule
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 trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
Checks: C-57227r1_chk

Verify the operating system generates audit records containing the full-text recording of privileged commands. If it does not, this is a finding.

Fix: F-61553r1_fix

Configure the operating system to generate audit records containing the full-text recording of privileged commands.

b
The operating system must produce audit records containing the individual identities of group account users.
AU-3 - Medium - CCI-000135 - V-56659 - SV-70919r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000135
Version
SRG-OS-000042-GPOS-00021
Vuln IDs
  • V-56659
Rule IDs
  • SV-70919r1_rule
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 sufficient detail to reconstruct events to determine the actual account involved in the activity.
Checks: C-57229r1_chk

Verify the operating system produces audit records containing the individual identities of group account users. If it does not, this is a finding.

Fix: F-61555r1_fix

Configure the operating system to produce audit records containing the individual identities of group account users.

b
The operating system must alert the ISSO and SA (at a minimum) in the event of an audit processing failure.
AU-5 - Medium - CCI-000139 - V-56661 - SV-70921r1_rule
RMF Control
AU-5
Severity
Medium
CCI
CCI-000139
Version
SRG-OS-000046-GPOS-00022
Vuln IDs
  • V-56661
Rule IDs
  • SV-70921r1_rule
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 operation may be adversely affected. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.
Checks: C-57231r1_chk

Verify the operating system alerts the ISSO and SA (at a minimum) in the event of an audit processing failure. If it does not, this is a finding.

Fix: F-61557r1_fix

Configure the operating system to alert the ISSO and SA (at a minimum) in the event of an audit processing failure.

b
The operating system must shut down by default upon audit failure (unless availability is an overriding concern).
AU-5 - Medium - CCI-000140 - V-56663 - SV-70923r1_rule
RMF Control
AU-5
Severity
Medium
CCI
CCI-000140
Version
SRG-OS-000047-GPOS-00023
Vuln IDs
  • V-56663
Rule IDs
  • SV-70923r1_rule
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 audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. When availability is an overriding concern, other approved actions in response to an audit failure are as follows: 1) If the failure was caused by the lack of audit record storage capacity, the operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner. 2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the operating system must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.
Checks: C-57233r1_chk

Verify the operating system shuts down by default upon audit failure (unless availability is an overriding concern). If it does not, this is a finding.

Fix: F-61559r1_fix

Configure the operating system to shut down by default upon audit failure (unless availability is an overriding concern).

b
The operating system must provide the capability to centrally review and analyze audit records from multiple components within the system.
AU-6 - Medium - CCI-000154 - V-56665 - SV-70925r1_rule
RMF Control
AU-6
Severity
Medium
CCI
CCI-000154
Version
SRG-OS-000051-GPOS-00024
Vuln IDs
  • V-56665
Rule IDs
  • SV-70925r1_rule
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 ability to centrally review the operating system logs, forensic analysis is negatively impacted. Segregation of logging data to multiple disparate computer systems is counterproductive and makes log analysis and log event alarming difficult to implement and manage, particularly when the system has multiple logging components writing to different locations or systems. To support the centralized capability, the operating system must be able to provide the information in a format that can be extracted and used, allowing the application performing the centralization of the log records to meet this requirement.
Checks: C-57235r1_chk

Verify the operating system provides the capability to centrally review and analyze audit records from multiple components within the system. If it does not, this is a finding.

Fix: F-61561r1_fix

Configure the operating system to provide the capability to centrally review and analyze audit records from multiple components within the system.

b
The operating system must provide the capability to filter audit records for events of interest based upon all audit fields within audit records.
AU-7 - Medium - CCI-000158 - V-56667 - SV-70927r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-000158
Version
SRG-OS-000054-GPOS-00025
Vuln IDs
  • V-56667
Rule IDs
  • SV-70927r1_rule
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 investigation. Without this capability, forensic investigations are impeded. Events of interest can be identified by the content of specific audit record fields, including, for example, identities of individuals, event types, event locations, event times, event dates, system resources involved, IP addresses involved, or information objects accessed. Organizations may define audit event criteria to any degree of granularity required, for example, locations selectable by general networking location (e.g., by network or subnetwork) or selectable by specific information system component. This requires operating systems to provide the capability to customize audit record reports based on all available criteria.
Checks: C-57237r1_chk

Verify the operating system provides the capability to filter audit records for events of interest based upon all audit fields within audit records. If it does not, this is a finding.

Fix: F-61563r1_fix

Configure the operating system to provide the capability to filter audit records for events of interest based upon all audit fields within audit records.

b
The operating system must use internal system clocks to generate time stamps for audit records.
AU-8 - Medium - CCI-000159 - V-56669 - SV-70929r1_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-000159
Version
SRG-OS-000055-GPOS-00026
Vuln IDs
  • V-56669
Rule IDs
  • SV-70929r1_rule
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 conducting forensic analysis and investigating system events. If the internal clock is not used, the system may not be able to provide time stamps for log messages. Additionally, externally generated time stamps may not be accurate.
Checks: C-57239r1_chk

Verify the operating system uses internal system clocks to generate time stamps for audit records. If it does not, this is a finding.

Fix: F-61565r1_fix

Configure the operating system to use internal system clocks to generate time stamps for audit records.

b
The operating system must protect audit information from unauthorized read access.
AU-9 - Medium - CCI-000162 - V-56671 - SV-70931r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000162
Version
SRG-OS-000057-GPOS-00027
Vuln IDs
  • V-56671
Rule IDs
  • SV-70931r1_rule
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 audit operating system activity.
Checks: C-57241r1_chk

Verify the operating system protects audit information from unauthorized read access. If it does not, this is a finding.

Fix: F-61567r1_fix

Configure the operating system to protect audit information from unauthorized read access.

b
The operating system must protect audit information from unauthorized modification.
AU-9 - Medium - CCI-000163 - V-56673 - SV-70933r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000163
Version
SRG-OS-000058-GPOS-00028
Vuln IDs
  • V-56673
Rule IDs
  • SV-70933r1_rule
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 audit information from unauthorized modification. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.
Checks: C-57243r1_chk

Verify the operating system protects audit information from unauthorized modification. If it does not, this is a finding.

Fix: F-61569r1_fix

Configure the operating system to protect audit information from unauthorized modification.

b
The operating system must protect audit information from unauthorized deletion.
AU-9 - Medium - CCI-000164 - V-56675 - SV-70935r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000164
Version
SRG-OS-000059-GPOS-00029
Vuln IDs
  • V-56675
Rule IDs
  • SV-70935r1_rule
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 audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.
Checks: C-57245r1_chk

Verify the operating system protects audit information from unauthorized deletion. If it does not, this is a finding.

Fix: F-61571r1_fix

Configure the operating system to protect audit information from unauthorized deletion.

b
The operating system must provide audit record generation capability for DoD-defined auditable events for all operating system components.
AU-12 - Medium - CCI-000169 - V-56677 - SV-70937r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000169
Version
SRG-OS-000062-GPOS-00031
Vuln IDs
  • V-56677
Rule IDs
  • SV-70937r1_rule
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 information system (e.g., module or policy filter). The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following: 1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); 2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; 3) All account creations, modifications, disabling, and terminations; and 4) All kernel module load, unload, and restart actions.
Checks: C-57247r1_chk

Verify the operating system provides audit record generation capability for DoD-defined auditable events for all operating system components. DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following: 1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); 2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; 3) All account creations, modifications, disabling, and terminations; and 4) All kernel module load, unload, and restart actions. If it does not, this is a finding.

Fix: F-61573r1_fix

Configure the operating system to provide audit record generation capability for DoD-defined auditable events for all operating system components. DoD has defined the list of events for which the operating system will provide an audit record generation capability as the following: 1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); 2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; 3) All account creations, modifications, disabling, and terminations; and 4) All kernel module load, unload, and restart actions.

b
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.
AU-12 - Medium - CCI-000171 - V-56679 - SV-70939r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000171
Version
SRG-OS-000063-GPOS-00032
Vuln IDs
  • V-56679
Rule IDs
  • SV-70939r1_rule
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 the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Checks: C-57249r1_chk

Verify the operating system allows only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. If it does not, this is a finding.

Fix: F-61575r1_fix

Configure the operating system to allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.

b
The operating system must generate audit records when successful/unsuccessful attempts to access privileges occur.
AU-12 - Medium - CCI-000172 - V-56681 - SV-70941r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000064-GPOS-00033
Vuln IDs
  • V-56681
Rule IDs
  • SV-70941r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57251r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to access privileges occur. If it does not, this is a finding.

Fix: F-61577r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to access privileges occur.

b
The operating system, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.
IA-5 - Medium - CCI-000185 - V-56683 - SV-70943r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000185
Version
SRG-OS-000066-GPOS-00034
Vuln IDs
  • V-56683
Rule IDs
  • SV-70943r1_rule
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 used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. This requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.
Checks: C-57253r1_chk

Verify the operating system, for PKI-based authentication, validates certificates by constructing a certification path (which includes status information) to an accepted trust anchor. If it does not, this is a finding.

Fix: F-61579r1_fix

Configure the operating system, for PKI-based authentication, to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.

b
The operating system, for PKI-based authentication, must enforce authorized access to the corresponding private key.
IA-5 - Medium - CCI-000186 - V-56685 - SV-70945r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000186
Version
SRG-OS-000067-GPOS-00035
Vuln IDs
  • V-56685
Rule IDs
  • SV-70945r1_rule
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 private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.
Checks: C-57255r1_chk

Verify the operating system, for PKI-based authentication, enforces authorized access to the corresponding private key. If it does not, this is a finding.

Fix: F-61581r1_fix

Configure the operating system, for PKI-based authentication, to enforce authorized access to the corresponding private key.

b
The operating system must map the authenticated identity to the user or group account for PKI-based authentication.
IA-5 - Medium - CCI-000187 - V-56687 - SV-70947r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000187
Version
SRG-OS-000068-GPOS-00036
Vuln IDs
  • V-56687
Rule IDs
  • SV-70947r1_rule
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.
Checks: C-57257r1_chk

Verify the operating system maps the authenticated identity to the user or group account for PKI-based authentication. If it does not, this is a finding.

Fix: F-61583r2_fix

Configure the operating system to map the authenticated identity to the user or group account for PKI-based authentication.

b
The operating system must enforce password complexity by requiring that at least one upper-case character be used.
IA-5 - Medium - CCI-000192 - V-56689 - SV-70949r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000192
Version
SRG-OS-000069-GPOS-00037
Vuln IDs
  • V-56689
Rule IDs
  • SV-70949r1_rule
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 complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-57259r1_chk

Verify the operating system enforces password complexity by requiring that at least one upper-case character be used. If it does not, this is a finding.

Fix: F-61585r1_fix

Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used.

b
The operating system must enforce password complexity by requiring that at least one lower-case character be used.
IA-5 - Medium - CCI-000193 - V-56691 - SV-70951r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000193
Version
SRG-OS-000070-GPOS-00038
Vuln IDs
  • V-56691
Rule IDs
  • SV-70951r1_rule
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 complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-57261r1_chk

Verify the operating system enforces password complexity by requiring that at least one lower-case character be used. If it does not, this is a finding.

Fix: F-61587r1_fix

Configure the operating system to enforce password complexity by requiring that at least one lower-case character be used.

b
The operating system must enforce password complexity by requiring that at least one numeric character be used.
IA-5 - Medium - CCI-000194 - V-56693 - SV-70953r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000194
Version
SRG-OS-000071-GPOS-00039
Vuln IDs
  • V-56693
Rule IDs
  • SV-70953r1_rule
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 complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
Checks: C-57263r1_chk

Verify the operating system enforces password complexity by requiring that at least one numeric character be used. If it does not, this is a finding.

Fix: F-61589r1_fix

Configure the operating system to enforce password complexity by requiring that at least one numeric character be used.

b
The operating system must require the change of at least 50% of the total number of characters when passwords are changed.
IA-5 - Medium - CCI-000195 - V-56695 - SV-70955r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000195
Version
SRG-OS-000072-GPOS-00040
Vuln IDs
  • V-56695
Rule IDs
  • SV-70955r2_rule
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 changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different. If the password length is an odd number then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least 8 characters.
Checks: C-57265r1_chk

Verify the operating system requires the change of at least eight of the total number of characters when passwords are changed. If it does not, this is a finding.

Fix: F-61591r1_fix

Configure the operating system to require the change of at least eight of the total number of characters when passwords are changed.

b
The operating system must store only encrypted representations of passwords.
IA-5 - Medium - CCI-000196 - V-56697 - SV-70957r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000196
Version
SRG-OS-000073-GPOS-00041
Vuln IDs
  • V-56697
Rule IDs
  • SV-70957r1_rule
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.
Checks: C-57267r1_chk

Verify the operating system stores only encrypted representations of passwords. If it does not, this is a finding.

Fix: F-61593r2_fix

Configure the operating system to store only encrypted representations of passwords.

b
The operating system must transmit only encrypted representations of passwords.
IA-5 - Medium - CCI-000197 - V-56699 - SV-70959r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000197
Version
SRG-OS-000074-GPOS-00042
Vuln IDs
  • V-56699
Rule IDs
  • SV-70959r1_rule
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.
Checks: C-57269r1_chk

Verify the operating system transmits only encrypted representations of passwords. If it does not, this is a finding.

Fix: F-61595r1_fix

Configure the operating system to transmit only encrypted representations of passwords.

b
Operating systems must enforce 24 hours/1 day as the minimum password lifetime.
IA-5 - Medium - CCI-000198 - V-56701 - SV-70961r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000198
Version
SRG-OS-000075-GPOS-00043
Vuln IDs
  • V-56701
Rule IDs
  • SV-70961r1_rule
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 repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.
Checks: C-57271r1_chk

Verify operating system enforces 24 hours/1 day as the minimum password lifetime. If it does not, this is a finding.

Fix: F-61597r1_fix

Configure operating system to enforce 24 hours/1 day as the minimum password lifetime.

b
Operating systems must enforce a 60-day maximum password lifetime restriction.
IA-5 - Medium - CCI-000199 - V-56703 - SV-70963r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000199
Version
SRG-OS-000076-GPOS-00044
Vuln IDs
  • V-56703
Rule IDs
  • SV-70963r1_rule
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 operating system passwords could be compromised.
Checks: C-57273r1_chk

Verify operating system enforces a 60-day maximum password lifetime restriction. If it does not, this is a finding.

Fix: F-61599r1_fix

Configure operating system to enforce a 60-day maximum password lifetime restriction.

b
The operating system must prohibit password reuse for a minimum of five generations.
IA-5 - Medium - CCI-000200 - V-56705 - SV-70965r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000200
Version
SRG-OS-000077-GPOS-00045
Vuln IDs
  • V-56705
Rule IDs
  • SV-70965r1_rule
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 has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.
Checks: C-57275r1_chk

Verify the operating system prohibits password reuse for a minimum of five generations. If it does not, this is a finding.

Fix: F-61601r1_fix

Configure the operating system to prohibit password reuse for a minimum of five generations.

b
The operating system must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur.
AU-12 - Medium - CCI-000172 - V-56711 - SV-70971r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000461-GPOS-00205
Vuln IDs
  • V-56711
Rule IDs
  • SV-70971r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57281r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. If it does not, this is a finding.

Fix: F-61607r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur.

b
The operating system must generate audit records when successful/unsuccessful attempts to access security objects occur.
AU-12 - Medium - CCI-000172 - V-56713 - SV-70973r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
SRG-OS-000458-GPOS-00203
Vuln IDs
  • V-56713
Rule IDs
  • SV-70973r1_rule
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 records can be generated from various components within the information system (e.g., module or policy filter).
Checks: C-57283r1_chk

Verify the operating system generates audit records when successful/unsuccessful attempts to access security objects occur. If it does not, this is a finding.

Fix: F-61609r1_fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to access security objects occur.

b
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.
SI-6 - Medium - CCI-002702 - V-56715 - SV-70975r1_rule
RMF Control
SI-6
Severity
Medium
CCI
CCI-002702
Version
SRG-OS-000447-GPOS-00201
Vuln IDs
  • V-56715
Rule IDs
  • SV-70975r1_rule
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 isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Notifications provided by information systems include messages to local computer consoles, and/or hardware indications, such as lights. This capability must take into account operational requirements for availability for selecting an appropriate response. The organization may choose to shut down or restart the information system upon security function anomaly detection.
Checks: C-57285r1_chk

Verify the operating system shuts down the information system, restarts the information system, and/or notifies the system administrator when anomalies in the operation of any security functions are discovered. If it does not, this is a finding.

Fix: F-61611r1_fix

Configure the operating system to shut down the information system, restart the information system, and/or notify the system administrator when anomalies in the operation of the security functions are discovered.

b
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.
SI-6 - Medium - CCI-002699 - V-56717 - SV-70977r1_rule
RMF Control
SI-6
Severity
Medium
CCI
CCI-002699
Version
SRG-OS-000446-GPOS-00200
Vuln IDs
  • V-56717
Rule IDs
  • SV-70977r1_rule
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 system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights. This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality.
Checks: C-57287r1_chk

Verify the operating system performs 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. If it does not, this is a finding.

Fix: F-61613r1_fix

Configure the operating system to 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.

b
The operating system must verify correct operation of all security functions.
SI-6 - Medium - CCI-002696 - V-56719 - SV-70979r1_rule
RMF Control
SI-6
Severity
Medium
CCI
CCI-002696
Version
SRG-OS-000445-GPOS-00199
Vuln IDs
  • V-56719
Rule IDs
  • SV-70979r1_rule
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 system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality.
Checks: C-57289r1_chk

Verify the operating system verifies correct operation of all security functions. If it does not, this is a finding.

Fix: F-61615r1_fix

Configure the operating system to verify correct operation of all security functions.

b
The operating system must remove all software components after updated versions have been installed.
SI-2 - Medium - CCI-002617 - V-56721 - SV-70981r1_rule
RMF Control
SI-2
Severity
Medium
CCI
CCI-002617
Version
SRG-OS-000437-GPOS-00194
Vuln IDs
  • V-56721
Rule IDs
  • SV-70981r1_rule
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 information system.
Checks: C-57291r1_chk

Verify the operating system removes all software components after updated versions have been installed. If it does not, this is a finding.

Fix: F-61617r1_fix

Configure the operating system to remove all software components after updated versions have been installed.

b
The operating system must implement address space layout randomization to protect its memory from unauthorized code execution.
SI-16 - Medium - CCI-002824 - V-56723 - SV-70983r1_rule
RMF Control
SI-16
Severity
Medium
CCI
CCI-002824
Version
SRG-OS-000433-GPOS-00193
Vuln IDs
  • V-56723
Rule IDs
  • SV-70983r1_rule
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 space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. Examples of attacks are buffer overflow attacks.
Checks: C-57293r1_chk

Verify the operating system implements address space layout randomization to protect its memory from unauthorized code execution. If it does not, this is a finding.

Fix: F-61619r1_fix

Configure the operating system to implement address space layout randomization to protect its memory from unauthorized code execution.

b
The operating system must implement non-executable data to protect its memory from unauthorized code execution.
SI-16 - Medium - CCI-002824 - V-56725 - SV-70985r1_rule
RMF Control
SI-16
Severity
Medium
CCI
CCI-002824
Version
SRG-OS-000433-GPOS-00192
Vuln IDs
  • V-56725
Rule IDs
  • SV-70985r1_rule
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 space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. Examples of attacks are buffer overflow attacks.
Checks: C-57295r1_chk

Verify the operating system implements non-executable data to protect its memory from unauthorized code execution. If it does not, this is a finding.

Fix: F-61621r1_fix

Configure the operating system to implement non-executable data to protect its memory from unauthorized code execution.

b
The operating system must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.
SI-10 - Medium - CCI-002754 - V-56727 - SV-70987r1_rule
RMF Control
SI-10
Severity
Medium
CCI
CCI-002754
Version
SRG-OS-000432-GPOS-00191
Vuln IDs
  • V-56727
Rule IDs
  • SV-70987r1_rule
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 may be disruptive or cause the system to fail into an unsafe state. The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.
Checks: C-57297r1_chk

Verify the operating system behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. If it does not, this is a finding.

Fix: F-61623r1_fix

Configure the operating system to behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.

b
The operating system must maintain the confidentiality and integrity of information during reception.
SC-8 - Medium - CCI-002422 - V-56729 - SV-70989r1_rule
RMF Control
SC-8
Severity
Medium
CCI
CCI-002422
Version
SRG-OS-000426-GPOS-00190
Vuln IDs
  • V-56729
Rule IDs
  • SV-70989r1_rule
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 compromise the confidentiality or integrity of the information. Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When receiving data, operating systems need to leverage protection mechanisms such as TLS, SSL VPNs, or IPSec.
Checks: C-57299r1_chk

Verify the operating system maintains the confidentiality and integrity of information during reception. If it does not, this is a finding.

Fix: F-61625r1_fix

Configure the operating system to maintain the confidentiality and integrity of information during reception.

b
The operating system must maintain the confidentiality and integrity of information during preparation for transmission.
SC-8 - Medium - CCI-002420 - V-56731 - SV-70991r1_rule
RMF Control
SC-8
Severity
Medium
CCI
CCI-002420
Version
SRG-OS-000425-GPOS-00189
Vuln IDs
  • V-56731
Rule IDs
  • SV-70991r1_rule
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 modifications compromise the confidentiality or integrity of the information. Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, SSL VPNs, or IPSec.
Checks: C-57301r1_chk

Verify the operating system maintains the confidentiality and integrity of information during preparation for transmission. If it does not, this is a finding.

Fix: F-61627r1_fix

Configure the operating system to maintain the confidentiality and integrity of information during preparation for transmission.

b
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).
SC-8 - Medium - CCI-002421 - V-56733 - SV-70993r1_rule
RMF Control
SC-8
Severity
Medium
CCI
CCI-002421
Version
SRG-OS-000424-GPOS-00188
Vuln IDs
  • V-56733
Rule IDs
  • SV-70993r1_rule
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 application in digital signatures, checksums, and message authentication codes. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to leverage transmission protection mechanisms such as TLS, SSL VPNs, or IPSec. Alternative physical protection measures include PDS. PDSs are used to transmit unencrypted classified National Security Information (NSI) through an area of lesser classification or control. Since the classified NSI is unencrypted, the PDS must provide adequate electrical, electromagnetic, and physical safeguards to deter exploitation.
Checks: C-57303r1_chk

Verify the operating system implements 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). If it does not, this is a finding.

Fix: F-61629r1_fix

Configure the operating system to 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).

b
The operating system must protect the confidentiality and integrity of transmitted information.
SC-8 - Medium - CCI-002418 - V-56735 - SV-70995r1_rule
RMF Control
SC-8
Severity
Medium
CCI
CCI-002418
Version
SRG-OS-000423-GPOS-00187
Vuln IDs
  • V-56735
Rule IDs
  • SV-70995r1_rule
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 types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.
Checks: C-57305r1_chk

Verify the operating system protects the confidentiality and integrity of transmitted information. If it does not, this is a finding.

Fix: F-61631r1_fix

Configure the operating system to protect the confidentiality and integrity of transmitted information.

b
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.
SC-5 - Medium - CCI-002385 - V-56737 - SV-70997r1_rule
RMF Control
SC-5
Severity
Medium
CCI
CCI-002385
Version
SRG-OS-000420-GPOS-00186
Vuln IDs
  • V-56737
Rule IDs
  • SV-70997r1_rule
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 to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.
Checks: C-57307r1_chk

Verify the operating system protects against or limits the effects of Denial of Service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces. If it does not, this is a finding.

Fix: F-61633r1_fix

Configure the operating system to 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.

b
The operating system must implement cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all operating system components.
SC-28 - Medium - CCI-002476 - V-56739 - SV-70999r1_rule
RMF Control
SC-28
Severity
Medium
CCI
CCI-002476
Version
SRG-OS-000405-GPOS-00184
Vuln IDs
  • V-56739
Rule IDs
  • SV-70999r1_rule
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 protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).
Checks: C-57309r1_chk

Verify the operating system implements cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all operating system components. If it does not, this is a finding.

Fix: F-61635r1_fix

Configure the operating system to implement cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all operating system components.

b
The operating system must implement cryptographic mechanisms to prevent unauthorized modification of all information at rest on all operating system components.
SC-28 - Medium - CCI-002475 - V-56741 - SV-71001r1_rule
RMF Control
SC-28
Severity
Medium
CCI
CCI-002475
Version
SRG-OS-000404-GPOS-00183
Vuln IDs
  • V-56741
Rule IDs
  • SV-71001r1_rule
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 protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).
Checks: C-57311r1_chk

Verify the operating system implements cryptographic mechanisms to prevent unauthorized modification of all information at rest on all operating system components. If it does not, this is a finding.

Fix: F-61637r1_fix

Configure the operating system to implement cryptographic mechanisms to prevent unauthorized modification of all information at rest on all operating system components.

b
The operating system must enforce a minimum 15-character password length.
IA-5 - Medium - CCI-000205 - V-56743 - SV-71003r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000205
Version
SRG-OS-000078-GPOS-00046
Vuln IDs
  • V-56743
Rule IDs
  • SV-71003r1_rule
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 brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.
Checks: C-57313r1_chk

Verify the operating system enforces a minimum 15-character password length. If it does not, this is a finding.

Fix: F-61639r1_fix

Configure the operating system to enforce a minimum 15-character password length.

b
The operating system must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
IA-6 - Medium - CCI-000206 - V-56745 - SV-71005r1_rule
RMF Control
IA-6
Severity
Medium
CCI
CCI-000206
Version
SRG-OS-000079-GPOS-00047
Vuln IDs
  • V-56745
Rule IDs
  • SV-71005r1_rule
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. Obfuscation of user-provided information that is typed into the system is a method used when addressing this risk. For example, displaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.
Checks: C-57315r1_chk

Verify the operating system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. If it does not, this is a finding.

Fix: F-61641r1_fix

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

b
The operating system must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
AC-3 - Medium - CCI-000213 - V-56747 - SV-71007r1_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
SRG-OS-000080-GPOS-00048
Vuln IDs
  • V-56747
Rule IDs
  • SV-71007r1_rule
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 that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.
Checks: C-57317r1_chk

Verify the operating system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies. If it does not, this is a finding.

Fix: F-61643r1_fix

Configure the operating system to enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

b
The operating system must be configured to disable non-essential capabilities.
CM-7 - Medium - CCI-000381 - V-56749 - SV-71009r1_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
SRG-OS-000095-GPOS-00049
Vuln IDs
  • V-56749
Rule IDs
  • SV-71009r1_rule
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 risk to the platform by providing additional attack vectors. Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.
Checks: C-57319r1_chk

Verify the operating system is configured to disable non-essential capabilities. If it does not, this is a finding.

Fix: F-61645r1_fix

Configure the operating system to disable non-essential capabilities.

b
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.
CM-7 - Medium - CCI-000382 - V-56751 - SV-71011r1_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000382
Version
SRG-OS-000096-GPOS-00050
Vuln IDs
  • V-56751
Rule IDs
  • SV-71011r1_rule
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 ports/protocols on information systems. Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.
Checks: C-57321r1_chk

Verify the operating system is configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. If it does not, this is a finding.

Fix: F-61647r1_fix

Configure the operating system to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

b
The operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users).
IA-2 - Medium - CCI-000764 - V-56753 - SV-71013r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
SRG-OS-000104-GPOS-00051
Vuln IDs
  • V-56753
Rule IDs
  • SV-71013r1_rule
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 organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: 1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and 2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.
Checks: C-57323r1_chk

Verify the operating system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users). If it does not, this is a finding.

Fix: F-61649r1_fix

Configure the operating system to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

b
The operating system must use multifactor authentication for network access to privileged accounts.
IA-2 - Medium - CCI-000765 - V-56755 - SV-71015r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000765
Version
SRG-OS-000105-GPOS-00052
Vuln IDs
  • V-56755
Rule IDs
  • SV-71015r1_rule
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., password/PIN); 2) something a user has (e.g., cryptographic identification device, token); and 3) something a user is (e.g., biometric). A privileged account is defined as an information system account with authorizations of a privileged user. Network access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the Internet). The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
Checks: C-57325r1_chk

Verify the operating system uses multifactor authentication for network access to privileged accounts. If it does not, this is a finding.

Fix: F-61651r1_fix

Configure the operating system to use multifactor authentication for network access to privileged accounts.

b
The operating system must use multifactor authentication for network access to non-privileged accounts.
IA-2 - Medium - CCI-000766 - V-56757 - SV-71017r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000766
Version
SRG-OS-000106-GPOS-00053
Vuln IDs
  • V-56757
Rule IDs
  • SV-71017r1_rule
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 authentication. Factors include: 1) Something you know (e.g., password/PIN); 2) Something you have (e.g., cryptographic identification device, token); and 3) Something you are (e.g., biometric). A non-privileged account is any information system account with authorizations of a non-privileged user. Network access is any access to an application by a user (or process acting on behalf of a user) where said access is obtained through a network connection. The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
Checks: C-57327r1_chk

Verify the operating system uses multifactor authentication for network access to non-privileged accounts. If it does not, this is a finding.

Fix: F-61653r1_fix

Configure the operating system to use multifactor authentication for network access to non-privileged accounts.

b
The operating system must use multifactor authentication for local access to privileged accounts.
IA-2 - Medium - CCI-000767 - V-56759 - SV-71019r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000767
Version
SRG-OS-000107-GPOS-00054
Vuln IDs
  • V-56759
Rule IDs
  • SV-71019r1_rule
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 authentication. Factors include: 1) Something you know (e.g., password/PIN); 2) Something you have (e.g., cryptographic identification device, token); and 3) Something you are (e.g., biometric). A privileged account is defined as an operating system account with authorizations of a privileged user. Local access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
Checks: C-57329r1_chk

Verify the operating system uses multifactor authentication for local access to privileged accounts. If it does not, this is a finding.

Fix: F-61655r1_fix

Configure the operating system to use multifactor authentication for local access to privileged accounts.

b
The operating system must use multifactor authentication for local access to non-privileged accounts.
IA-2 - Medium - CCI-000768 - V-56761 - SV-71021r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000768
Version
SRG-OS-000108-GPOS-00055
Vuln IDs
  • V-56761
Rule IDs
  • SV-71021r1_rule
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 authentication. Factors include: 1) Something you know (e.g., password/PIN); 2) Something you have (e.g., cryptographic identification device or token); and 3) Something you are (e.g., biometric). A non-privileged account is defined as an operating system account with authorizations of a regular or non-privileged user. Local access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. The DoD CAC with DoD-approved PKI is an example of multifactor authentication.
Checks: C-57331r1_chk

Verify the operating system uses multifactor authentication for local access to non-privileged accounts. If it does not, this is a finding.

Fix: F-61657r1_fix

Configure the operating system to use multifactor authentication for local access to non-privileged accounts.

b
The operating system must require individuals to be authenticated with an individual authenticator prior to using a group authenticator.
IA-2 - Medium - CCI-000770 - V-56763 - SV-71023r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
SRG-OS-000109-GPOS-00056
Vuln IDs
  • V-56763
Rule IDs
  • SV-71023r1_rule
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 not uniquely identify individual users. Examples of the group authenticator is the UNIX OS "root" user account, the Windows "Administrator" account, the "sa" account, or a "helpdesk" account. For example, the UNIX and Windows operating systems offer a 'switch user' capability allowing users to authenticate with their individual credentials and, when needed, 'switch' to the administrator role. This method provides for unique individual authentication prior to using a group authenticator. Users (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on the operating system without identification or authentication. Requiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.
Checks: C-57333r1_chk

Verify the operating system requires individuals to be authenticated with an individual authenticator prior to using a group authenticator. If it does not, this is a finding.

Fix: F-61659r1_fix

Configure the operating system to require individuals to be authenticated with an individual authenticator prior to using a group authenticator.

b
The operating system must implement replay-resistant authentication mechanisms for network access to privileged accounts.
IA-2 - Medium - CCI-001941 - V-56765 - SV-71025r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-001941
Version
SRG-OS-000112-GPOS-00057
Vuln IDs
  • V-56765
Rule IDs
  • SV-71025r1_rule
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 authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. A privileged account is any information system account with authorizations of a privileged user. Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.
Checks: C-57335r1_chk

Verify the operating system implements replay-resistant authentication mechanisms for network access to privileged accounts. If it does not, this is a finding.

Fix: F-61661r1_fix

Configure the operating system to implement replay-resistant authentication mechanisms for network access to privileged accounts.

b
The operating system must implement replay-resistant authentication mechanisms for network access to non-privileged accounts.
IA-2 - Medium - CCI-001942 - V-56767 - SV-71027r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-001942
Version
SRG-OS-000113-GPOS-00058
Vuln IDs
  • V-56767
Rule IDs
  • SV-71027r1_rule
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 authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. A non-privileged account is any operating system account with authorizations of a non-privileged user. Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.
Checks: C-57337r1_chk

Verify the operating system implements replay-resistant authentication mechanisms for network access to non-privileged accounts. If it does not, this is a finding.

Fix: F-61663r1_fix

Configure the operating system to implement replay-resistant authentication mechanisms for network access to non-privileged accounts.

b
The operating system must uniquely identify peripherals before establishing a connection.
IA-3 - Medium - CCI-000778 - V-56769 - SV-71029r1_rule
RMF Control
IA-3
Severity
Medium
CCI
CCI-000778
Version
SRG-OS-000114-GPOS-00059
Vuln IDs
  • V-56769
Rule IDs
  • SV-71029r1_rule
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.
Checks: C-57339r1_chk

Verify the operating system uniquely identifies peripherals before establishing a connection. If it does not, this is a finding.

Fix: F-61665r1_fix

Configure the operating system to uniquely identify peripherals before establishing a connection.

b
The operating system must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.
IA-4 - Medium - CCI-000795 - V-56771 - SV-71031r1_rule
RMF Control
IA-4
Severity
Medium
CCI
CCI-000795
Version
SRG-OS-000118-GPOS-00060
Vuln IDs
  • V-56771
Rule IDs
  • SV-71031r1_rule
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 account has been obtained. Operating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.
Checks: C-57341r1_chk

Verify the operating system disables account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. If it does not, this is a finding.

Fix: F-61667r1_fix

Configure the operating system to disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.

b
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.
SC-23 - Medium - CCI-002470 - V-56773 - SV-71033r2_rule
RMF Control
SC-23
Severity
Medium
CCI
CCI-002470
Version
SRG-OS-000403-GPOS-00182
Vuln IDs
  • V-56773
Rule IDs
  • SV-71033r2_rule
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 is not a DoD-approved CA, trust of this CA has not been established. The DoD will only accept PKI-certificates obtained from a DoD-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of SSL/TLS certificates.
Checks: C-57343r1_chk

Verify the operating system only allows the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions. If it does not, this is a finding.

Fix: F-61669r1_fix

Configure the operating system to only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.

b
The operating system must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002468 - V-56775 - SV-71035r1_rule
RMF Control
SC-21
Severity
Medium
CCI
CCI-002468
Version
SRG-OS-000402-GPOS-00181
Vuln IDs
  • V-56775
Rule IDs
  • SV-71035r1_rule
If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data origin authentication verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-57345r1_chk

Verify the operating system performs data origin verification authentication on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-61671r1_fix

Configure the operating system to perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.

b
The operating system must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002467 - V-56777 - SV-71037r1_rule
RMF Control
SC-21
Severity
Medium
CCI
CCI-002467
Version
SRG-OS-000401-GPOS-00180
Vuln IDs
  • V-56777
Rule IDs
  • SV-71037r1_rule
If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data integrity verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-57347r1_chk

Verify the operating system performs data integrity verification on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-61673r1_fix

Configure the operating system to perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.

b
The operating system must request data integrity verification on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002466 - V-56779 - SV-71039r1_rule
RMF Control
SC-21
Severity
Medium
CCI
CCI-002466
Version
SRG-OS-000400-GPOS-00179
Vuln IDs
  • V-56779
Rule IDs
  • SV-71039r1_rule
If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data integrity verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-57349r1_chk

Verify the operating system requests data integrity verification on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-61675r1_fix

Configure the operating system to request data integrity verification on the name/address resolution responses the system receives from authoritative sources.

b
The operating system must request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.
SC-21 - Medium - CCI-002465 - V-56781 - SV-71041r1_rule
RMF Control
SC-21
Severity
Medium
CCI
CCI-002465
Version
SRG-OS-000399-GPOS-00178
Vuln IDs
  • V-56781
Rule IDs
  • SV-71041r1_rule
If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed, which would result in query failure or DoS. Data origin authentication must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity of response data. This is not applicable if DNSSEC is not implemented on the local network.
Checks: C-57351r1_chk

Verify the operating system requests data origin authentication verification on the name/address resolution responses the system receives from authoritative sources. If it does not, this is a finding.

Fix: F-61677r1_fix

Configure the operating system to request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.

b
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.
SC-13 - Medium - CCI-002450 - V-56783 - SV-71043r1_rule
RMF Control
SC-13
Severity
Medium
CCI
CCI-002450
Version
SRG-OS-000396-GPOS-00176
Vuln IDs
  • V-56783
Rule IDs
  • SV-71043r1_rule
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 provides assurance they have been tested and validated.
Checks: C-57353r1_chk

Verify the operating system implements NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. If it does not, this is a finding.

Fix: F-61679r1_fix

Configure the operating system to implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

b
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.
IA-7 - Medium - CCI-000803 - V-56785 - SV-71045r1_rule
RMF Control
IA-7
Severity
Medium
CCI
CCI-000803
Version
SRG-OS-000120-GPOS-00061
Vuln IDs
  • V-56785
Rule IDs
  • SV-71045r1_rule
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 required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system.
Checks: C-57355r1_chk

Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. If it does not, this is a finding.

Fix: F-61681r1_fix

Configure the operating system to use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.

b
The operating system must verify remote disconnection at the termination of nonlocal maintenance and diagnostic sessions, when used for nonlocal maintenance sessions.
MA-4 - Medium - CCI-002891 - V-56787 - SV-71047r1_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-002891
Version
SRG-OS-000395-GPOS-00175
Vuln IDs
  • V-56787
Rule IDs
  • SV-71047r1_rule
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 maintenance sessions have been terminated and are no longer available for use.
Checks: C-57357r1_chk

Verify the operating system verifies remote disconnection at the termination of nonlocal maintenance and diagnostic sessions, when used for nonlocal maintenance sessions. If it does not, this is a finding.

Fix: F-61683r1_fix

Configure the operating system to verify remote disconnection at the termination of nonlocal maintenance and diagnostic sessions, when used for nonlocal maintenance sessions.

b
The operating system must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions.
MA-4 - Medium - CCI-003123 - V-56789 - SV-71049r1_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-003123
Version
SRG-OS-000394-GPOS-00174
Vuln IDs
  • V-56789
Rule IDs
  • SV-71049r1_rule
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 maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch). The operating system can meet this requirement through leveraging a cryptographic module.
Checks: C-57359r1_chk

Verify the operating system implements cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding.

Fix: F-61685r1_fix

Configure the operating system to implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions.

b
The operating system must uniquely identify and must authenticate non-organizational users (or processes acting on behalf of non-organizational users).
IA-8 - Medium - CCI-000804 - V-56791 - SV-71051r1_rule
RMF Control
IA-8
Severity
Medium
CCI
CCI-000804
Version
SRG-OS-000121-GPOS-00062
Vuln IDs
  • V-56791
Rule IDs
  • SV-71051r1_rule
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 system. Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of an employee (e.g., contractors and guest researchers). Non-organizational users shall be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access.
Checks: C-57361r1_chk

Verify the operating system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users). If it does not, this is a finding.

Fix: F-61687r1_fix

Configure the operating system to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

b
The operating system must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions.
MA-4 - Medium - CCI-002890 - V-56793 - SV-71053r1_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-002890
Version
SRG-OS-000393-GPOS-00173
Vuln IDs
  • V-56793
Rule IDs
  • SV-71053r1_rule
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 integrity. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. The operating system can meet this requirement through leveraging a cryptographic module. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).
Checks: C-57363r1_chk

Verify the operating system implements cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions. If it does not, this is a finding.

Fix: F-61689r1_fix

Configure the operating system to implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions.

b
The operating system must audit all activities performed during nonlocal maintenance and diagnostic sessions.
MA-4 - Medium - CCI-002884 - V-56795 - SV-71055r1_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-002884
Version
SRG-OS-000392-GPOS-00172
Vuln IDs
  • V-56795
Rule IDs
  • SV-71055r1_rule
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 tools used specifically for diagnostic and repair actions on organizational information systems. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch.
Checks: C-57365r1_chk

Verify the operating system audits all activities performed during nonlocal maintenance and diagnostic sessions. If it does not, this is a finding.

Fix: F-61691r1_fix

Configure the operating system to audit all activities performed during nonlocal maintenance and diagnostic sessions.

b
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.
IA-5 - Medium - CCI-001991 - V-56797 - SV-71057r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-001991
Version
SRG-OS-000384-GPOS-00167
Vuln IDs
  • V-56797
Rule IDs
  • SV-71057r1_rule
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).
Checks: C-57369r1_chk

Verify the operating system, for PKI-based authentication, implements a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. If it does not, this is a finding.

Fix: F-61695r1_fix

Configure the operating system, for PKI-based authentication, to 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.

b
The operating system must provide an audit reduction capability that supports on-demand reporting requirements.
AU-7 - Medium - CCI-001876 - V-56799 - SV-71059r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001876
Version
SRG-OS-000122-GPOS-00063
Vuln IDs
  • V-56799
Rule IDs
  • SV-71059r1_rule
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 incidents. Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports.
Checks: C-57367r1_chk

Verify the operating system provides an audit reduction capability that supports on-demand reporting requirements. If it does not, this is a finding.

Fix: F-61693r1_fix

Configure the operating system to provide an audit reduction capability that supports on-demand reporting requirements.

b
The operating system must prohibit the use of cached authenticators after one day.
IA-5 - Medium - CCI-002007 - V-56801 - SV-71061r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-002007
Version
SRG-OS-000383-GPOS-00166
Vuln IDs
  • V-56801
Rule IDs
  • SV-71061r1_rule
If cached authentication information is out-of-date, the validity of the authentication information may be questionable.
Checks: C-57371r1_chk

Verify the operating system prohibits the use of cached authenticators after one day. If it does not, this is a finding.

Fix: F-61697r1_fix

Configure the operating system to prohibit the use of cached authenticators after one day.

b
The operating system must allow the use of a temporary password for system logons with an immediate change to a permanent password.
IA-5 - Medium - CCI-002041 - V-56803 - SV-71063r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-002041
Version
SRG-OS-000380-GPOS-00165
Vuln IDs
  • V-56803
Rule IDs
  • SV-71063r1_rule
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 typically used to allow access when new accounts are created or passwords are changed. It is common practice for administrators to create temporary passwords for user accounts which allow the users to log on, yet force them to change the password once they have successfully authenticated.
Checks: C-57373r1_chk

Verify the operating system allows the use of a temporary password for system logons with an immediate change to a permanent password. If it does not, this is a finding.

Fix: F-61699r1_fix

Configure the operating system to allow the use of a temporary password for system logons with an immediate change to a permanent password.

b
The information system must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.
AC-2 - Medium - CCI-001682 - V-56805 - SV-71065r3_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001682
Version
SRG-OS-000123-GPOS-00064
Vuln IDs
  • V-56805
Rule IDs
  • SV-71065r3_rule
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 accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. Emergency accounts are different from infrequently used accounts (i.e., local logon accounts used by the organization's system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.
Checks: C-57375r3_chk

Verify the operating system is configured such that emergency administrator accounts are automatically removed or disabled within 72 hours. If it is not, this is a finding.

Fix: F-61701r3_fix

Configure the operating system such that emergency administrator accounts are automatically removed or disabled within 72 hours.

b
The operating system must authenticate all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based.
IA-3 - Medium - CCI-001967 - V-56807 - SV-71067r1_rule
RMF Control
IA-3
Severity
Medium
CCI
CCI-001967
Version
SRG-OS-000379-GPOS-00164
Vuln IDs
  • V-56807
Rule IDs
  • SV-71067r1_rule
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 greater risk. Bidirectional authentication solutions include, but are not limited to, IEEE 802.1x and Extensible Authentication Protocol [EAP], RADIUS server with EAP-Transport Layer Security [TLS] authentication, Kerberos, and SSL mutual authentication. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area network, wide area network, or the Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply this requirement to those limited number (and type) of devices that truly need to support this capability.
Checks: C-57377r1_chk

Verify the operating system authenticates all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based. If it does not, this is a finding.

Fix: F-61703r1_fix

Configure the operating system to authenticate all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based.

b
The operating system must authenticate peripherals before establishing a connection.
IA-3 - Medium - CCI-001958 - V-56809 - SV-71069r1_rule
RMF Control
IA-3
Severity
Medium
CCI
CCI-001958
Version
SRG-OS-000378-GPOS-00163
Vuln IDs
  • V-56809
Rule IDs
  • SV-71069r1_rule
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.
Checks: C-57379r1_chk

Verify the operating system authenticates peripherals before establishing a connection. If it does not, this is a finding.

Fix: F-61705r1_fix

Configure the operating system to authenticate peripherals before establishing a connection.

b
The operating system must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.
MA-4 - Medium - CCI-000877 - V-56811 - SV-71071r1_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-000877
Version
SRG-OS-000125-GPOS-00065
Vuln IDs
  • V-56811
Rule IDs
  • SV-71071r1_rule
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 configuration details, diagnostic information, user information, and potentially sensitive application data. Some maintenance and test tools are either standalone devices with their own operating systems or are applications bundled with an operating system. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric.
Checks: C-57381r1_chk

Verify the operating system employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. If it does not, this is a finding.

Fix: F-61707r1_fix

Configure the operating system to employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.

b
The operating system must electronically verify Personal Identity Verification (PIV) credentials.
IA-2 - Medium - CCI-001954 - V-56813 - SV-71073r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-001954
Version
SRG-OS-000377-GPOS-00162
Vuln IDs
  • V-56813
Rule IDs
  • SV-71073r1_rule
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 Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.
Checks: C-57383r1_chk

Verify the operating system electronically verifies Personal Identity Verification (PIV) credentials. If it does not, this is a finding.

Fix: F-61709r1_fix

Configure the operating system to electronically verify Personal Identity Verification (PIV) credentials.

b
The operating system must accept Personal Identity Verification (PIV) credentials.
IA-2 - Medium - CCI-001953 - V-56815 - SV-71075r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-001953
Version
SRG-OS-000376-GPOS-00161
Vuln IDs
  • V-56815
Rule IDs
  • SV-71075r1_rule
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 Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.
Checks: C-57385r1_chk

Verify the operating system accepts Personal Identity Verification (PIV) credentials. If it does not, this is a finding.

Fix: F-61711r1_fix

Configure the operating system to accept Personal Identity Verification (PIV) credentials.

b
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.
IA-2 - Medium - CCI-001948 - V-56817 - SV-71077r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-001948
Version
SRG-OS-000375-GPOS-00160
Vuln IDs
  • V-56817
Rule IDs
  • SV-71077r1_rule
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 solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card. A privileged account is defined as an information system account with authorizations of a privileged user. Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management). Requires further clarification from NIST.
Checks: C-57387r1_chk

Verify the operating system implements 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. If it does not, this is a finding.

Fix: F-61713r1_fix

Configure the operating system to 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.

b
The operating system must require devices to re-authenticate when changing authenticators.
IA-11 - Medium - CCI-002039 - V-56823 - SV-71083r1_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002039
Version
SRG-OS-000374-GPOS-00159
Vuln IDs
  • V-56823
Rule IDs
  • SV-71083r1_rule
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.
Checks: C-57393r1_chk

Verify the operating system requires devices to re-authenticate when changing authenticators. If it does not, this is a finding.

Fix: F-61719r1_fix

Configure the operating system to require devices to re-authenticate when changing authenticators.

b
The operating system must require users to re-authenticate when changing authenticators.
IA-11 - Medium - CCI-002038 - V-56827 - SV-71087r1_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
SRG-OS-000373-GPOS-00158
Vuln IDs
  • V-56827
Rule IDs
  • SV-71087r1_rule
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.
Checks: C-57397r1_chk

Verify the operating system requires users to re-authenticate when changing authenticators. If it does not, this is a finding.

Fix: F-61723r1_fix

Configure the operating system to require users to re-authenticate when changing authenticators.

b
The operating system must terminate all sessions and network connections related to nonlocal maintenance when nonlocal maintenance is completed.
MA-4 - Medium - CCI-000879 - V-56829 - SV-71089r1_rule
RMF Control
MA-4
Severity
Medium
CCI
CCI-000879
Version
SRG-OS-000126-GPOS-00066
Vuln IDs
  • V-56829
Rule IDs
  • SV-71089r1_rule
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 systems or are applications bundled with an operating system. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.
Checks: C-57399r1_chk

Verify the operating system terminates all sessions and network connections related to nonlocal maintenance when nonlocal maintenance is completed. If it does not, this is a finding.

Fix: F-61725r1_fix

Configure the operating system to terminate all sessions and network connections related to nonlocal maintenance when nonlocal maintenance is completed.

b
The operating system must require users to re-authenticate when changing roles.
IA-11 - Medium - CCI-002038 - V-56831 - SV-71091r1_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
SRG-OS-000373-GPOS-00157
Vuln IDs
  • V-56831
Rule IDs
  • SV-71091r1_rule
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.
Checks: C-57401r1_chk

Verify the operating system requires users to re-authenticate when changing roles. If it does not, this is a finding.

Fix: F-61727r1_fix

Configure the operating system to require users to re-authenticate when changing roles.

b
The operating system must separate user functionality (including user interface services) from operating system management functionality.
SC-2 - Medium - CCI-001082 - V-56835 - SV-71095r1_rule
RMF Control
SC-2
Severity
Medium
CCI
CCI-001082
Version
SRG-OS-000132-GPOS-00067
Vuln IDs
  • V-56835
Rule IDs
  • SV-71095r1_rule
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-privileged users may obtain elevated privileges. Operating system management functionality includes functions necessary to administer console, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, different TCP/UDP ports, virtualization techniques, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different security domain and with additional access controls.
Checks: C-57405r1_chk

Verify the operating system separates user functionality (including user interface services) from operating system management functionality. If it does not, this is a finding.

Fix: F-61731r1_fix

Configure the operating system to separate user functionality (including user interface services) from operating system management functionality.

b
The operating system must require users to re-authenticate for privilege escalation.
IA-11 - Medium - CCI-002038 - V-56837 - SV-71097r1_rule
RMF Control
IA-11
Severity
Medium
CCI
CCI-002038
Version
SRG-OS-000373-GPOS-00156
Vuln IDs
  • V-56837
Rule IDs
  • SV-71097r1_rule
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.
Checks: C-57407r1_chk

Verify the operating system requires users to re-authenticate for privilege escalation. If it does not, this is a finding.

Fix: F-61733r1_fix

Configure the operating system to require users to re-authenticate for privilege escalation.

b
The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.
CM-7 - Medium - CCI-001774 - V-56841 - SV-71101r2_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-001774
Version
SRG-OS-000370-GPOS-00155
Vuln IDs
  • V-56841
Rule IDs
  • SV-71101r2_rule
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 authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. Verification of white-listed software occurs prior to execution or at system startup. This requirement applies to operating system programs, functions, and services designed to manage system processes and configurations (e.g., group policies).
Checks: C-57413r1_chk

Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. If it does not, this is a finding.

Fix: F-61739r1_fix

Configure the operating system to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.

b
The operating system must isolate security functions from nonsecurity functions.
SC-3 - Medium - CCI-001084 - V-56843 - SV-71103r1_rule
RMF Control
SC-3
Severity
Medium
CCI
CCI-001084
Version
SRG-OS-000134-GPOS-00068
Vuln IDs
  • V-56843
Rule IDs
  • SV-71103r1_rule
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 enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code. Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.
Checks: C-57411r1_chk

Verify the operating system isolates security functions from nonsecurity functions. If it does not, this is a finding.

Fix: F-61737r1_fix

Configure the operating system to isolate security functions from nonsecurity functions.

b
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.
CM-7 - Medium - CCI-001764 - V-56845 - SV-71105r1_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-001764
Version
SRG-OS-000368-GPOS-00154
Vuln IDs
  • V-56845
Rule IDs
  • SV-71105r1_rule
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 includes functions and services installed at the operating system-level. Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).
Checks: C-57415r1_chk

Verify the operating system prevents 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. If it does not, this is a finding.

Fix: F-61741r1_fix

Configure the operating system to 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.

b
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.
CM-5 - Medium - CCI-001749 - V-56849 - SV-71109r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001749
Version
SRG-OS-000366-GPOS-00153
Vuln IDs
  • V-56849
Rule IDs
  • SV-71109r1_rule
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, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.
Checks: C-57419r1_chk

Verify the operating system prevents 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. If it does not, this is a finding.

Fix: F-61745r1_fix

Configure the operating system to 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.

b
The operating system must audit the enforcement actions used to restrict access associated with changes to the system.
CM-5 - Medium - CCI-001814 - V-56851 - SV-71111r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001814
Version
SRG-OS-000365-GPOS-00152
Vuln IDs
  • V-56851
Rule IDs
  • SV-71111r1_rule
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. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.
Checks: C-57421r1_chk

Verify the operating system audits the enforcement actions used to restrict access associated with changes to the system. If it does not, this is a finding.

Fix: F-61747r1_fix

Configure the operating system to audit the enforcement actions used to restrict access associated with changes to the system.

b
Operating systems must prevent unauthorized and unintended information transfer via shared system resources.
SC-4 - Medium - CCI-001090 - V-56853 - SV-71113r1_rule
RMF Control
SC-4
Severity
Medium
CCI
CCI-001090
Version
SRG-OS-000138-GPOS-00069
Vuln IDs
  • V-56853
Rule IDs
  • SV-71113r1_rule
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 being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies. There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components.
Checks: C-57423r1_chk

Verify operating systems prevents unauthorized and unintended information transfer via shared system resources. If it does not, this is a finding.

Fix: F-61749r1_fix

Configure operating systems to prevent unauthorized and unintended information transfer via shared system resources.

b
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.
SC-5 - Medium - CCI-001095 - V-56861 - SV-71121r1_rule
RMF Control
SC-5
Severity
Medium
CCI
CCI-001095
Version
SRG-OS-000142-GPOS-00071
Vuln IDs
  • V-56861
Rule IDs
  • SV-71121r1_rule
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 available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning.
Checks: C-57431r1_chk

Verify the operating system manages excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service (DoS) attacks. If it does not, this is a finding.

Fix: F-61757r1_fix

Configure the operating system to manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service (DoS) attacks.

b
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.
SC-10 - Medium - CCI-001133 - V-56865 - SV-71125r1_rule
RMF Control
SC-10
Severity
Medium
CCI
CCI-001133
Version
SRG-OS-000163-GPOS-00072
Vuln IDs
  • V-56865
Rule IDs
  • SV-71125r1_rule
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 terminating an idle session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
Checks: C-57435r1_chk

Verify the operating system terminates 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. If it does not, this is a finding.

Fix: F-61761r1_fix

Configure the operating system to 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.

b
The operating system must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
SC-24 - Medium - CCI-001190 - V-56869 - SV-71129r1_rule
RMF Control
SC-24
Severity
Medium
CCI
CCI-001190
Version
SRG-OS-000184-GPOS-00078
Vuln IDs
  • V-56869
Rule IDs
  • SV-71129r1_rule
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 available but with a reduced security protection capability. Preserving operating system state information also facilitates system restart and return to the operational mode of the organization with less disruption to mission-essential processes. Abort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations.
Checks: C-57439r1_chk

Verify the operating system fails to a secure state if system initialization fails, shutdown fails, or aborts fail. If it does not, this is a finding.

Fix: F-61765r1_fix

Configure the operating system to fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

b
The operating system must protect the confidentiality and integrity of all information at rest.
SC-28 - Medium - CCI-001199 - V-56877 - SV-71137r1_rule
RMF Control
SC-28
Severity
Medium
CCI
CCI-001199
Version
SRG-OS-000185-GPOS-00079
Vuln IDs
  • V-56877
Rule IDs
  • SV-71137r1_rule
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 well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.
Checks: C-57447r1_chk

Verify the operating system protects the confidentiality and integrity of all information at rest. If it does not, this is a finding.

Fix: F-61773r1_fix

Configure the operating system to protect the confidentiality and integrity of all information at rest.

b
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 HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).
SI-2 - Medium - CCI-001233 - V-56883 - SV-71143r1_rule
RMF Control
SI-2
Severity
Medium
CCI
CCI-001233
Version
SRG-OS-000191-GPOS-00080
Vuln IDs
  • V-56883
Rule IDs
  • SV-71143r1_rule
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 requirement, the operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools, as specified in the requirement.
Checks: C-57453r1_chk

Verify the operating system employs automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). If it does not, this is a finding.

Fix: F-61779r1_fix

Configure the operating system to employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).

b
The operating system must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
SI-11 - Medium - CCI-001312 - V-56887 - SV-71147r1_rule
RMF Control
SI-11
Severity
Medium
CCI
CCI-001312
Version
SRG-OS-000205-GPOS-00083
Vuln IDs
  • V-56887
Rule IDs
  • SV-71147r1_rule
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 structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers.
Checks: C-57457r1_chk

Verify the operating system generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. If it does not, this is a finding.

Fix: F-61783r1_fix

Configure the operating system to generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

b
The operating system must reveal error messages only to authorized users.
SI-11 - Medium - CCI-001314 - V-56903 - SV-71163r1_rule
RMF Control
SI-11
Severity
Medium
CCI
CCI-001314
Version
SRG-OS-000206-GPOS-00084
Vuln IDs
  • V-56903
Rule IDs
  • SV-71163r1_rule
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 (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Checks: C-57473r1_chk

Verify the operating system reveals error messages only to authorized users. If it does not, this is a finding.

Fix: F-61799r1_fix

Configure the operating system to reveal error messages only to authorized users.

b
Any publically accessible connection to the operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
AC-8 - Medium - CCI-001384 - V-56909 - SV-71169r1_rule
RMF Control
AC-8
Severity
Medium
CCI
CCI-001384
Version
SRG-OS-000228-GPOS-00088
Vuln IDs
  • V-56909
Rule IDs
  • SV-71169r1_rule
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, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."
Checks: C-57477r2_chk

Verify any publically accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." If it does not, this is a finding.

Fix: F-61803r1_fix

Configure any publically accessible connection to the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

b
The operating system must audit all account modifications.
AC-2 - Medium - CCI-001403 - V-56913 - SV-71173r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001403
Version
SRG-OS-000239-GPOS-00089
Vuln IDs
  • V-56913
Rule IDs
  • SV-71173r2_rule
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 provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57483r1_chk

Verify the operating system automatically audits account modification. If it does not, this is a finding.

Fix: F-61809r1_fix

Configure the operating system to automatically audit account modification.

b
The operating system must audit all account disabling actions.
AC-2 - Medium - CCI-001404 - V-56917 - SV-71177r1_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001404
Version
SRG-OS-000240-GPOS-00090
Vuln IDs
  • V-56917
Rule IDs
  • SV-71177r1_rule
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 accessibility and system processing, operating systems must audit account disabling actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57487r1_chk

Verify the operating system automatically audits account disabling actions. If it does not, this is a finding.

Fix: F-61813r1_fix

Configure the operating system to automatically audit account disabling actions.

b
The operating system must audit all account removal actions.
AC-2 - Medium - CCI-001405 - V-56921 - SV-71181r1_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001405
Version
SRG-OS-000241-GPOS-00091
Vuln IDs
  • V-56921
Rule IDs
  • SV-71181r1_rule
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 accessibility and system processing, operating systems must audit account removal actions and, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57491r1_chk

Verify the operating system automatically audits account removal actions. If it does not, this is a finding.

Fix: F-61817r1_fix

Configure the operating system to automatically audit account removal actions.

b
The operating system must implement cryptography to protect the integrity of remote access sessions.
AC-17 - Medium - CCI-001453 - V-56935 - SV-71195r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001453
Version
SRG-OS-000250-GPOS-00093
Vuln IDs
  • V-56935
Rule IDs
  • SV-71195r1_rule
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 through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.
Checks: C-57505r1_chk

Verify the operating system implements cryptography to protect the integrity of remote access sessions. If it does not, this is a finding.

Fix: F-61831r1_fix

Configure the operating system to implement cryptography to protect the integrity of remote access sessions.

b
The operating system must initiate session audits at system start-up.
AU-14 - Medium - CCI-001464 - V-56939 - SV-71199r1_rule
RMF Control
AU-14
Severity
Medium
CCI
CCI-001464
Version
SRG-OS-000254-GPOS-00095
Vuln IDs
  • V-56939
Rule IDs
  • SV-71199r1_rule
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.
Checks: C-57509r1_chk

Verify the operating system initiates session audits at system start-up. If it does not, this is a finding.

Fix: F-61835r1_fix

Configure the operating system to initiate session audits at system start-up.

b
The operating system must enforce access restrictions.
CM-5 - Medium - CCI-001813 - V-57169 - SV-71429r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001813
Version
SRG-OS-000364-GPOS-00151
Vuln IDs
  • V-57169
Rule IDs
  • SV-71429r1_rule
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 any changes to the hardware, software, and/or firmware components of the operating system can have significant effects on the overall security of the system. Accordingly, only qualified and authorized individuals should be allowed to obtain access to operating system components for the purposes of initiating changes, including upgrades and modifications. Logical access restrictions include, for example, controls that restrict access to workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover).
Checks: C-57739r1_chk

Verify the operating system enforces access restrictions. If it does not, this is a finding.

Fix: F-62065r1_fix

Configure the operating system to enforce access restrictions.

b
The operating system must produce audit records containing information to establish the identity of any individual or process associated with the event.
AU-3 - Medium - CCI-001487 - V-57171 - SV-71431r1_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-001487
Version
SRG-OS-000255-GPOS-00096
Vuln IDs
  • V-57171
Rule IDs
  • SV-71431r1_rule
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.
Checks: C-57743r1_chk

Verify the operating system produces audit records containing information to establish the identity of any individual or process associated with the event. If it does not, this is a finding.

Fix: F-62067r1_fix

Configure the operating system to produce audit records containing information to establish the identity of any individual or process associated with the event.

b
The operating system must protect audit tools from unauthorized access.
AU-9 - Medium - CCI-001493 - V-57173 - SV-71433r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-001493
Version
SRG-OS-000256-GPOS-00097
Vuln IDs
  • V-57173
Rule IDs
  • SV-71433r1_rule
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 to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Checks: C-57745r1_chk

Verify the operating system protects audit tools from unauthorized access. If it does not, this is a finding.

Fix: F-62069r1_fix

Configure the operating system to protect audit tools from unauthorized access.

b
The operating system must protect audit tools from unauthorized modification.
AU-9 - Medium - CCI-001494 - V-57175 - SV-71435r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-001494
Version
SRG-OS-000257-GPOS-00098
Vuln IDs
  • V-57175
Rule IDs
  • SV-71435r1_rule
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 to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has in order to make access decisions regarding the modification of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Checks: C-57747r1_chk

Verify the operating system protects audit tools from unauthorized modification. If it does not, this is a finding.

Fix: F-62071r1_fix

Configure the operating system to protect audit tools from unauthorized modification.

b
The operating system must protect audit tools from unauthorized deletion.
AU-9 - Medium - CCI-001495 - V-57177 - SV-71437r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-001495
Version
SRG-OS-000258-GPOS-00099
Vuln IDs
  • V-57177
Rule IDs
  • SV-71437r1_rule
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 to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has in order to make access decisions regarding the deletion of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Checks: C-57749r1_chk

Verify the operating system protects audit tools from unauthorized deletion. If it does not, this is a finding.

Fix: F-62073r1_fix

Configure the operating system to protect audit tools from unauthorized deletion.

b
The operating system must notify designated personnel if baseline configurations are changed in an unauthorized manner.
CM-3 - Medium - CCI-001744 - V-57179 - SV-71439r1_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-001744
Version
SRG-OS-000363-GPOS-00150
Vuln IDs
  • V-57179
Rule IDs
  • SV-71439r1_rule
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 relevant to security. Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.
Checks: C-57751r1_chk

Verify the operating system notifies designated personnel if baseline configurations are changed in an unauthorized manner. If it does not, this is a finding.

Fix: F-62075r1_fix

Configure the operating system to notify designated personnel if baseline configurations are changed in an unauthorized manner.

b
The operating system must prohibit user installation of system software without explicit privileged status.
CM-11 - Medium - CCI-001812 - V-57181 - SV-71441r1_rule
RMF Control
CM-11
Severity
Medium
CCI
CCI-001812
Version
SRG-OS-000362-GPOS-00149
Vuln IDs
  • V-57181
Rule IDs
  • SV-71441r1_rule
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 user with explicit capabilities and control that exceeds the rights of a regular user. Operating system functionality will vary, and while users are not permitted to install unapproved software, there may be instances where the organization allows the user to install approved software packages, such as from an approved software repository. The operating system or software configuration management utility must enforce control of software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization.
Checks: C-57755r1_chk

Verify the operating system prohibits user installation of system software without explicit privileged status. If it does not, this is a finding.

Fix: F-62079r1_fix

Configure the operating system to prohibit user installation of system software without explicit privileged status.

b
The operating system must limit privileges to change software resident within software libraries.
CM-5 - Medium - CCI-001499 - V-57183 - SV-71443r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
SRG-OS-000259-GPOS-00100
Vuln IDs
  • V-57183
Rule IDs
  • SV-71443r1_rule
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 applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
Checks: C-57753r1_chk

Verify the operating system limits privileges to change software resident within software libraries. If it does not, this is a finding.

Fix: F-62077r1_fix

Configure the operating system to limit privileges to change software resident within software libraries.

b
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.
CM-6 - Medium - CCI-000366 - V-57185 - SV-71445r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
SRG-OS-000360-GPOS-00147
Vuln IDs
  • V-57185
Rule IDs
  • SV-71445r1_rule
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 information must require dual authorization. Dual authorization mechanisms require the approval of two authorized individuals to execute.
Checks: C-57757r1_chk

Verify the operating system enforces dual authorization for movement and/or deletion of all audit information, when such movement or deletion is not part of an authorized automatic process. If it does not, this is a finding.

Fix: F-62081r1_fix

Configure the operating system to 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.

b
The operating system must enforce password complexity by requiring that at least one special character be used.
IA-5 - Medium - CCI-001619 - V-57187 - SV-71447r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-001619
Version
SRG-OS-000266-GPOS-00101
Vuln IDs
  • V-57187
Rule IDs
  • SV-71447r1_rule
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 complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Special characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.
Checks: C-57759r1_chk

Verify the operating system enforces password complexity by requiring that at least one special character be used. If it does not, this is a finding.

Fix: F-62083r1_fix

Configure the operating system to enforce password complexity by requiring that at least one special character be used.

b
The operating system must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
AU-8 - Medium - CCI-001890 - V-57189 - SV-71449r1_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-001890
Version
SRG-OS-000359-GPOS-00146
Vuln IDs
  • V-57189
Rule IDs
  • SV-71449r1_rule
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 (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.
Checks: C-57761r1_chk

Verify the operating system records time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). If it does not, this is a finding.

Fix: F-62085r1_fix

Configure the operating system to record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).

b
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.
SC-24 - Medium - CCI-001665 - V-57191 - SV-71451r1_rule
RMF Control
SC-24
Severity
Medium
CCI
CCI-001665
Version
SRG-OS-000269-GPOS-00103
Vuln IDs
  • V-57191
Rule IDs
  • SV-71451r1_rule
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 information system or a component of the system. Preserving operating system state information helps to facilitate operating system restart and return to the operational mode of the organization with least disruption to mission/business processes.
Checks: C-57765r1_chk

Verify, in the event of a system failure, the operating system preserves any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. If it does not, this is a finding.

Fix: F-62087r1_fix

Configure the operating system to preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes, in the event of a system failure.

b
The operating system must record time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision.
AU-8 - Medium - CCI-001889 - V-57193 - SV-71453r1_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-001889
Version
SRG-OS-000358-GPOS-00145
Vuln IDs
  • V-57193
Rule IDs
  • SV-71453r1_rule
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 synchronization between information system clocks and reference clocks.
Checks: C-57763r1_chk

Verify the operating system records time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision. If it does not, this is a finding.

Fix: F-62089r1_fix

Configure the operating system to record time stamps for audit records that meet a minimum granularity of one second for a minimum degree of precision.

b
The operating system must notify system administrators and ISSOs when accounts are created.
AC-2 - Medium - CCI-001683 - V-57195 - SV-71455r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001683
Version
SRG-OS-000274-GPOS-00104
Vuln IDs
  • V-57195
Rule IDs
  • SV-71455r2_rule
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 for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the creation of operating system user accounts and notifies administrators and ISSOs that it exists. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57767r1_chk

Verify the operating system notifies System Administrators and Information System Security Officers when accounts are created. If it does not, this is a finding.

Fix: F-62091r1_fix

Configure the operating system to notify System Administrators and Information System Security Officers when accounts are created.

b
The operating system must notify system administrators and ISSOs when accounts are modified.
AC-2 - Medium - CCI-001684 - V-57197 - SV-71457r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001684
Version
SRG-OS-000275-GPOS-00105
Vuln IDs
  • V-57197
Rule IDs
  • SV-71457r2_rule
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 method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the modification of operating system user accounts and notifies the system administrator and ISSO of changes. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57769r1_chk

Verify the operating system notifies System Administrators and Information System Security Officers when accounts are modified. If it does not, this is a finding.

Fix: F-62093r1_fix

Configure the operating system to notify System Administrators and Information System Security Officers when accounts are modified.

b
The operating system must notify system administrators and ISSOs when accounts are disabled.
AC-2 - Medium - CCI-001685 - V-57199 - SV-71459r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001685
Version
SRG-OS-000276-GPOS-00106
Vuln IDs
  • V-57199
Rule IDs
  • SV-71459r2_rule
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 events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57771r1_chk

Verify the operating system notifies System Administrators and Information System Security Officers when accounts are disabled. If it does not, this is a finding.

Fix: F-62095r1_fix

Configure the operating system to notify System Administrators and Information System Security Officers when accounts are disabled.

b
The operating system must notify system administrators and ISSOs when accounts are removed.
AC-2 - Medium - CCI-001686 - V-57201 - SV-71461r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001686
Version
SRG-OS-000277-GPOS-00107
Vuln IDs
  • V-57201
Rule IDs
  • SV-71461r2_rule
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 events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57773r1_chk

Verify the operating system notifies System Administrators and Information System Security Officers for account removal actions. If it does not, this is a finding.

Fix: F-62097r1_fix

Configure the operating system to notify System Administrators and Information System Security Officers for account removal actions.

b
The operating system must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.
AU-8 - Medium - CCI-002046 - V-57203 - SV-71463r1_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-002046
Version
SRG-OS-000356-GPOS-00144
Vuln IDs
  • V-57203
Rule IDs
  • SV-71463r1_rule
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. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems). Organizations should also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 because a comparison must be done in order to determine the time difference.
Checks: C-57775r1_chk

Verify the operating system synchronizes internal information system clocks to the authoritative time source when the time difference is greater than one second. If it does not, this is a finding.

Fix: F-62099r1_fix

Configure the operating system to synchronize internal information system clocks to the authoritative time source when the time difference is greater than the organization-defined time period.

b
The operating system must use cryptographic mechanisms to protect the integrity of audit tools.
AU-9 - Medium - CCI-001496 - V-57205 - SV-71465r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-001496
Version
SRG-OS-000278-GPOS-00108
Vuln IDs
  • V-57205
Rule IDs
  • SV-71465r1_rule
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 successfully audit information system activity. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. It is not uncommon for attackers to replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs. To address this risk, audit tools must be cryptographically signed in order to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files.
Checks: C-57791r1_chk

Verify the operating system uses cryptographic mechanisms to protect the integrity of audit tools. If it does not, this is a finding.

Fix: F-62115r1_fix

Configure the operating system to use cryptographic mechanisms to protect the integrity of audit tools.

b
The operating system must automatically terminate a user session after inactivity time-outs have expired or at shutdown.
AC-12 - Medium - CCI-002361 - V-57207 - SV-71467r1_rule
RMF Control
AC-12
Severity
Medium
CCI
CCI-002361
Version
SRG-OS-000279-GPOS-00109
Vuln IDs
  • V-57207
Rule IDs
  • SV-71467r1_rule
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, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. This capability is typically reserved for specific operating system functionality where the system owner, data owner, or organization requires additional assurance.
Checks: C-57795r1_chk

Verify the operating system automatically terminates a user session after inactivity time-outs have expired or at shutdown. If it does not, this is a finding.

Fix: F-62119r1_fix

Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown.

b
The operating system must provide a logoff capability for user-initiated communications sessions when requiring user access authentication.
AC-12 - Medium - CCI-002363 - V-57209 - SV-71469r1_rule
RMF Control
AC-12
Severity
Medium
CCI
CCI-002363
Version
SRG-OS-000280-GPOS-00110
Vuln IDs
  • V-57209
Rule IDs
  • SV-71469r1_rule
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, local workstations and remote services. For some types of interactive sessions, including, for example, remote logon, information systems typically send logoff messages as final messages prior to terminating sessions.
Checks: C-57797r1_chk

Verify the operating system provides a logoff capability for user-initiated communications sessions when requiring user access authentication. If it does not, this is a finding.

Fix: F-62121r1_fix

Configure the operating system to provide a logoff capability for user-initiated communications sessions when requiring user access authentication.

b
The operating system must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.
AC-12 - Medium - CCI-002364 - V-57211 - SV-71471r1_rule
RMF Control
AC-12
Severity
Medium
CCI
CCI-002364
Version
SRG-OS-000281-GPOS-00111
Vuln IDs
  • V-57211
Rule IDs
  • SV-71471r1_rule
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 resources to which users gain access via authentication include, for example, local workstations and remote services. Logoff messages can be displayed after authenticated sessions have been terminated. However, for some types of interactive sessions, including, for example, remote logon, information systems typically send logoff messages as final messages prior to terminating sessions.
Checks: C-57801r1_chk

Verify the operating system displays an explicit logoff message to users indicating the reliable termination of authenticated communications sessions. If it does not, this is a finding.

Fix: F-62125r1_fix

Configure the operating system to display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.

b
The operating system must control remote access methods.
AC-17 - Medium - CCI-002314 - V-57213 - SV-71473r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-002314
Version
SRG-OS-000297-GPOS-00115
Vuln IDs
  • V-57213
Rule IDs
  • SV-71473r1_rule
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 nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Operating system functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).
Checks: C-57805r1_chk

Verify the operating system controls remote access methods. If it does not, this is a finding.

Fix: F-62129r1_fix

Configure the operating system to control remote access methods.

b
The operating system must provide the capability to immediately disconnect or disable remote access to the operating system.
AC-17 - Medium - CCI-002322 - V-57215 - SV-71475r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-002322
Version
SRG-OS-000298-GPOS-00116
Vuln IDs
  • V-57215
Rule IDs
  • SV-71475r1_rule
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 users remotely accessing the information system and/or disable further remote access. The speed of disconnect or disablement varies based on the criticality of missions functions and the need to eliminate immediate or future remote access to organizational information systems. The remote access functionality (e.g., RDP) may implement features such as automatic disconnect (or user-initiated disconnect) in case of adverse information based on an indicator of compromise or attack.
Checks: C-57807r1_chk

Verify the operating system provides the capability to immediately disconnect or disable remote access to the operating system. If it does not, this is a finding.

Fix: F-62131r1_fix

Configure the operating system to provide the capability to immediately disconnect or disable remote access to the operating system.

b
The operating system must protect wireless access to and from the system using encryption.
AC-18 - Medium - CCI-001444 - V-57217 - SV-71477r1_rule
RMF Control
AC-18
Severity
Medium
CCI
CCI-001444
Version
SRG-OS-000299-GPOS-00117
Vuln IDs
  • V-57217
Rule IDs
  • SV-71477r1_rule
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 the confidentiality of information in transit. Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication. This requirement applies to those operating systems that control wireless devices.
Checks: C-57811r1_chk

Verify the operating system protects wireless access to and from the system using encryption. If it does not, this is a finding.

Fix: F-62135r1_fix

Configure the operating system to protect wireless access to and from the system using encryption.

b
The operating system must protect wireless access to the system using authentication of users and/or devices.
AC-18 - Medium - CCI-001443 - V-57219 - SV-71479r1_rule
RMF Control
AC-18
Severity
Medium
CCI
CCI-001443
Version
SRG-OS-000300-GPOS-00118
Vuln IDs
  • V-57219
Rule IDs
  • SV-71479r1_rule
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. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual authentication. This requirement applies to those operating systems that control wireless devices.
Checks: C-57815r1_chk

Verify the operating system protects wireless access to the system using authentication of users and/or devices. If it does not, this is a finding.

Fix: F-62139r1_fix

Configure the operating system to protect wireless access to the system using authentication of users and/or devices.

b
The operating system must audit all account enabling actions.
AC-2 - Medium - CCI-002130 - V-57221 - SV-71481r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-002130
Version
SRG-OS-000303-GPOS-00120
Vuln IDs
  • V-57221
Rule IDs
  • SV-71481r2_rule
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 actions provides logging that can be used for forensic purposes. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57817r1_chk

Verify the operating system automatically audits account enabling actions. If it does not, this is a finding.

Fix: F-62141r1_fix

Configure the operating system to automatically audit account enabling actions.

b
The operating system must notify system administrators and ISSOs of account enabling actions.
AC-2 - Medium - CCI-002132 - V-57223 - SV-71483r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-002132
Version
SRG-OS-000304-GPOS-00121
Vuln IDs
  • V-57223
Rule IDs
  • SV-71483r2_rule
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 enabling actions to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes. In order to detect and respond to events that affect user accessibility and application processing, operating systems must audit account enabling actions and, as required, notify the appropriate individuals so they can investigate the event. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.
Checks: C-57821r1_chk

Verify the operating system notifies the System Administrator and Information System Security Officer(s) when accounts are created, or enabled when previously disabled. If it does not, this is a finding.

Fix: F-62145r1_fix

Configure the operating system to notify the System Administrator(s) and Information System Security Officer(s) when accounts are created, or enabled when previously disabled.

b
The operating system must allow operating system admins to pass information to any other operating system admin or user.
AC-3 - Medium - CCI-002165 - V-57225 - SV-71485r1_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-002165
Version
SRG-OS-000312-GPOS-00122
Vuln IDs
  • V-57225
Rule IDs
  • SV-71485r1_rule
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 as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
Checks: C-57825r1_chk

Verify the operating system allows operating system admins to pass information to any other operating system admin or user. If it does not, this is a finding.

Fix: F-62149r1_fix

Configure the operating system to allow operating system admins to pass information to any other operating system admin or user.

b
The operating system must allow operating system admins to grant their privileges to other operating system admins.
AC-3 - Medium - CCI-002165 - V-57227 - SV-71487r1_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-002165
Version
SRG-OS-000312-GPOS-00123
Vuln IDs
  • V-57227
Rule IDs
  • SV-71487r1_rule
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 as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
Checks: C-57829r1_chk

Verify the operating system allows operating system admins to grant their privileges to other operating system admins. If it does not, this is a finding.

Fix: F-62153r1_fix

Configure the operating system to allow operating system admins to grant their privileges to other operating system admins.

b
The operating system must allow operating system admins to change security attributes on users, the operating system, or the operating systems components.
AC-3 - Medium - CCI-002165 - V-57229 - SV-71489r1_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-002165
Version
SRG-OS-000312-GPOS-00124
Vuln IDs
  • V-57229
Rule IDs
  • SV-71489r1_rule
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 as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.
Checks: C-57831r1_chk

Verify the operating system allows operating system admins to change security attributes on users, the operating system, or the operating system's components. If it does not, this is a finding.

Fix: F-62155r1_fix

Configure the operating system to allow operating system admins to change security attributes on users, the operating system, or the operating system's components.

b
The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
AC-6 - Medium - CCI-002235 - V-57231 - SV-71491r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-002235
Version
SRG-OS-000324-GPOS-00125
Vuln IDs
  • V-57231
Rule IDs
  • SV-71491r1_rule
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, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.
Checks: C-57835r1_chk

Verify that the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. If it does not, this is a finding.

Fix: F-62159r1_fix

Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.

b
The operating system must prevent all software from executing at higher privilege levels than users executing the software.
AC-6 - Medium - CCI-002233 - V-57233 - SV-71493r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-002233
Version
SRG-OS-000326-GPOS-00126
Vuln IDs
  • V-57233
Rule IDs
  • SV-71493r1_rule
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 invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations. Some programs and processes are required to operate at a higher privilege level and therefore should be excluded from the organization-defined software list after review.
Checks: C-57839r1_chk

Verify that the operating system prevents all software from executing at higher privilege levels than users executing the software. If it does not, this is a finding.

Fix: F-62163r1_fix

Configure the operating system to prevent all software from executing at higher privilege levels than users executing the software.

b
The operating system must audit the execution of privileged functions.
AC-6 - Medium - CCI-002234 - V-57235 - SV-71495r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-002234
Version
SRG-OS-000327-GPOS-00127
Vuln IDs
  • V-57235
Rule IDs
  • SV-71495r1_rule
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 on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.
Checks: C-57843r1_chk

Verify that the operating system audits the execution of privileged functions. If it does not, this is a finding.

Fix: F-62165r1_fix

Configure the operating system to audit the execution of privileged functions.

b
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.
AC-7 - Medium - CCI-002238 - V-57237 - SV-71497r1_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-002238
Version
SRG-OS-000329-GPOS-00128
Vuln IDs
  • V-57237
Rule IDs
  • SV-71497r1_rule
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.
Checks: C-57845r1_chk

Verify the operating system automatically locks an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. If it does not, this is a finding.

Fix: F-62169r1_fix

Configure the operating system to automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.

b
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.
AU-12 - Medium - CCI-001914 - V-57239 - SV-71499r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-001914
Version
SRG-OS-000337-GPOS-00129
Vuln IDs
  • V-57239
Rule IDs
  • SV-71499r1_rule
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 enables organizations to extend or limit auditing as necessary to meet organizational requirements. Auditing that is limited to conserve information system resources may be extended to address certain threat situations. In addition, auditing may be limited to a specific set of events to facilitate audit reduction, analysis, and reporting.
Checks: C-57849r1_chk

Verify the operating system provides 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 it does not, this is a finding.

Fix: F-62173r1_fix

Configure the operating system to 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.

b
The operating system must allocate audit record storage capacity to store at least one weeks worth of audit records, when audit records are not immediately sent to a central audit record storage facility.
AU-4 - Medium - CCI-001849 - V-57245 - SV-71505r1_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001849
Version
SRG-OS-000341-GPOS-00132
Vuln IDs
  • V-57245
Rule IDs
  • SV-71505r1_rule
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 performed during initial installation of the operating system.
Checks: C-57855r1_chk

Verify the operating system allocates 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. If it does not, this is a finding.

Fix: F-62179r1_fix

Configure the operating system to 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.

b
The operating system must off-load audit records onto a different system or media from the system being audited.
AU-4 - Medium - CCI-001851 - V-57247 - SV-71507r1_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001851
Version
SRG-OS-000342-GPOS-00133
Vuln IDs
  • V-57247
Rule IDs
  • SV-71507r1_rule
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.
Checks: C-57857r1_chk

Verify the operating system off-loads audit records onto a different system or media from the system being audited. If it does not, this is a finding.

Fix: F-62181r1_fix

Configure the operating system to off-load audit records onto a different system or media from the system being audited.

b
The operating system must immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.
AU-5 - Medium - CCI-001855 - V-57249 - SV-71509r1_rule
RMF Control
AU-5
Severity
Medium
CCI
CCI-001855
Version
SRG-OS-000343-GPOS-00134
Vuln IDs
  • V-57249
Rule IDs
  • SV-71509r1_rule
If security personnel are not notified immediately when storage volume reaches 75% utilization, they are unable to plan for audit record storage capacity expansion.
Checks: C-57859r1_chk

Verify the operating system immediately notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. If it does not, this is a finding.

Fix: F-62183r1_fix

Configure the operating system to immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.

b
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.
AU-5 - Medium - CCI-001858 - V-57251 - SV-71511r1_rule
RMF Control
AU-5
Severity
Medium
CCI
CCI-001858
Version
SRG-OS-000344-GPOS-00135
Vuln IDs
  • V-57251
Rule IDs
  • SV-71511r1_rule
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 may be adversely affected. Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less).
Checks: C-57861r1_chk

Verify the operating system provides an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts. If it does not, this is a finding.

Fix: F-62185r1_fix

Configure the operating system to provide an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts.

b
The operating system must provide an audit reduction capability that supports on-demand audit review and analysis.
AU-7 - Medium - CCI-001875 - V-57253 - SV-71513r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001875
Version
SRG-OS-000348-GPOS-00136
Vuln IDs
  • V-57253
Rule IDs
  • SV-71513r1_rule
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 complex security incidents. Audit reduction is a technique used to reduce the volume of audit records in order to facilitate a manual review. Audit reduction does not alter original audit records. The report generation capability provided by the application must support on-demand (i.e., customizable, ad hoc, and as-needed) reports.
Checks: C-57863r1_chk

Verify the operating system provides an audit reduction capability that supports on-demand audit review and analysis. If it does not, this is a finding.

Fix: F-62187r1_fix

Configure the operating system to provide an audit reduction capability that supports on-demand audit review and analysis.

b
The operating system must provide an audit reduction capability that supports after-the-fact investigations of security incidents.
AU-7 - Medium - CCI-001877 - V-57255 - SV-71515r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001877
Version
SRG-OS-000349-GPOS-00137
Vuln IDs
  • V-57255
Rule IDs
  • SV-71515r1_rule
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 to comply with applicable Federal laws and DoD policies. Audit reduction capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools. This requirement is specific to operating systems with audit reduction capabilities.
Checks: C-57865r1_chk

Verify the operating system provides an audit reduction capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding.

Fix: F-62189r1_fix

Configure the operating system to provide an audit reduction capability that supports after-the-fact investigations of security incidents.

b
The operating system must provide a report generation capability that supports on-demand audit review and analysis.
AU-7 - Medium - CCI-001878 - V-57257 - SV-71517r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001878
Version
SRG-OS-000350-GPOS-00138
Vuln IDs
  • V-57257
Rule IDs
  • SV-71517r1_rule
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 must be capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective.
Checks: C-57867r1_chk

Verify the operating system provides a report generation capability that supports on-demand audit review and analysis. If it does not, this is a finding.

Fix: F-62191r1_fix

Configure the operating system to provide a report generation capability that supports on-demand audit review and analysis.

b
The operating system must provide a report generation capability that supports on-demand reporting requirements.
AU-7 - Medium - CCI-001879 - V-57259 - SV-71519r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001879
Version
SRG-OS-000351-GPOS-00139
Vuln IDs
  • V-57259
Rule IDs
  • SV-71519r1_rule
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 capable of generating on-demand (i.e., customizable, ad hoc, and as-needed) reports. On-demand reporting allows personnel to report issues more rapidly to more effectively meet reporting requirements. Collecting log data and aggregating it to present the data in a single, consolidated report achieves this objective.
Checks: C-57869r1_chk

Verify the operating system provides a report generation capability that supports on-demand reporting requirements. If it does not, this is a finding.

Fix: F-62193r1_fix

Ensure the operating system provides a report generation capability that supports on-demand reporting requirements.

b
The operating system must provide a report generation capability that supports after-the-fact investigations of security incidents.
AU-7 - Medium - CCI-001880 - V-57261 - SV-71521r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001880
Version
SRG-OS-000352-GPOS-00140
Vuln IDs
  • V-57261
Rule IDs
  • SV-71521r1_rule
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 to comply with applicable Federal laws and DoD policies. The report generation capability must support after-the-fact investigations of security incidents either natively or through the use of third-party tools.
Checks: C-57871r1_chk

Verify the operating system provides a report generation capability that supports after-the-fact investigations of security incidents. If it does not, this is a finding.

Fix: F-62195r1_fix

Ensure the operating system provides a report generation capability that supports after-the-fact investigations of security incidents.

b
The operating system must not alter original content or time ordering of audit records when it provides an audit reduction capability.
AU-7 - Medium - CCI-001881 - V-57263 - SV-71523r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001881
Version
SRG-OS-000353-GPOS-00141
Vuln IDs
  • V-57263
Rule IDs
  • SV-71523r1_rule
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 audit information and organizes such information in a summary format that is more meaningful to analysts. Time ordering refers to the chronological organization of records based on time stamps. The degree of time stamp precision can affect this. This requirement is specific to operating systems providing audit reduction capabilities. The audit reduction capability can be met either natively or through the use of third-party tools.
Checks: C-57873r1_chk

Verify the operating system does not alter original content or time ordering of audit records when it provides an audit reduction capability. If it does not, this is a finding.

Fix: F-62197r1_fix

Configure the operating system to not alter original content or time ordering of audit records when it provides an audit reduction capability.

b
The operating system must not alter original content or time ordering of audit records when it provides a report generation capability.
AU-7 - Medium - CCI-001882 - V-57265 - SV-71525r1_rule
RMF Control
AU-7
Severity
Medium
CCI
CCI-001882
Version
SRG-OS-000354-GPOS-00142
Vuln IDs
  • V-57265
Rule IDs
  • SV-71525r1_rule
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 organization of records based on time stamps. The degree of time stamp precision can affect this. This requirement is specific to operating systems providing report generation capabilities. The report generation capability can be met either natively or through the use of third-party tools.
Checks: C-57875r1_chk

Verify the operating system does not alter original content or time ordering of audit records when it provides a report generation capability. If it does not, this is a finding.

Fix: F-62199r1_fix

Configure the operating system to not alter original content or time ordering of audit records when it provides a report generation capability.

b
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).
AU-8 - Medium - CCI-001891 - V-57267 - SV-71527r1_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-001891
Version
SRG-OS-000355-GPOS-00143
Vuln IDs
  • V-57267
Rule IDs
  • SV-71527r1_rule
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. Sources outside the configured acceptable allowance (drift) may be inaccurate. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).
Checks: C-57877r1_chk

Verify the operating system, for networked systems, compares 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). If it does not, this is a finding.

Fix: F-62201r1_fix

Configure the operating system to, 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).

b
The operating system must protect the confidentiality and integrity of communications with wireless peripherals.
SC-8 - Medium - CCI-002418 - V-64813 - SV-79303r1_rule
RMF Control
SC-8
Severity
Medium
CCI
CCI-002418
Version
SRG-OS-000481-GPOS-000481
Vuln IDs
  • V-64813
Rule IDs
  • SV-79303r1_rule
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 applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with an operating system. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR Keyboards, Mice, and Pointing Devices and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DoD requirements for wireless data transmission and be approved for use by the AO. Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise the operating system. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required.
Checks: C-65497r1_chk

Verify the operating system protects the confidentiality and integrity of communications with wireless peripherals. If it does not, this is a finding.

Fix: F-70755r1_fix

Configure the operating system to protect the confidentiality and integrity of communications with wireless peripherals.