ID | Severity | Title | Discussion (Rationale) | Fix Text (Description) | Check Text (OCIL Check) | SRG Refs | CCI Refs | 800-53 Refs |
xccdf_org.ssgproject.content_rule_account_disable_inactivity_password_auth | medium | Set Account Expiration Following Inactivity in password-auth | 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. | Verify the account identifiers (individuals, groups, roles, and devices) are disabled after
or less days of inactivity by
checking the account inactivity value with the following command:
grep 'inactive\|pam_unix' /etc/pam.d/password-auth | grep -w auth auth required pam_lastlog.so inactive=35 auth sufficient pam_unix.soThe line with the inactive parameter should be placed before pam_unix.so module as in
the example output. |
To verify the inactive setting, run the following command: $ grep 'inactive\|pam_unix' /etc/pam.d/password-auth | grep -w auth The output should indicate the inactive configuration option is set to an appropriate integer between 1 and ; and should appear before the pam_unix.so module as shown in the example below: $ grep 'inactive\|pam_unix' /etc/pam.d/password-auth | grep -w auth auth required pam_lastlog.so inactive= auth sufficient pam_unix.so Is it the case that the value of inactive is incorrect or is not set before pam_unix.so? |
SRG-OS-000118-GPOS-00060 |
CCI-000795 |
IA-4 e |
xccdf_org.ssgproject.content_rule_account_disable_inactivity_system_auth | medium | Set Account Expiration Following Inactivity in system-auth | 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. | Verify the account identifiers (individuals, groups, roles, and devices) are disabled after
or less days of inactivity by
checking the account inactivity value with the following command:
grep 'inactive\|pam_unix' /etc/pam.d/password-auth | grep -w auth auth required pam_lastlog.so inactive=35 auth sufficient pam_unix.soThe line with the inactive parameter should be placed before pam_unix.so module as in
the example output. |
To verify the inactive setting, run the following command: $ grep 'inactive\|pam_unix' /etc/pam.d/system-auth | grep -w auth The output should indicate the inactive configuration option is set to an appropriate integer between 1 and ; and should appear before the pam_unix.so module as shown in the example below: $ grep 'inactive\|pam_unix' /etc/pam.d/system-auth | grep -w auth auth required pam_lastlog.so inactive= auth sufficient pam_unix.so Is it the case that the value of inactive is incorrect or is not set before pam_unix.so? |
SRG-OS-000118-GPOS-00060 |
CCI-000795 |
IA-4 e |
xccdf_org.ssgproject.content_rule_account_disable_post_pw_expiration | medium | Set Account Expiration Following Inactivity | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Disabling inactive accounts ensures that accounts which may not have been responsibly removed are not available to attackers who may have compromised their credentials. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. | To specify the number of days after a password expires (which
signifies inactivity) until an account is permanently disabled, add or correct
the following line in /etc/default/useradd :
INACTIVE=If a password is currently on the verge of expiration, then
day(s) remain(s) until the account is automatically
disabled. However, if the password will not expire for another 60 days, then 60
days plus day(s) could
elapse until the account would be automatically disabled. See the
useradd man page for more information. |
To verify the INACTIVE setting, run the following command: $ grep "INACTIVE" /etc/default/useradd The output should indicate the INACTIVE configuration option is set to an appropriate integer as shown in the example below: $ grep "INACTIVE" /etc/default/useradd INACTIVE= Is it the case that the value of INACTIVE is greater than the expected value or is -1? |
SRG-OS-000118-GPOS-00060 |
CCI-000017 CCI-000795 |
AC-2 (3) IA-4 e |
xccdf_org.ssgproject.content_rule_account_emergency_expire_date | medium | Assign Expiration Date to Emergency Accounts | If emergency 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 emergency accounts
must be set upon account creation.
|
Emergency accounts are privileged accounts established in response to
crisis situations where the need for rapid account activation is required.
In the event emergency accounts are required, configure the system to
terminate them after a documented time period. For every emergency account,
run the following command to set an expiration date on it, substituting
ACCOUNT_NAME and YYYY-MM-DD
appropriately:
$ sudo chage -E YYYY-MM-DD ACCOUNT_NAME YYYY-MM-DD indicates the documented expiration date for the
account. For U.S. Government systems, the operating system must be
configured to automatically terminate these types of accounts after a
period of 72 hours. |
Verify emergency accounts have been provisioned with an expiration date of 72 hours. For every emergency account, run the following command to obtain its account aging and expiration information: $ sudo chage -l emergency_account_name Verify each of these accounts has an expiration date set within 72 hours or as documented. Is it the case that any emergency accounts have no expiration date set or do not expire within 72 hours? |
SRG-OS-000002-GPOS-00002 SRG-OS-000123-GPOS-00064 |
CCI-000016 CCI-001682 |
AC-2 (2) AC-2 (2) |
xccdf_org.ssgproject.content_rule_account_password_selinux_faillock_dir | medium | An SELinux Context must be configured for the pam_faillock.so records directory | Not having the correct SELinux context on the pam_faillock.so records directory may lead to unauthorized access to the directory. | The dir configuration option in PAM pam_faillock.so module defines where the lockout
records is stored. The configured directory must have the correct SELinux context. |
If the system does not have SELinux enabled and enforcing a targeted policy, or if the pam_faillock.so module is not configured for use, this requirement is not applicable. Verify the location of the non-default tally directory for the pam_faillock.so module with the following command: $ sudo grep -w dir /etc/security/faillock.conf dir = /var/log/faillock Check the security context type of the non-default tally directory with the following command: $ sudo ls -Zd /var/log/faillock unconfined_u:object_r:faillog_t:s0 /var/log/faillock Is it the case that the security context type of the non-default tally directory is not "faillog_t"? |
SRG-OS-000021-GPOS-00005 |
CCI-000044 |
AC-7 a |
xccdf_org.ssgproject.content_rule_account_passwords_pam_faillock_audit | medium | Account Lockouts Must Be Logged | Without auditing of these events it may be harder or impossible to identify what an attacker did after an attack. | PAM faillock locks an account due to excessive password failures, this event must be logged. | Verify the "/etc/security/faillock.conf" file is configured to log user name information when unsuccessful logon attempts occur: $ sudo grep audit /etc/security/faillock.conf audit Is it the case that the "audit" option is not set, is missing or commented out? |
SRG-OS-000021-GPOS-00005 |
CCI-000044 |
AC-7 a |
xccdf_org.ssgproject.content_rule_account_temp_expire_date | medium | Assign Expiration Date to Temporary Accounts | 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. In the event
temporary accounts are required, configure the system to
terminate them after a documented time period. For every temporary account, run the following command to set an expiration date on
it, substituting USER and YYYY-MM-DD
appropriately:
$ sudo chage -E YYYY-MM-DD USER YYYY-MM-DD indicates the documented expiration date for the
account. For U.S. Government systems, the operating system must be
configured to automatically terminate these types of accounts after a
period of 72 hours. |
Verify that temporary accounts have been provisioned with an expiration date of 72 hours. For every temporary account, run the following command to obtain its account aging and expiration information: $ sudo chage -l temporary_account_name Verify each of these accounts has an expiration date set within 72 hours or as documented. Is it the case that any temporary accounts have no expiration date set or do not expire within 72 hours? |
SRG-OS-000002-GPOS-00002 SRG-OS-000123-GPOS-00064 |
CCI-000016 CCI-001682 |
AC-2 (2) AC-2 (2) |
xccdf_org.ssgproject.content_rule_account_unique_id | medium | Ensure All Accounts on the System Have Unique User IDs | To assure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system. | Change user IDs (UIDs), or delete accounts, so each has a unique name. | Run the following command to check for duplicate account names: Check that the operating system contains no duplicate UIDs for interactive users by running the following command: # awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd If output is produced, this is a finding. Configure the operating system to contain no duplicate UIDs for interactive users. Edit the file "/etc/passwd" and provide each interactive user account that has a duplicate UID with a unique UID. Is it the case that a line is returned? |
SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000104-GPOS-00051 SRG-OS-000121-GPOS-00062 |
CCI-000135 CCI-000764 CCI-000804 |
AU-3 (1) IA-2 IA-8 |
xccdf_org.ssgproject.content_rule_accounts_authorized_local_users | medium | Only Authorized Local User Accounts Exist on Operating System | Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system. | Enterprise Application tends to use the server or virtual machine exclusively.
Besides the default operating system user, there should be only authorized local
users required by the installed software groups and applications that exist on
the operating system. The authorized user list can be customized in the refine
value variable var_accounts_authorized_local_users_regex .
OVAL regular expression is used for the user list.
Configure the system so all accounts on the system are assigned to an active system,
application, or user account. Remove accounts that do not support approved system
activities or that allow for a normal user to perform administrative-level actions.
To remove unauthorized system accounts, use the following command:
$ sudo userdel unauthorized_user |
To verify that there are no unauthorized local user accounts, run the following command: $ less /etc/passwd Inspect the results, and if unauthorized local user accounts exist, remove them by running the following command: $ sudo userdel unauthorized_user Is it the case that there are unauthorized local user accounts on the system? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_have_homedir_login_defs | medium | Ensure Home Directories are Created for New Users | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own. | All local interactive user accounts, upon creation, should be assigned a home directory.
Configure the operating system to assign home directories to all new local interactive users by setting the CREATE_HOME
parameter in /etc/login.defs to yes as follows:
CREATE_HOME yes |
Verify all local interactive users on Oracle Linux 8 are assigned a home directory upon creation with the following command: $ grep -i create_home /etc/login.defs CREATE_HOME yes Is it the case that the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_logon_fail_delay | medium | Ensure the Logon Failure Delay is Set Correctly in login.defs | Increasing the time between a failed authentication attempt and re-prompting to enter credentials helps to slow a single-threaded brute force attack. | To ensure the logon failure delay controlled by /etc/login.defs is set properly,
add or correct the FAIL_DELAY setting in /etc/login.defs to read as follows:
FAIL_DELAY |
Verify the FAIL_DELAY setting is configured correctly in the /etc/login.defs file by running the following command: $ sudo grep -i "FAIL_DELAY" /etc/login.defs All output must show the value of FAIL_DELAY set as shown in the below: $ sudo grep -i "FAIL_DELAY" /etc/login.defs FAIL_DELAY Is it the case that the above command returns no output, or FAIL_DELAY is configured less than the expected value? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_max_concurrent_login_sessions | low | Limit the Number of Concurrent Login Sessions Allowed Per User | Limiting simultaneous user logins can insulate the system from denial of service problems caused by excessive logins. Automated login processes operating improperly or maliciously may result in an exceptional number of simultaneous login sessions. | Limiting the number of allowed users and sessions per user can limit risks related to Denial of
Service attacks. This addresses concurrent sessions for a single account and does not address
concurrent sessions by a single user via multiple accounts. To set the number of concurrent
sessions per user add the following line in /etc/security/limits.conf or
a file under /etc/security/limits.d/ :
* hard maxlogins |
Verify Oracle Linux 8 limits the number of concurrent sessions to "" for all accounts and/or account types with the following command: $ grep -r -s maxlogins /etc/security/limits.conf /etc/security/limits.d/*.conf /etc/security/limits.conf:* hard maxlogins 10 This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains. Is it the case that the "maxlogins" item is missing, commented out, or the value is set greater than "<sub idref="var_accounts_max_concurrent_login_sessions" />" and is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "maxlogins" item assigned'? |
SRG-OS-000027-GPOS-00008 |
CCI-000054 |
AC-10 |
xccdf_org.ssgproject.content_rule_accounts_maximum_age_login_defs | medium | Set Password Maximum Age | 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.
Setting the password maximum age ensures users are required to periodically change their passwords. Requiring shorter password lifetimes increases the risk of users writing down the password in a convenient location subject to physical compromise. |
To specify password maximum age for new accounts,
edit the file /etc/login.defs
and add or correct the following line:
PASS_MAX_DAYSA value of 180 days is sufficient for many environments. The DoD requirement is 60. The profile requirement is . |
To check the maximum password age, run the command: $ grep PASS_MAX_DAYS /etc/login.defs The profile requirement is . Is it the case that PASS_MAX_DAYS is not set equal to or greater than the required value? |
SRG-OS-000076-GPOS-00044 |
CCI-000199 |
IA-5 (1) (d) |
xccdf_org.ssgproject.content_rule_accounts_minimum_age_login_defs | medium | Set Password Minimum Age | 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.
Setting the minimum password age protects against users cycling back to a favorite password after satisfying the password reuse requirement. |
To specify password minimum age for new accounts,
edit the file /etc/login.defs
and add or correct the following line:
PASS_MIN_DAYSA value of 1 day is considered sufficient for many environments. The DoD requirement is 1. The profile requirement is . |
To check the minimum password age, run the command: $ grep PASS_MIN_DAYS /etc/login.defs Is it the case that it is not equal to or greater than the required value? |
SRG-OS-000075-GPOS-00043 |
CCI-000198 |
IA-5 (1) (d) |
xccdf_org.ssgproject.content_rule_accounts_no_uid_except_zero | high | Verify Only Root Has UID 0 | An account has root authority if it has a UID of 0. Multiple accounts with a UID of 0 afford more opportunity for potential intruders to guess a password for a privileged account. Proper configuration of sudo is recommended to afford multiple system administrators access to root privileges in an accountable manner. | If any account other than root has a UID of 0, this misconfiguration should
be investigated and the accounts other than root should be removed or have
their UID changed.
If the account is associated with system commands or applications the UID should be changed to one greater than "0" but less than "1000." Otherwise assign a UID greater than "1000" that has not already been assigned. |
Verify that only the "root" account has a UID "0" assignment with the following command: $ awk -F: '$3 == 0 {print $1}' /etc/passwd root Is it the case that any accounts other than "root" have a UID of "0"? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_password_all_shadowed_sha512 | medium | Verify All Account Password Hashes are Shadowed with SHA512 | 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. | Verify the operating system requires the shadow password suite
configuration be set to encrypt interactive user passwords using a strong
cryptographic hash.
Check that the interactive user account passwords are using a strong
password hash with the following command:
$ sudo cut -d: -f2 /etc/shadow $6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/Password hashes ! or * indicate inactive accounts not
available for logon and are not evaluated.
If any interactive user password hash does not begin with $6 ,
this is a finding. |
Verify that the interactive user account passwords are using a strong password hash with the following command: $ sudo cut -d: -f2 /etc/shadow $6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/ Password hashes ! or * indicate inactive accounts not available for logon and are not evaluated. Is it the case that any interactive user password hash does not begin with "$6"? |
SRG-OS-000073-GPOS-00041 SRG-OS-000120-GPOS-00061 |
CCI-000196 CCI-000803 |
IA-5 (1) (c) IA-7 |
xccdf_org.ssgproject.content_rule_accounts_password_minlen_login_defs | medium | Set Password Minimum Length in login.defs | Requiring a minimum password length makes password cracking attacks more difficult by ensuring a larger search space. However, any security benefit from an onerous requirement must be carefully weighed against usability problems, support costs, or counterproductive behavior that may result. | To specify password length requirements for new accounts, edit the file
/etc/login.defs and add or correct the following line:
PASS_MIN_LEN The DoD requirement is 15 .
The FISMA requirement is 12 .
The profile requirement is
.
If a program consults /etc/login.defs and also another PAM module
(such as pam_pwquality ) during a password change operation, then
the most restrictive must be satisfied. See PAM section for more
information about enforcing password quality requirements. |
To check the minimum password length, run the command: $ grep PASS_MIN_LEN /etc/login.defs The DoD requirement is 15. Is it the case that it is not set to the required value? |
SRG-OS-000078-GPOS-00046 |
CCI-000205 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_dcredit | medium | Ensure PAM Enforces Password Requirements - Minimum Digit Characters | 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. Requiring digits makes password guessing attacks more difficult by ensuring a larger search space. |
The pam_pwquality module's dcredit parameter controls requirements for
usage of digits in a password. When set to a negative number, any password will be required to
contain that many digits. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each digit. Modify the dcredit setting in
/etc/security/pwquality.conf to require the use of a digit in passwords. |
To check how many digits are required in a password, run the following command: $ grep dcredit /etc/security/pwquality.conf The dcredit parameter (as a negative number) will indicate how many digits are required. Is it the case that dcredit is not found or not equal to or less than the required value? |
SRG-OS-000071-GPOS-00039 |
CCI-000194 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_dictcheck | medium | Ensure PAM Enforces Password Requirements - Prevent the Use of Dictionary Words | 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. Passwords with dictionary words may be more vulnerable to password-guessing attacks. |
The pam_pwquality module's dictcheck check if passwords contains dictionary words. When
dictcheck is set to 1 passwords will be checked for dictionary words. |
To check if dictionary words are disallowed run the following command: $ sudo grep dictcheck /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf The dictcheck parameter should be equal to 1. The value should look like dictcheck=1 Is it the case that dictcheck is not found or not equal to the required value? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_password_pam_difok | medium | Ensure PAM Enforces Password Requirements - Minimum Different Characters | 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. Requiring a minimum number of different characters during password changes ensures that newly changed passwords should not resemble previously compromised ones. Note that passwords which are changed on compromised systems will still be compromised, however. |
The pam_pwquality module's difok parameter sets the number of characters
in a password that must not be present in and old password during a password change.
Modify the difok setting in /etc/security/pwquality.conf
to equal to require differing characters
when changing passwords. |
To check how many characters must differ during a password change, run the following command: $ sudo grep difok /etc/security/pwquality.conf difok = The difok parameter will indicate how many characters must differ. Is it the case that difok is not found or set to less than the required value? |
SRG-OS-000072-GPOS-00040 |
CCI-000195 |
IA-5 (1) (b) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_lcredit | medium | Ensure PAM Enforces Password Requirements - Minimum Lowercase Characters | 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 possble combinations that need to be tested before the password is compromised. Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space. |
The pam_pwquality module's lcredit parameter controls requirements for
usage of lowercase letters in a password. When set to a negative number, any password will be required to
contain that many lowercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each lowercase character. Modify the lcredit setting in
/etc/security/pwquality.conf to require the use of a lowercase character in passwords. |
To check how many lowercase characters are required in a password, run the following command: $ grep lcredit /etc/security/pwquality.conf The lcredit parameter (as a negative number) will indicate how many special characters are required. Is it the case that lcredit is not found or not less than or equal to the required value? |
SRG-OS-000070-GPOS-00038 |
CCI-000193 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_maxclassrepeat | medium | Ensure PAM Enforces Password Requirements - Maximum Consecutive Repeating Characters from Same Character Class | 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 a password, the greater the number of possible combinations that need to be tested before the password is compromised. |
The pam_pwquality module's maxclassrepeat parameter controls requirements for
consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters from the same character class. Modify the
maxclassrepeat setting in /etc/security/pwquality.conf to equal
to prevent a run of ( + 1) or more identical characters. |
To check the value for maximum consecutive repeating characters, run the following command: $ sudo grep maxclassrepeat /etc/security/pwquality.conf Is it the case that the value of "maxclassrepeat" is set to "0", more than "<sub idref="var_password_pam_maxclassrepeat" />" or is commented out? |
SRG-OS-000072-GPOS-00040 |
CCI-000195 |
IA-5 (1) (b) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_maxrepeat | medium | Set Password Maximum Consecutive Repeating Characters | 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. Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks. |
The pam_pwquality module's maxrepeat parameter controls requirements for
consecutive repeating characters. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters. Modify the maxrepeat setting
in /etc/security/pwquality.conf to equal to prevent a
run of ( + 1) or more identical characters. |
To check the maximum value for consecutive repeating characters, run the following command: $ sudo grep maxrepeat /etc/security/pwquality.conf Is it the case that the value of "maxrepeat" is set to more than "<sub idref="var_password_pam_maxrepeat" />" or is commented out? |
SRG-OS-000072-GPOS-00040 |
CCI-000195 |
IA-5 (1) (b) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_minclass | medium | Ensure PAM Enforces Password Requirements - Minimum Different Categories | 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. Requiring a minimum number of character categories makes password guessing attacks more difficult by ensuring a larger search space. |
The pam_pwquality module's minclass parameter controls
requirements for usage of different character classes, or types, of character
that must exist in a password before it is considered valid. For example,
setting this value to three (3) requires that any password must have characters
from at least three different categories in order to be approved. The default
value is zero (0), meaning there are no required classes. There are four
categories available:
* Upper-case characters * Lower-case characters * Digits * Special characters (for example, punctuation)Modify the minclass setting in /etc/security/pwquality.conf entry
to require
differing categories of characters when changing passwords. |
To check how many categories of characters must be used in password during a password change, run the following command: $ sudo grep minclass /etc/security/pwquality.conf The minclass parameter will indicate how many character classes must be used. If the requirement was for the password to contain characters from different categories, then this would appear as minclass = . Is it the case that the value of "minclass" is set to less than "<sub idref="var_password_pam_minclass" />" or is commented out? |
SRG-OS-000072-GPOS-00040 |
CCI-000195 |
IA-5 (1) (b) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_minlen | medium | Ensure PAM Enforces Password Requirements - Minimum Length | The shorter the password, the lower the number of possible combinations
that need to be tested before the password is compromised.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and 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. |
The pam_pwquality module's minlen parameter controls requirements for
minimum characters required in a password. Add minlen=
after pam_pwquality to set minimum password length requirements. |
To check how many characters are required in a password, run the following command: $ grep minlen /etc/security/pwquality.conf Your output should contain minlen = Is it the case that minlen is not found, or not equal to or greater than the required value? |
SRG-OS-000078-GPOS-00046 |
CCI-000205 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_ocredit | medium | Ensure PAM Enforces Password Requirements - Minimum Special Characters | 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. Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space. |
The pam_pwquality module's ocredit= parameter controls requirements for
usage of special (or "other") characters in a password. When set to a negative number,
any password will be required to contain that many special characters.
When set to a positive number, pam_pwquality will grant +1
additional length credit for each special character. Modify the ocredit setting
in /etc/security/pwquality.conf to equal
to require use of a special character in passwords. |
To check how many special characters are required in a password, run the following command: $ grep ocredit /etc/security/pwquality.conf The ocredit parameter (as a negative number) will indicate how many special characters are required. Is it the case that value of "ocredit" is a positive number or is commented out? |
SRG-OS-000266-GPOS-00101 |
CCI-001619 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_pwhistory_remember_password_auth | medium | Limit Password Reuse: password-auth | Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user. | Do not allow users to reuse recent passwords. This can be accomplished by using the
remember option for the pam_pwhistory PAM module.
In the file /etc/pam.d/password-auth , make sure the parameter
remember is present and it has a value equal to or greater than
. For example:
password control_flag pam_pwhistory.so ...existing_options... remember= use_authtokcontrol_flag should be one of the next values:
|
Verify Oracle Linux 8 is configured in the password-auth file to prohibit password reuse for a minimum of generations with the following command: $ grep -i remember /etc/pam.d/password-auth password pam_pwhistory.so use_authtok remember= retry=3 Is it the case that the line containing "pam_pwhistory.so" does not have the "remember" module argument set, is commented out, or the value of the "remember" module argument is set to less than "<sub idref="var_password_pam_remember" />"? |
SRG-OS-000077-GPOS-00045 |
CCI-000200 |
IA-5 (1) (e) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_pwhistory_remember_system_auth | medium | Limit Password Reuse: system-auth | Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user. | Do not allow users to reuse recent passwords. This can be accomplished by using the
remember option for the pam_pwhistory PAM module.
In the file /etc/pam.d/system-auth , make sure the parameter
remember is present and it has a value equal to or greater than
For example:
password control_flag pam_pwhistory.so ...existing_options... remember= use_authtokcontrol_flag should be one of the next values:
|
Verify Oracle Linux 8 is configured in the system-auth file to prohibit password reuse for a minimum of generations with the following command: $ grep -i remember /etc/pam.d/system-auth password pam_pwhistory.so use_authtok remember= retry=3 Is it the case that the line containing "pam_pwhistory.so" does not have the "remember" module argument set, is commented out, or the value of the "remember" module argument is set to less than "<sub idref="var_password_pam_remember" />"? |
SRG-OS-000077-GPOS-00045 |
CCI-000200 |
IA-5 (1) (e) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_password_auth | medium | Ensure PAM password complexity module is enabled in password-auth | Enabling PAM password complexity permits to enforce strong passwords and consequently makes the system less prone to dictionary attacks. | To enable PAM password complexity in password-auth file:
Edit the password section in
/etc/pam.d/password-auth to show
password requisite pam_pwquality.so . |
To check if pam_pwquality.so is enabled in password-auth, run the following command: $ grep pam_pwquality /etc/pam.d/password-auth The output should be similar to the following: password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in password-auth? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_system_auth | medium | Ensure PAM password complexity module is enabled in system-auth | Enabling PAM password complexity permits to enforce strong passwords and consequently makes the system less prone to dictionary attacks. | To enable PAM password complexity in system-auth file:
Edit the password section in
/etc/pam.d/system-auth to show
password requisite pam_pwquality.so . |
To check if pam_pwquality.so is enabled in system-auth, run the following command: $ grep pam_pwquality /etc/pam.d/system-auth The output should be similar to the following: password requisite pam_pwquality.so Is it the case that pam_pwquality.so is not enabled in system-auth? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_password_pam_retry | medium | Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session | Setting the password retry prompts that are permitted on a per-session basis to a low value requires some software, such as SSH, to re-connect. This can slow down and draw additional attention to some types of password-guessing attacks. Note that this is different from account lockout, which is provided by the pam_faillock module. | To configure the number of retry prompts that are permitted per-session:
Edit the pam_pwquality.so statement in
/etc/pam.d/system-auth to show
retry= , or a lower value if site
policy is more restrictive. The DoD requirement is a maximum of 3 prompts
per session. |
Verify Oracle Linux 8 is configured to limit the "pwquality" retry option to . Check for the use of the "pwquality" retry option in the PAM files with the following command: $ grep pam_pwquality /etc/pam.d/system-auth password required pam_pwquality.so retry= Is it the case that the value of "retry" is set to "0" or greater than "<sub idref="var_password_pam_retry" />", or is missing? |
SRG-OS-000069-GPOS-00037 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000192 CCI-000366 |
IA-5 (1) (a) CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_password_pam_ucredit | medium | Ensure PAM Enforces Password Requirements - Minimum Uppercase Characters | 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. |
The pam_pwquality module's ucredit= parameter controls requirements for
usage of uppercase letters in a password. When set to a negative number, any password will be required to
contain that many uppercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each uppercase character. Modify the ucredit setting in
/etc/security/pwquality.conf to require the use of an uppercase character in passwords. |
To check how many uppercase characters are required in a password, run the following command: $ grep ucredit /etc/security/pwquality.conf The ucredit parameter (as a negative number) will indicate how many uppercase characters are required. This would appear as ucredit = -1. Is it the case that ucredit is not found or not set to the required value? |
SRG-OS-000069-GPOS-00037 SRG-OS-000070-GPOS-00038 |
CCI-000192 CCI-000193 |
IA-5 (1) (a) IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_accounts_password_pam_unix_rounds_system_auth | medium | Set number of Password Hashing Rounds - system-auth | Using a higher number of rounds makes password cracking attacks more difficult. | Configure the number or rounds for the password hashing algorithm. This can be
accomplished by using the rounds option for the pam_unix PAM module.
In file /etc/pam.d/system-auth append rounds=
to the pam_unix.so entry, as shown below:
password sufficient pam_unix.so ...existing_options... rounds=The system's default number of rounds is 5000. |
To verify the number of rounds for the password hashing algorithm is configured, run the following command: $ sudo grep rounds /etc/pam.d/system-auth The output should show the following match: password sufficient pam_unix.so sha512 rounds= Is it the case that rounds is not set to <sub idref="var_password_pam_unix_rounds" /> or is commented out? |
SRG-OS-000073-GPOS-00041 |
CCI-000196 |
IA-5 (1) (c) |
xccdf_org.ssgproject.content_rule_accounts_password_set_max_life_existing | medium | Set Existing Passwords Maximum Age | 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. | Configure non-compliant accounts to enforce a -day maximum password lifetime
restriction by running the following command:
$ sudo chage -M USER |
Check whether the maximum time period for existing passwords is restricted to days with the following commands: $ sudo awk -F: '$5 > 60 {print $1 " " $5}' /etc/shadow $ sudo awk -F: '$5 <= 0 {print $1 " " $5}' /etc/shadow Is it the case that any results are returned that are not associated with a system account? |
SRG-OS-000076-GPOS-00044 |
CCI-000199 |
IA-5 (1) (d) |
xccdf_org.ssgproject.content_rule_accounts_password_set_min_life_existing | medium | Set Existing Passwords Minimum Age | 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, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse. | Configure non-compliant accounts to enforce a 24 hours/1 day minimum password
lifetime by running the following command:
$ sudo chage -m 1 USER |
Check whether the minimum time period between password changes for each user account is one day or greater. $ sudo awk -F: '$4 < 1 {print $1 " " $4}' /etc/shadow Is it the case that any results are returned that are not associated with a system account? |
SRG-OS-000075-GPOS-00043 |
CCI-000198 |
IA-5 (1) (d) |
xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny | medium | Lock Accounts After Failed Password Attempts | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, also known as brute-forcing, is reduced. Limits are imposed by locking the account. | This rule configures the system to lock out accounts after a number of incorrect login attempts
using pam_faillock.so .
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig ,
depending on the OS version. |
Verify Oracle Linux 8 is configured to lock an account after unsuccessful logon attempts with the command: $ grep 'deny =' /etc/security/faillock.conf deny = . Is it the case that the "deny" option is not set to "<sub idref="var_accounts_passwords_pam_faillock_deny" />" or less (but not "0"), is missing or commented out? |
SRG-OS-000021-GPOS-00005 SRG-OS-000329-GPOS-00128 |
CCI-000044 CCI-002236 CCI-002237 CCI-002238 |
AC-7 a |
xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny_root | medium | Configure the root Account for Failed Password Attempts | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, also known as brute-forcing, is reduced. Limits are imposed by locking the account. | This rule configures the system to lock out the root account after a number of
incorrect login attempts using pam_faillock.so .
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig ,
depending on the OS version. |
Verify Oracle Linux 8 is configured to lock the root account after unsuccessful logon attempts with the command: $ grep even_deny_root /etc/security/faillock.conf even_deny_root Is it the case that the "even_deny_root" option is not set, is missing or commented out? |
SRG-OS-000329-GPOS-00128 SRG-OS-000021-GPOS-00005 |
CCI-002238 CCI-000044 |
AC-7 a |
xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_dir | medium | Lock Accounts Must Persist | Locking out user accounts after a number of incorrect attempts prevents direct password
guessing attacks. In combination with the silent option, user enumeration attacks
are also mitigated. |
This rule ensures that the system lock out accounts using pam_faillock.so persist
after system reboot. From "Pam_Faillock" man pages:
Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be reenabled after system reboot. If that is undesirable, a different tally directory must be set with the "dir" option.pam_faillock.so module requires multiple entries in pam files. These entries must be carefully defined to work as expected. In order to avoid errors when manually editing these files, it is recommended to use the appropriate tools, such as authselect or authconfig ,
depending on the OS version. |
To ensure the tally directory is configured correctly, run the following command: $ grep 'dir =' /etc/security/faillock.conf The output should show that dir is set to something different to "/var/run/faillock" Is it the case that dir is not set or is set to /var/run/faillock? |
SRG-OS-000021-GPOS-00005 SRG-OS-000329-GPOS-00128 |
CCI-000044 CCI-002238 |
AC-7 a |
xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_interval | medium | Set Interval For Counting Failed Password Attempts | 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. | Utilizing pam_faillock.so , the fail_interval directive configures the system
to lock out an account after a number of incorrect login attempts within a specified time
period. |
To ensure the failed password attempt policy is configured correctly, run the following command: $ grep fail_interval /etc/security/faillock.conf The output should show fail_interval = <interval-in-seconds> where interval-in-seconds is or greater. Is it the case that the "fail_interval" option is not set to "<sub idref="var_accounts_passwords_pam_faillock_fail_interval" />" or less (but not "0"), the line is commented out, or the line is missing? |
SRG-OS-000021-GPOS-00005 SRG-OS-000329-GPOS-00128 |
CCI-000044 CCI-002236 CCI-002237 CCI-002238 |
AC-7 a |
xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_silent | medium | Do Not Show System Messages When Unsuccessful Logon Attempts Occur | The pam_faillock module without the silent option will leak information about the existence or non-existence of a user account in the system because the failures are not recorded for unknown users. The message about the user account being locked is never displayed for non-existing user accounts allowing the adversary to infer that a particular account exists or not on the system. | This rule ensures the system prevents informative messages from being presented to the user
pertaining to logon information after a number of incorrect login attempts using
pam_faillock.so .
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig ,
depending on the OS version. |
To ensure that the system prevents messages from being shown when three unsuccessful logon attempts occur, run the following command: $ grep silent /etc/security/faillock.conf The output should show silent. Is it the case that the system shows messages when three unsuccessful logon attempts occur? |
SRG-OS-000329-GPOS-00128 SRG-OS-000021-GPOS-00005 |
CCI-002238 CCI-000044 |
AC-7 a |
xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_unlock_time | medium | Set Lockout Time for Failed Password Attempts | 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. | This rule configures the system to lock out accounts during a specified time period after a
number of incorrect login attempts using pam_faillock.so .
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid any errors when manually editing these files,
it is recommended to use the appropriate tools, such as authselect or authconfig ,
depending on the OS version.
If unlock_time is set to 0 , manual intervention by an administrator is required
to unlock a user. This should be done using the faillock tool. |
Verify Oracle Linux 8 is configured to lock an account until released by an administrator after unsuccessful logon attempts with the command: $ grep 'unlock_time =' /etc/security/faillock.conf unlock_time = Is it the case that the "unlock_time" option is not set to "<sub idref="var_accounts_passwords_pam_faillock_unlock_time" />", the line is missing, or commented out? |
SRG-OS-000021-GPOS-00005 SRG-OS-000329-GPOS-00128 |
CCI-000044 CCI-002236 CCI-002237 CCI-002238 |
AC-7 a |
xccdf_org.ssgproject.content_rule_accounts_umask_etc_bashrc | medium | Ensure the Default Bash Umask is Set Correctly | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read or written to by unauthorized users. | To ensure the default umask for users of the Bash shell is set properly,
add or correct the umask setting in /etc/bashrc to read
as follows:
umask |
Verify the umask setting is configured correctly in the /etc/bashrc file by running the following command: $ sudo grep "umask" /etc/bashrc All output must show the value of umask set as shown below: umask Is it the case that the above command returns no output, or the umask is configured incorrectly? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_umask_etc_csh_cshrc | medium | Ensure the Default C Shell Umask is Set Correctly | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read or written to by unauthorized users. | To ensure the default umask for users of the C shell is set properly,
add or correct the umask setting in /etc/csh.cshrc to read as follows:
umask |
Verify the umask setting is configured correctly in the /etc/csh.cshrc file by running the following command: $ sudo grep "umask" /etc/csh.cshrc All output must show the value of umask set as shown in the below: umask Is it the case that the above command returns no output, or the umask is configured incorrectly? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_umask_etc_login_defs | medium | Ensure the Default Umask is Set Correctly in login.defs | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read and written to by unauthorized users. | To ensure the default umask controlled by /etc/login.defs is set properly,
add or correct the UMASK setting in /etc/login.defs to read as follows:
UMASK |
Verify the UMASK setting is configured correctly in the /etc/login.defs file by running the following command: $ sudo grep "UMASK" /etc/login.defs All output must show the value of UMASK set as shown in the below: UMASK Is it the case that the above command returns no output, or the umask is configured incorrectly? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_umask_etc_profile | medium | Ensure the Default Umask is Set Correctly in /etc/profile | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read or written to by unauthorized users. | To ensure the default umask controlled by /etc/profile is set properly,
add or correct the umask setting in /etc/profile to read as follows:
umask |
Verify the umask setting is configured correctly in the /etc/profile file with the following command: $ grep "umask" /etc/profile umask Is it the case that the value for the "umask" parameter is not "<sub idref="var_accounts_user_umask" />", or the "umask" parameter is missing or is commented out? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_umask_interactive_users | medium | Ensure the Default Umask is Set Correctly For Interactive Users | The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 700 or less permissive. Although umask can be represented as a four-digit number, the first digit representing special access modes is typically ignored or required to be 0. This requirement applies to the globally configured system defaults and the local interactive user defaults for each account on the system. | Remove the UMASK environment variable from all interactive users initialization files. |
Verify the UMASK setting is not configured for interactive users, run the following command: $ sudo grep -ri "UMASK" /home Is it the case that the above command returns no output, or if the umask is configured incorrectly? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000365-GPOS-00152 |
CCI-000366 CCI-001814 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_user_dot_no_world_writable_programs | medium | User Initialization Files Must Not Run World-Writable Programs | If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level. | Set the mode on files being executed by the user initialization files with the
following command:
$ sudo chmod o-w FILE |
Verify that local initialization files do not execute world-writable programs, execute the following command: $ sudo find /home -perm -002 -type f -name ".[^.]*" -exec ls -ld {} \; For all files listed, check for their presence in the local initialization files with the following command: Note: The example will be for a system that is configured to create users' home directories in the "/home" directory. sudo find /home/* -maxdepth 1 -type f -name \.\* -exec grep -H <file> {} \; Is it the case that user initialization files are executing world-writable programs? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_user_home_paths_only | medium | Ensure that Users Path Contains Only Local Directories | The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory (other than the users home directory), executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is interpreted as the current working directory. If deviations from the default system search path for the local interactive user are required, they must be documented with the Information System Security Officer (ISSO). | Ensure that all interactive user initialization files executable search path statements do not contain statements that will reference a working directory other than the users home directory. | To verify that all interactive user initialization files executable search path statements do not contain statements that will reference a working directory other than the users home directory, run the following command: $ sudo grep -r PATH /home/ Inspect the output for any PATH is references directories outside the home directory. Is it the case that paths contain more than local home directories? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_user_interactive_home_directory_defined | medium | All Interactive Users Must Have A Home Directory Defined | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own. | Assign home directories to all interactive users that currently do not
have a home directory assigned.
This rule checks if the home directory is properly defined in a folder which has
at least one parent folder, like "user" in "/home/user" or "/remote/users/user".
Therefore, this rule will report a finding for home directories like /users ,
/tmp or / . |
To verify interactive users on the system have a home directory assigned, run the following command: $ sudo awk -F":" '{print $1 ":" $6}' /etc/passwd Inspect the output and verify that all interactive users have a home directory defined. Is it the case that users home directory is not defined? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_user_interactive_home_directory_exists | medium | All Interactive Users Home Directories Must Exist | If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a Denial of Service because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to access. | Create home directories to all interactive users that currently do not
have a home directory assigned. Use the following commands to create the user
home directory assigned in /etc/passwd :
$ sudo mkdir /home/USER |
To verify the assigned home directory of all interactive users on the system exist, run the following command: $ sudo pwck -r Is it the case that users home directory does not exist? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_users_home_files_groupownership | medium | All User Files and Directories In The Home Directory Must Be Group-Owned By The Primary User | If a local interactive users files are group-owned by a group of which the user is not a member, unintended users may be able to access them. | Change the group of a local interactive users files and directories to a
group that the interactive user is a member of. To change the group owner of a
local interactive users files and directories, use the following command:
$ sudo chgrp USER_GROUP /home/USER/FILE_DIRThis rule ensures every file or directory under the home directory related to an interactive user is group-owned by an interactive user. |
To verify all files and directories in interactive user home directory are group-owned by a group the user is a member of, run the following command: $ sudo ls -lLR /home/USER Is it the case that the group ownership is incorrect? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_accounts_users_home_files_permissions | medium | All User Files and Directories In The Home Directory Must Have Mode 0750 Or Less Permissive | If a local interactive user files have excessive permissions, unintended users may be able to access or modify them. | Set the mode on files and directories in the local interactive user home
directory with the following command:
$ sudo chmod 0750 /home/USER/FILE_DIRFiles that begin with a "." are excluded from this requirement. |
To verify all files and directories contained in interactive user home directory, excluding local initialization files, have a mode of 0750, run the following command: $ sudo ls -lLR /home/USER Is it the case that home directory files or folders have incorrect permissions? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_agent_mfetpd_running | medium | Ensure McAfee Endpoint Security for Linux (ENSL) is running | Virus scanning software can be used to detect if a system has been compromised by computer viruses, as well as to limit their spread to other systems. | Install McAfee Endpoint Security for Linux antivirus software which is provided for DoD systems and uses signatures to search for the presence of viruses on the filesystem. | To verify that McAfee Endpoint Security for Linux is running, run the following command: $ sudo ps -ef | grep -i mfetpd Is it the case that virus scanning software is not running? |
SRG-OS-000191-GPOS-00080 |
CCI-001233 |
SI-2 (2) |
xccdf_org.ssgproject.content_rule_aide_check_audit_tools | medium | Configure AIDE to Verify the Audit Tools | Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to 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 to provide the capability to hide or erase system activity from the audit logs. To address this risk, audit tools must be cryptographically signed 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. | The operating system file integrity tool must be configured to protect the integrity of the audit tools. | Check that AIDE is properly configured to protect the integrity of the audit tools by running the following command: # sudo cat /etc/aide.conf | grep /usr/sbin/au /usr/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/rsyslogd p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512 If AIDE is configured properly to protect the integrity of the audit tools, all lines listed above will be returned from the command. If one or more lines are missing, this is a finding. Is it the case that integrity checks of the audit tools are missing or incomplete? |
SRG-OS-000278-GPOS-00108 |
CCI-001496 |
AU-9 (3) |
xccdf_org.ssgproject.content_rule_aide_scan_notification | medium | Configure Notification of Post-AIDE Scan Details | 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 Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item. |
AIDE should notify appropriate personnel of the details of a scan after the scan has been run.
If AIDE has already been configured for periodic execution in /etc/crontab , append the
following line to the existing AIDE line:
| /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhostOtherwise, add the following line to /etc/crontab :
05 4 * * * root /usr/sbin/aide --check | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhostAIDE can be executed periodically through other means; this is merely one example. |
To determine that periodic AIDE execution has been scheduled, run the following command: $ grep aide /etc/crontab The output should return something similar to the following: 05 4 * * * root /usr/sbin/aide --check | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost The email address that the notifications are sent to can be changed by overriding . Is it the case that AIDE has not been configured or has not been configured to notify personnel of scan details? |
SRG-OS-000363-GPOS-00150 SRG-OS-000446-GPOS-00200 SRG-OS-000447-GPOS-00201 |
CCI-001744 CCI-002699 CCI-002702 |
|
xccdf_org.ssgproject.content_rule_aide_verify_acls | low | Configure AIDE to Verify Access Control Lists (ACLs) | ACLs can provide permissions beyond those permitted through the file mode and must be verified by the file integrity tools. | By default, the acl option is added to the FIPSR ruleset in AIDE.
If using a custom ruleset or the acl option is missing, add acl
to the appropriate ruleset.
For example, add acl to the following line in /etc/aide.conf :
FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds acl to all rule sets available in
/etc/aide.conf
|
To determine that AIDE is verifying ACLs, run the following command: $ grep acl /etc/aide.conf Verify that the acl option is added to the correct ruleset. Is it the case that the acl option is missing or not added to the correct ruleset? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_aide_verify_ext_attributes | low | Configure AIDE to Verify Extended Attributes | Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications. | By default, the xattrs option is added to the FIPSR ruleset in AIDE.
If using a custom ruleset or the xattrs option is missing, add xattrs
to the appropriate ruleset.
For example, add xattrs to the following line in /etc/aide.conf :
FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds xattrs to all rule sets available in
/etc/aide.conf
|
To determine that AIDE is verifying extended file attributes, run the following command: $ grep xattrs /etc/aide.conf Verify that the xattrs option is added to the correct ruleset. Is it the case that the xattrs option is missing or not added to the correct ruleset? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_audit_immutable_login_uids | medium | Configure immutable Audit login UIDs | If modification of login UIDs is not prevented, they can be changed by unprivileged users and make auditing complicated or impossible. | Configure kernel to prevent modification of login UIDs once they are set.
Changing login UIDs while this configuration is enforced requires special capabilities which
are not available to unprivileged users.
The following rules configure audit as described above:
## Make the loginuid immutable. This prevents tampering with the auid. --loginuid-immutableLoad new Audit rules into kernel by running: augenrules --load |
To verify that the Audit is correctly configured according to recommended rules, check the content of the file with the following command: $ sudo cat /etc/audit/rules.d/11-loginuid.rules The output has to be exactly as follows: ## Make the loginuid immutable. This prevents tampering with the auid. --loginuid-immutable Is it the case that the file does not exist or the content differs? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 |
CCI-000162 CCI-000163 CCI-000164 |
AU-9 AU-9 AU-9 |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_chmod | medium | Record Events that Modify the System's Discretionary Access Controls - chmod | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the chmod system call, run the following command: $ sudo grep "chmod" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_chown | medium | Record Events that Modify the System's Discretionary Access Controls - chown | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the chown system call, run the following command: $ sudo grep "chown" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchmod | medium | Record Events that Modify the System's Discretionary Access Controls - fchmod | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the fchmod system call, run the following command: $ sudo grep "fchmod" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchmodat | medium | Record Events that Modify the System's Discretionary Access Controls - fchmodat | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the fchmodat system call, run the following command: $ sudo grep "fchmodat" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchown | medium | Record Events that Modify the System's Discretionary Access Controls - fchown | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the fchown system call, run the following command: $ sudo grep "fchown" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchownat | medium | Record Events that Modify the System's Discretionary Access Controls - fchownat | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the fchownat system call, run the following command: $ sudo grep "fchownat" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fremovexattr | medium | Record Events that Modify the System's Discretionary Access Controls - fremovexattr | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root.
If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod |
To determine if the system is configured to audit calls to the fremovexattr system call, run the following command: $ sudo grep "fremovexattr" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fsetxattr | medium | Record Events that Modify the System's Discretionary Access Controls - fsetxattr | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod |
To determine if the system is configured to audit calls to the fsetxattr system call, run the following command: $ sudo grep "fsetxattr" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lchown | medium | Record Events that Modify the System's Discretionary Access Controls - lchown | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the lchown system call, run the following command: $ sudo grep "lchown" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lremovexattr | medium | Record Events that Modify the System's Discretionary Access Controls - lremovexattr | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root.
If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod |
To determine if the system is configured to audit calls to the lremovexattr system call, run the following command: $ sudo grep "lremovexattr" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lsetxattr | medium | Record Events that Modify the System's Discretionary Access Controls - lsetxattr | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod |
To determine if the system is configured to audit calls to the lsetxattr system call, run the following command: $ sudo grep "lsetxattr" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_removexattr | medium | Record Events that Modify the System's Discretionary Access Controls - removexattr | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following line to a file with suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod |
To determine if the system is configured to audit calls to the removexattr system call, run the following command: $ sudo grep "removexattr" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_setxattr | medium | Record Events that Modify the System's Discretionary Access Controls - setxattr | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod |
To determine if the system is configured to audit calls to the setxattr system call, run the following command: $ sudo grep "setxattr" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_execution_chacl | medium | Record Any Attempts to Run chacl | 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). | At a minimum, the audit system should collect any execution attempt
of the chacl command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "chacl" command with the following command: $ sudo auditctl -l | grep chacl -a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_execution_chcon | medium | Record Any Attempts to Run chcon | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect any execution attempt
of the chcon command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "chcon" command with the following command: $ sudo auditctl -l | grep chcon -a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_execution_semanage | medium | Record Any Attempts to Run semanage | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect any execution attempt
of the semanage command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "semanage" command with the following command: $ sudo auditctl -l | grep semanage -a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000169 CCI-000172 CCI-002884 |
AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_execution_setfacl | medium | Record Any Attempts to Run setfacl | 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). | At a minimum, the audit system should collect any execution attempt
of the setfacl command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "setfacl" command with the following command: $ sudo auditctl -l | grep setfacl -a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_execution_setfiles | medium | Record Any Attempts to Run setfiles | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect any execution attempt
of the setfiles command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "setfiles" command with the following command: $ sudo auditctl -l | grep setfiles -a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000169 CCI-000172 CCI-002884 |
AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_execution_setsebool | medium | Record Any Attempts to Run setsebool | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect any execution attempt
of the setsebool command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "setsebool" command with the following command: $ sudo auditctl -l | grep setsebool -a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_rename | medium | Ensure auditd Collects File Deletion Events by User - rename | Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d , setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete |
To determine if the system is configured to audit calls to the rename system call, run the following command: $ sudo grep "rename" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-000366 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c CM-6 b |
xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_renameat | medium | Ensure auditd Collects File Deletion Events by User - renameat | Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d , setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete |
To determine if the system is configured to audit calls to the renameat system call, run the following command: $ sudo grep "renameat" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-000366 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c CM-6 b |
xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_rmdir | medium | Ensure auditd Collects File Deletion Events by User - rmdir | Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d , setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
To determine if the system is configured to audit calls to the rmdir system call, run the following command: $ sudo grep "rmdir" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-000366 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c CM-6 b |
xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_unlink | medium | Ensure auditd Collects File Deletion Events by User - unlink | Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d , setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete |
To determine if the system is configured to audit calls to the unlink system call, run the following command: $ sudo grep "unlink" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-000366 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c CM-6 b |
xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_unlinkat | medium | Ensure auditd Collects File Deletion Events by User - unlinkat | Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d , setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
To determine if the system is configured to audit calls to the unlinkat system call, run the following command: $ sudo grep "unlinkat" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-000366 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c CM-6 b |
xccdf_org.ssgproject.content_rule_audit_rules_immutable | medium | Make the auditd Configuration Immutable | Making the audit configuration immutable prevents accidental as well as malicious modification of the audit rules, although it may be problematic if legitimate changes are needed during system operation. | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d in order to make the auditd configuration
immutable:
-e 2If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file in order to make the auditd configuration
immutable:
-e 2With this setting, a reboot will be required to change any audit rules. |
Verify the audit system prevents unauthorized changes with the following command: $ sudo grep "^\s*[^#]" /etc/audit/audit.rules | tail -1 -e 2 Is it the case that the audit system is not set to be immutable by adding the "-e 2" option to the end of "/etc/audit/audit.rules"? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 |
CCI-000162 CCI-000163 CCI-000164 |
AU-9 AU-9 AU-9 |
xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_delete | medium | Ensure auditd Collects Information on Kernel Module Unloading - delete_module | The removal of kernel modules can be used to alter the behavior of the kernel and potentially introduce malicious code into kernel space. It is important to have an audit trail of modules that have been introduced into the kernel. | To capture kernel module unloading events, use following line, setting ARCH to
either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modulesPlace to add the line depends on a way auditd daemon is configured. If it is configured
to use the augenrules program (the default), add the line to a file with suffix
.rules in the directory /etc/audit/rules.d .
If the auditd daemon is configured to use the auditctl utility,
add the line to file /etc/audit/audit.rules . |
To determine if the system is configured to audit calls to the delete_module system call, run the following command: $ sudo grep "delete_module" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_finit | medium | Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module | The addition/removal of kernel modules can be used to alter the behavior of the kernel and potentially introduce malicious code into kernel space. It is important to have an audit trail of modules that have been introduced into the kernel. | If the auditd daemon is configured to use the augenrules program
to read audit rules during daemon startup (the default), add the following lines to a file
with suffix .rules in the directory /etc/audit/rules.d to capture kernel module
loading and unloading events, setting ARCH to either b32 or b64 as appropriate for your system:
-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modulesIf the auditd daemon is configured to use the auditctl utility to read audit
rules during daemon startup, add the following lines to /etc/audit/audit.rules file
in order to capture kernel module loading and unloading events, setting ARCH to either b32 or
b64 as appropriate for your system:
-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modules |
To determine if the system is configured to audit calls to the finit_module system call, run the following command: $ sudo grep "finit_module" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_init | medium | Ensure auditd Collects Information on Kernel Module Loading - init_module | The addition of kernel modules can be used to alter the behavior of the kernel and potentially introduce malicious code into kernel space. It is important to have an audit trail of modules that have been introduced into the kernel. | To capture kernel module loading events, use following line, setting ARCH to
either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modulesPlace to add the line depends on a way auditd daemon is configured. If it is configured
to use the augenrules program (the default), add the line to a file with suffix
.rules in the directory /etc/audit/rules.d .
If the auditd daemon is configured to use the auditctl utility,
add the line to file /etc/audit/audit.rules . |
To determine if the system is configured to audit calls to the init_module system call, run the following command: $ sudo grep "init_module" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_login_events_faillock | medium | Record Attempts to Alter Logon and Logout Events - faillock | Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. | The audit system already collects login information for all users
and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d in order to watch for attempted manual
edits of files involved in storing logon events:
-w /var/log/faillock -p wa -k loginsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file in order to watch for unattempted manual
edits of files involved in storing logon events:
-w /var/log/faillock -p wa -k logins |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command: $ sudo auditctl -l | grep /var/run/faillock -w /var/run/faillock -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000172 CCI-002884 |
AU-2 d AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_login_events_lastlog | medium | Record Attempts to Alter Logon and Logout Events - lastlog | Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. | The audit system already collects login information for all users
and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d in order to watch for attempted manual
edits of files involved in storing logon events:
-w /var/log/lastlog -p wa -k loginsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file in order to watch for unattempted manual
edits of files involved in storing logon events:
-w /var/log/lastlog -p wa -k logins |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command: $ sudo auditctl -l | grep /var/log/lastlog -w /var/log/lastlog -p wa -k logins Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000126 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-2 d AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_media_export | medium | Ensure auditd Collects Information on Exporting to Media (successful) | The unauthorized exportation of data to external media could result in an information leak where classified information, Privacy Act information, and intellectual property could be lost. An audit trail should be created each time a filesystem is mounted to help identify and guard against information loss. | At a minimum, the audit system should collect media exportation
events for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d , setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=unset -F key=exportIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=unset -F key=export |
To determine if the system is configured to audit calls to the mount system call, run the following command: $ sudo grep "mount" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line. Is it the case that no line is returned? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_chage | medium | Ensure auditd Collects Information on the Use of Privileged Commands - chage | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "chage" command with the following command: $ sudo auditctl -l | grep chage -a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_chsh | medium | Ensure auditd Collects Information on the Use of Privileged Commands - chsh | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "chsh" command with the following command: $ sudo auditctl -l | grep chsh -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chsh Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_crontab | medium | Ensure auditd Collects Information on the Use of Privileged Commands - crontab | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "crontab" command with the following command: $ sudo auditctl -l | grep crontab -a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_gpasswd | medium | Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "gpasswd" command with the following command: $ sudo auditctl -l | grep gpasswd -a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_kmod | medium | Ensure auditd Collects Information on the Use of Privileged Commands - kmod | 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). | At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-w /usr/bin/kmod -p x -k modulesIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-w /usr/bin/kmod -p x -k modules |
Verify that Oracle Linux 8 is configured to audit the execution of the "kmod" command with the following command: $ sudo auditctl -l | grep kmod -a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-kmod Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_mount | medium | Ensure auditd Collects Information on the Use of Privileged Commands - mount | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "mount" command with the following command: $ sudo auditctl -l | grep mount -a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_newgrp | medium | Ensure auditd Collects Information on the Use of Privileged Commands - newgrp | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "newgrp" command with the following command: $ sudo auditctl -l | grep newgrp -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k privileged-newgrp Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000062-GPOS-00031 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000169 CCI-000135 CCI-000172 CCI-002884 |
AU-3 AU-12 a AU-3 (1) AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_pam_timestamp_check | medium | Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "pam_timestamp_check" command with the following command: $ sudo auditctl -l | grep pam_timestamp_check -a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_passwd | medium | Ensure auditd Collects Information on the Use of Privileged Commands - passwd | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "passwd" command with the following command: $ sudo auditctl -l | grep passwd -a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_postdrop | medium | Ensure auditd Collects Information on the Use of Privileged Commands - postdrop | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "postdrop" command with the following command: $ sudo auditctl -l | grep postdrop -a always,exit -F path=/usr/bin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postdrop Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_postqueue | medium | Ensure auditd Collects Information on the Use of Privileged Commands - postqueue | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "postqueue" command with the following command: $ sudo auditctl -l | grep postqueue -a always,exit -F path=/usr/bin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-postqueue Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_ssh_agent | medium | Record Any Attempts to Run ssh-agent | 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). | At a minimum, the audit system should collect any execution attempt
of the ssh-agent command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agentIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent |
Verify that Oracle Linux 8 is configured to audit the execution of the "ssh-agent" command with the following command: $ sudo auditctl -l | grep ssh-agent -a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_ssh_keysign | medium | Ensure auditd Collects Information on the Use of Privileged Commands - ssh-keysign | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "ssh-keysign" command with the following command: $ sudo auditctl -l | grep ssh-keysign -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-keysign Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_su | medium | Ensure auditd Collects Information on the Use of Privileged Commands - su | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "su" command with the following command: $ sudo auditctl -l | grep su -a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-su Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_sudo | medium | Ensure auditd Collects Information on the Use of Privileged Commands - sudo | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "sudo" command with the following command: $ sudo auditctl -l | grep sudo -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudo Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_umount | medium | Ensure auditd Collects Information on the Use of Privileged Commands - umount | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "umount" command with the following command: $ sudo auditctl -l | grep umount -a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000062-GPOS-00031 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000169 CCI-000135 CCI-000172 CCI-002884 |
AU-3 AU-12 a AU-3 (1) AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_unix_chkpwd | medium | Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "unix_chkpwd" command with the following command: $ sudo auditctl -l | grep unix_chkpwd -a always,exit -F path=/usr/bin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_chkpwd Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_unix_update | medium | Ensure auditd Collects Information on the Use of Privileged Commands - unix_update | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "unix_update" command with the following command: $ sudo auditctl -l | grep unix_update -a always,exit -F path=/usr/bin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix_update Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_userhelper | medium | Ensure auditd Collects Information on the Use of Privileged Commands - userhelper | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "userhelper" command with the following command: $ sudo auditctl -l | grep userhelper -a always,exit -F path=/usr/bin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-userhelper Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_usermod | medium | Ensure auditd Collects Information on the Use of Privileged Commands - usermod | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised 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 and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d :
-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules :
-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that Oracle Linux 8 is configured to audit the execution of the "usermod" command with the following command: $ sudo auditctl -l | grep usermod -a always,exit -F path=/usr/bin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_sudoers | medium | Ensure auditd Collects System Administrator Actions - /etc/sudoers | The actions taken by system administrators should be audited to keep a record of what was executed on the system, as well as, for accountability purposes. Editing the sudoers file may be sign of an attacker trying to establish persistent methods to a system, auditing the editing of the sudoers files mitigates this risk. | At a minimum, the audit system should collect administrator actions
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the default),
add the following line to a file with suffix .rules in the directory
/etc/audit/rules.d :
-w /etc/sudoers -p wa -k actionsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-w /etc/sudoers -p wa -k actions |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command: $ sudo auditctl -l | grep /etc/sudoers -w /etc/sudoers -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000004-GPOS-00004 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000239-GPOS-00089 SRG-OS-000240-GPOS-00090 SRG-OS-000303-GPOS-00120 SRG-OS-000304-GPOS-00121 SRG-OS-000392-GPOS-00172 |
CCI-000018 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001403 CCI-001404 CCI-002130 CCI-002132 CCI-002884 |
AC-2 (4) AU-3 AU-3 (1) AU-12 a AU-12 c AC-2 (4) AC-2 (4) |
xccdf_org.ssgproject.content_rule_audit_rules_sudoers_d | medium | Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/ | The actions taken by system administrators should be audited to keep a record of what was executed on the system, as well as, for accountability purposes. Editing the sudoers file may be sign of an attacker trying to establish persistent methods to a system, auditing the editing of the sudoers files mitigates this risk. | At a minimum, the audit system should collect administrator actions
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the default),
add the following line to a file with suffix .rules in the directory
/etc/audit/rules.d :
-w /etc/sudoers.d/ -p wa -k actionsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-w /etc/sudoers.d/ -p wa -k actions |
Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command: $ sudo auditctl -l | grep/etc/sudoers.d -w /etc/sudoers.d/ -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000004-GPOS-00004 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000239-GPOS-00089 SRG-OS-000240-GPOS-00090 SRG-OS-000303-GPOS-00120 SRG-OS-000304-GPOS-00121 SRG-OS-000392-GPOS-00172 |
CCI-000018 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001403 CCI-001404 CCI-002130 CCI-002132 CCI-002884 |
AC-2 (4) AU-3 AU-3 (1) AU-12 a AU-12 c AC-2 (4) AC-2 (4) |
xccdf_org.ssgproject.content_rule_audit_rules_suid_privilege_function | medium | Record Events When Privileged Executables Are Run | 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. | Verify the system generates an audit record when privileged functions are executed.
If audit is using the "auditctl" tool to load the rules, run the following command:
$ sudo grep execve /etc/audit/audit.rulesIf audit is using the "augenrules" tool to load the rules, run the following command: $ sudo grep -r execve /etc/audit/rules.d -a always,exit -F arch=b32 -S execve -C uid!=euid -k setuid -a always,exit -F arch=b64 -S execve -C uid!=euid -k setuid -a always,exit -F arch=b32 -S execve -C gid!=egid -k setgid -a always,exit -F arch=b64 -S execve -C gid!=egid -k setgidIf both the "b32" and "b64" audit rules for "SUID" files are not defined, this is a finding. If both the "b32" and "b64" audit rules for "SGID" files are not defined, this is a finding. |
Verify Oracle Linux 8 audits the execution of privileged functions. Check if Oracle Linux 8 is configured to audit the execution of the "execve" system call using the following command: $ sudo grep execve /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S execve -C uid!=euid -k setuid -a always,exit -F arch=b64 -S execve -C uid!=euid -k setuid -a always,exit -F arch=b32 -S execve -C gid!=egid -k setgid -a always,exit -F arch=b64 -S execve -C gid!=egid -k setgid Is it the case that the command does not return all lines, or the lines are commented out? |
SRG-OS-000365-GPOS-00152 SRG-OS-000354-GPOS-00142 SRG-OS-000358-GPOS-00145 SRG-OS-000352-GPOS-00140 SRG-OS-000353-GPOS-00141 SRG-OS-000350-GPOS-00138 SRG-OS-000351-GPOS-00139 SRG-OS-000348-GPOS-00136 SRG-OS-000349-GPOS-00137 SRG-OS-000337-GPOS-00129 SRG-OS-000326-GPOS-00126 SRG-OS-000327-GPOS-00127 |
CCI-001814 CCI-001882 CCI-001889 CCI-001880 CCI-001881 CCI-001878 CCI-001879 CCI-001875 CCI-001877 CCI-001914 CCI-002233 CCI-002234 |
|
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_creat | medium | Record Unsuccessful Access Attempts to Files - creat | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access |
Verify Oracle Linux 8 generates an audit record for unsuccessful attempts to use the creat system call. If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command: $ sudo grep -r creat /etc/audit/rules.d If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command: $ sudo grep creat /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_ftruncate | medium | Record Unsuccessful Access Attempts to Files - ftruncate | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access |
Verify Oracle Linux 8 generates an audit record for unsuccessful attempts to use the ftruncate system call. If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command: $ sudo grep -r ftruncate /etc/audit/rules.d If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command: $ sudo grep ftruncate /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_open | medium | Record Unsuccessful Access Attempts to Files - open | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access |
Verify Oracle Linux 8 generates an audit record for unsuccessful attempts to use the open system call. If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command: $ sudo grep -r open /etc/audit/rules.d If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command: $ sudo grep open /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_open_by_handle_at | medium | Record Unsuccessful Access Attempts to Files - open_by_handle_at | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access |
Verify Oracle Linux 8 generates an audit record for unsuccessful attempts to use the open_by_handle_at system call. If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command: $ sudo grep -r open_by_handle_at /etc/audit/rules.d If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command: $ sudo grep open_by_handle_at /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_openat | medium | Record Unsuccessful Access Attempts to Files - openat | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access |
Verify Oracle Linux 8 generates an audit record for unsuccessful attempts to use the openat system call. If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command: $ sudo grep -r openat /etc/audit/rules.d If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command: $ sudo grep openat /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_truncate | medium | Record Unsuccessful Access Attempts to Files - truncate | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d :
-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access |
Verify Oracle Linux 8 generates an audit record for unsuccessful attempts to use the truncate system call. If the auditd daemon is configured to use the "augenrules" program to to read audit rules during daemon startup (the default), run the following command: $ sudo grep -r truncate /etc/audit/rules.d If the auditd daemon is configured to use the "auditctl" utility to read audit rules during daemon startup, run the following command: $ sudo grep truncate /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_group | medium | Record Events that Modify User/Group Information - /etc/group | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be investigated for legitimacy. | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d , in order to capture events that modify
account changes:
-w /etc/group -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file, in order to capture events that modify
account changes:
-w /etc/group -p wa -k audit_rules_usergroup_modification |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command: $ sudo auditctl -l | egrep '(/etc/group)' -w /etc/group -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000004-GPOS-00004 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000239-GPOS-00089 SRG-OS-000240-GPOS-00090 SRG-OS-000241-GPOS-00091 SRG-OS-000274-GPOS-00104 SRG-OS-000275-GPOS-00105 SRG-OS-000276-GPOS-00106 SRG-OS-000277-GPOS-00107 SRG-OS-000303-GPOS-00120 SRG-OS-000304-GPOS-00121 SRG-OS-000392-GPOS-00172 |
CCI-000018 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001403 CCI-001404 CCI-001405 CCI-001683 CCI-001684 CCI-001685 CCI-001686 CCI-002130 CCI-002132 CCI-002884 |
AC-2 (4) AU-3 AU-3 (1) AU-12 a AU-12 c AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) |
xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_gshadow | medium | Record Events that Modify User/Group Information - /etc/gshadow | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be investigated for legitimacy. | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d , in order to capture events that modify
account changes:
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file, in order to capture events that modify
account changes:
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command: $ sudo auditctl -l | egrep '(/etc/gshadow)' -w /etc/gshadow -p wa -k identity If the command does not return a line, or the line is commented out, this is a finding. Is it the case that the system is not configured to audit account changes? |
SRG-OS-000004-GPOS-00004 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000239-GPOS-00089 SRG-OS-000240-GPOS-00090 SRG-OS-000241-GPOS-00091 SRG-OS-000274-GPOS-00104 SRG-OS-000275-GPOS-00105 SRG-OS-000276-GPOS-00106 SRG-OS-000277-GPOS-00107 SRG-OS-000303-GPOS-00120 SRG-OS-000304-GPOS-00121 SRG-OS-000392-GPOS-00172 |
CCI-000018 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001403 CCI-001404 CCI-001405 CCI-001683 CCI-001684 CCI-001685 CCI-001686 CCI-002130 CCI-002132 CCI-002884 |
AC-2 (4) AU-3 AU-3 (1) AU-12 a AU-12 c AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) |
xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_opasswd | medium | Record Events that Modify User/Group Information - /etc/security/opasswd | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be investigated for legitimacy. | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d , in order to capture events that modify
account changes:
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file, in order to capture events that modify
account changes:
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command: $ sudo auditctl -l | egrep '(/etc/security/opasswd)' -w /etc/security/opasswd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000004-GPOS-00004 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000239-GPOS-00089 SRG-OS-000240-GPOS-00090 SRG-OS-000241-GPOS-00091 SRG-OS-000274-GPOS-00104 SRG-OS-000275-GPOS-00105 SRG-OS-000276-GPOS-00106 SRG-OS-000277-GPOS-00107 SRG-OS-000303-GPOS-00120 SRG-OS-000304-GPOS-00121 SRG-OS-000392-GPOS-00172 |
CCI-000018 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001403 CCI-001404 CCI-001405 CCI-001683 CCI-001684 CCI-001685 CCI-001686 CCI-002130 CCI-002132 CCI-002884 |
AC-2 (4) AU-3 AU-3 (1) AU-12 a AU-12 c AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) |
xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_passwd | medium | Record Events that Modify User/Group Information - /etc/passwd | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be investigated for legitimacy. | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d , in order to capture events that modify
account changes:
-w /etc/passwd -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file, in order to capture events that modify
account changes:
-w /etc/passwd -p wa -k audit_rules_usergroup_modification |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command: $ sudo auditctl -l | egrep '(/etc/passwd)' -w /etc/passwd -p wa -k identity Is it the case that the command does not return a line, or the line is commented out? |
SRG-OS-000004-GPOS-00004 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000239-GPOS-00089 SRG-OS-000240-GPOS-00090 SRG-OS-000241-GPOS-00091 SRG-OS-000274-GPOS-00104 SRG-OS-000275-GPOS-00105 SRG-OS-000276-GPOS-00106 SRG-OS-000277-GPOS-00107 SRG-OS-000303-GPOS-00120 SRG-OS-000304-GPOS-00121 SRG-OS-000392-GPOS-00172 |
CCI-000018 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001403 CCI-001404 CCI-001405 CCI-001683 CCI-001684 CCI-001685 CCI-001686 CCI-002130 CCI-002132 CCI-002884 |
AC-2 (4) AU-3 AU-3 (1) AU-12 a AU-12 c AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) |
xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_shadow | medium | Record Events that Modify User/Group Information - /etc/shadow | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be investigated for legitimacy. | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d , in order to capture events that modify
account changes:
-w /etc/shadow -p wa -k audit_rules_usergroup_modification If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file, in order to capture events that modify
account changes:
-w /etc/shadow -p wa -k audit_rules_usergroup_modification |
Verify Oracle Linux 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command: $ sudo auditctl -l | egrep '(/etc/shadow)' -w /etc/shadow -p wa -k identity Is it the case that command does not return a line, or the line is commented out? |
SRG-OS-000004-GPOS-00004 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000239-GPOS-00089 SRG-OS-000240-GPOS-00090 SRG-OS-000241-GPOS-00091 SRG-OS-000274-GPOS-00104 SRG-OS-000275-GPOS-00105 SRG-OS-000276-GPOS-00106 SRG-OS-000277-GPOS-00107 SRG-OS-000303-GPOS-00120 SRG-OS-000304-GPOS-00121 SRG-OS-000392-GPOS-00172 |
CCI-000018 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001403 CCI-001404 CCI-001405 CCI-001683 CCI-001684 CCI-001685 CCI-001686 CCI-002130 CCI-002132 CCI-002884 |
AC-2 (4) AU-3 AU-3 (1) AU-12 a AU-12 c AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) AC-2 (4) |
xccdf_org.ssgproject.content_rule_auditd_audispd_configure_sufficiently_large_partition | medium | Configure a Sufficiently Large Partition for Audit Logs | 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. | The Oracle Linux 8 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.
The partition size needed to capture a week's worth of audit records is
based on the activity level of the system and the total storage capacity
available. In normal circumstances, 10.0 GB of storage space for audit
records will be sufficient.
Determine which partition the audit records are being written to with the
following command:
$ sudo grep log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.logCheck the size of the partition that audit records are written to with the following command: $ sudo df -h /var/log/audit/ /dev/sda2 24G 10.4G 13.6G 43% /var/log/audit |
To verify whether audispd plugin off-loads audit records onto a different system or media from the system being audited, run the following command: $ sudo grep -i remote_server /etc/audit/audisp-remote.conf The output should return something similar to where REMOTE_SYSTEM is an IP address or hostname: remote_server = REMOTE_SYSTEM Determine which partition the audit records are being written to with the following command: $ sudo grep log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log Check the size of the partition that audit records are written to with the following command and verify whether it is sufficiently large: $ sudo df -h /var/log/audit/ /dev/sda2 24G 10.4G 13.6G 43% /var/log/audit Is it the case that audispd is not sending logs to a remote system and the local partition has inadequate space? |
SRG-OS-000341-GPOS-00132 |
CCI-001849 |
|
xccdf_org.ssgproject.content_rule_auditd_data_disk_error_action | medium | Configure auditd Disk Error Action on Disk Error | Taking appropriate action in case of disk errors will minimize the possibility of losing audit records. | The auditd service can be configured to take an action
when there is a disk error.
Edit the file /etc/audit/auditd.conf . Add or modify the following line,
substituting ACTION appropriately:
disk_error_action = ACTIONSet this value to single to cause the system to switch to single-user
mode for corrective action. Acceptable values also include syslog ,
exec , single , and halt . For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. Details regarding all possible values for ACTION are described in the
auditd.conf man page. |
Verify Oracle Linux 8 takes the appropriate action when an audit processing failure occurs. Check that Oracle Linux 8 takes the appropriate action when an audit processing failure occurs with the following command: $ sudo grep disk_error_action /etc/audit/auditd.conf disk_error_action = If the value of the "disk_error_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, ask the system administrator to indicate how the system takes appropriate action when an audit process failure occurs. Is it the case that there is no evidence of appropriate action? |
SRG-OS-000047-GPOS-00023 |
CCI-000140 |
AU-5 b |
xccdf_org.ssgproject.content_rule_auditd_data_disk_full_action | medium | Configure auditd Disk Full Action when Disk Space Is Full | Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records. | The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf . Add or modify the following line,
substituting ACTION appropriately:
disk_full_action = ACTIONSet this value to single to cause the system to switch to single-user
mode for corrective action. Acceptable values also include syslog ,
exec ,
single , and halt . For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. Details regarding all possible values for ACTION are described in the
auditd.conf man page. |
Verify Oracle Linux 8 takes the appropriate action when the audit storage volume is full. Check that Oracle Linux 8 takes the appropriate action when the audit storage volume is full with the following command: $ sudo grep disk_full_action /etc/audit/auditd.conf disk_full_action = If the value of the "disk_full_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, ask the system administrator to indicate how the system takes appropriate action when an audit storage volume is full. Is it the case that there is no evidence of appropriate action? |
SRG-OS-000047-GPOS-00023 |
CCI-000140 |
AU-5 b |
xccdf_org.ssgproject.content_rule_auditd_data_retention_action_mail_acct | medium | Configure auditd mail_acct Action on Low Disk Space | Email sent to the root account is typically aliased to the administrators of the system, who can take appropriate action. | The auditd service can be configured to send email to
a designated account in certain situations. Add or correct the following line
in /etc/audit/auditd.conf to ensure that administrators are notified
via email for those situations:
action_mail_acct = |
Verify that the Oracle Linux 8 "auditd" service is configured to notify the SA and ISSO in the event of an audit processing failure. Inspect /etc/audit/auditd.conf and locate the following line to determine if the system is configured to send email to an account when it needs to notify an administrator: action_mail_acct = Is it the case that auditd is not configured to send emails per identified actions? |
SRG-OS-000046-GPOS-00022 SRG-OS-000343-GPOS-00134 |
CCI-000139 CCI-001855 |
AU-5 a |
xccdf_org.ssgproject.content_rule_auditd_data_retention_space_left_action | medium | Configure auditd space_left Action on Low Disk Space | Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption. | The auditd service can be configured to take an action
when disk space starts to run low.
Edit the file /etc/audit/auditd.conf . Modify the following line,
substituting ACTION appropriately:
space_left_action = ACTIONPossible values for ACTION are described in the auditd.conf man page.
These include:
email (instead of the default,
which is suspend ) as it is more likely to get prompt attention. Acceptable values
also include suspend , single , and halt . |
Inspect /etc/audit/auditd.conf and locate the following line to determine if the system is configured to email the administrator when disk space is starting to run low: $ sudo grep space_left_action /etc/audit/auditd.conf space_left_action Acceptable values are email, suspend, single, and halt. Is it the case that the system is not configured to send an email to the system administrator when disk space is starting to run low? |
SRG-OS-000343-GPOS-00134 |
CCI-001855 |
|
xccdf_org.ssgproject.content_rule_auditd_data_retention_space_left_percentage | medium | Configure auditd space_left on Low Disk Space | Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption. | The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf . Add or modify the following line,
substituting PERCENTAGE appropriately:
space_left = PERCENTAGE%Set this value to at least 25 to cause the system to notify the user of an issue. |
Inspect /etc/audit/auditd.conf and locate the following line to determine if the system is configured correctly: space_left PERCENTAGE% Is it the case that the system is not configured with a specific percentage to notify administrators of an issue? |
SRG-OS-000343-GPOS-00134 |
CCI-001855 |
|
xccdf_org.ssgproject.content_rule_auditd_local_events | medium | Include Local Events in Audit Logs | If option local_events isn't set to yes only events from
network will be aggregated. |
To configure Audit daemon to include local events in Audit logs, set
local_events to yes in /etc/audit/auditd.conf .
This is the default setting. |
To verify that Audit Daemon is configured to include local events, run the following command: $ sudo grep local_events /etc/audit/auditd.conf The output should return the following: local_events = yes Is it the case that local_events isn't set to yes? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_auditd_log_format | medium | Resolve information before writing to audit logs | If option log_format isn't set to ENRICHED , the
audit records will be stored in a format exactly as the kernel sends them. |
To configure Audit daemon to resolve all uid, gid, syscall,
architecture, and socket address information before writing the
events to disk, set log_format to ENRICHED
in /etc/audit/auditd.conf . |
To verify that Audit Daemon is configured to resolve all uid, gid, syscall, architecture, and socket address information before writing the event to disk, run the following command: $ sudo grep log_format /etc/audit/auditd.conf The output should return the following: log_format = ENRICHED Is it the case that log_format isn't set to ENRICHED? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_auditd_name_format | medium | Set hostname as computer node name in audit logs | If option name_format is left at its default value of
none , audit events from different computers may be hard
to distinguish. |
To configure Audit daemon to use value returned by gethostname
syscall as computer node name in the audit events,
set name_format to hostname
in /etc/audit/auditd.conf . |
To verify that Audit Daemon is configured to record the hostname in audit events, run the following command: $ sudo grep name_format /etc/audit/auditd.conf The output should return the following: name_format = hostname Is it the case that name_format isn't set to hostname? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
xccdf_org.ssgproject.content_rule_auditd_overflow_action | medium | Appropriate Action Must be Setup When the Internal Audit Event Queue is Full | The audit system should have an action setup in the event the internal event queue becomes full so that no data is lost. | The audit system should have an action setup in the event the internal event queue becomes full.
To setup an overflow action edit /etc/audit/auditd.conf . Set overflow_action
to one of the following values: syslog , single , halt . |
Verify the audit system is configured to take an appropriate action when the internal event queue is full: $ sudo grep -i overflow_action /etc/audit/auditd.conf The output should contain overflow_action = syslog If the value of the "overflow_action" option is not set to syslog, single, halt or the line is commented out, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or media. Is it the case that auditd overflow action is not set correctly? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
xccdf_org.ssgproject.content_rule_banner_etc_issue | medium | Modify the System Login Banner | 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 login interfaces with human users and are not required when such human interfaces do not exist. |
To configure the system login banner edit /etc/issue . Replace the
default text with a message compliant with the local site policy or a legal
disclaimer.
The DoD required text is either:
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:
OR: I've read & consent to terms in IS user agreem't.
|
To check if the system login banner is compliant, run the following command: $ cat /etc/issue Is it the case that it does not display the required banner? |
SRG-OS-000023-GPOS-00006 SRG-OS-000024-GPOS-00007 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 |
CCI-000048 CCI-000050 CCI-001384 CCI-001385 CCI-001386 CCI-001387 CCI-001388 |
AC-8 a AC-8 b AC-8 c AC-8 c AC-8 c AC-8 c AC-8 c |
xccdf_org.ssgproject.content_rule_bios_enable_execution_restrictions | medium | Enable NX or XD Support in the BIOS | Computers with the ability to prevent this type of code execution frequently put an option in the BIOS that will allow users to turn the feature on or off at will. | Reboot the system and enter the BIOS or Setup configuration menu. Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX) on AMD-based systems. | Verify the NX (no-execution) bit flag is set on the system. Check that the no-execution bit flag is set with the following commands: $ sudo dmesg | grep NX [ 0.000000] NX (Execute Disable) protection: active If "dmesg" does not show "NX (Execute Disable) protection" active, check the cpuinfo settings with the following command: $ sudo grep flags /proc/cpuinfo flags : fpu vme de pse tsc ms nx rdtscp lm constant_ts The output should contain the "nx" flag. Then, verify that there are no log messsages stating that NX is disabled in the system log. Run the following command: $ sudo grep -P "^.+protection: disabled.+" /var/log/dmesg The output should be empty. Then, check that NX is not disabled in the kernel command line. $ sudo grep -P ".+noexec[0-9]*=off.+" /proc/cmdline The output should be empty. Is it the case that NX is disabled? |
SRG-OS-000433-GPOS-00192 SRG-OS-000433-GPOS-00193 |
CCI-002824 |
|
xccdf_org.ssgproject.content_rule_chronyd_client_only | low | Disable chrony daemon from acting as server | Minimizing the exposure of the server functionality of the chrony daemon diminishes the attack surface. | The port option in /etc/chrony.conf can be set to
0 to make chrony daemon to never open any listening port
for server operation and to operate strictly in a client-only mode. |
To verify that port has been set properly, perform the following: $ grep '\bport\b' /etc/chrony.conf The output should return port 0 Is it the case that port is not set or port is set to a non-zero value? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_chronyd_no_chronyc_network | low | Disable network management of chrony daemon | Not exposing the management interface of the chrony daemon on the network diminishes the attack space. | The cmdport option in /etc/chrony.conf can be set to
0 to stop chrony daemon from listening on the UDP port 323
for management connections made by chronyc. |
To verify that cmdport has been set properly, perform the following: $ grep '\bcmdport\b' /etc/chrony.conf The output should return cmdport 0 Is it the case that cmdport is not set or cmdport is set to a non-zero value? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_chronyd_or_ntpd_set_maxpoll | medium | Configure Time Service Maxpoll Interval | 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). | The maxpoll should be configured to
in /etc/ntp.conf or
/etc/chrony.conf to continuously poll time servers. To configure
maxpoll in /etc/ntp.conf or /etc/chrony.conf
add the following after each `server`, `pool` or `peer` entry:
maxpollto serverdirectives. If using chrony any pooldirectives should be configured too. If no server or pool directives are configured, the rule evaluates
to pass. |
Verify Oracle Linux 8 is securely comparing internal information system clocks at a regular interval with an NTP server with the following command: $ sudo grep maxpoll /etc/ntp.conf /etc/chrony.conf server [ntp.server.name] iburst maxpoll . Is it the case that "maxpoll" has not been set to the value of "<sub idref="var_time_service_set_maxpoll" />", is commented out, or is missing? |
SRG-OS-000355-GPOS-00143 SRG-OS-000356-GPOS-00144 |
CCI-001891 CCI-002046 |
|
xccdf_org.ssgproject.content_rule_chronyd_server_directive | medium | Ensure Chrony is only configured with the server directive | Depending on the infrastruture being used the pool directive may not be supported. |
Check that Chrony only has time sources configured with the server directive. |
Run the following command and verify that time sources are only configure with server directive: # grep -E "^(server|pool)" /etc/chrony.conf A line with the appropriate server should be returned, any line returned starting with pool is a finding. Is it the case that an authoritative remote time server is not configured or configured with pool directive? |
SRG-OS-000355-GPOS-00143 |
CCI-001891 |
|
xccdf_org.ssgproject.content_rule_clean_components_post_updating | low | Ensure yum Removes Previous Package Versions | Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by some adversaries. |
yum should be configured to remove previous software components after
new versions have been installed. To configure yum to remove the
previous software components after updating, set the clean_requirements_on_remove
to 1 in /etc/yum.conf . |
Verify Oracle Linux 8 removes all software components after updated versions have been installed. $ grep clean_requirements_on_remove /etc/yum.conf clean_requirements_on_remove=1 Is it the case that '"clean_requirements_on_remove" is not set to "1"'? |
SRG-OS-000437-GPOS-00194 |
CCI-002617 |
|
xccdf_org.ssgproject.content_rule_configure_bashrc_exec_tmux | medium | Support session locking with tmux | Unlike bash itself, the tmux terminal multiplexer
provides a mechanism to lock sessions after period of inactivity.
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 tmux terminal multiplexer is used to implement
automatic session locking. It should be started from
/etc/bashrc or drop-in files within /etc/profile.d/ . |
To verify that tmux is configured to execute, run the following command: $ grep -A1 -B3 "case ..name. in sshd|login) exec tmux ;; esac" /etc/bashrc /etc/profile.d/* The output should return the following: if [ "$PS1" ]; then parent=$(ps -o ppid= -p $$) name=$(ps -o comm= -p $parent) case "$name" in sshd|login) exec tmux ;; esac fi Is it the case that exec tmux is not present at the end of bashrc? |
SRG-OS-000028-GPOS-00009 SRG-OS-000030-GPOS-00011 |
CCI-000056 CCI-000058 |
AC-11 b AC-11 a |
xccdf_org.ssgproject.content_rule_configure_bind_crypto_policy | high | Configure BIND to use System Crypto Policy | Overriding the system crypto policy makes the behavior of the BIND service violate expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
BIND is supported by crypto policy, but the BIND configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that the /etc/named.conf
includes the appropriate configuration:
In the options section of /etc/named.conf , make sure that the following line
is not commented out or superseded by later includes:
include "/etc/crypto-policies/back-ends/bind.config";
|
To verify that BIND uses the system crypto policy, check out that the BIND config file /etc/named.conf contains the include "/etc/crypto-policies/back-ends/bind.config"; directive: $ sudo grep 'include "/etc/crypto-policies/back-ends/bind.config";' /etc/named.conf Verify that the directive is at the bottom of the options section of the config file. Is it the case that BIND is installed and the BIND config file doesn't contain the <pre>include "/etc/crypto-policies/back-ends/bind.config";</pre> directive? |
|||
xccdf_org.ssgproject.content_rule_configure_crypto_policy | high | Configure System Cryptography Policy | Centralized cryptographic policies simplify applying secure ciphers across an operating system and the applications that run on that operating system. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. | To configure the system cryptography policy to use ciphers only from the
policy, run the following command:
$ sudo update-crypto-policies --setThe rule checks if settings for selected crypto policy are configured as expected. Configuration files in the /etc/crypto-policies/back-ends are either symlinks to correct files provided by Crypto-policies package or they are regular files in case crypto policy customizations are applied.
Crypto policies may be customized by crypto policy modules, in which case it is delimited from the base policy using a colon. |
To verify that cryptography policy has been configured correctly, run the following command: $ update-crypto-policies --show The output should return . Run the command to check if the policy is correctly applied: $ update-crypto-policies --is-applied The output should be The configured policy is applied. Moreover, check if settings for selected crypto policy are as expected. List all libraries for which it holds that their crypto policies do not have symbolic link in /etc/crypto-policies/back-ends. $ ls -l /etc/crypto-policies/back-ends/ | grep '^[^l]' | tail -n +2 | awk -F' ' '{print $NF}' | awk -F'.' '{print $1}' | sort Subsequently, check if matching libraries have drop in files in the /etc/crypto-policies/local.d directory. $ ls /etc/crypto-policies/local.d/ | awk -F'-' '{print $1}' | uniq | sort Outputs of two previous commands should match. Is it the case that cryptographic policy is not configured or is configured incorrectly? |
|||
xccdf_org.ssgproject.content_rule_configure_firewalld_ports | medium | Configure the Firewalld Ports | 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 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. |
Configure the firewalld ports to allow approved services to have access to the system.
To configure firewalld to open ports, run the following command:
firewall-cmd --permanent --add-port=port_number/tcpTo configure firewalld to allow access for pre-defined services, run the following
command:
firewall-cmd --permanent --add-service=service_name |
Inspect the list of enabled firewall ports and verify they are configured correctly by running the following command: $ sudo firewall-cmd --list-all Is it the case that the firewalld rules are not configured? |
SRG-OS-000096-GPOS-00050 SRG-OS-000297-GPOS-00115 |
CCI-000382 CCI-002314 |
CM-7 |
xccdf_org.ssgproject.content_rule_configure_gnutls_tls_crypto_policy | medium | Configure GnuTLS library to use DoD-approved TLS Encryption | Overriding the system crypto policy makes the behavior of the GnuTLS library violate expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that
/etc/crypto-policies/back-ends/gnutls.config contains the following
line and is not commented out:
+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0
|
To verify if GnuTLS uses defined DoD-approved TLS Crypto Policy, run: $ sudo grep '+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0' /etc/crypto-policies/back-ends/gnutls.config and verify that a match exists. Is it the case that cryptographic policy for gnutls is not configured or is configured incorrectly? |
SRG-OS-000250-GPOS-00093 |
CCI-001453 |
AC-17 (2) |
xccdf_org.ssgproject.content_rule_configure_kerberos_crypto_policy | high | Configure Kerberos to use System Crypto Policy | Overriding the system crypto policy makes the behavior of Kerberos violate expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages. Kerberos is supported by crypto policy, but it's configuration may be set up to ignore it. To check that Crypto Policies settings for Kerberos are configured correctly, examine that there is a symlink at /etc/krb5.conf.d/crypto-policies targeting /etc/cypto-policies/back-ends/krb5.config. If the symlink exists, Kerberos is configured to use the system-wide crypto policy settings. | Check that the symlink exists and target the correct Kerberos crypto policy, with the following command: file /etc/krb5.conf.d/crypto-policies If command ouput shows the following line, Kerberos is configured to use the system-wide crypto policy. /etc/krb5.conf.d/crypto-policies: symbolic link to /etc/crypto-policies/back-ends/krb5.config Is it the case that the symlink does not exist or points to a different target? |
|||
xccdf_org.ssgproject.content_rule_configure_libreswan_crypto_policy | high | Configure Libreswan to use System Crypto Policy | Overriding the system crypto policy makes the behavior of the Libreswan service violate expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
Libreswan is supported by system crypto policy, but the Libreswan configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that the /etc/ipsec.conf
includes the appropriate configuration file.
In /etc/ipsec.conf , make sure that the following line
is not commented out or superseded by later includes:
include /etc/crypto-policies/back-ends/libreswan.config
|
Verify that the IPSec service uses the system crypto policy. If the ipsec service is not installed is not applicable. Check to see if the "IPsec" service is active with the following command: $ systemctl status ipsec ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled) Active: inactive (dead) If the "IPsec" service is active, check to see if it is using the system crypto policy with the following command: $ sudo grep include /etc/ipsec.conf /etc/ipsec.d/*.conf /etc/ipsec.conf:include /etc/crypto-policies/back-ends/libreswan.config Is it the case that the "IPsec" service is active and the ipsec configuration file does not contain does not contain <tt>include /etc/crypto-policies/back-ends/libreswan.config</tt>? |
|||
xccdf_org.ssgproject.content_rule_configure_openssl_crypto_policy | medium | Configure OpenSSL library to use System Crypto Policy | Overriding the system crypto policy makes the behavior of the Java runtime violates expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSL is supported by crypto policy, but the OpenSSL configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, you have to examine the OpenSSL config file
available under /etc/pki/tls/openssl.cnf .
This file has the ini format, and it enables crypto policy support
if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/opensslcnf.config directive. |
To verify that OpenSSL uses the system crypto policy, check out that the OpenSSL config file /etc/pki/tls/openssl.cnf contains the [ crypto_policy ] section with the .include /etc/crypto-policies/back-ends/opensslcnf.config directive: $ sudo grep '\.include\s* /etc/crypto-policies/back-ends/opensslcnf.config$' /etc/pki/tls/openssl.cnf. Is it the case that the OpenSSL config file doesn't contain the whole section, or the section doesn't contain the <pre>.include /etc/crypto-policies/back-ends/opensslcnf.config</pre> directive? |
SRG-OS-000250-GPOS-00093 |
CCI-001453 |
AC-17 (2) |
xccdf_org.ssgproject.content_rule_configure_openssl_tls_crypto_policy | medium | Configure OpenSSL library to use TLS Encryption | Without cryptographic integrity protections, information can be altered by unauthorized users without detection. | Crypto Policies are means of enforcing certain cryptographic settings for
selected applications including OpenSSL. OpenSSL is by default configured to
modify its configuration based on currently configured Crypto Policy.
Editing the Crypto Policy back-end is not recommended.
Check the crypto-policies(7) man page and choose a policy that configures TLS
protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
Or create and apply a custom policy that restricts minimum TLS version to 1.2.
For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
this is expected:
$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config MinProtocol = TLSv1.2Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is expected: $ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config TLS.MinProtocol = TLSv1.2 DTLS.MinProtocol = DTLSv1.2 |
To verify if the OpenSSL uses defined TLS Crypto Policy, run: $ grep -P '^(TLS\.)?MinProtocol' /etc/crypto-policies/back-ends/opensslcnf.config and verify that the value is TLSv1.2 Is it the case that cryptographic policy for openssl is not configured or is configured incorrectly? |
SRG-OS-000250-GPOS-00093 |
CCI-001453 |
AC-17 (2) |
xccdf_org.ssgproject.content_rule_configure_ssh_crypto_policy | medium | Configure SSH to use System Crypto Policy | Overriding the system crypto policy makes the behavior of the SSH service violate expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
SSH is supported by crypto policy, but the SSH configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that
the CRYPTO_POLICY variable is either commented or not set at all
in the /etc/sysconfig/sshd . |
Verify that sshd isn't configured to ignore the system wide cryptographic policy. Check that the CRYPTO_POLICY variable is not set or is commented out in the /etc/sysconfig/sshd. Run the following command: $ sudo grep CRYPTO_POLICY /etc/sysconfig/sshd Is it the case that the CRYPTO_POLICY variable is set or is not commented out in the /etc/sysconfig/sshd? |
SRG-OS-000250-GPOS-00093 |
CCI-001453 |
AC-17 (2) |
xccdf_org.ssgproject.content_rule_configure_tmux_lock_after_time | medium | Configure tmux to lock session after inactivity | Locking the session after a period of inactivity limits the potential exposure if the session is left unattended. | To enable console screen locking in tmux terminal multiplexer
after a period of inactivity,
the lock-after-time option has to be set to a value greater than 0 and less than
or equal to 900 in /etc/tmux.conf . |
To verify that session locking after period of inactivity is configured in tmux, run the following command: $ sudo grep lock-after-time /etc/tmux.conf The output should return the following: set -g lock-after-time 900 Then, verify that the /etc/tmux.conf file can be read by other users than root: $ sudo ls -al /etc/tmux.conf Is it the case that lock-after-time is set to a value greater than 900 or zero? |
SRG-OS-000029-GPOS-00010 SRG-OS-000031-GPOS-00012 |
CCI-000057 CCI-000060 |
AC-11 a AC-11 (1) |
xccdf_org.ssgproject.content_rule_configure_tmux_lock_command | medium | Configure the tmux Lock Command | The tmux package allows for a session lock to be implemented and configured.
However, the session lock is implemented by an external command. The tmux
default configuration does not contain an effective session lock. |
To enable console screen locking in tmux terminal multiplexer,
the vlock command must be configured to be used as a locking
mechanism.
Add the following line to /etc/tmux.conf :
set -g lock-command vlock. The console can now be locked with the following key combination: ctrl+b :lock-session |
To verify that vlock is configured as a locking mechanism in tmux, run the following command: $ sudo grep lock-command /etc/tmux.conf The output should return the following: set -g lock-command vlock Then, verify that the /etc/tmux.conf file can be read by other users than root: $ sudo ls -al /etc/tmux.conf Is it the case that lock-command is not set? |
SRG-OS-000028-GPOS-00009 SRG-OS-000030-GPOS-00011 |
CCI-000056 CCI-000058 |
AC-11 b AC-11 a |
xccdf_org.ssgproject.content_rule_configure_usbguard_auditbackend | medium | Log USBGuard daemon audit events using Linux Audit | Using the Linux Audit logging allows for centralized trace of events. | To configure USBGuard daemon to log via Linux Audit
(as opposed directly to a file),
AuditBackend option in /etc/usbguard/usbguard-daemon.conf
needs to be set to LinuxAudit . |
To verify that Linux Audit logging is enabled for the USBGuard daemon, run the following command: $ sudo grep AuditBackend /etc/usbguard/usbguard-daemon.conf The output should be AuditBackend=LinuxAudit Is it the case that AuditBackend is not set to LinuxAudit? |
SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 |
CCI-000169 CCI-000172 |
AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_coredump_disable_backtraces | medium | Disable core dump backtraces | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers or system operators trying to debug problems. Enabling core dumps on production systems is not recommended, however there may be overriding operational requirements to enable advanced debuging. Permitting temporary enablement of core dumps during such situations should be reviewed through local needs and policy. | The ProcessSizeMax option in [Coredump] section
of /etc/systemd/coredump.conf
specifies the maximum size in bytes of a core which will be processed.
Core dumps exceeding this size may be stored, but the backtrace will not
be generated. |
Verify that logging core dump backtraces is disabled, run the following command: $ grep ProcessSizeMax /etc/systemd/coredump.conf Is it the case that ProcessSizeMax is not set to zero? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_coredump_disable_storage | medium | Disable storing core dump | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers or system operators trying to debug problems. Enabling core dumps on production systems is not recommended, however there may be overriding operational requirements to enable advanced debuging. Permitting temporary enablement of core dumps during such situations should be reviewed through local needs and policy. | The Storage option in [Coredump] section
of /etc/systemd/coredump.conf
can be set to none to disable storing core dumps permanently. |
Verify Oracle Linux 8 disables storing core dumps for all users by issuing the following command: $ grep -i storage /etc/systemd/coredump.conf Storage=none Is it the case that Storage is not set to none or is commented out and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_dconf_gnome_banner_enabled | medium | Enable GNOME3 Login Warning Banner | 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.
For U.S. Government systems, system use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist. |
In the default graphical environment, displaying a login warning banner
in the GNOME Display Manager's login screen can be enabled on the login
screen by setting banner-message-enable to true .
To enable, add or edit banner-message-enable to
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/login-screen] banner-message-enable=trueOnce the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/login-screen/banner-message-enableAfter the settings have been set, run dconf update .
The banner text must also be set. |
To ensure a login warning banner is enabled, run the following: $ grep banner-message-enable /etc/dconf/db/local.d/* If properly configured, the output should be true. To ensure a login warning banner is locked and cannot be changed by a user, run the following: $ grep banner-message-enable /etc/dconf/db/local.d/locks/* If properly configured, the output should be /org/gnome/login-screen/banner-message-enable. Is it the case that it is not? |
SRG-OS-000023-GPOS-00006 SRG-OS-000024-GPOS-00007 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 |
CCI-000048 CCI-000050 CCI-001384 CCI-001385 CCI-001386 CCI-001387 CCI-001388 |
AC-8 a AC-8 b AC-8 c AC-8 c AC-8 c AC-8 c AC-8 c |
xccdf_org.ssgproject.content_rule_dconf_gnome_disable_ctrlaltdel_reboot | high | Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3 | A locally logged-in user who presses Ctrl-Alt-Del, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. | By default, GNOME will reboot the system if the
Ctrl-Alt-Del key sequence is pressed.
To configure the system to ignore the Ctrl-Alt-Del key sequence
from the Graphical User Interface (GUI) instead of rebooting the system,
add or set logout to '' in
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/settings-daemon/plugins/media-keys] logout=''Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent
user modification. For example:
/org/gnome/settings-daemon/plugins/media-keys/logoutAfter the settings have been set, run dconf update . |
To ensure the system is configured to ignore the Ctrl-Alt-Del sequence, run the following command: $ gsettings get org.gnome.settings-daemon.plugins.media-keys logout $ grep logout /etc/dconf/db/local.d/locks/* If properly configured, the output should be /org/gnome/settings-daemon/plugins/media-keys/logout Is it the case that GNOME3 is configured to reboot when Ctrl-Alt-Del is pressed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_dconf_gnome_disable_user_list | medium | Disable the GNOME3 Login User List | Leaving the user list enabled is a security risk since it allows anyone with physical access to the system to quickly enumerate known user accounts without logging in. | In the default graphical environment, users logging directly into the
system are greeted with a login screen that displays all known users.
This functionality should be disabled by setting disable-user-list
to true .
To disable, add or edit disable-user-list to
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/login-screen] disable-user-list=trueOnce the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent
user modification. For example:
/org/gnome/login-screen/disable-user-listAfter the settings have been set, run dconf update . |
To ensure the user list is disabled, run the following command: $ grep disable-user-list /etc/dconf/db/local.d/* The output should be true. To ensure that users cannot enable displaying the user list, run the following: $ grep disable-user-list /etc/dconf/db/local.d/locks/* If properly configured, the output should be /org/gnome/login-screen/disable-user-list Is it the case that disable-user-list has not been configured or is not disabled? |
|||
xccdf_org.ssgproject.content_rule_dconf_gnome_lock_screen_on_smartcard_removal | medium | Enable the GNOME3 Screen Locking On Smartcard Removal | Locking the screen automatically when removing the smartcard can prevent undesired access to system. | In the default graphical environment, screen locking on smartcard removal
can be enabled by setting removal-action
to 'lock-screen' .
To enable, add or edit removal-action to
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/settings-daemon/peripherals/smartcard] removal-action='lock-screen'Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/settings-daemon/peripherals/smartcard/removal-actionAfter the settings have been set, run dconf update . |
To ensure screen locking on smartcard removal is enabled, run the following command: $ grep removal-action /etc/dconf/db/local.d/* The output should be 'lock-screen'. To ensure that users cannot disable screen locking on smartcard removal, run the following: $ grep removal-action /etc/dconf/db/local.d/locks/* If properly configured, the output should be /org/gnome/settings-daemon/peripherals/smartcard/removal-action Is it the case that removal-action has not been configured? |
SRG-OS-000028-GPOS-00009 SRG-OS-000030-GPOS-00011 |
CCI-000056 CCI-000058 |
AC-11 b AC-11 a |
xccdf_org.ssgproject.content_rule_dconf_gnome_login_banner_text | medium | Set the GNOME3 Login Warning Banner Text | An appropriate warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. | In the default graphical environment, configuring the login warning banner text
in the GNOME Display Manager's login screen can be configured on the login
screen by setting banner-message-text to 'APPROVED_BANNER'
where APPROVED_BANNER is the approved banner for your environment.
To enable, add or edit banner-message-text to
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/login-screen] banner-message-text='APPROVED_BANNER'Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/login-screen/banner-message-textAfter the settings have been set, run dconf update .
When entering a warning banner that spans several lines, remember
to begin and end the string with ' and use \n for new lines. |
To ensure the login warning banner text is properly set, run the following: $ grep banner-message-text /etc/dconf/db/local.d/* If properly configured, the proper banner text will appear. To ensure the login warning banner text is locked and cannot be changed by a user, run the following: $ grep banner-message-text /etc/dconf/db/local.d/locks/* If properly configured, the output should be /org/gnome/login-screen/banner-message-text. Is it the case that it does not? |
SRG-OS-000023-GPOS-00006 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 |
CCI-000048 CCI-001384 CCI-001385 CCI-001386 CCI-001387 CCI-001388 |
AC-8 a AC-8 c AC-8 c AC-8 c AC-8 c AC-8 c |
xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_idle_delay | medium | Set GNOME3 Screensaver Inactivity Timeout | 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 logout 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, GNOME3 can be configured to identify when a user's session has idled and take action to initiate a session lock. | The idle time-out value for inactivity in the GNOME3 desktop is configured via the idle-delay
setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory
and locked in /etc/dconf/db/local.d/locks directory to prevent user modification.
For example, to configure the system for a 15 minute delay, add the following to /etc/dconf/db/local.d/00-security-settings :
[org/gnome/desktop/session] idle-delay=uint32 900 |
To check the current idle time-out value, run the following command: $ gsettings get org.gnome.desktop.session idle-delay If properly configured, the output should be 'uint32 '. To ensure that users cannot change the screensaver inactivity timeout setting, run the following: $ grep idle-delay /etc/dconf/db/local.d/locks/* If properly configured, the output should be /org/gnome/desktop/session/idle-delay Is it the case that idle-delay is set to 0 or a value greater than <sub idref="inactivity_timeout_value" />? |
SRG-OS-000029-GPOS-00010 SRG-OS-000031-GPOS-00012 |
CCI-000057 CCI-000060 |
AC-11 a AC-11 (1) |
xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_delay | medium | Set GNOME3 Screensaver Lock Delay After Activation Period | 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 logout because of the temporary nature of the absense. | To activate the locking delay of the screensaver in the GNOME3 desktop when
the screensaver is activated, add or set lock-delay to uint32 in
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/desktop/screensaver] lock-delay=uint32After the settings have been set, run dconf update . |
To check that the screen locks immediately when activated, run the following command: $ gsettings get org.gnome.desktop.screensaver lock-delay If properly configured, the output should be 'uint32 '. Is it the case that the screensaver lock delay is missing, or is set to a value greater than <sub idref="var_screensaver_lock_delay" />? |
SRG-OS-000028-GPOS-00009 SRG-OS-000029-GPOS-00010 SRG-OS-000031-GPOS-00012 |
CCI-000056 CCI-000057 CCI-000060 |
AC-11 b AC-11 a AC-11 (1) |
xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_enabled | medium | Enable GNOME3 Screensaver Lock After Idle Period | 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 logout because of the temporary nature of the absense. |
To activate locking of the screensaver in the GNOME3 desktop when it is activated,
add or set lock-enabled to true in
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/desktop/screensaver] lock-enabled=trueOnce the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/screensaver/lock-enabledAfter the settings have been set, run dconf update . |
To check the status of the idle screen lock activation, run the following command: $ gsettings get org.gnome.desktop.screensaver lock-enabled If properly configured, the output should be true. To ensure that users cannot change how long until the screensaver locks, run the following: $ grep lock-enabled /etc/dconf/db/local.d/locks/* If properly configured, the output for lock-enabled should be /org/gnome/desktop/screensaver/lock-enabled Is it the case that screensaver locking is not enabled and/or has not been set or configured correctly? |
SRG-OS-000028-GPOS-00009 SRG-OS-000030-GPOS-00011 SRG-OS-000031-GPOS-00012 |
CCI-000056 CCI-000058 CCI-000060 |
AC-11 b AC-11 a AC-11 (1) |
xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_user_locks | medium | Ensure Users Cannot Change GNOME3 Screensaver Settings | 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 logout 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, GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the session lock. As such, users should not be allowed to change session settings. | If not already configured, ensure that users cannot change GNOME3 screensaver lock settings
by adding /org/gnome/desktop/screensaver/lock-delay
to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/screensaver/lock-delayAfter the settings have been set, run dconf update . |
To ensure that users cannot change session idle and lock settings, run the following: $ grep 'lock-delay' /etc/dconf/db/local.d/locks/* If properly configured, the output should return: /org/gnome/desktop/screensaver/lock-delay Is it the case that GNOME3 session settings are not locked or configured properly? |
SRG-OS-000029-GPOS-00010 SRG-OS-000031-GPOS-00012 |
CCI-000057 CCI-000060 |
AC-11 a AC-11 (1) |
xccdf_org.ssgproject.content_rule_dconf_gnome_session_idle_user_locks | medium | Ensure Users Cannot Change GNOME3 Session Idle Settings | 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 logout 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, GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the session lock. As such, users should not be allowed to change session settings. | If not already configured, ensure that users cannot change GNOME3 session idle settings
by adding /org/gnome/desktop/session/idle-delay
to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/session/idle-delayAfter the settings have been set, run dconf update . |
To ensure that users cannot change session idle and lock settings, run the following: $ grep 'idle-delay' /etc/dconf/db/local.d/locks/* If properly configured, the output should return: /org/gnome/desktop/session/idle-delay Is it the case that idle-delay is not locked? |
SRG-OS-000029-GPOS-00010 SRG-OS-000031-GPOS-00012 |
CCI-000057 CCI-000060 |
AC-11 a AC-11 (1) |
xccdf_org.ssgproject.content_rule_dir_group_ownership_library_dirs | medium | Verify that Shared Library Directories Have Root Group Ownership | Files from shared library directories are loaded into the address space of processes (including privileged ones) or of the kernel itself at runtime. Proper ownership of library directories is necessary to protect the integrity of the system. | System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules . All files in these directories should be
group-owned by the root user. If the directories, is found to be owned
by a user other than root correct its
ownership with the following command:
$ sudo chgrp root DIR |
Verify the system-wide shared library directories are group-owned by "root" with the following command: $ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \; If any system-wide shared library directory is returned and is not group-owned by a required system account, this is a finding. Is it the case that any system-wide shared library directory is returned and is not group-owned by a required system account? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_dir_ownership_library_dirs | medium | Verify that Shared Library Directories Have Root Ownership | Files from shared library directories are loaded into the address space of processes (including privileged ones) or of the kernel itself at runtime. Proper ownership of library directories is necessary to protect the integrity of the system. | System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules . All files in these directories should be
owned by the root user. If the directories, is found to be owned
by a user other than root correct its
ownership with the following command:
$ sudo chown root DIR |
Verify the system-wide shared library directories are owned by "root" with the following command: $ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; Is it the case that any system-wide shared library directory is not owned by root? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_dir_permissions_library_dirs | medium | Verify that Shared Library Directories Have Restrictive Permissions | 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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. | System-wide shared library directories, which contain are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are stored in /lib/modules . All sub-directories in these directories
should not be group-writable or world-writable. If any file in these
directories is found to be group-writable or world-writable, correct
its permission with the following command:
$ sudo chmod go-w DIR |
Shared libraries are stored in the following directories: /lib /lib64 /usr/lib /usr/lib64 To find shared libraries that are group-writable or world-writable, run the following command for each directory DIR which contains shared libraries: $ sudo find -L DIR -perm /022 -type d Is it the case that any of these files are group-writable or world-writable? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_dir_perms_world_writable_sticky_bits | medium | Verify that All World-Writable Directories Have Sticky Bits Set | Failing to set the sticky bit on public directories allows unauthorized
users to delete files in the directory structure.
The only authorized public directories are those temporary directories supplied with the system, or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system, by users for temporary file storage (such as /tmp ), and
for directories requiring global read/write access. |
When the so-called 'sticky bit' is set on a directory,
only the owner of a given file may remove that file from the
directory. Without the sticky bit, any user with write access to a
directory may remove any file in the directory. Setting the sticky
bit prevents users from removing each other's files. In cases where
there is no reason for a directory to be world-writable, a better
solution is to remove that permission rather than to set the sticky
bit. However, if a directory is used by a particular application,
consult that application's documentation instead of blindly
changing modes.
To set the sticky bit on a world-writable directory DIR, run the following command: $ sudo chmod +t DIR |
To find world-writable directories that lack the sticky bit, run the following command: $ sudo find / -type d \( -perm -0002 -a ! -perm -1000 \) -print 2>/dev/null Is it the case that any world-writable directories are missing the sticky bit? |
SRG-OS-000138-GPOS-00069 |
CCI-001090 |
SC-4 |
xccdf_org.ssgproject.content_rule_dir_perms_world_writable_system_owned | medium | Ensure All World-Writable Directories Are Owned by a System Account | Allowing a user account to own a world-writable directory is undesirable because it allows the owner of that directory to remove or replace any files that may be placed in the directory by other users. | All directories in local partitions which are world-writable should be owned by root or another system account. If any world-writable directories are not owned by a system account, this should be investigated. Following this, the files should be deleted or assigned to an appropriate owner. | The following command will discover and print world-writable directories that are not owned by a system account, given the assumption that only system accounts have a uid lower than 500. Run it once for each local partition PART: $ sudo find PART -xdev -type d -perm -0002 -uid +499 -print Is it the case that there is output? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_dir_perms_world_writable_system_owned_group | medium | Ensure All World-Writable Directories Are Group Owned by a System Account | Allowing a user account to group own a world-writable directory is undesirable because it allows the owner of that directory to remove or replace any files that may be placed in the directory by other users. | All directories in local partitions which are world-writable should be group owned by root or another system account. If any world-writable directories are not group owned by a system account, this should be investigated. Following this, the files should be deleted or assigned to an appropriate group. | The following command will discover and print world-writable directories that are not group owned by a system account, given the assumption that only system accounts have a gid lower than 1000. Run it once for each local partition PART: $ sudo find PART -xdev -type d -perm -0002 -gid +999 -print Is it the case that there is output? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_directory_group_ownership_var_log_audit | medium | System Audit Directories Must Be Group Owned By Root | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. | All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/. To properly set the group owner of /var/log/audit , run the command:
$ sudo chgrp root /var/log/audit |
Determine where the audit logs are stored with the following command: $ sudo grep -iw log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log Determine the group owner of the audit log directory by using the output of the above command (default: "/var/log/audit/"). Run the following command with the correct audit log directory path: $ sudo ls -ld /var/log/audit drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit The audit log directory must be group-owned by "root". Is it the case that there is a directory owned by different group? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 SRG-OS-000206-GPOS-00084 |
CCI-000162 CCI-000163 CCI-000164 CCI-001314 |
AU-9 AU-9 AU-9 SI-11 c |
xccdf_org.ssgproject.content_rule_directory_ownership_var_log_audit | medium | System Audit Directories Must Be Owned By Root | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. | All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/. To properly set the owner of /var/log/audit , run the command:
$ sudo chown root /var/log/audit |
Determine where the audit logs are stored with the following command: $ sudo grep -iw log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log Determine the owner of the audit log directory by using the output of the above command (default: "/var/log/audit/"). Run the following command with the correct audit log directory path: $ sudo ls -ld /var/log/audit drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit The audit log directory must be owned by "root" Is it the case that the directory is not owned by root? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 SRG-OS-000206-GPOS-00084 |
CCI-000162 CCI-000163 CCI-000164 CCI-001314 |
AU-9 AU-9 AU-9 SI-11 c |
xccdf_org.ssgproject.content_rule_directory_permissions_var_log_audit | medium | System Audit Logs Must Have Mode 0750 or Less Permissive | If users can write to audit logs, audit trails can be modified or destroyed. |
Verify the audit log directories have a mode of "0700" or less permissive by first determining
where the audit logs are stored with the following command:
$ sudo grep -iw log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.logConfigure the audit log directory to be protected from unauthorized read access by setting the correct permissive mode with the following command: $ sudo chmod 0700 audit_log_directoryBy default, audit_log_directory is "/var/log/audit". |
Verify the audit log directories have a correct mode or less permissive mode. Find the location of the audit logs: $ sudo grep "^log_file" /etc/audit/auditd.conf Run the following command to check the mode of the system audit logs: $ sudo stat -c "%a %n" [audit_log_directory] Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit". The correct permissions are 0700 Is it the case that audit logs have a more permissive mode? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 |
CCI-000162 CCI-000163 CCI-000164 |
AU-9 AU-9 AU-9 |
xccdf_org.ssgproject.content_rule_disable_ctrlaltdel_burstaction | high | Disable Ctrl-Alt-Del Burst Action | A locally logged-in user who presses Ctrl-Alt-Del, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. | By default, SystemD will reboot the system if the Ctrl-Alt-Del
key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
To configure the system to ignore the CtrlAltDelBurstAction
setting, add or modify the following to /etc/systemd/system.conf :
CtrlAltDelBurstAction=none |
To ensure the system is configured to ignore the Ctrl-Alt-Del setting, enter the following command: $ sudo grep -i ctrlaltdelburstaction /etc/systemd/system.conf The output should return: CtrlAltDelBurstAction=none Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed more than 7 times in 2 seconds.? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_disable_ctrlaltdel_reboot | high | Disable Ctrl-Alt-Del Reboot Activation | A locally logged-in user who presses Ctrl-Alt-Del, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. | By default, SystemD will reboot the system if the Ctrl-Alt-Del
key sequence is pressed.
To configure the system to ignore the Ctrl-Alt-Del key sequence from the
command line instead of rebooting the system, do either of the following:
ln -sf /dev/null /etc/systemd/system/ctrl-alt-del.targetor systemctl mask ctrl-alt-del.target Do not simply delete the /usr/lib/systemd/system/ctrl-alt-del.service file,
as this file may be restored during future system updates. |
To ensure the system is configured to mask the Ctrl-Alt-Del sequence, Check that the ctrl-alt-del.target is masked and not active with the following command: sudo systemctl status ctrl-alt-del.target The output should indicate that the target is masked and not active. It might resemble following output: ctrl-alt-del.target Loaded: masked (/dev/null; bad) Active: inactive (dead) Is it the case that the system is configured to reboot when Ctrl-Alt-Del is pressed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_disable_users_coredumps | medium | Disable Core Dumps for All Users | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems. | To disable core dumps for all users, add the following line to
/etc/security/limits.conf , or to a file within the
/etc/security/limits.d/ directory:
* hard core 0 |
Verify that core dumps are disabled for all users, run the following command: $ grep core /etc/security/limits.conf * hard core 0 Is it the case that the "core" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core"? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_disallow_bypass_password_sudo | medium | Disallow Configuration to Bypass Password Requirements for Privilege Escalation | Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate. | Verify the operating system is not configured to bypass password requirements for privilege
escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
$ sudo grep pam_succeed_if /etc/pam.d/sudoIf any occurrences of "pam_succeed_if" is returned from the command, this is a finding. |
Verify the operating system is not configured to bypass password requirements for privilege escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command: $ sudo grep pam_succeed_if /etc/pam.d/sudo Is it the case that system is configured to bypass password requirements for privilege escalation? |
SRG-OS-000373-GPOS-00156 SRG-OS-000373-GPOS-00157 SRG-OS-000373-GPOS-00158 |
CCI-002038 |
|
xccdf_org.ssgproject.content_rule_display_login_attempts | low | Ensure PAM Displays Last Logon/Access Notification | Users need to be aware of activity that occurs regarding their account. Providing users with information regarding the number of unsuccessful attempts that were made to login to their account allows the user to determine if any unauthorized activity has occurred and gives them an opportunity to notify administrators. | To configure the system to notify users of last logon/access
using pam_lastlog , add or correct the pam_lastlog
settings in
/etc/pam.d/postlogin to read as follows:
session required pam_lastlog.so showfailedAnd make sure that the silent option is not set for
pam_lastlog module. |
Verify users are provided with feedback on when account accesses last occurred with the following command: $ sudo grep pam_lastlog /etc/pam.d/postlogin session required pam_lastlog.so showfailed Is it the case that "pam_lastlog" is missing from "/etc/pam.d/postlogin" file, or the silent option is present? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_enable_dracut_fips_module | high | Enable Dracut FIPS Module | 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. | To enable FIPS mode, run the following command:
fips-mode-setup --enableTo enable FIPS, the system requires that the fips module is added in dracut configuration.
Check if /etc/dracut.conf.d/40-fips.conf contain add_dracutmodules+=" fips "
|
To verify that the Dracut FIPS module is enabled, run the following command: grep "add_dracutmodules" /etc/dracut.conf.d/40-fips.conf The output should look like this: add_dracutmodules+=" fips " Is it the case that the Dracut FIPS module is not enabled? |
SRG-OS-000033-GPOS-00014 SRG-OS-000120-GPOS-00061 SRG-OS-000396-GPOS-00176 SRG-OS-000478-GPOS-00223 |
CCI-000068 CCI-000803 CCI-002450 |
AC-17 (2) IA-7 |
xccdf_org.ssgproject.content_rule_enable_fips_mode | high | Enable FIPS Mode | 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. | To enable FIPS mode, run the following command:
fips-mode-setup --enable The fips-mode-setup command will configure the system in
FIPS mode by automatically configuring the following:
|
To verify that FIPS mode is enabled properly, run the following command: fips-mode-setup --check The output should contain the following: FIPS mode is enabled. To verify that the cryptographic policy has been configured correctly, run the following command: $ update-crypto-policies --show The output should return . Is it the case that FIPS mode is not enabled? |
SRG-OS-000033-GPOS-00014 SRG-OS-000120-GPOS-00061 SRG-OS-000396-GPOS-00176 SRG-OS-000478-GPOS-00223 |
CCI-000068 CCI-000803 CCI-002450 |
AC-17 (2) IA-7 |
xccdf_org.ssgproject.content_rule_encrypt_partitions | high | Encrypt Partitions | The risk of a system's physical compromise, particularly mobile systems such as laptops, places its data at risk of compromise. Encrypting this data mitigates the risk of its loss if the system is lost. | Oracle Linux 8 natively supports partition encryption through the
Linux Unified Key Setup-on-disk-format (LUKS) technology. The easiest way to
encrypt a partition is during installation time.
For manual installations, select the Encrypt checkbox during
partition creation to encrypt the partition. When this
option is selected the system will prompt for a passphrase to use in
decrypting the partition. The passphrase will subsequently need to be entered manually
every time the system boots.
For automated/unattended installations, it is possible to use Kickstart by adding the --encrypted and --passphrase= options to the definition of each partition to be
encrypted. For example, the following line would encrypt the root partition:
part / --fstype=ext4 --size=100 --onpart=hda1 --encrypted --passphrase=PASSPHRASEAny PASSPHRASE is stored in the Kickstart in plaintext, and the Kickstart must then be protected accordingly. Omitting the --passphrase= option from the partition definition will cause the
installer to pause and interactively ask for the passphrase during installation.
By default, the Anaconda installer uses aes-xts-plain64 cipher
with a minimum 512 bit key size which should be compatible with FIPS enabled.
Detailed information on encrypting partitions using LUKS or LUKS ciphers can be found on the Oracle Linux 8 Documentation web site: https://docs.oracle.com/en/operating-systems/oracle-linux/8/install/install-InstallingOracleLinuxManually.html#install-storage-network . |
Check the system partitions to determine if they are encrypted with the following command: blkid Output will be similar to: /dev/sda1: UUID=" ab12c3de-4f56-789a-8f33-3850cc8ce3a2 " TYPE="crypto_LUKS" /dev/sda2: UUID=" bc98d7ef-6g54-321h-1d24-9870de2ge1a2 " TYPE="crypto_LUKS" The boot partition and pseudo-file systems, such as /proc, /sys, and tmpfs, are not required to use disk encryption and are not a finding. Is it the case that partitions do not have a type of crypto_LUKS? |
SRG-OS-000185-GPOS-00079 SRG-OS-000404-GPOS-00183 SRG-OS-000405-GPOS-00184 |
CCI-001199 CCI-002475 CCI-002476 |
SC-28 |
xccdf_org.ssgproject.content_rule_ensure_gpgcheck_globally_activated | high | Ensure gpgcheck Enabled In Main yum Configuration | 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. Certificates used to verify the software must be from an approved Certificate Authority (CA). |
The gpgcheck option controls whether
RPM packages' signatures are always checked prior to installation.
To configure yum to check package signatures before installing
them, ensure the following line appears in /etc/yum.conf in
the [main] section:
gpgcheck=1 |
To determine whether yum is configured to use gpgcheck, inspect /etc/yum.conf and ensure the following appears in the [main] section: gpgcheck=1 A value of 1 indicates that gpgcheck is enabled. Absence of a gpgcheck line or a setting of 0 indicates that it is disabled. Is it the case that GPG checking is not enabled? |
SRG-OS-000366-GPOS-00153 |
CCI-001749 |
|
xccdf_org.ssgproject.content_rule_ensure_gpgcheck_local_packages | high | Ensure gpgcheck Enabled for Local Packages | Changes to any software components can have significant effects to the overall security
of the operating system. This requirement ensures the software has not been tampered and
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. |
yum should be configured to verify the signature(s) of local packages
prior to installation. To configure yum to verify signatures of local
packages, set the localpkg_gpgcheck to 1 in /etc/yum.conf . |
To verify that localpkg_gpgcheck is configured properly, run the following command: $ grep localpkg_gpgcheck /etc/yum.conf The output should return something similar to: localpkg_gpgcheck=1 Is it the case that gpgcheck is not enabled or configured correctly to verify local packages? |
SRG-OS-000366-GPOS-00153 |
CCI-001749 |
|
xccdf_org.ssgproject.content_rule_ensure_gpgcheck_never_disabled | high | Ensure gpgcheck Enabled for All yum Package Repositories | 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. Certificates used to verify the software must be from an approved Certificate Authority (CA)." | To ensure signature checking is not disabled for
any repos, remove any lines from files in /etc/yum.repos.d of the form:
gpgcheck=0 |
To determine whether yum has been configured to disable gpgcheck for any repos, inspect all files in /etc/yum.repos.d and ensure the following does not appear in any sections: gpgcheck=0 A value of 0 indicates that gpgcheck has been disabled for that repo. Is it the case that GPG checking is disabled? |
SRG-OS-000366-GPOS-00153 |
CCI-001749 |
|
xccdf_org.ssgproject.content_rule_fapolicy_default_deny | medium | Configure Fapolicy Module to Employ a Deny-all, Permit-by-exception Policy to Allow the Execution of Authorized Software Programs. | Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. Verification of whitelisted software occurs prior to execution or at system startup. Proceed with caution with enforcing the use of this daemon. Improper configuration may render the system non-functional. The "fapolicyd" API is not namespace aware and can cause issues when launching or running containers. | The Fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and to prevent unauthorized software from running. | Verify the Oracle Linux 8 "fapolicyd" employs a deny-all, permit-by-exception policy. Check that "fapolicyd" is in enforcement mode with the following command: $ sudo grep permissive /etc/fapolicyd/fapolicyd.conf permissive = 0 Check that fapolicyd employs a deny-all policy on system mounts with the following command: $ sudo tail /etc/fapolicyd/fapolicyd.rules allow exe=/usr/bin/python3.7 : ftype=text/x-python deny_audit perm=any pattern=ld_so : all deny perm=any all : all Is it the case that fapolicyd is not running in enforcement mode with a deny-all, permit-by-exception policy? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_file_audit_tools_group_ownership | medium | Audit Tools Must Be Group-owned by Root | 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 operations on audit information. | Oracle Linux 8 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, 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. Audit tools must have the correct group owner. | Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification. Check the group-owner of each audit tool by running the following command: $ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules root /sbin/auditctl root /sbin/aureport root /sbin/ausearch root /sbin/autrace root /sbin/auditd root /sbin/rsyslogd root /sbin/augenrules Is it the case that any audit tools are not group-owned by root? |
SRG-OS-000256-GPOS-00097 SRG-OS-000257-GPOS-00098 SRG-OS-000258-GPOS-00099 |
CCI-001493 CCI-001494 CCI-001495 |
AU-9 AU-9 AU-9 |
xccdf_org.ssgproject.content_rule_file_audit_tools_ownership | medium | Audit Tools Must Be Owned by Root | 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 operations on audit information. | Oracle Linux 8 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, 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. Audit tools must have the correct owner. | Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification. Check the owner of each audit tool by running the following command: $ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules root /sbin/auditctl root /sbin/aureport root /sbin/ausearch root /sbin/autrace root /sbin/auditd root /sbin/rsyslogd root /sbin/augenrules Is it the case that any audit tools are not owned by root? |
SRG-OS-000256-GPOS-00097 SRG-OS-000257-GPOS-00098 SRG-OS-000258-GPOS-00099 |
CCI-001493 CCI-001494 CCI-001495 |
AU-9 AU-9 AU-9 |
xccdf_org.ssgproject.content_rule_file_audit_tools_permissions | medium | Audit Tools Must Have a Mode of 0755 or Less Permissive | 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 operations on audit information. | Oracle Linux 8 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, 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. Audit tools must have a mode of 0755 or less permissive. | Verify the audit tools are protected from unauthorized access, deletion, or modification by checking the permissive mode. Check the octal permission of each audit tool by running the following command: $ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules Is it the case that any of these files have more permissive permissions than 0755? |
SRG-OS-000256-GPOS-00097 |
CCI-001493 |
AU-9 |
xccdf_org.ssgproject.content_rule_file_group_ownership_var_log_audit | medium | System Audit Logs Must Be Group Owned By Root | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. | All audit logs must be group owned by root user. The path for audit log can
be configured via log_file parameter in /etc/audit/auditd.confor, by default, the path for audit log is /var/log/audit/. To properly set the group owner of /var/log/audit/* , run the command:
$ sudo chgrp root /var/log/audit/* |
Check group owners of the system audit logs. First, determine where the audit log file is located. $ sudo grep -iw ^log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log The log_file option specifies the audit log file path. If the log_file option isn't defined, check all files within /var/log/audit directory. Then, check that the audit log file is owned by the correct group. Run the following command to display the owner of the audit log file: $ sudo stat -c "%n %G" log_file The audit log file must be owned by root Is it the case that audit log files are owned by incorrect group? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 SRG-OS-000206-GPOS-00084 |
CCI-000162 CCI-000163 CCI-000164 CCI-001314 |
AU-9 AU-9 AU-9 SI-11 c |
xccdf_org.ssgproject.content_rule_file_groupowner_var_log | medium | Verify Group Who Owns /var/log Directory | The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel. |
To properly set the group owner of /var/log , run the command: $ sudo chgrp root /var/log |
To check the group ownership of /var/log, run the command: $ ls -lL /var/log If properly configured, the output should indicate the following group-owner: root Is it the case that /var/log does not have a group owner of root? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_groupowner_var_log_messages | medium | Verify Group Who Owns /var/log/messages File | The /var/log/messages file contains logs of error messages in
the system and should only be accessed by authorized personnel. |
To properly set the group owner of /var/log/messages , run the command: $ sudo chgrp root /var/log/messages |
To check the group ownership of /var/log/messages, run the command: $ ls -lL /var/log/messages If properly configured, the output should indicate the following group-owner: root Is it the case that /var/log/messages does not have a group owner of root? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_groupownership_home_directories | medium | All Interactive User Home Directories Must Be Group-Owned By The Primary User | If the Group Identifier (GID) of a local interactive users home directory is not the same as the primary GID of the user, this would allow unauthorized access to the users files, and users that share the same group may not be able to access files that they legitimately should. | Change the group owner of interactive users home directory to the
group found in /etc/passwd . To change the group owner of
interactive users home directory, use the following command:
$ sudo chgrp USER_GROUP /home/USERThis rule ensures every home directory related to an interactive user is group-owned by an interactive user. It also ensures that interactive users are group-owners of one and only one home directory. |
To verify the assigned home directory of all interactive users is group- owned by that users primary GID, run the following command: # ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) Is it the case that the group ownership is incorrect? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_file_groupownership_lastlog | medium | Verify Group Who Owns lastlog Command | Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to attackers, thus compromising its confidentiality. |
To properly set the group owner of /var/log/lastlog , run the command:
$ sudo chgrp root /var/log/lastlog |
To check the group ownership of /var/log/lastlog, run the command: $ ls -lL /var/log/lastlog If properly configured, the output should indicate the following group-owner: root Is it the case that /var/log/lastlog does not have a group owner of root? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_groupownership_system_commands_dirs | medium | Verify that system commands files are group owned by root or a system account | If the operating system allows 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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. | System commands files are stored in the following directories by default:
/bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbinAll files in these directories should be owned by the root group,
or a system account.
If the directory, or any file in these directories, is found to be owned
by a group other than root or a a system account correct its ownership
with the following command:
$ sudo chgrp root FILE |
Verify the system commands contained in the following directories are group-owned by "root", or a required system account, with the following command: $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -exec ls -l {} \; Is it the case that any system commands are returned and is not group-owned by a required system account? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_file_owner_var_log | medium | Verify User Who Owns /var/log Directory | The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel. |
To properly set the owner of /var/log , run the command: $ sudo chown root /var/log |
To check the ownership of /var/log, run the command: $ ls -lL /var/log If properly configured, the output should indicate the following owner: root Is it the case that /var/log does not have an owner of root? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_owner_var_log_messages | medium | Verify User Who Owns /var/log/messages File | The /var/log/messages file contains logs of error messages in
the system and should only be accessed by authorized personnel. |
To properly set the owner of /var/log/messages , run the command: $ sudo chown root /var/log/messages |
To check the ownership of /var/log/messages, run the command: $ ls -lL /var/log/messages If properly configured, the output should indicate the following owner: root Is it the case that /var/log/messages does not have an owner of root? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_ownership_binary_dirs | medium | Verify that System Executables Have Root Ownership | System binaries are executed by privileged users as well as system services, and restrictive permissions are necessary to ensure that their execution of these programs cannot be co-opted. | System executables are stored in the following directories by default:
/bin /sbin /usr/bin /usr/libexec /usr/local/bin /usr/local/sbin /usr/sbinAll files in these directories should be owned by the root user.
If any file FILE in these directories is found
to be owned by a user other than root, correct its ownership with the
following command:
$ sudo chown root FILE |
Verify the system commands contained in the following directories are owned by "root" with the following command: $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/libexec /usr/local/bin /usr/local/sbin ! -user root -exec ls -l {} \; Is it the case that any system commands are found to not be owned by root? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_file_ownership_lastlog | medium | Verify Owner on lastlog Command | Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to attackers, thus compromising its confidentiality. |
To properly set the owner of /usr/bin/lastlog , run the command:
$ sudo chown root /usr/bin/lastlog |
To check the ownership of /usr/bin/lastlog, run the command: $ ls -lL /usr/bin/lastlog If properly configured, the output should indicate the following owner: root Is it the case that /usr/bin/lastlog does not have an owner of root? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_ownership_library_dirs | medium | Verify that Shared Library Files Have Root Ownership | Files from shared library directories are loaded into the address space of processes (including privileged ones) or of the kernel itself at runtime. Proper ownership is necessary to protect the integrity of the system. | System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules . All files in these directories should be
owned by the root user. If the directory, or any file in these
directories, is found to be owned by a user other than root correct its
ownership with the following command:
$ sudo chown root FILE |
Verify the system-wide shared library files are owned by "root" with the following command: $ sudo find -L /lib /lib64 /usr/lib /usr/lib64 ! -user root -exec ls -l {} \; Is it the case that any system wide shared library file is not owned by root? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_file_ownership_var_log_audit_stig | medium | System Audit Logs Must Be Owned By Root | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. | All audit logs must be owned by root user. The path for audit log can be
configured via log_file parameter in /etc/audit/auditd.confor by default, the path for audit log is /var/log/audit/. To properly set the owner of /var/log/audit/* , run the command:
$ sudo chown root /var/log/audit/* |
Verify the audit logs are owned by "root". First, determine where the audit logs are stored with the following command: $ sudo grep -iw log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log Using the location of the audit log file, determine if the audit log is owned by "root" using the following command: $ sudo stat -c "%n %U" /var/log/audit/audit.log Audit logs must be owned by user root. If the log_file isn't defined in /etc/audit/auditd.conf, check all files in /var/log/audit/ directory instead. Is it the case that the audit log is not owned by root? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 SRG-OS-000206-GPOS-00084 |
CCI-000162 CCI-000163 CCI-000164 CCI-001314 |
AU-9 AU-9 AU-9 SI-11 c |
xccdf_org.ssgproject.content_rule_file_permission_user_init_files | medium | Ensure All User Initialization Files Have Mode 0740 Or Less Permissive | Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon. | Set the mode of the user initialization files to 0740 with the
following command:
$ sudo chmod 0740 /home/USER/.INIT_FILE |
To verify that all user initialization files have a mode of 0740 or less permissive, run the following command: $ sudo find /home -type f -name '\.*' \( -perm -0002 -o -perm -0020 \) There should be no output. Is it the case that they are not 0740 or more permissive? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_file_permissions_binary_dirs | medium | Verify that System Executables Have Restrictive Permissions | System binaries are executed by privileged users, as well as system services, and restrictive permissions are necessary to ensure execution of these programs cannot be co-opted. | System executables are stored in the following directories by default:
/bin /sbin /usr/bin /usr/libexec /usr/local/bin /usr/local/sbin /usr/sbinAll files in these directories should not be group-writable or world-writable. If any file FILE in these directories is found to be group-writable or world-writable, correct its permission with the following command: $ sudo chmod go-w FILE |
Verify the system commands contained in the following directories have mode "755" or less permissive with the following command: $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/libexec /usr/local/bin /usr/local/sbin -perm /022 -exec ls -l {} \; Is it the case that any system commands are found to be group-writable or world-writable? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_file_permissions_etc_audit_auditd | medium | Verify Permissions on /etc/audit/auditd.conf | Without the capability to restrict the roles and individuals that 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. |
To properly set the permissions of /etc/audit/auditd.conf , run the command:
$ sudo chmod 0640 /etc/audit/auditd.conf |
To check the permissions of /etc/audit/auditd.conf, run the command: $ ls -l /etc/audit/auditd.conf If properly configured, the output should indicate the following permissions: -rw-r----- Is it the case that /etc/audit/auditd.conf does not have unix mode -rw-r-----? |
SRG-OS-000063-GPOS-00032 |
CCI-000171 |
AU-12 b |
xccdf_org.ssgproject.content_rule_file_permissions_etc_audit_rulesd | medium | Verify Permissions on /etc/audit/rules.d/*.rules | Without the capability to restrict the roles and individuals that 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. |
To properly set the permissions of /etc/audit/rules.d/*.rules , run the command:
$ sudo chmod 0640 /etc/audit/rules.d/*.rules |
To check the permissions of /etc/audit/rules.d/*.rules, run the command: $ ls -l /etc/audit/rules.d/*.rules If properly configured, the output should indicate the following permissions: -rw-r----- Is it the case that /etc/audit/rules.d/*.rules does not have unix mode -rw-r-----? |
SRG-OS-000063-GPOS-00032 |
CCI-000171 |
AU-12 b |
xccdf_org.ssgproject.content_rule_file_permissions_home_directories | medium | All Interactive User Home Directories Must Have mode 0750 Or Less Permissive | Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users. | Change the mode of interactive users home directories to 0750 . To
change the mode of interactive users home directory, use the
following command:
$ sudo chmod 0750 /home/USER |
To verify the assigned home directory of all interactive user home directories have a mode of 0750 or less permissive, run the following command: $ sudo ls -l /home Inspect the output for any directories with incorrect permissions. Is it the case that they are more permissive? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_file_permissions_lastlog | medium | Verify Permissions on lastlog Command | Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to attackers, thus compromising its confidentiality. |
To properly set the permissions of /usr/bin/lastlog , run the command:
$ sudo chmod 0750 /usr/bin/lastlog |
To check the permissions of /usr/bin/lastlog, run the command: $ ls -l /usr/bin/lastlog If properly configured, the output should indicate the following permissions: -rwxr-x--- Is it the case that /usr/bin/lastlog does not have unix mode -rwxr-x---? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_permissions_library_dirs | medium | Verify that Shared Library Files Have Restrictive Permissions | Files from shared library directories are loaded into the address space of processes (including privileged ones) or of the kernel itself at runtime. Restrictive permissions are necessary to protect the integrity of the system. | System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are stored in /lib/modules . All files in these directories
should not be group-writable or world-writable. If any file in these
directories is found to be group-writable or world-writable, correct
its permission with the following command:
$ sudo chmod go-w FILE |
Verify the system-wide shared library files contained in the following directories have mode "755" or less permissive with the following command: $ sudo find -L /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type f -exec ls -l {} \; Is it the case that any system-wide shared library file is found to be group-writable or world-writable? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_file_permissions_sshd_private_key | medium | Verify Permissions on SSH Server Private *_key Key Files | If an unauthorized user obtains the private SSH host key file, the host could be impersonated. | SSH server private keys - files that match the /etc/ssh/*_key glob, have to have restricted permissions.
If those files are owned by the root user and the root group, they have to have the 0600 permission or stricter. |
To check the permissions of /etc/ssh/*_key, run the command: $ ls -l /etc/ssh/*_key If properly configured, the output should indicate the following permissions: -rw------- Is it the case that /etc/ssh/*_key does not have unix mode -rw-------? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_file_permissions_sshd_pub_key | medium | Verify Permissions on SSH Server Public *.pub Key Files | If a public host key file is modified by an unauthorized user, the SSH service may be compromised. | To properly set the permissions of /etc/ssh/*.pub , run the command: $ sudo chmod 0644 /etc/ssh/*.pub |
To check the permissions of /etc/ssh/*.pub, run the command: $ ls -l /etc/ssh/*.pub If properly configured, the output should indicate the following permissions: -rw-r--r-- Is it the case that /etc/ssh/*.pub does not have unix mode -rw-r--r--? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_file_permissions_ungroupowned | medium | Ensure All Files Are Owned by a Group | Unowned files do not directly imply a security problem, but they are generally a sign that something is amiss. They may be caused by an intruder, by incorrect software installation or draft software removal, or by failure to remove all files belonging to a deleted account. The files should be repaired so they will not cause problems when accounts are created in the future, and the cause should be discovered and addressed. | If any files are not owned by a group, then the
cause of their lack of group-ownership should be investigated.
Following this, the files should be deleted or assigned to an
appropriate group. The following command will discover and print
any files on local partitions which do not belong to a valid group:
$ df --local -P | awk '{if (NR!=1) print $6}' | sudo xargs -I '{}' find '{}' -xdev -nogroupTo search all filesystems on a system including network mounted filesystems the following command can be run manually for each partition: $ sudo find PARTITION -xdev -nogroup |
The following command will discover and print any files on local partitions which do not belong to a valid group. $ df --local -P | awk '{if (NR!=1) print $6}' | sudo xargs -I '{}' find '{}' -xdev -nogroup Either remove all files and directories from the system that do not have a valid group, or assign a valid group with the chgrp command: $ sudo chgrp group file Is it the case that there is output? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 |
CCI-000366 CCI-002165 |
CM-6 b |
xccdf_org.ssgproject.content_rule_file_permissions_var_log | medium | Verify Permissions on /var/log Directory | The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel. |
To properly set the permissions of /var/log , run the command:
$ sudo chmod 0755 /var/log |
To check the permissions of /var/log, run the command: $ ls -l /var/log If properly configured, the output should indicate the following permissions: drwxr-xr-x Is it the case that /var/log does not have unix mode drwxr-xr-x? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_file_permissions_var_log_audit | medium | System Audit Logs Must Have Mode 0640 or Less Permissive | If users can write to audit logs, audit trails can be modified or destroyed. |
Determine where the audit logs are stored with the following command:
$ sudo grep -iw log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.logConfigure the audit log to be protected from unauthorized read access by setting the correct permissive mode with the following command: $ sudo chmod 0600 audit_log_fileBy default, audit_log_file is "/var/log/audit/audit.log". |
Run the following command to check the mode of the system audit logs: $ sudo grep -iw log_file /etc/audit/auditd.conf log_file=/var/log/audit/audit.log $ sudo stat -c "%n %a" /var/log/audit/* $ sudo ls -l /var/log/audit Audit logs must be mode 0640 or less permissive. Is it the case that any permissions are more permissive? |
SRG-OS-000057-GPOS-00027 SRG-OS-000058-GPOS-00028 SRG-OS-000059-GPOS-00029 SRG-OS-000206-GPOS-00084 |
CCI-000162 CCI-000163 CCI-000164 CCI-001314 |
AU-9 AU-9 AU-9 SI-11 c |
xccdf_org.ssgproject.content_rule_file_permissions_var_log_messages | medium | Verify Permissions on /var/log/messages File | The /var/log/messages file contains logs of error messages in
the system and should only be accessed by authorized personnel. |
To properly set the permissions of /var/log/messages , run the command:
$ sudo chmod 0640 /var/log/messages |
To check the permissions of /var/log/messages, run the command: $ ls -l /var/log/messages If properly configured, the output should indicate the following permissions: -rw-r----- Is it the case that /var/log/messages does not have unix mode -rw-r-----? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
xccdf_org.ssgproject.content_rule_firewalld-backend | medium | Configure Firewalld to Use the Nftables Backend | Nftables is modern kernel module for controling network connections coming into a system. Utilizing the limit statement in "nftables" can help to mitigate DoS attacks. | Firewalld can be configured with many backends, such as nftables. | Verify "nftables" is configured to allow rate limits on any connection to the system with the following command: Verify "firewalld" has "nftables" set as the default backend: $ sudo grep -i firewallbackend /etc/firewalld/firewalld.conf # FirewallBackend FirewallBackend=nftables Is it the case that the "nftables" is not set as the "firewallbackend"? |
SRG-OS-000420-GPOS-00186 |
CCI-002385 |
|
xccdf_org.ssgproject.content_rule_gnome_gdm_disable_automatic_login | high | Disable GDM Automatic Login | Failure to restrict system access to authenticated users negatively impacts operating system security. | The GNOME Display Manager (GDM) can allow users to automatically login without
user interaction or credentials. User should always be required to authenticate themselves
to the system that they are authorized to use. To disable user ability to automatically
login to the system, set the AutomaticLoginEnable to false in the
[daemon] section in /etc/gdm/custom.conf . For example:
[daemon] AutomaticLoginEnable=false |
To verify that automatic logins are disabled, run the following command: $ grep -Pzoi "^\[daemon]\\nautomaticlogin.*" /etc/gdm/custom.conf The output should show the following: [daemon] AutomaticLoginEnable=false Is it the case that GDM allows users to automatically login? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_grub2_admin_username | medium | Set the Boot Loader Admin Username to a Non-Default Value | Having a non-default grub superuser username makes password-guessing attacks less effective. | The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
To maximize the protection, select a password-protected superuser account with unique name, and modify the /etc/grub.d/01_users configuration file to reflect the account name change.
Do not to use common administrator account names like root, admin, or administrator for the grub2 superuser account. Change the superuser to a different username (The default is 'root'). $ sed -i 's/\(set superuser=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users Once the superuser account has been added, update the grub.cfg file by running:
grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
To verify the boot loader superuser account has been set, run the following command: sudo grep -A1 "superusers" /boot/grub2/grub.cfg The output should show the following: set superusers="superusers-account" export superusers where superusers-account is the actual account name different from common names like root, admin, or administrator and different from any other existing user name. Is it the case that superuser account is not set or is set to root, admin, administrator or any other existing user name? |
SRG-OS-000080-GPOS-00048 |
CCI-000213 |
AC-3 |
xccdf_org.ssgproject.content_rule_grub2_audit_argument | medium | Enable Auditing for Processes Which Start Prior to the Audit Daemon | Each process on the system carries an "auditable" flag which indicates whether
its activities can be audited. Although auditd takes care of enabling
this for all processes which launch after it does, adding the kernel argument
ensures it is set for every process during boot. |
To ensure all processes can be audited, even those which start
prior to the audit daemon, add the argument audit=1 to the default
GRUB 2 command line for the Linux operating system.
To ensure that audit=1 is added as a kernel command line
argument to newly installed kernels, add audit=1 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... audit=1 ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="audit=1" |
Inspect the form of default GRUB 2 command line for the Linux operating system in /etc/default/grub. If it includes audit=1, then the parameter will be configured for newly installed kernels. First check if the GRUB recovery is enabled: $ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub If this option is set to true, then check that a line is output by the following command: $ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit=1.*' /etc/default/grub If the recovery is disabled, check the line with $ sudo grep 'GRUB_CMDLINE_LINUX.*audit=1.*' /etc/default/grub.Moreover, command line parameters for currently installed kernels should be checked as well. Run the following command: $ sudo grubby --info=ALL | grep args | grep -v 'audit=1' The command should not return any output. Is it the case that auditing is not enabled at boot time? |
SRG-OS-000254-GPOS-00095 SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000392-GPOS-00172 |
CCI-001464 CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-002884 |
AU-14 (1) AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_grub2_audit_backlog_limit_argument | low | Extend Audit Backlog Limit for the Audit Daemon | audit_backlog_limit sets the queue length for audit events awaiting transfer to the audit daemon. Until the audit daemon is up and running, all log messages are stored in this queue. If the queue is overrun during boot process, the action defined by audit failure flag is taken. | To improve the kernel capacity to queue all log events, even those which occurred
prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
GRUB 2 command line for the Linux operating system.
To ensure that audit_backlog_limit=8192 is added as a kernel command line
argument to newly installed kernels, add audit_backlog_limit=8192 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="audit_backlog_limit=8192" |
Inspect the form of default GRUB 2 command line for the Linux operating system in /etc/default/grub. If it includes audit_backlog_limit=8192, then the parameter will be configured for newly installed kernels. First check if the GRUB recovery is enabled: $ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub If this option is set to true, then check that a line is output by the following command: $ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*audit_backlog_limit=8192.*' /etc/default/grub If the recovery is disabled, check the line with $ sudo grep 'GRUB_CMDLINE_LINUX.*audit_backlog_limit=8192.*' /etc/default/grub.Moreover, command line parameters for currently installed kernels should be checked as well. Run the following command: $ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192' The command should not return any output. Is it the case that audit backlog limit is not configured? |
SRG-OS-000037-GPOS-00015 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000062-GPOS-00031 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000341-GPOS-00132 SRG-OS-000392-GPOS-00172 |
CCI-000130 CCI-000135 CCI-000169 CCI-000172 CCI-001849 CCI-002884 |
AU-3 AU-3 (1) AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_grub2_mitigation_argument | medium | System Must Avoid Meltdown and Spectre Exploit Vulnerabilities in Modern Processors | Hardware vulnerabilities allow programs to steal data that is currently processed on the computer. While programs are typically not permitted to read data from other programs, a malicious program can exploit Meltdown and Spectre to obtain secrets stored in the memory of other running programs. This might include passwords stored in a password manager or browser; personal photos, emails, and instant messages; and business-critical documents. | Determine the default kernel:
$ sudo grubby --default-kernel /boot/vmlinuz-5.4.17-2011.1.2.el8uek.x86_64Using the default kernel, verify that Meltdown mitigations are not disabled: $ sudo grubby --info=path-to-default-kernel | grep mitigationThe mitigation must be set to "on". |
Inspect the form of default GRUB 2 command line for the Linux operating system in /etc/default/grub. If it includes mitigation=on, then the parameter will be configured for newly installed kernels. First check if the GRUB recovery is enabled: $ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub If this option is set to true, then check that a line is output by the following command: $ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*mitigation=on.*' /etc/default/grub If the recovery is disabled, check the line with $ sudo grep 'GRUB_CMDLINE_LINUX.*mitigation=on.*' /etc/default/grub.Moreover, command line parameters for currently installed kernels should be checked as well. Run the following command: $ sudo grubby --info=ALL | grep args | grep -v 'mitigation=on' The command should not return any output. Is it the case that mitigation is not set to on? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_grub2_page_poison_argument | medium | Enable page allocator poisoning | Poisoning writes an arbitrary value to freed pages, so any modification or reference to that page after being freed or before being initialized will be detected and prevented. This prevents many types of use-after-free vulnerabilities at little performance cost. Also prevents leak of data and detection of corrupted memory. | To enable poisoning of free pages,
add the argument page_poison=1 to the default
GRUB 2 command line for the Linux operating system.
To ensure that page_poison=1 is added as a kernel command line
argument to newly installed kernels, add page_poison=1 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... page_poison=1 ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="page_poison=1" |
Inspect the form of default GRUB 2 command line for the Linux operating system in /etc/default/grub. If it includes page_poison=1, then the parameter will be configured for newly installed kernels. First check if the GRUB recovery is enabled: $ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub If this option is set to true, then check that a line is output by the following command: $ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*page_poison=1.*' /etc/default/grub If the recovery is disabled, check the line with $ sudo grep 'GRUB_CMDLINE_LINUX.*page_poison=1.*' /etc/default/grub.Moreover, command line parameters for currently installed kernels should be checked as well. Run the following command: $ sudo grubby --info=ALL | grep args | grep -v 'page_poison=1' The command should not return any output. Is it the case that page allocator poisoning is not enabled? |
SRG-OS-000134-GPOS-00068 |
CCI-001084 |
SC-3 |
xccdf_org.ssgproject.content_rule_grub2_password | high | Set Boot Loader Password in grub2 | Password protection on the boot loader configuration ensures users with physical access cannot trivially alter important bootloader settings. These include which kernel to use, and whether to enter single-user mode. | The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
Since plaintext passwords are a security risk, generate a hash for the password by running the following command: # grub2-setpasswordWhen prompted, enter the password that was selected. |
First, check whether the password is defined in either /boot/grub2/user.cfg or /boot/grub2/grub.cfg. Run the following commands: $ sudo grep '^[\s]*GRUB2_PASSWORD=grub\.pbkdf2\.sha512.*$' /boot/grub2/user.cfg $ sudo grep '^[\s]*password_pbkdf2[\s]+.*[\s]+grub\.pbkdf2\.sha512.*$' /boot/grub2/grub.cfg Second, check that a superuser is defined in /boot/grub2/grub.cfg. $ sudo grep '^[\s]*set[\s]+superusers=("?)[a-zA-Z_]+\1$' /boot/grub2/grub.cfg Is it the case that it does not produce any output? |
SRG-OS-000080-GPOS-00048 |
CCI-000213 |
AC-3 |
xccdf_org.ssgproject.content_rule_grub2_pti_argument | low | Enable Kernel Page-Table Isolation (KPTI) | Kernel page-table isolation is a kernel feature that mitigates the Meltdown security vulnerability and hardens the kernel against attempts to bypass kernel address space layout randomization (KASLR). | To enable Kernel page-table isolation,
add the argument pti=on to the default
GRUB 2 command line for the Linux operating system.
To ensure that pti=on is added as a kernel command line
argument to newly installed kernels, add pti=on to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... pti=on ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="pti=on" |
Inspect the form of default GRUB 2 command line for the Linux operating system in /etc/default/grub. If it includes pti=on, then the parameter will be configured for newly installed kernels. First check if the GRUB recovery is enabled: $ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub If this option is set to true, then check that a line is output by the following command: $ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*pti=on.*' /etc/default/grub If the recovery is disabled, check the line with $ sudo grep 'GRUB_CMDLINE_LINUX.*pti=on.*' /etc/default/grub.Moreover, command line parameters for currently installed kernels should be checked as well. Run the following command: $ sudo grubby --info=ALL | grep args | grep -v 'pti=on' The command should not return any output. Is it the case that Kernel page-table isolation is not enabled? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_grub2_slub_debug_argument | medium | Enable SLUB/SLAB allocator poisoning | Poisoning writes an arbitrary value to freed objects, so any modification or reference to that object after being freed or before being initialized will be detected and prevented. This prevents many types of use-after-free vulnerabilities at little performance cost. Also prevents leak of data and detection of corrupted memory. | To enable poisoning of SLUB/SLAB objects,
add the argument slub_debug= to the default
GRUB 2 command line for the Linux operating system.
To ensure that slub_debug= is added as a kernel command line
argument to newly installed kernels, add slub_debug= to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... slub_debug= ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="slub_debug=" |
Inspect the form of default GRUB 2 command line for the Linux operating system in /etc/default/grub. If it includes slub_debug=, then the parameter will be configured for newly installed kernels. First check if the GRUB recovery is enabled: $ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub If this option is set to true, then check that a line is output by the following command: $ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*slub_debug=.*' /etc/default/grub If the recovery is disabled, check the line with $ sudo grep 'GRUB_CMDLINE_LINUX.*slub_debug=.*' /etc/default/grub.Moreover, command line parameters for currently installed kernels should be checked as well. Run the following command: $ sudo grubby --info=ALL | grep args | grep -v 'slub_debug=' The command should not return any output. Is it the case that SLUB/SLAB poisoning is not enabled? |
SRG-OS-000134-GPOS-00068 |
CCI-001084 |
SC-3 |
xccdf_org.ssgproject.content_rule_grub2_uefi_admin_username | medium | Set the UEFI Boot Loader Admin Username to a Non-Default Value | Having a non-default grub superuser username makes password-guessing attacks less effective. | The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
To maximize the protection, select a password-protected superuser account with unique name, and modify the /etc/grub.d/01_users configuration file to reflect the account name change.
It is highly suggested not to use common administrator account names like root, admin, or administrator for the grub2 superuser account. Change the superuser to a different username (The default is 'root'). $ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users Once the superuser account has been added, update the grub.cfg file by running:
grubby --update-kernel=ALL --env=/boot/grub2/grubenv |
To verify the boot loader superuser account has been set, run the following command: sudo grep -A1 "superusers" /boot/efi/EFI/redhat/grub.cfg The output should show the following: set superusers="superusers-account" export superusers where superusers-account is the actual account name different from common names like root, admin, or administrator and different from any other existing user name. Is it the case that superuser account is not set or is set to an existing name or to a common name? |
SRG-OS-000080-GPOS-00048 |
CCI-000213 |
AC-3 |
xccdf_org.ssgproject.content_rule_grub2_uefi_password | high | Set the UEFI Boot Loader Password | Password protection on the boot loader configuration ensures users with physical access cannot trivially alter important bootloader settings. These include which kernel to use, and whether to enter single-user mode. | The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
Since plaintext passwords are a security risk, generate a hash for the password by running the following command: # grub2-setpasswordWhen prompted, enter the password that was selected. |
To verify the boot loader superuser password has been set, run the following command: $ sudo grep "^[\s]*GRUB2_PASSWORD=grub\.pbkdf2\.sha512.*$" /boot/efi/EFI/redhat/user.cfg The output should be similar to: GRUB2_PASSWORD=grub.pbkdf2.sha512.10000.C4E08AC72FBFF7E837FD267BFAD7AEB3D42DDC 2C99F2A94DD5E2E75C2DC331B719FE55D9411745F82D1B6CFD9E927D61925F9BBDD1CFAA0080E0 916F7AB46E0D.1302284FCCC52CD73BA3671C6C12C26FF50BA873293B24EE2A96EE3B57963E6D7 0C83964B473EC8F93B07FE749AA6710269E904A9B08A6BBACB00A2D242AD828 Is it the case that no password is set? |
SRG-OS-000080-GPOS-00048 |
CCI-000213 |
AC-3 |
xccdf_org.ssgproject.content_rule_grub2_vsyscall_argument | medium | Disable vsyscalls | Virtual Syscalls provide an opportunity of attack for a user who has control of the return instruction pointer. | To disable use of virtual syscalls,
add the argument vsyscall=none to the default
GRUB 2 command line for the Linux operating system.
To ensure that vsyscall=none is added as a kernel command line
argument to newly installed kernels, add vsyscall=none to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... vsyscall=none ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="vsyscall=none" |
Inspect the form of default GRUB 2 command line for the Linux operating system in /etc/default/grub. If it includes vsyscall=none, then the parameter will be configured for newly installed kernels. First check if the GRUB recovery is enabled: $ sudo grep 'GRUB_DISABLE_RECOVERY' /etc/default/grub If this option is set to true, then check that a line is output by the following command: $ sudo grep 'GRUB_CMDLINE_LINUX_DEFAULT.*vsyscall=none.*' /etc/default/grub If the recovery is disabled, check the line with $ sudo grep 'GRUB_CMDLINE_LINUX.*vsyscall=none.*' /etc/default/grub.Moreover, command line parameters for currently installed kernels should be checked as well. Run the following command: $ sudo grubby --info=ALL | grep args | grep -v 'vsyscall=none' The command should not return any output. Is it the case that vsyscalls are enabled? |
SRG-OS-000134-GPOS-00068 |
CCI-001084 |
SC-3 |
xccdf_org.ssgproject.content_rule_harden_sshd_ciphers_openssh_conf_crypto_policy | high | Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config | Overriding the system crypto policy makes the behavior of the OpenSSH client violate expectations, and makes system configuration more fragmented. By specifying a cipher list with the order of ciphers being in a “strongest to weakest” orientation, the system will automatically attempt to use the strongest cipher for securing SSH connections. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings for ciphers are configured correctly, ensure that
/etc/crypto-policies/back-ends/openssh.config contains the following
line and is not commented out:
Ciphers |
To verify if the OpenSSH client uses defined Cipher suite in the Crypto Policy, run: $ grep -i ciphers /etc/crypto-policies/back-ends/openssh.config and verify that the line matches: Ciphers Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
SRG-OS-000033-GPOS-00014 SRG-OS-000125-GPOS-00065 SRG-OS-000250-GPOS-00093 SRG-OS-000423-GPOS-00187 SRG-OS-000481-GPOS-00481 SRG-OS-000393-GPOS-00173 SRG-OS-000394-GPOS-00174 |
CCI-000068 CCI-000877 CCI-001453 CCI-002418 CCI-002890 CCI-003123 |
AC-17 (2) MA-4 c AC-17 (2) |
xccdf_org.ssgproject.content_rule_harden_sshd_ciphers_opensshserver_conf_crypto_policy | medium | Configure SSH Server to Use FIPS 140-2 Validated Ciphers: opensshserver.config | Overriding the system crypto policy makes the behavior of the OpenSSH server violate expectations, and makes system configuration more fragmented. By specifying a cipher list with the order of ciphers being in a “strongest to weakest” orientation, the system will automatically attempt to use the strongest cipher for securing SSH connections. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings for ciphers are configured correctly, ensure that
/etc/crypto-policies/back-ends/opensshserver.config contains the following
text and is not commented out:
-oCiphers= |
To verify if the OpenSSH server uses defined ciphers in the Crypto Policy, run: $ grep -Po '(-oCiphers=\S+)' /etc/crypto-policies/back-ends/opensshserver.config and verify that the line matches: -oCiphers= Is it the case that Crypto Policy for OpenSSH Server is not configured correctly? |
SRG-OS-000125-GPOS-00065 SRG-OS-000250-GPOS-00093 |
CCI-000877 CCI-001453 |
MA-4 c AC-17 (2) |
xccdf_org.ssgproject.content_rule_harden_sshd_macs_openssh_conf_crypto_policy | medium | Configure SSH Client to Use FIPS 140-2 Validated MACs: openssh.config | Overriding the system crypto policy makes the behavior of the OpenSSH client violate expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings are configured correctly, ensure that
/etc/crypto-policies/back-ends/openssh.config contains the following
line and is not commented out:
MACs hmac-sha2-512,hmac-sha2-256
|
To verify if the OpenSSH client uses defined MACs in the Crypto Policy, run: $ grep -i macs /etc/crypto-policies/back-ends/openssh.config and verify that the line matches: MACs hmac-sha2-512,hmac-sha2-256 Is it the case that Crypto Policy for OpenSSH client is not configured correctly? |
SRG-OS-000125-GPOS-00065 SRG-OS-000250-GPOS-00093 |
CCI-000877 CCI-001453 |
MA-4 c AC-17 (2) |
xccdf_org.ssgproject.content_rule_harden_sshd_macs_opensshserver_conf_crypto_policy | medium | Configure SSH Server to Use FIPS 140-2 Validated MACs: opensshserver.config | Overriding the system crypto policy makes the behavior of the OpenSSH server violate expectations, and makes system configuration more fragmented. | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings are configured correctly, ensure that
/etc/crypto-policies/back-ends/opensshserver.config contains the following
text and is not commented out:
-oMACS=hmac-sha2-512,hmac-sha2-256
|
To verify if the OpenSSH server uses defined MACs in the Crypto Policy, run: $ grep -Po '(-oMACs=\S+)' /etc/crypto-policies/back-ends/opensshserver.config and verify that the line matches: -oMACS=hmac-sha2-512,hmac-sha2-256 Is it the case that Crypto Policy for OpenSSH Server is not configured correctly? |
SRG-OS-000125-GPOS-00065 SRG-OS-000250-GPOS-00093 |
CCI-000877 CCI-001453 |
MA-4 c AC-17 (2) |
xccdf_org.ssgproject.content_rule_install_smartcard_packages | medium | Install Smart Card Packages For Multifactor Authentication | 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. |
Configure the operating system to implement multifactor authentication by
installing the required package with the following command:
The openssl-pkcs11 package can be installed with the following command:
$ sudo yum install openssl-pkcs11 |
Check that Oracle Linux 8 has the packages for smart card support installed. Run the following command to determine if the openssl-pkcs11 package is installed: $ rpm -q openssl-pkcs11 Is it the case that smartcard software is not installed? |
SRG-OS-000105-GPOS-00052 SRG-OS-000375-GPOS-00160 SRG-OS-000376-GPOS-00161 SRG-OS-000377-GPOS-00162 |
CCI-000765 CCI-001948 CCI-001953 CCI-001954 |
IA-2 (1) |
xccdf_org.ssgproject.content_rule_installed_OS_is_vendor_supported | high | The Installed Operating System Is Vendor Supported | An operating system is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve any security issue discovered in the system software. | The installed operating system must be maintained by a vendor. Oracle Linux is supported by Oracle Corporation. As the Oracle Linux vendor, Oracle Corporation is responsible for providing security patches. | To verify that the installed operating system is supported, run the following command: $ grep -i "oracle" /etc/oracle-release Oracle Linux 8 Is it the case that the installed operating system is not supported? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_kerberos_disable_no_keytab | medium | Disable Kerberos by removing host keytab | The key derivation function (KDF) in Kerberos is not FIPS compatible. | Kerberos is not an approved key distribution method for
Common Criteria. To prevent using Kerberos by system daemons,
remove the Kerberos keytab files, especially
/etc/krb5.keytab . |
Run the following command to see if there are some keytabs that would potentially allow the use of Kerberos by system daemons. $ ls -la /etc/*.keytab The expected result is ls: cannot access '/etc/*.keytab': No such file or directory Is it the case that a keytab file is present on the system? |
SRG-OS-000120-GPOS-00061 |
CCI-000803 |
IA-7 |
xccdf_org.ssgproject.content_rule_kernel_module_atm_disabled | medium | Disable ATM Support | Disabling ATM protects the system against exploitation of any flaws in its implementation. | The Asynchronous Transfer Mode (ATM) is a protocol operating on
network, data link, and physical layers, based on virtual circuits
and virtual paths.
To configure the system to prevent the atm
kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf :
install atm /bin/trueTo configure the system to prevent the atm from being used,
add the following line to file /etc/modprobe.d/atm.conf :
blacklist atm |
If the system is configured to prevent the loading of the atm kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the atm kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r atm /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000095-GPOS-00049 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000381 CCI-000366 |
CM-7 CM-6 b |
xccdf_org.ssgproject.content_rule_kernel_module_bluetooth_disabled | medium | Disable Bluetooth Kernel Module | If Bluetooth functionality must be disabled, preventing the kernel from loading the kernel module provides an additional safeguard against its activation. | The kernel's module loading system can be configured to prevent
loading of the Bluetooth module. Add the following to
the appropriate /etc/modprobe.d configuration file
to prevent the loading of the Bluetooth module:
install bluetooth /bin/true |
If the system is configured to prevent the loading of the bluetooth kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the bluetooth kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r bluetooth /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000300-GPOS-00118 SRG-OS-000299-GPOS-00117 SRG-OS-000423-GPOS-00187 SRG-OS-000481-GPOS-00481 |
CCI-000085 CCI-001443 CCI-001444 CCI-001551 CCI-002418 |
AC-19 c AC-18 (1) AC-18 (1) AC-4 |
xccdf_org.ssgproject.content_rule_kernel_module_can_disabled | medium | Disable CAN Support | Disabling CAN protects the system against exploitation of any flaws in its implementation. | The Controller Area Network (CAN) is a serial communications
protocol which was initially developed for automotive and
is now also used in marine, industrial, and medical applications.
To configure the system to prevent the can
kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf :
install can /bin/trueTo configure the system to prevent the can from being used,
add the following line to file /etc/modprobe.d/can.conf :
blacklist can |
If the system is configured to prevent the loading of the can kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the can kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r can /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000095-GPOS-00049 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000381 CCI-000366 |
CM-7 CM-6 b |
xccdf_org.ssgproject.content_rule_kernel_module_cramfs_disabled | low | Disable Mounting of cramfs | Removing support for unneeded filesystem types reduces the local attack surface of the server. |
To configure the system to prevent the cramfs
kernel module from being loaded, add the following line to the file /etc/modprobe.d/cramfs.conf :
install cramfs /bin/trueTo configure the system to prevent the cramfs from being used,
add the following line to file /etc/modprobe.d/cramfs.conf :
blacklist cramfsThis effectively prevents usage of this uncommon filesystem. The cramfs filesystem type is a compressed read-only
Linux filesystem embedded in small footprint systems. A
cramfs image can be used without having to first
decompress the image. |
If the system is configured to prevent the loading of the cramfs kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the cramfs kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r cramfs /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_kernel_module_firewire-core_disabled | low | Disable IEEE 1394 (FireWire) Support | Disabling FireWire protects the system against exploitation of any flaws in its implementation. | The IEEE 1394 (FireWire) is a serial bus standard for
high-speed real-time communication.
To configure the system to prevent the firewire-core
kernel module from being loaded, add the following line to the file /etc/modprobe.d/firewire-core.conf :
install firewire-core /bin/trueTo configure the system to prevent the firewire-core from being used,
add the following line to file /etc/modprobe.d/firewire-core.conf :
blacklist firewire-core |
If the system is configured to prevent the loading of the firewire-core kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the firewire-core kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r firewire-core /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_kernel_module_sctp_disabled | medium | Disable SCTP Support | Disabling SCTP protects the system against exploitation of any flaws in its implementation. | The Stream Control Transmission Protocol (SCTP) is a
transport layer protocol, designed to support the idea of
message-oriented communication, with several streams of messages
within one connection.
To configure the system to prevent the sctp
kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf :
install sctp /bin/trueTo configure the system to prevent the sctp from being used,
add the following line to file /etc/modprobe.d/sctp.conf :
blacklist sctp |
If the system is configured to prevent the loading of the sctp kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the sctp kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r sctp /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000095-GPOS-00049 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000381 CCI-000366 |
CM-7 CM-6 b |
xccdf_org.ssgproject.content_rule_kernel_module_tipc_disabled | low | Disable TIPC Support | Disabling TIPC protects the system against exploitation of any flaws in its implementation. | The Transparent Inter-Process Communication (TIPC) protocol
is designed to provide communications between nodes in a
cluster.
To configure the system to prevent the tipc
kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf :
install tipc /bin/trueTo configure the system to prevent the tipc from being used,
add the following line to file /etc/modprobe.d/tipc.conf :
blacklist tipc |
If the system is configured to prevent the loading of the tipc kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the tipc kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r tipc /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_kernel_module_usb-storage_disabled | medium | Disable Modprobe Loading of USB Storage Driver | USB storage devices such as thumb drives can be used to introduce malicious software. | To prevent USB storage devices from being used, configure the kernel module loading system
to prevent automatic loading of the USB storage driver.
To configure the system to prevent the usb-storage
kernel module from being loaded, add the following line to the file /etc/modprobe.d/usb-storage.conf :
install usb-storage /bin/trueTo configure the system to prevent the usb-storage from being used,
add the following line to file /etc/modprobe.d/usb-storage.conf :
blacklist usb-storageThis will prevent the modprobe program from loading the usb-storage
module, but will not prevent an administrator (or another program) from using the
insmod program to load the module manually. |
If the system is configured to prevent the loading of the usb-storage kernel module, it will contain lines inside any file in /etc/modprobe.d or the deprecated /etc/modprobe.conf. These lines instruct the module loading system to run another program (such as /bin/true) upon a module install event. These lines can also instruct the module loading system to ignore the usb-storage kernel module via blacklist keyword. Run the following command to search for such lines in all files in /etc/modprobe.d and the deprecated /etc/modprobe.conf: $ grep -r usb-storage /etc/modprobe.conf /etc/modprobe.d Is it the case that no line is returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000114-GPOS-00059 SRG-OS-000378-GPOS-00163 |
CCI-000366 CCI-000778 CCI-001958 |
CM-6 b IA-3 |
xccdf_org.ssgproject.content_rule_kernel_module_uvcvideo_disabled | medium | Disable the uvcvideo module | Failing to disconnect from collaborative computing devices (i.e., cameras) can result in subsequent compromises of organizational information. Providing easy methods to physically disconnect from such devices after a collaborative computing session helps to ensure participants actually carry out the disconnect activity without having to go through complex and tedious procedures. | If the device contains a camera it should be covered or disabled when not in use. | If the device or Oracle Linux 8 does not have a camera installed, this requirement is not applicable. This requirement is not applicable to mobile devices (smartphones and tablets), where the use of the camera is a local AO decision. This requirement is not applicable to dedicated VTC suites located in approved VTC locations that are centrally managed. For an external camera, if there is not a method for the operator to manually disconnect the camera at the end of collaborative computing sessions, this is a finding. For a built-in camera, the camera must be protected by a camera cover (e.g., laptop camera cover slide) when not in use. If the built-in camera is not protected with a camera cover, or is not physically disabled, this is a finding. If the camera is not disconnected, covered, or physically disabled, determine if it is being disabled via software with the following commands: Verify the operating system disables the ability to load the uvcvideo kernel module. $ sudo grep -r uvcvideo /etc/modprobe.d/* | grep "/bin/true" install uvcvideo /bin/true Is it the case that the command does not return any output, or the line is commented out, and the collaborative computing device has not been authorized for use? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_mount_option_boot_efi_nosuid | medium | Add nosuid Option to /boot/efi | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from boot partitions. | The nosuid mount option can be used to prevent
execution of setuid programs in /boot/efi . The SUID and SGID permissions
should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/boot/efi . |
Verify the nosuid option is configured for the /boot/efi mount point, run the following command: $ sudo mount | grep '\s/boot/efi\s' . . . /boot/efi . . . nosuid . . . Is it the case that the "/boot/efi" file system does not have the "nosuid" option set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_boot_nosuid | medium | Add nosuid Option to /boot | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from boot partitions. | The nosuid mount option can be used to prevent
execution of setuid programs in /boot . The SUID and SGID permissions
should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/boot . |
Verify the nosuid option is configured for the /boot mount point, run the following command: $ sudo mount | grep '\s/boot\s' . . . /boot . . . nosuid . . . Is it the case that the "/boot" file system does not have the "nosuid" option set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_dev_shm_nodev | medium | Add nodev Option to /dev/shm | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
The nodev mount option can be used to prevent creation of device
files in /dev/shm . Legitimate character and block devices should
not exist within temporary directories like /dev/shm .
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm . |
Verify the nodev option is configured for the /dev/shm mount point, run the following command: $ sudo mount | grep '\s/dev/shm\s' . . . /dev/shm . . . nodev . . . Is it the case that the "/dev/shm" file system does not have the "nodev" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_dev_shm_noexec | medium | Add noexec Option to /dev/shm | Allowing users to execute binaries from world-writable directories
such as /dev/shm can expose the system to potential compromise. |
The noexec mount option can be used to prevent binaries
from being executed out of /dev/shm .
It can be dangerous to allow the execution of binaries
from world-writable temporary storage directories such as /dev/shm .
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm . |
Verify the noexec option is configured for the /dev/shm mount point, run the following command: $ sudo mount | grep '\s/dev/shm\s' . . . /dev/shm . . . noexec . . . Is it the case that the "/dev/shm" file system does not have the "noexec" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_dev_shm_nosuid | medium | Add nosuid Option to /dev/shm | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from temporary storage partitions. | The nosuid mount option can be used to prevent execution
of setuid programs in /dev/shm . The SUID and SGID permissions should not
be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm . |
Verify the nosuid option is configured for the /dev/shm mount point, run the following command: $ sudo mount | grep '\s/dev/shm\s' . . . /dev/shm . . . nosuid . . . Is it the case that the "/dev/shm" file system does not have the "nosuid" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_home_noexec | medium | Add noexec Option to /home | The /home directory contains data of individual users. Binaries in
this directory should not be considered as trusted and users should not be
able to execute them. |
The noexec mount option can be used to prevent binaries from being
executed out of /home .
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/home . |
Verify the noexec option is configured for the /home mount point, run the following command: $ sudo mount | grep '\s/home\s' . . . /home . . . noexec . . . Is it the case that the "/home" file system does not have the "noexec" option set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_home_nosuid | medium | Add nosuid Option to /home | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from user home directory partitions. | The nosuid mount option can be used to prevent
execution of setuid programs in /home . The SUID and SGID permissions
should not be required in these user data directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/home . |
Verify the nosuid option is configured for the /home mount point, run the following command: $ sudo mount | grep '\s/home\s' . . . /home . . . nosuid . . . Is it the case that the "/home" file system does not have the "nosuid" option set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_nodev_nonroot_local_partitions | medium | Add nodev Option to Non-Root Local Partitions | The nodev mount option prevents files from being
interpreted as character or block devices. The only legitimate location
for device files is the /dev directory located on the root partition.
The only exception to this is chroot jails, for which it is not advised
to set nodev on these filesystems. |
The nodev mount option prevents files from being interpreted as
character or block devices. Legitimate character and block devices should
exist only in the /dev directory on the root partition or within
chroot jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
any non-root local partitions. |
To verify the nodev option is configured for non-root local partitions, run the following command: $ sudo mount | grep '^/dev\S* on /\S' | grep --invert-match 'nodev' The output shows local non-root partitions mounted without the nodev option, and there should be no output at all. Is it the case that some mounts appear among output lines? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_nodev_remote_filesystems | medium | Mount Remote Filesystems with nodev | Legitimate device files should only exist in the /dev directory. NFS mounts should not present device files to users. | Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts. |
To verify the nodev option is configured for all NFS mounts, run the following command: $ mount | grep nfs All NFS mounts should show the nodev setting in parentheses. This is not applicable if NFS is not implemented. Is it the case that the setting does not show? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_nodev_removable_partitions | medium | Add nodev Option to Removable Media Partitions | The only legitimate location for device files is the /dev directory
located on the root partition. An exception to this is chroot jails, and it is
not advised to set nodev on partitions which contain their root
filesystems. |
The nodev mount option prevents files from being
interpreted as character or block devices.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
any removable media partitions. |
Verify file systems that are used for removable media are mounted with the "nodev" option with the following command: $ sudo more /etc/fstab UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 Is it the case that a file system found in "/etc/fstab" refers to removable media and it does not have the "nodev" option set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_noexec_remote_filesystems | medium | Mount Remote Filesystems with noexec | The noexec mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved binary files as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. | Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts. |
To verify the noexec option is configured for all NFS mounts, run the following command: $ mount | grep nfs All NFS mounts should show the noexec setting in parentheses. This is not applicable if NFS is not implemented. Is it the case that the setting does not show? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_noexec_removable_partitions | medium | Add noexec Option to Removable Media Partitions | Allowing users to execute binaries from removable media such as USB keys exposes the system to potential compromise. | The noexec mount option prevents the direct execution of binaries
on the mounted filesystem. Preventing the direct execution of binaries from
removable media (such as a USB key) provides a defense against malicious
software that may be present on such untrusted media.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
any removable media partitions. |
To verify that binaries cannot be directly executed from removable media, run the following command: $ grep -v noexec /etc/fstab The resulting output will show partitions which do not have the noexec flag. Verify all partitions in the output are not removable media. Is it the case that removable media partitions are present? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000087 CCI-000366 |
AC-19 e CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_nosuid_remote_filesystems | medium | Mount Remote Filesystems with nosuid | NFS mounts should not present suid binaries to users. Only vendor-supplied suid executables should be installed to their default location on the local filesystem. | Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts. |
To verify the nosuid option is configured for all NFS mounts, run the following command: $ mount | grep nfs All NFS mounts should show the nosuid setting in parentheses. This is not applicable if NFS is not implemented. Is it the case that the setting does not show? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_nosuid_removable_partitions | medium | Add nosuid Option to Removable Media Partitions | The presence of SUID and SGID executables should be tightly controlled. Allowing users to introduce SUID or SGID binaries from partitions mounted off of removable media would allow them to introduce their own highly-privileged programs. | The nosuid mount option prevents set-user-identifier (SUID)
and set-group-identifier (SGID) permissions from taking effect. These permissions
allow users to execute binaries with the same permissions as the owner and group
of the file respectively. Users should not be allowed to introduce SUID and SGID
files into the system via partitions mounted from removeable media.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
any removable media partitions. |
Verify file systems that are used for removable media are mounted with the "nosuid" option with the following command: $ sudo more /etc/fstab UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 Is it the case that file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_mount_option_tmp_nodev | medium | Add nodev Option to /tmp | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
The nodev mount option can be used to prevent device files from
being created in /tmp . Legitimate character and block devices
should not exist within temporary directories like /tmp .
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp . |
Verify the nodev option is configured for the /tmp mount point, run the following command: $ sudo mount | grep '\s/tmp\s' . . . /tmp . . . nodev . . . Is it the case that the "/tmp" file system does not have the "nodev" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_tmp_noexec | medium | Add noexec Option to /tmp | Allowing users to execute binaries from world-writable directories
such as /tmp should never be necessary in normal operation and
can expose the system to potential compromise. |
The noexec mount option can be used to prevent binaries
from being executed out of /tmp .
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp . |
Verify the noexec option is configured for the /tmp mount point, run the following command: $ sudo mount | grep '\s/tmp\s' . . . /tmp . . . noexec . . . Is it the case that the "/tmp" file system does not have the "noexec" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_tmp_nosuid | medium | Add nosuid Option to /tmp | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from temporary storage partitions. | The nosuid mount option can be used to prevent
execution of setuid programs in /tmp . The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp . |
Verify the nosuid option is configured for the /tmp mount point, run the following command: $ sudo mount | grep '\s/tmp\s' . . . /tmp . . . nosuid . . . Is it the case that the "/tmp" file system does not have the "nosuid" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_log_audit_nodev | medium | Add nodev Option to /var/log/audit | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
The nodev mount option can be used to prevent device files from
being created in /var/log/audit .
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit . |
Verify the nodev option is configured for the /var/log/audit mount point, run the following command: $ sudo mount | grep '\s/var/log/audit\s' . . . /var/log/audit . . . nodev . . . Is it the case that the "/var/log/audit" file system does not have the "nodev" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_log_audit_noexec | medium | Add noexec Option to /var/log/audit | Allowing users to execute binaries from directories containing audit log files
such as /var/log/audit should never be necessary in normal operation and
can expose the system to potential compromise. |
The noexec mount option can be used to prevent binaries
from being executed out of /var/log/audit .
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit . |
Verify the noexec option is configured for the /var/log/audit mount point, run the following command: $ sudo mount | grep '\s/var/log/audit\s' . . . /var/log/audit . . . noexec . . . Is it the case that the "/var/log/audit" file system does not have the "noexec" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_log_audit_nosuid | medium | Add nosuid Option to /var/log/audit | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from partitions designated for audit log files. | The nosuid mount option can be used to prevent
execution of setuid programs in /var/log/audit . The SUID and SGID permissions
should not be required in directories containing audit log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit . |
Verify the nosuid option is configured for the /var/log/audit mount point, run the following command: $ sudo mount | grep '\s/var/log/audit\s' . . . /var/log/audit . . . nosuid . . . Is it the case that the "/var/log/audit" file system does not have the "nosuid" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_log_nodev | medium | Add nodev Option to /var/log | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
The nodev mount option can be used to prevent device files from
being created in /var/log .
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log . |
Verify the nodev option is configured for the /var/log mount point, run the following command: $ sudo mount | grep '\s/var/log\s' . . . /var/log . . . nodev . . . Is it the case that the "/var/log" file system does not have the "nodev" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_log_noexec | medium | Add noexec Option to /var/log | Allowing users to execute binaries from directories containing log files
such as /var/log should never be necessary in normal operation and
can expose the system to potential compromise. |
The noexec mount option can be used to prevent binaries
from being executed out of /var/log .
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log . |
Verify the noexec option is configured for the /var/log mount point, run the following command: $ sudo mount | grep '\s/var/log\s' . . . /var/log . . . noexec . . . Is it the case that the "/var/log" file system does not have the "noexec" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_log_nosuid | medium | Add nosuid Option to /var/log | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from partitions designated for log files. | The nosuid mount option can be used to prevent
execution of setuid programs in /var/log . The SUID and SGID permissions
should not be required in directories containing log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log . |
Verify the nosuid option is configured for the /var/log mount point, run the following command: $ sudo mount | grep '\s/var/log\s' . . . /var/log . . . nosuid . . . Is it the case that the "/var/log" file system does not have the "nosuid" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_tmp_nodev | medium | Add nodev Option to /var/tmp | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
The nodev mount option can be used to prevent device files from
being created in /var/tmp . Legitimate character and block devices
should not exist within temporary directories like /var/tmp .
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp . |
Verify the nodev option is configured for the /var/tmp mount point, run the following command: $ sudo mount | grep '\s/var/tmp\s' . . . /var/tmp . . . nodev . . . Is it the case that the "/var/tmp" file system does not have the "nodev" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_tmp_noexec | medium | Add noexec Option to /var/tmp | Allowing users to execute binaries from world-writable directories
such as /var/tmp should never be necessary in normal operation and
can expose the system to potential compromise. |
The noexec mount option can be used to prevent binaries
from being executed out of /var/tmp .
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp . |
Verify the noexec option is configured for the /var/tmp mount point, run the following command: $ sudo mount | grep '\s/var/tmp\s' . . . /var/tmp . . . noexec . . . Is it the case that the "/var/tmp" file system does not have the "noexec" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_mount_option_var_tmp_nosuid | medium | Add nosuid Option to /var/tmp | The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from temporary storage partitions. | The nosuid mount option can be used to prevent
execution of setuid programs in /var/tmp . The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp . |
Verify the nosuid option is configured for the /var/tmp mount point, run the following command: $ sudo mount | grep '\s/var/tmp\s' . . . /var/tmp . . . nosuid . . . Is it the case that the "/var/tmp" file system does not have the "nosuid" option set? |
SRG-OS-000368-GPOS-00154 |
CCI-001764 |
|
xccdf_org.ssgproject.content_rule_network_configure_name_resolution | medium | Configure Multiple DNS Servers in /etc/resolv.conf | To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging. |
Determine whether the system is using local or DNS name resolution with the
following command:
$ sudo grep hosts /etc/nsswitch.conf hosts: files dnsIf the DNS entry is missing from the host's line in the "/etc/nsswitch.conf" file, the "/etc/resolv.conf" file must be empty. Verify the "/etc/resolv.conf" file is empty with the following command: $ sudo ls -al /etc/resolv.conf -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.confIf the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file, then verify the following: Multiple Domain Name System (DNS) Servers should be configured in /etc/resolv.conf . This provides redundant name resolution services
in the event that a domain server crashes. To configure the system to contain
as least 2 DNS servers, add a corresponding nameserver
ip_address entry in /etc/resolv.conf for each DNS
server where ip_address is the IP address of a valid DNS server.
For example:
search example.com nameserver 192.168.0.1 nameserver 192.168.0.2 |
Verify that DNS servers have been configured properly, perform the following: $ sudo grep nameserver /etc/resolv.conf Is it the case that less than two lines are returned that are not commented out? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_network_sniffer_disabled | medium | Ensure System is Not Acting as a Network Sniffer | Network interfaces in promiscuous mode allow for the capture of all network traffic
visible to the system. If unauthorized individuals can access these applications, it
may allow them to collect information such as logon IDs, passwords, and key exchanges
between systems.
If the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information Systems Security Manager (ISSM) and restricted to only authorized personnel. |
The system should not be acting as a network sniffer, which can
capture all traffic on the network to which it is connected. Run the following
to determine if any interface is running in promiscuous mode:
$ ip link | grep PROMISCPromiscuous mode of an interface can be disabled with the following command: $ sudo ip link set dev
|
Verify that Promiscuous mode of an interface is disabled, run the following command: $ ip link | grep PROMISC Is it the case that any network device is in promiscuous mode? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_no_empty_passwords | high | Prevent Login to Accounts With Empty Password | If an account has an empty password, anyone could log in and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments. | If an account is configured for password authentication
but does not have an assigned password, it may be possible to log
into the account without authentication. Remove any instances of the
nullok in
/etc/pam.d/system-auth and
/etc/pam.d/password-auth
to prevent logins with empty passwords. |
To verify that null passwords cannot be used, run the following command: $ grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth If this produces any output, it may be possible to log into accounts with empty passwords. Remove any instances of the nullok option to prevent logins with empty passwords. Is it the case that NULL passwords can be used? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_no_empty_passwords_etc_shadow | high | Ensure There Are No Accounts With Blank or Null Passwords | If an account has an empty password, anyone could log in and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments. | Check the "/etc/shadow" file for blank passwords with the
following command:
$ sudo awk -F: '!$2 {print $1}' /etc/shadowIf the command returns any results, this is a finding. Configure all accounts on the system to have a password or lock the account with the following commands: Perform a password reset: $ sudo passwd [username]Lock an account: $ sudo passwd -l [username] |
To verify that null passwords cannot be used, run the following command: $ sudo awk -F: '!$2 {print $1}' /etc/shadow If this produces any output, it may be possible to log into accounts with empty passwords. Is it the case that Blank or NULL passwords can be used? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_no_files_unowned_by_user | medium | Ensure All Files Are Owned by a User | Unowned files do not directly imply a security problem, but they are generally a sign that something is amiss. They may be caused by an intruder, by incorrect software installation or draft software removal, or by failure to remove all files belonging to a deleted account. The files should be repaired so they will not cause problems when accounts are created in the future, and the cause should be discovered and addressed. | If any files are not owned by a user, then the
cause of their lack of ownership should be investigated.
Following this, the files should be deleted or assigned to an
appropriate user. The following command will discover and print
any files on local partitions which do not belong to a valid user:
$ df --local -P | awk {'if (NR!=1) print $6'} | sudo xargs -I '{}' find '{}' -xdev -nouserTo search all filesystems on a system including network mounted filesystems the following command can be run manually for each partition: $ sudo find PARTITION -xdev -nouser |
The following command will discover and print any files on local partitions which do not belong to a valid user. $ df --local -P | awk {'if (NR!=1) print $6'} | sudo xargs -I '{}' find '{}' -xdev -nouser Either remove all files and directories from the system that do not have a valid user, or assign a valid user to all unowned files and directories on the system with the chown command: $ sudo chown user file Is it the case that files exist that are not owned by a valid user? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 |
CCI-000366 CCI-002165 |
CM-6 b |
xccdf_org.ssgproject.content_rule_no_host_based_files | high | Remove Host-Based Authentication Files | The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication. | The shosts.equiv file list remote hosts
and users that are trusted by the local system.
To remove these files, run the following command to delete them from any
location:
$ sudo rm /[path]/[to]/[file]/shosts.equiv |
Verify that there are no shosts.equiv files on the system, run the following command: $ find / -name shosts.equiv Is it the case that shosts.equiv files exist? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_no_tmux_in_shells | low | Prevent user from disabling the screen lock | Not listing tmux among permitted shells
prevents malicious program running as user
from lowering security by disabling the screen lock. |
The tmux terminal multiplexer is used to implement
automatic session locking. It should not be listed in
/etc/shells . |
To verify that tmux is not listed as allowed shell on the system run the following command: $ grep 'tmux$' /etc/shells The output should be empty. Is it the case that tmux is listed in /etc/shells? |
SRG-OS-000028-GPOS-00009 SRG-OS-000030-GPOS-00011 |
CCI-000056 CCI-000058 |
AC-11 b AC-11 a |
xccdf_org.ssgproject.content_rule_no_user_host_based_files | high | Remove User Host-Based Authentication Files | The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication. | The ~/.shosts (in each user's home directory) files
list remote hosts and users that are trusted by the
local system. To remove these files, run the following command
to delete them from any location:
$ sudo find / -name '.shosts' -type f -delete |
To verify that there are no .shosts files on the system, run the following command: $ sudo find / -name '.shosts' Is it the case that .shosts files exist? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_package_abrt-libs_removed | medium | Uninstall abrt-libs Package |
abrt-libs provides libraries for the ABRT package. |
The abrt-libs package can be removed with the following command:
$ sudo yum erase abrt-libs |
Run the following command to determine if the abrt-libs package is installed: $ rpm -q abrt-libs Is it the case that the package is installed? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_package_abrt-server-info-page_removed | medium | Uninstall abrt-server-info-page Package |
abrt-server-info-page provides a web page with summary of ABRT services. |
The abrt-server-info-page package can be removed with the following command:
$ sudo yum erase abrt-server-info-page |
Run the following command to determine if the abrt-server-info-page package is installed: $ rpm -q abrt-server-info-page Is it the case that the package is installed? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_package_abrt_removed | medium | Uninstall Automatic Bug Reporting Tool (abrt) | Mishandling crash data could expose sensitive information about vulnerabilities in software executing on the system, as well as sensitive information from within a process's address space or registers. | The Automatic Bug Reporting Tool (abrt ) collects
and reports crash data when an application crash is detected. Using a variety
of plugins, abrt can email crash reports to system administrators, log crash
reports to files, or forward crash reports to a centralized issue tracking
system such as RHTSupport.
The abrt package can be removed with the following command:
$ sudo yum erase abrt |
Run the following command to determine if the abrt package is installed: $ rpm -q abrt Is it the case that the package is installed? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_package_aide_installed | medium | Install AIDE | The AIDE package must be installed if it is to be available for integrity checking. | The aide package can be installed with the following command:
$ sudo yum install aide |
Run the following command to determine if the aide package is installed: $ rpm -q aide Is it the case that the package is not installed? |
SRG-OS-000445-GPOS-00199 SRG-OS-000446-GPOS-00200 SRG-OS-000363-GPOS-00150 |
CCI-002696 CCI-002699 CCI-001744 |
|
xccdf_org.ssgproject.content_rule_package_audit_installed | medium | Ensure the audit Subsystem is Installed | The auditd service is an access monitoring and accounting daemon, watching system calls to audit any access, in comparison with potential local access control policy such as SELinux policy. | The audit package should be installed. | Run the following command to determine if the audit package is installed: $ rpm -q audit Is it the case that the audit package is not installed? |
SRG-OS-000037-GPOS-00015 SRG-OS-000038-GPOS-00016 SRG-OS-000039-GPOS-00017 SRG-OS-000040-GPOS-00018 SRG-OS-000041-GPOS-00019 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000051-GPOS-00024 SRG-OS-000054-GPOS-00025 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000254-GPOS-00095 SRG-OS-000255-GPOS-00096 SRG-OS-000365-GPOS-00152 SRG-OS-000348-GPOS-00136 SRG-OS-000122-GPOS-00063 SRG-OS-000349-GPOS-00137 SRG-OS-000350-GPOS-00138 SRG-OS-000351-GPOS-00139 SRG-OS-000352-GPOS-00140 SRG-OS-000353-GPOS-00141 SRG-OS-000354-GPOS-00142 SRG-OS-000358-GPOS-00145 SRG-OS-000337-GPOS-00129 SRG-OS-000392-GPOS-00172 SRG-OS-000062-GPOS-00031 |
CCI-000130 CCI-000131 CCI-000132 CCI-000133 CCI-000134 CCI-000135 CCI-000154 CCI-000158 CCI-000172 CCI-001464 CCI-001487 CCI-001814 CCI-001875 CCI-001876 CCI-001877 CCI-001878 CCI-001879 CCI-001880 CCI-001881 CCI-001882 CCI-001889 CCI-001914 CCI-002884 CCI-000169 |
AU-3 AU-3 AU-3 AU-3 AU-3 AU-3 (1) AU-6 (4) AU-7 (1) AU-12 c AU-14 (1) AU-3 AU-12 a |
xccdf_org.ssgproject.content_rule_package_fapolicyd_installed | medium | Install fapolicyd Package |
fapolicyd (File Access Policy Daemon)
implements application whitelisting to decide file access rights. |
The fapolicyd package can be installed with the following command:
$ sudo yum install fapolicyd |
Run the following command to determine if the fapolicyd package is installed: $ rpm -q fapolicyd Is it the case that the fapolicyd package is not installed? |
SRG-OS-000368-GPOS-00154 SRG-OS-000370-GPOS-00155 |
CCI-001764 CCI-001774 |
|
xccdf_org.ssgproject.content_rule_package_firewalld_installed | medium | Install firewalld Package | "Firewalld" provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols. 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. Oracle Linux 8 functionality (e.g., SSH) 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)." | The firewalld package can be installed with the following command:
$ sudo yum install firewalld |
Run the following command to determine if the firewalld package is installed: $ rpm -q firewalld Is it the case that the package is not installed? |
SRG-OS-000297-GPOS-00115 |
CCI-002314 |
|
xccdf_org.ssgproject.content_rule_package_gssproxy_removed | medium | Uninstall gssproxy Package |
gssproxy is a proxy for GSS API credential handling. |
The gssproxy package can be removed with the following command:
$ sudo yum erase gssproxy |
Run the following command to determine if the gssproxy package is installed: $ rpm -q gssproxy Is it the case that the package is installed? |
SRG-OS-000095-GPOS-00049 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000381 CCI-000366 |
CM-7 CM-6 b |
xccdf_org.ssgproject.content_rule_package_iprutils_removed | medium | Uninstall iprutils Package |
iprutils provides a suite of utlilities to manage and configure SCSI devices
supported by the ipr SCSI storage device driver. |
The iprutils package can be removed with the following command:
$ sudo yum erase iprutils |
Run the following command to determine if the iprutils package is installed: $ rpm -q iprutils Is it the case that the package is installed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_package_krb5-server_removed | medium | Remove the Kerberos Server Package | Unnecessary packages should not be installed to decrease the attack surface of the system. While this software is clearly essential on an KDC server, it is not necessary on typical desktop or workstation systems. | The krb5-server package should be removed if not in use.
Is this system the Kerberos server? If not, remove the package.
The krb5-server package can be removed with the following command:
$ sudo yum erase krb5-serverThe krb5-server RPM is not installed by default on a Oracle Linux 8 system. It is needed only by the Kerberos servers, not by the clients which use Kerberos for authentication. If the system is not intended for use as a Kerberos Server it should be removed. |
Run the following command to determine if the krb5-server package is installed: $ rpm -q krb5-server Is it the case that the package is installed? |
SRG-OS-000120-GPOS-00061 |
CCI-000803 |
IA-7 |
xccdf_org.ssgproject.content_rule_package_krb5-workstation_removed | medium | Uninstall krb5-workstation Package | Kerberos is a network authentication system. The krb5-workstation package contains the basic
Kerberos programs (kinit , klist , kdestroy , kpasswd ). |
The krb5-workstation package can be removed with the following command:
$ sudo yum erase krb5-workstation |
Run the following command to determine if the krb5-workstation package is installed: $ rpm -q krb5-workstation Is it the case that the package is installed? |
SRG-OS-000120-GPOS-00061 |
CCI-000803 |
IA-7 |
xccdf_org.ssgproject.content_rule_package_mcafeetp_installed | medium | Install McAfee Endpoint Security for Linux (ENSL) | Virus scanning software can be used to detect if a system has been compromised by computer viruses, as well as to limit their spread to other systems. | Install McAfee Endpoint Security for Linux antivirus software
which is provided for DoD systems and uses signatures to search for the
presence of viruses on the filesystem.
The McAfeeTP package can be installed with the following command:
$ sudo yum install McAfeeTP |
Run the following command to determine if the McAfeeTP package is installed: $ rpm -q McAfeeTP Is it the case that the package is not installed? |
SRG-OS-000191-GPOS-00080 |
CCI-001233 |
SI-2 (2) |
xccdf_org.ssgproject.content_rule_package_opensc_installed | medium | Install the opensc Package For Multifactor Authentication | 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. |
The opensc package can be installed with the following command:
$ sudo yum install opensc |
Run the following command to determine if the opensc package is installed: $ rpm -q opensc Is it the case that the package is not installed? |
SRG-OS-000377-GPOS-00162 SRG-OS-000376-GPOS-00161 |
CCI-001954 CCI-001953 |
|
xccdf_org.ssgproject.content_rule_package_openssh-server_installed | medium | Install the OpenSSH Server Package | Without protection of the transmitted information, confidentiality, and integrity may be compromised because unprotected communications can be intercepted and either read or altered. | The openssh-server package should be installed.
The openssh-server package can be installed with the following command:
$ sudo yum install openssh-server |
Run the following command to determine if the openssh-server package is installed: $ rpm -q openssh-server Is it the case that the package is not installed? |
SRG-OS-000423-GPOS-00187 SRG-OS-000481-GPOS-00481 SRG-OS-000425-GPOS-00189 SRG-OS-000424-GPOS-00188 SRG-OS-000426-GPOS-00190 |
CCI-002418 CCI-002420 CCI-002421 CCI-002422 |
|
xccdf_org.ssgproject.content_rule_package_policycoreutils_installed | low | Install policycoreutils Package | Security-enhanced Linux is a feature of the Linux kernel and a number of utilities
with enhanced security functionality designed to add mandatory access controls to Linux.
The Security-enhanced Linux kernel contains new architectural components originally
developed to improve security of the Flask operating system. These architectural components
provide general support for the enforcement of many kinds of mandatory access control
policies, including those based on the concepts of Type Enforcement, Role-based Access
Control, and Multi-level Security.
policycoreutils contains the policy core utilities that are required for
basic operation of an SELinux-enabled system. These utilities include load_policy
to load SELinux policies, setfiles to label filesystems, newrole to
switch roles, and so on. |
The policycoreutils package can be installed with the following command:
$ sudo yum install policycoreutils |
Run the following command to determine if the policycoreutils package is installed: $ rpm -q policycoreutils Is it the case that the policycoreutils package is not installed? |
SRG-OS-000134-GPOS-00068 |
CCI-001084 |
SC-3 |
xccdf_org.ssgproject.content_rule_package_rng-tools_installed | low | Install rng-tools Package |
rng-tools provides hardware random number generator tools,
such as those used in the formation of x509/PKI certificates. |
The rng-tools package can be installed with the following command:
$ sudo yum install rng-tools |
Run the following command to determine if the rng-tools package is installed: $ rpm -q rng-tools Is it the case that the package is not installed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_package_rsh-server_removed | high | Uninstall rsh-server Package | The rsh-server service provides unencrypted remote access service which does not
provide for the confidentiality and integrity of user passwords or the remote session and has very weak
authentication. If a privileged user were to login using this service, the privileged user password
could be compromised. The rsh-server package provides several obsolete and insecure
network services. Removing it decreases the risk of those services' accidental (or intentional)
activation. |
The rsh-server package can be removed with the following command:
$ sudo yum erase rsh-server |
Run the following command to determine if the rsh-server package is installed: $ rpm -q rsh-server Is it the case that the package is installed? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_package_rsyslog-gnutls_installed | medium | Ensure rsyslog-gnutls is installed | The rsyslog-gnutls package provides Transport Layer Security (TLS) support for the rsyslog daemon, which enables secure remote logging. | TLS protocol support for rsyslog is installed.
The rsyslog-gnutls package can be installed with the following command:
$ sudo yum install rsyslog-gnutls |
Run the following command to determine if the rsyslog-gnutls package is installed: $ rpm -q rsyslog-gnutls Is it the case that the package is not installed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_package_rsyslog_installed | medium | Ensure rsyslog is Installed | The rsyslog package provides the rsyslog daemon, which provides system logging services. | Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
Run the following command to determine if the rsyslog package is installed: $ rpm -q rsyslog Is it the case that the package is not installed? |
SRG-OS-000205-GPOS-00083 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-001311 CCI-001312 CCI-000366 |
SI-11 a SI-11 b CM-6 b |
xccdf_org.ssgproject.content_rule_package_sendmail_removed | medium | Uninstall Sendmail Package | The sendmail software was not developed with security in mind and its design prevents it from being effectively contained by SELinux. Postfix should be used instead. | Sendmail is not the default mail transfer agent and is
not installed by default.
The sendmail package can be removed with the following command:
$ sudo yum erase sendmail |
Run the following command to determine if the sendmail package is installed: $ rpm -q sendmail Is it the case that the package is installed? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_package_telnet-server_removed | high | Uninstall telnet-server Package | It is detrimental for operating systems to provide, or install by default,
functionality exceeding requirements or mission objectives. These
unnecessary capabilities are often overlooked and therefore may remain
unsecure. They increase the risk to the platform by providing additional
attack vectors.
The telnet service provides an unencrypted remote access service which does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to login using this service, the privileged user password could be compromised. Removing the telnet-server package decreases the risk of the
telnet service's accidental (or intentional) activation. |
The telnet-server package can be removed with the following command:
$ sudo yum erase telnet-server |
Run the following command to determine if the telnet-server package is installed: $ rpm -q telnet-server Is it the case that the package is installed? |
SRG-OS-000095-GPOS-00049 |
CCI-000381 |
CM-7 |
xccdf_org.ssgproject.content_rule_package_tftp-server_removed | high | Uninstall tftp-server Package | Removing the tftp-server package decreases the risk of the accidental
(or intentional) activation of tftp services.
If TFTP is required for operational support (such as transmission of router configurations), its use must be documented with the Information Systems Securty Manager (ISSM), restricted to only authorized personnel, and have access control rules established. |
The tftp-server package can be removed with the following command: $ sudo yum erase tftp-server |
Run the following command to determine if the tftp-server package is installed: $ rpm -q tftp-server Is it the case that the package is installed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000362-GPOS-00149 SRG-OS-000364-GPOS-00151 SRG-OS-000365-GPOS-00152 |
CCI-000318 CCI-000366 CCI-000368 CCI-001812 CCI-001813 CCI-001814 |
CM-3 e CM-6 b CM-6 c |
xccdf_org.ssgproject.content_rule_package_tmux_installed | medium | Install the tmux Package | 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 logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operation 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 tmux package allows for a session lock to be implemented and configured. |
To enable console screen locking, install the tmux package.
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, Oracle Linux 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
Instruct users to begin new terminal sessions with the following command:
$ tmuxThe console can now be locked with the following key combination: ctrl+b :lock-session |
Run the following command to determine if the tmux package is installed: $ rpm -q tmux Is it the case that the package is not installed? |
SRG-OS-000030-GPOS-00011 SRG-OS-000028-GPOS-00009 |
CCI-000058 CCI-000056 |
AC-11 a AC-11 b |
xccdf_org.ssgproject.content_rule_package_tuned_removed | medium | Uninstall tuned Package |
tuned contains a daemon that tunes the system settings dynamically.
It does so by monitoring the usage of several system components periodically. Based
on that information, components will then be put into lower or higher power savings
modes to adapt to the current usage. |
The tuned package can be removed with the following command:
$ sudo yum erase tuned |
Run the following command to determine if the tuned package is installed: $ rpm -q tuned Is it the case that the package is installed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_package_usbguard_installed | medium | Install usbguard Package |
usbguard is a software framework that helps to protect
against rogue USB devices by implementing basic whitelisting/blacklisting
capabilities based on USB device attributes. |
The usbguard package can be installed with the following command:
$ sudo yum install usbguard |
Run the following command to determine if the usbguard package is installed: $ rpm -q usbguard Is it the case that the package is not installed? |
SRG-OS-000378-GPOS-00163 |
CCI-001958 |
|
xccdf_org.ssgproject.content_rule_package_vsftpd_removed | high | Uninstall vsftpd Package | Removing the vsftpd package decreases the risk of its
accidental activation. |
The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
Run the following command to determine if the vsftpd package is installed: $ rpm -q vsftpd Is it the case that the package is installed? |
SRG-OS-000074-GPOS-00042 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000095-GPOS-00049 |
CCI-000197 CCI-000366 CCI-000381 |
IA-5 (1) (c) CM-6 b CM-7 |
xccdf_org.ssgproject.content_rule_partition_for_home | low | Ensure /home Located On Separate Partition | Ensuring that /home is mounted on its own partition enables the
setting of more restrictive mount options, and also helps ensure that
users cannot trivially fill partitions used for log or audit data storage. |
If user home directories will be stored locally, create a separate partition
for /home at installation time (or migrate it later using LVM). If
/home will be mounted from another system such as an NFS server, then
creating a separate partition is not necessary at installation time, and the
mountpoint can instead be configured later. |
Verify that a separate file system/partition has been created for /home with the following command: $ mountpoint /home Is it the case that "/home is not a mountpoint" is returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001208 |
CM-6 b SC-32 |
xccdf_org.ssgproject.content_rule_partition_for_tmp | low | Ensure /tmp Located On Separate Partition | The /tmp partition is used as temporary storage by many programs.
Placing /tmp in its own partition enables the setting of more
restrictive mount options, which can help protect programs which use it. |
The /tmp directory is a world-writable directory used
for temporary file storage. Ensure it has its own partition or
logical volume at installation time, or migrate it using LVM. |
Verify that a separate file system/partition has been created for /tmp with the following command: $ mountpoint /tmp Is it the case that "/tmp is not a mountpoint" is returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_partition_for_var | low | Ensure /var Located On Separate Partition | Ensuring that /var is mounted on its own partition enables the
setting of more restrictive mount options. This helps protect
system services such as daemons or other programs which use it.
It is not uncommon for the /var directory to contain
world-writable directories installed by other software packages. |
The /var directory is used by daemons and other system
services to store frequently-changing data. Ensure that /var has its own partition
or logical volume at installation time, or migrate it using LVM. |
Verify that a separate file system/partition has been created for /var with the following command: $ mountpoint /var Is it the case that "/var is not a mountpoint" is returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_partition_for_var_log | low | Ensure /var/log Located On Separate Partition | Placing /var/log in its own partition
enables better separation between log files
and other files in /var/ . |
System logs are stored in the /var/log directory.
Ensure that /var/log has its own partition or logical
volume at installation time, or migrate it using LVM. |
Verify that a separate file system/partition has been created for /var/log with the following command: $ mountpoint /var/log Is it the case that "/var/log is not a mountpoint" is returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_partition_for_var_log_audit | low | Ensure /var/log/audit Located On Separate Partition | Placing /var/log/audit in its own partition
enables better separation between audit files
and other files, and helps ensure that
auditing cannot be halted due to the partition running out
of space. |
Audit logs are stored in the /var/log/audit directory.
Ensure that /var/log/audit has its own partition or logical
volume at installation time, or migrate it using LVM.
Make absolutely certain that it is large enough to store all
audit logs that will be created by the auditing daemon. |
Verify that a separate file system/partition has been created for /var/log/audit with the following command: $ mountpoint /var/log/audit Is it the case that "/var/log/audit is not a mountpoint" is returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000341-GPOS-00132 |
CCI-000366 CCI-001849 |
CM-6 b |
xccdf_org.ssgproject.content_rule_partition_for_var_tmp | medium | Ensure /var/tmp Located On Separate Partition | The /var/tmp partition is used as temporary storage by many programs.
Placing /var/tmp in its own partition enables the setting of more
restrictive mount options, which can help protect programs which use it. |
The /var/tmp directory is a world-writable directory used
for temporary file storage. Ensure it has its own partition or
logical volume at installation time, or migrate it using LVM. |
Verify that a separate file system/partition has been created for /var/tmp with the following command: $ mountpoint /var/tmp Is it the case that "/var/tmp is not a mountpoint" is returned? |
|||
xccdf_org.ssgproject.content_rule_postfix_client_configure_mail_alias_postmaster | medium | Configure System to Forward All Mail From Postmaster to The Root Account | 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. | Verify the administrators are notified in the event of an audit processing failure.
Check that the "/etc/aliases" file has a defined value for "root".
$ sudo grep "postmaster:\s*root$" /etc/aliases postmaster: root |
Find the list of alias maps used by the Postfix mail server: $ sudo postconf alias_maps Query the Postfix alias maps for an alias for the postmaster user: $ sudo postmap -q postmaster hash:/etc/aliases The output should return root. Is it the case that the alias is not set or is not root? |
SRG-OS-000046-GPOS-00022 |
CCI-000139 |
AU-5 a |
xccdf_org.ssgproject.content_rule_postfix_prevent_unrestricted_relay | medium | Prevent Unrestricted Mail Relaying | If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity. | Modify the /etc/postfix/main.cffile to restrict client connections to the local network with the following command: $ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject' |
Verify that Oracle Linux 8 is configured to prevent unrestricted mail relaying, run the following command: $ sudo postconf -n smtpd_client_restrictions Is it the case that the "smtpd_client_restrictions" parameter contains any entries other than "permit_mynetworks" and "reject"? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_require_emergency_target_auth | medium | Require Authentication for Emergency Systemd Target | This prevents attackers with physical access from trivially bypassing security on the machine and gaining root access. Such accesses are further prevented by configuring the bootloader password. | Emergency mode is intended as a system recovery
method, providing a single user root access to the system
during a failed boot sequence.
By default, Emergency mode is protected by requiring a password and is set in /usr/lib/systemd/system/emergency.service . |
To check if authentication is required for emergency mode, run the following command: $ grep sulogin /usr/lib/systemd/system/emergency.service The output should be similar to the following, and the line must begin with ExecStart and /usr/lib/systemd/systemd-sulogin-shell. ExecStart=-/usr/lib/systemd/systemd-sulogin-shell emergency Then, check if the emergency target requires the emergency service: Run the following command: $ sudo grep Requires /usr/lib/systemd/system/emergency.target The output should be the following: Requires=emergency.service Then, check if there is no custom emergency target configured in systemd configuration. Run the following command: $ sudo grep -r emergency.target /etc/systemd/system/ The output should be empty. Then, check if there is no custom emergency service configured in systemd configuration. Run the following command: $ sudo grep -r emergency.service /etc/systemd/system/ The output should be empty. Is it the case that the output is different? |
SRG-OS-000080-GPOS-00048 |
CCI-000213 |
AC-3 |
xccdf_org.ssgproject.content_rule_require_singleuser_auth | medium | Require Authentication for Single User Mode | This prevents attackers with physical access from trivially bypassing security on the machine and gaining root access. Such accesses are further prevented by configuring the bootloader password. | Single-user mode is intended as a system recovery
method, providing a single user root access to the system by
providing a boot option at startup.
By default, single-user mode is protected by requiring a password and is set in /usr/lib/systemd/system/rescue.service . |
To check if authentication is required for single-user mode, run the following command: $ grep sulogin /usr/lib/systemd/system/rescue.service The output should be similar to the following, and the line must begin with ExecStart and /usr/lib/systemd/systemd-sulogin-shell. ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue Is it the case that the output is different? |
SRG-OS-000080-GPOS-00048 |
CCI-000213 |
AC-3 |
xccdf_org.ssgproject.content_rule_root_permissions_syslibrary_files | medium | Verify the system-wide library files in directories "/lib", "/lib64", "/usr/lib/" and "/usr/lib64" are group-owned by root. | 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 must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. | System-wide library files are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64All system-wide shared library files should be protected from unauthorised access. If any of these files is not group-owned by root, correct its group-owner with the following command: $ sudo chgrp root FILE |
Verify the system-wide shared library files are group-owned by "root" with the following command: $ sudo find -L /lib /lib64 /usr/lib /usr/lib64 ! -group root -exec ls -l {} \; Is it the case that any system wide shared library file is returned and is not group-owned by a required system account? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_rsyslog_cron_logging | medium | Ensure cron Is Logging To Rsyslog | Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users. | Cron logging must be implemented to spot intrusions or trace
cron job status. If cron is not logging to rsyslog , it
can be implemented by adding the following to the RULES section of
/etc/rsyslog.conf :
cron.* /var/log/cron |
Verify that cron is logging to rsyslog, run the following command: grep -rni "cron\.\*" /etc/rsyslog.* cron.* /var/log/cron Is it the case that cron is not logging to rsyslog? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_actionsendstreamdriverauthmode | medium | Ensure Rsyslog Authenticates Off-Loaded Audit Records | The audit records generated by Rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Audit records should be protected from unauthorized access. | Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging. Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
When using rsyslogd to off-load logs the remote system must be authenticated. |
Verify the operating system authenticates the remote logging server for off-loading audit logs with the following command: $ sudo grep -i '$ActionSendStreamDriverAuthMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf The output should be $/etc/rsyslog.conf:$ActionSendStreamDriverAuthMode x509/name Is it the case that $ActionSendStreamDriverAuthMode in /etc/rsyslog.conf is not set to x509/name? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
xccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_actionsendstreamdrivermode | medium | Ensure Rsyslog Encrypts Off-Loaded Audit Records | The audit records generated by Rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Audit records should be protected from unauthorized access. | Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging. Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
When using rsyslogd to off-load logs off a encrpytion system must be used. |
Verify the operating system encrypts audit records off-loaded onto a different system or media from the system being audited with the following commands: $ sudo grep -i '$ActionSendStreamDriverMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf The output should be: /etc/rsyslog.conf:$ActionSendStreamDriverMode 1 Is it the case that rsyslogd ActionSendStreamDriverMode is not set to 1? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
xccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_defaultnetstreamdriver | medium | Ensure Rsyslog Encrypts Off-Loaded Audit Records | The audit records generated by Rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Audit records should be protected from unauthorized access. | Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging. Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
When using rsyslogd to off-load logs off an encryption system must be used. |
Verify the operating system encrypts audit records off-loaded onto a different system or media from the system being audited with the following commands: $ sudo grep -i '$DefaultNetstreamDriver' /etc/rsyslog.conf /etc/rsyslog.d/*.conf The output should be: /etc/rsyslog.conf:$DefaultNetstreamDriver gtls Is it the case that rsyslogd DefaultNetstreamDriver not set to gtls? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
xccdf_org.ssgproject.content_rule_rsyslog_remote_access_monitoring | medium | Ensure remote access methods are monitored in Rsyslog | Logging remote access methods can be used to trace the decrease the risks associated with remote user access management. It can also be used to spot cyber attacks and ensure ongoing compliance with organizational policies surrounding the use of remote access methods. | Logging of remote access methods must be implemented to help identify cyber
attacks and ensure ongoing compliance with remote access policies are being
audited and upheld. An examples of a remote access method is the use of the
Remote Desktop Protocol (RDP) from an external, non-organization controlled
network. The /etc/rsyslog.conf or
/etc/rsyslog.d/*.conf file should contain a match for the following
selectors: auth.* , authpriv.* , and daemon.* . If
not, use the following as an example configuration:
auth.*;authpriv.*;daemon.* /var/log/secure |
To verify that remote access methods are logging to rsyslog, run the following command: grep -rE '(auth.\*|authpriv.\*|daemon.\*)' /etc/rsyslog.* The output should contain auth.*, authpriv.*, and daemon.* pointing to a log file. Is it the case that remote access methods are not logging to rsyslog? |
SRG-OS-000032-GPOS-00013 |
CCI-000067 |
AC-17 (1) |
xccdf_org.ssgproject.content_rule_rsyslog_remote_loghost | medium | Ensure Logs Sent To Remote Host | A log server (loghost) receives syslog messages from one or more systems. This data can be used as an additional log source in the event a system is compromised and its local logs are suspect. Forwarding log messages to a remote loghost also provides system administrators with a centralized place to view the status of multiple hosts within the enterprise. | To configure rsyslog to send logs to a remote log server,
open /etc/rsyslog.conf and read and understand the last section of the file,
which describes the multiple directives necessary to activate remote
logging.
Along with these other directives, the system can be configured
to forward its logs to a particular log server by
adding or correcting one of the following lines,
substituting appropriately.
The choice of protocol depends on the environment of the system;
although TCP and RELP provide more reliable message delivery,
they may not be supported in all environments.
To use UDP for log message delivery: *.* @ To use TCP for log message delivery: *.* @@ To use RELP for log message delivery: *.* :omrelp: There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility. |
To ensure logs are sent to a remote host, examine the file /etc/rsyslog.conf. If using UDP, a line similar to the following should be present: *.* @ If using TCP, a line similar to the following should be present: *.* @@ If using RELP, a line similar to the following should be present: *.* :omrelp: Is it the case that no evidence that the audit logs are being off-loaded to another system or media? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-000366 CCI-001348 CCI-000136 CCI-001851 |
CM-6 b AU-9 (2) AU-3 (2) |
xccdf_org.ssgproject.content_rule_security_patches_up_to_date | medium | Ensure Software Patches Installed | Installing software updates is a fundamental mitigation against the exploitation of publicly-known vulnerabilities. If the most recent security patches and updates are not installed, unauthorized users may take advantage of weaknesses in the unpatched software. The lack of prompt attention to patching could result in a system compromise. |
If the system is joined to the ULN
or a yum server, run the following command to install updates:
$ sudo yum updateIf the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded from the ULN and installed using rpm .
NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy dictates. |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001227 |
CM-6 b SI-2 a |
|
xccdf_org.ssgproject.content_rule_selinux_policytype | medium | Configure SELinux Policy | Setting the SELinux policy to targeted or a more specialized policy
ensures the system will confine processes that are likely to be
targeted for exploitation, such as network or system services.
Note: During the development or debugging of SELinux modules, it is common to temporarily place non-production systems in permissive mode. In such
temporary cases, SELinux policies should be developed, and once work
is completed, the system should be reconfigured to
. |
The SELinux targeted policy is appropriate for
general-purpose desktops and servers, as well as systems in many other roles.
To configure the system to use this policy, add or correct the following line
in /etc/selinux/config :
SELINUXTYPE=Other policies, such as mls , provide additional security labeling
and greater confinement but are not compatible with many general-purpose
use cases. |
Verify the SELINUX on Oracle Linux 8 is using the policy with the following command: $ sestatus | grep policy Loaded policy name: Is it the case that the loaded policy name is not "<sub idref="var_selinux_policy_name" />"? |
SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 SRG-OS-000445-GPOS-00199 |
CCI-002165 CCI-002696 |
|
xccdf_org.ssgproject.content_rule_selinux_state | medium | Ensure SELinux State is Enforcing | Setting the SELinux state to enforcing ensures SELinux is able to confine potentially compromised processes to the security policy, which is designed to prevent them from causing damage to the system or further elevating their privileges. | The SELinux state should be set to at
system boot time. In the file /etc/selinux/config , add or correct the
following line to configure the system to boot into enforcing mode:
SELINUX= |
Ensure that Oracle Linux 8 verifies correct operation of security functions. Check if "SELinux" is active and in "" mode with the following command: $ sudo getenforce Is it the case that SELINUX is not set to enforcing? |
SRG-OS-000134-GPOS-00068 SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 SRG-OS-000445-GPOS-00199 |
CCI-001084 CCI-002165 CCI-002696 |
SC-3 |
xccdf_org.ssgproject.content_rule_selinux_user_login_roles | medium | Map System Users To The Appropriate SELinux Role | 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 who 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. |
Configure the operating system to prevent non-privileged users from executing
privileged functions to include disabling, circumventing, or altering
implemented security safeguards/countermeasures. All administrators must be
mapped to the sysadm_u or staff_u users with the
appropriate domains (sysadm_t and staff_t ).
$ sudo semanage login -m -s sysadm_u USERor $ sudo semanage login -m -s staff_u USER All authorized non-administrative users must be mapped to the user_u role or the appropriate domain
(user_t).
$ sudo semanage login -m -s user_u USER |
To verify the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures, run the following command: $ sudo semanage login -l All administrators must be mapped to the sysadm_u or staff_u users with the appropriate domains (sysadm_t and staff_t). All authorized non-administrative users must be mapped to the user_u role or the appropriate domain (user_t). Is it the case that non-admin users are not confined correctly? |
SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 SRG-OS-000324-GPOS-00125 |
CCI-002165 CCI-002235 |
|
xccdf_org.ssgproject.content_rule_service_auditd_enabled | medium | Enable auditd Service | 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.
Ensuring the auditd service is active ensures audit records
generated by the kernel are appropriately recorded.
Additionally, a properly configured audit subsystem ensures that actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. |
The auditd service is an essential userspace component of
the Linux Auditing System, as it is responsible for writing audit records to
disk.
The auditd service can be enabled with the following command:
$ sudo systemctl enable auditd.service |
Run the following command to determine the current status of the auditd service: $ sudo systemctl is-active auditd If the service is running, it should return the following: active Is it the case that the auditd service is not running? |
SRG-OS-000037-GPOS-00015 SRG-OS-000038-GPOS-00016 SRG-OS-000039-GPOS-00017 SRG-OS-000040-GPOS-00018 SRG-OS-000041-GPOS-00019 SRG-OS-000042-GPOS-00020 SRG-OS-000042-GPOS-00021 SRG-OS-000051-GPOS-00024 SRG-OS-000054-GPOS-00025 SRG-OS-000064-GPOS-00033 SRG-OS-000458-GPOS-00203 SRG-OS-000461-GPOS-00205 SRG-OS-000462-GPOS-00206 SRG-OS-000463-GPOS-00207 SRG-OS-000465-GPOS-00209 SRG-OS-000466-GPOS-00210 SRG-OS-000467-GPOS-00211 SRG-OS-000468-GPOS-00212 SRG-OS-000470-GPOS-00214 SRG-OS-000471-GPOS-00215 SRG-OS-000471-GPOS-00216 SRG-OS-000472-GPOS-00217 SRG-OS-000473-GPOS-00218 SRG-OS-000474-GPOS-00219 SRG-OS-000475-GPOS-00220 SRG-OS-000476-GPOS-00221 SRG-OS-000477-GPOS-00222 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000254-GPOS-00095 SRG-OS-000255-GPOS-00096 SRG-OS-000365-GPOS-00152 SRG-OS-000348-GPOS-00136 SRG-OS-000122-GPOS-00063 SRG-OS-000349-GPOS-00137 SRG-OS-000392-GPOS-00172 SRG-OS-000350-GPOS-00138 SRG-OS-000351-GPOS-00139 SRG-OS-000352-GPOS-00140 SRG-OS-000353-GPOS-00141 SRG-OS-000354-GPOS-00142 SRG-OS-000358-GPOS-00145 SRG-OS-000337-GPOS-00129 SRG-OS-000062-GPOS-00031 |
CCI-000126 CCI-000130 CCI-000131 CCI-000132 CCI-000133 CCI-000134 CCI-000135 CCI-000154 CCI-000158 CCI-000172 CCI-000366 CCI-001464 CCI-001487 CCI-001814 CCI-001875 CCI-001876 CCI-001877 CCI-002884 CCI-001878 CCI-001879 CCI-001880 CCI-001881 CCI-001882 CCI-001889 CCI-001914 CCI-000169 |
AU-2 d AU-3 AU-3 AU-3 AU-3 AU-3 AU-3 (1) AU-6 (4) AU-7 (1) AU-12 c CM-6 b AU-14 (1) AU-3 AU-12 a |
xccdf_org.ssgproject.content_rule_service_autofs_disabled | medium | Disable the Automounter | Disabling the automounter permits the administrator to
statically control filesystem mounting through /etc/fstab .
Additionally, automatically mounting filesystems permits easy introduction of unknown devices, thereby facilitating malicious activity. |
The autofs daemon mounts and unmounts filesystems, such as user
home directories shared via NFS, on demand. In addition, autofs can be used to handle
removable media, and the default configuration provides the cdrom device as /misc/cd .
However, this method of providing access to removable media is not common, so autofs
can almost always be disabled if NFS is not in use. Even if NFS is required, it may be
possible to configure filesystem mounts statically by editing /etc/fstab
rather than relying on the automounter.
The autofs service can be disabled with the following command:
$ sudo systemctl mask --now autofs.service |
To check that the autofs service is disabled in system boot configuration, run the following command: $ sudo systemctl is-enabled autofs Output should indicate the autofs service has either not been installed, or has been disabled at all runlevels, as shown in the example below: $ sudo systemctl is-enabled autofs disabled Run the following command to verify autofs is not active (i.e. not running) through current runtime configuration: $ sudo systemctl is-active autofs If the service is not running the command will return the following output: inactive The service will also be masked, to check that the autofs is masked, run the following command: $ sudo systemctl show autofs | grep "LoadState\|UnitFileState" If the service is masked the command will return the following outputs: LoadState=masked UnitFileState=masked Is it the case that the "autofs" is loaded and not masked? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000114-GPOS-00059 SRG-OS-000378-GPOS-00163 |
CCI-000366 CCI-000778 CCI-001958 |
CM-6 b IA-3 |
xccdf_org.ssgproject.content_rule_service_debug-shell_disabled | medium | Disable debug-shell SystemD Service | This prevents attackers with physical access from trivially bypassing security on the machine through valid troubleshooting configurations and gaining root access when the system is rebooted. | SystemD's debug-shell service is intended to
diagnose SystemD related boot issues with various systemctl
commands. Once enabled and following a system reboot, the root shell
will be available on tty9 which is access by pressing
CTRL-ALT-F9 . The debug-shell service should only be used
for SystemD related issues and should otherwise be disabled.
By default, the debug-shell SystemD service is already disabled.
The debug-shell service can be disabled with the following command:
$ sudo systemctl mask --now debug-shell.service |
To check that the debug-shell service is disabled in system boot configuration, run the following command: $ sudo systemctl is-enabled debug-shell Output should indicate the debug-shell service has either not been installed, or has been disabled at all runlevels, as shown in the example below: $ sudo systemctl is-enabled debug-shell disabled Run the following command to verify debug-shell is not active (i.e. not running) through current runtime configuration: $ sudo systemctl is-active debug-shell If the service is not running the command will return the following output: inactive The service will also be masked, to check that the debug-shell is masked, run the following command: $ sudo systemctl show debug-shell | grep "LoadState\|UnitFileState" If the service is masked the command will return the following outputs: LoadState=masked UnitFileState=masked Is it the case that the "debug-shell" is loaded and not masked? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_service_fapolicyd_enabled | medium | Enable the File Access Policy Service | The fapolicyd service (File Access Policy Daemon)
implements application whitelisting to decide file access rights. |
The File Access Policy service should be enabled.
The fapolicyd service can be enabled with the following command:
$ sudo systemctl enable fapolicyd.service |
Run the following command to determine the current status of the fapolicyd service: $ sudo systemctl is-active fapolicyd If the service is running, it should return the following: active Is it the case that the service is not enabled? |
SRG-OS-000368-GPOS-00154 SRG-OS-000370-GPOS-00155 |
CCI-001764 CCI-001774 |
|
xccdf_org.ssgproject.content_rule_service_firewalld_enabled | medium | Verify firewalld Enabled | Access control methods provide the ability to enhance system security posture by restricting services and known good IP addresses and address ranges. This prevents connections from unknown hosts and protocols. |
The firewalld service can be enabled with the following command:
$ sudo systemctl enable firewalld.service |
Run the following command to determine the current status of the firewalld service: $ sudo systemctl is-active firewalld If the service is running, it should return the following: active Is it the case that the "firewalld" service is disabled, masked, or not started.? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000096-GPOS-00050 SRG-OS-000297-GPOS-00115 |
CCI-000366 CCI-000382 CCI-002314 |
CM-6 b CM-7 |
xccdf_org.ssgproject.content_rule_service_kdump_disabled | medium | Disable KDump Kernel Crash Analyzer (kdump) | Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps consume a considerable amount of disk space and may result in denial of service by exhausting the available space on the target file system partition. Unless the system is used for kernel development or testing, there is little need to run the kdump service. | The kdump service provides a kernel crash dump analyzer. It uses the kexec
system call to boot a secondary kernel ("capture" kernel) following a system
crash, which can load information from the crashed kernel for analysis.
The kdump service can be disabled with the following command:
$ sudo systemctl mask --now kdump.service |
To check that the kdump service is disabled in system boot configuration, run the following command: $ sudo systemctl is-enabled kdump Output should indicate the kdump service has either not been installed, or has been disabled at all runlevels, as shown in the example below: $ sudo systemctl is-enabled kdump disabled Run the following command to verify kdump is not active (i.e. not running) through current runtime configuration: $ sudo systemctl is-active kdump If the service is not running the command will return the following output: inactive The service will also be masked, to check that the kdump is masked, run the following command: $ sudo systemctl show kdump | grep "LoadState\|UnitFileState" If the service is masked the command will return the following outputs: LoadState=masked UnitFileState=masked Is it the case that the "kdump" is loaded and not masked? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000269-GPOS-00103 |
CCI-000366 CCI-001665 |
CM-6 b SC-24 |
xccdf_org.ssgproject.content_rule_service_rngd_enabled | low | Enable the Hardware RNG Entropy Gatherer Service | The rngd service
feeds random data from hardware device to kernel random device. |
The Hardware RNG Entropy Gatherer service should be enabled.
The rngd service can be enabled with the following command:
$ sudo systemctl enable rngd.service |
Run the following command to determine the current status of the rngd service: $ sudo systemctl is-active rngd If the service is running, it should return the following: active Is it the case that the "rngd" service is disabled, masked, or not started.? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_service_rsyslog_enabled | medium | Enable rsyslog Service | The rsyslog service must be running in order to provide
logging services, which are essential to system administration. |
The rsyslog service provides syslog-style logging by default on Oracle Linux 8.
The rsyslog service can be enabled with the following command:
$ sudo systemctl enable rsyslog.service |
Run the following command to determine the current status of the rsyslog service: $ sudo systemctl is-active rsyslog If the service is running, it should return the following: active Is it the case that the "rsyslog" service is disabled, masked, or not started.? |
SRG-OS-000205-GPOS-00083 SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-001311 CCI-001312 CCI-001557 CCI-001851 CCI-000366 |
SI-11 a SI-11 b AC-4 (17) c CM-6 b |
xccdf_org.ssgproject.content_rule_service_sshd_enabled | medium | Enable the OpenSSH Service | Without protection of the transmitted information, confidentiality, and
integrity may be compromised because unprotected communications can be
intercepted and either read or altered.
This checklist item 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, etc). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. |
The SSH server service, sshd, is commonly needed.
The sshd service can be enabled with the following command:
$ sudo systemctl enable sshd.service |
Run the following command to determine the current status of the sshd service: $ sudo systemctl is-active sshd If the service is running, it should return the following: active Is it the case that sshd service is disabled? |
SRG-OS-000423-GPOS-00187 SRG-OS-000481-GPOS-00481 SRG-OS-000425-GPOS-00189 SRG-OS-000424-GPOS-00188 SRG-OS-000426-GPOS-00190 |
CCI-002418 CCI-002420 CCI-002421 CCI-002422 |
|
xccdf_org.ssgproject.content_rule_service_systemd-coredump_disabled | medium | Disable acquiring, saving, and processing core dumps | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems. | The systemd-coredump.socket unit is a socket activation of
the systemd-coredump@.service which processes core dumps.
By masking the unit, core dump processing is disabled. |
To verify that acquiring, saving, and processing core dumps is disabled, run the following command: $ systemctl status systemd-coredump.socket The output should be similar to: â—Ź systemd-coredump.socket Loaded: masked (Reason: Unit systemd-coredump.socket is masked.) Active: inactive (dead) ... Is it the case that unit systemd-coredump.socket is not masked or running? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_service_usbguard_enabled | medium | Enable the USBGuard Service | The usbguard service must be running in order to
enforce the USB device authorization policy for all USB devices. |
The USBGuard service should be enabled.
The usbguard service can be enabled with the following command:
$ sudo systemctl enable usbguard.service |
Run the following command to determine the current status of the usbguard service: $ sudo systemctl is-active usbguard If the service is running, it should return the following: active Is it the case that the service is not enabled? |
SRG-OS-000378-GPOS-00163 |
CCI-000416 CCI-001958 |
CM-8 (3) (a) |
xccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_logindefs | medium | Set Password Hashing Algorithm in /etc/login.defs | 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. Passwords
that are encrypted with a weak algorithm are no more protected than if they are kept in plain text.
Using a stronger hashing algorithm makes password cracking attacks more difficult. |
In /etc/login.defs , add or correct the following line to ensure
the system will use SHA-512 as the hashing algorithm:
ENCRYPT_METHOD SHA512 |
Verify that the shadow password suite configuration is set to encrypt password with a FIPS 140-2 approved cryptographic hashing algorithm. Check the hashing algorithm that is being used to hash passwords with the following command: $ sudo grep -i ENCRYPT_METHOD /etc/login.defs ENCRYPT_METHOD SHA512 Is it the case that ENCRYPT_METHOD is not set to SHA512? |
SRG-OS-000073-GPOS-00041 |
CCI-000196 |
IA-5 (1) (c) |
xccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_passwordauth | medium | Set PAM''s Password Hashing Algorithm - password-auth | 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. Passwords that
are encrypted with a weak algorithm are no more protected than if they are
kepy in plain text.
This setting ensures user and group account administration utilities are configured to store only encrypted representations of passwords. Additionally, the crypt_style configuration option ensures the use
of a strong hashing algorithm that makes password cracking attacks more
difficult. |
The PAM system service can be configured to only store encrypted
representations of passwords. In
/etc/pam.d/password-auth ,
the
password section of the file controls which PAM modules execute
during a password change. Set the pam_unix.so module in the
password section to include the argument sha512 , as shown
below:
password sufficient pam_unix.so sha512 other arguments... This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default. |
Inspect the password section of /etc/pam.d/password-auth and ensure that the pam_unix.so module includes the argument sha512: $ grep sha512 /etc/pam.d/password-auth Is it the case that it does not? |
SRG-OS-000073-GPOS-00041 SRG-OS-000120-GPOS-00061 |
CCI-000196 CCI-000803 |
IA-5 (1) (c) IA-7 |
xccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_systemauth | medium | Set PAM''s Password Hashing Algorithm | 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. Passwords that
are encrypted with a weak algorithm are no more protected than if they are
kepy in plain text.
This setting ensures user and group account administration utilities are configured to store only encrypted representations of passwords. Additionally, the crypt_style configuration option ensures the use
of a strong hashing algorithm that makes password cracking attacks more
difficult. |
The PAM system service can be configured to only store encrypted
representations of passwords. In "/etc/pam.d/system-auth", the
password section of the file controls which PAM modules execute
during a password change. Set the pam_unix.so module in the
password section to include the argument sha512 , as shown
below:
password sufficient pam_unix.so sha512 other arguments... This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default. |
Inspect the password section of /etc/pam.d/system-auth and ensure that the pam_unix.so module is configured to use the argument sha512: $ sudo grep "^password.*pam_unix\.so.*sha512" /etc/pam.d/system-auth password sufficient pam_unix.so sha512 Is it the case that "sha512" is missing, or is commented out? |
SRG-OS-000073-GPOS-00041 SRG-OS-000120-GPOS-00061 |
CCI-000196 CCI-000803 |
IA-5 (1) (c) IA-7 |
xccdf_org.ssgproject.content_rule_set_password_hashing_min_rounds_logindefs | medium | Set Password Hashing Rounds in /etc/login.defs | 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. Passwords
that are encrypted with a weak algorithm are no more protected than if
they are kept in plain text.
Using more hashing rounds makes password cracking attacks more difficult. |
In /etc/login.defs , ensure SHA_CRYPT_MIN_ROUNDS and
SHA_CRYPT_MAX_ROUNDS has the minimum value of 5000 .
For example:
SHA_CRYPT_MIN_ROUNDS 5000 SHA_CRYPT_MAX_ROUNDS 5000Notice that if neither are set, they already have the default value of 5000. If either is set, they must have the minimum value of 5000. |
Inspect /etc/login.defs and ensure that if eihter SHA_CRYPT_MIN_ROUNDS or SHA_CRYPT_MAX_ROUNDS are set, they must have the minimum value of 5000. Is it the case that it does not? |
SRG-OS-000073-GPOS-00041 SRG-OS-000120-GPOS-00061 |
CCI-000196 CCI-000803 |
IA-5 (1) (c) IA-7 |
xccdf_org.ssgproject.content_rule_ssh_private_keys_have_passcode | medium | OpenSSH Service Must Use Passcode for Their Private Keys | If an unauthorized user obtains access to a private key without a passcode, that user would have unauthorized access to any system where the associated public key has been installed. | Verify the SSH private key files have a passcode.
For each private key stored on the system, use the following command:
$ sudo ssh-keygen -y -f /path/to/fileIf the contents of the key are displayed, without asking a passphrase this is a finding. |
For each private key stored on the system, use the following command: $ sudo ssh-keygen -y -f /path/to/file Is it the case that Any contents were displayed without asking a passphrase? |
SRG-OS-000067-GPOS-00035 |
CCI-000186 |
IA-5 (2) |
xccdf_org.ssgproject.content_rule_sshd_disable_compression | medium | Disable Compression Or Set Compression to delayed | If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges. | Compression is useful for slow network connections over long
distances but can cause performance issues on local LANs. If use of compression
is required, it should be enabled only after a user has authenticated; otherwise,
it should be disabled. To disable compression or delay compression until after
a user has successfully authenticated, add or correct the following line in the
/etc/ssh/sshd_config file:
Compression |
To check if compression is enabled or set correctly, run the following command: $ sudo grep Compression /etc/ssh/sshd_config If configured properly, output should be no or delayed. Is it the case that it is commented out, or is not set to no or delayed? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_disable_empty_passwords | high | Disable SSH Access via Empty Passwords | Configuring this setting for the SSH daemon provides additional assurance that remote login via SSH will require a password, even in the event of misconfiguration elsewhere. | Disallow SSH login with empty passwords.
The default SSH configuration disables logins with empty passwords. The appropriate
configuration is used if no value is set for PermitEmptyPasswords .
To explicitly disallow SSH login from accounts with empty passwords, add or correct the following line in /etc/ssh/sshd_config :
PermitEmptyPasswords noAny accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords. |
To determine how the SSH daemon's PermitEmptyPasswords option is set, run the following command: $ sudo grep -i PermitEmptyPasswords /etc/ssh/sshd_config If a line indicating no is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000106-GPOS-00053 |
CCI-000366 CCI-000766 |
CM-6 b IA-2 (2) |
xccdf_org.ssgproject.content_rule_sshd_disable_gssapi_auth | medium | Disable GSSAPI Authentication | GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, increasing the attack surface of the system. | Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like GSSAPI.
The default SSH configuration disallows authentications based on GSSAPI. The appropriate configuration is used if no value is set for GSSAPIAuthentication .
To explicitly disable GSSAPI authentication, add or correct the following line in /etc/ssh/sshd_config :
GSSAPIAuthentication no |
To determine how the SSH daemon's GSSAPIAuthentication option is set, run the following command: $ sudo grep -i GSSAPIAuthentication /etc/ssh/sshd_config If a line indicating no is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000362-GPOS-00149 SRG-OS-000364-GPOS-00151 SRG-OS-000365-GPOS-00152 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000318 CCI-000368 CCI-001812 CCI-001813 CCI-001814 CCI-000366 |
CM-3 e CM-6 c CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_disable_kerb_auth | medium | Disable Kerberos Authentication | Kerberos authentication for SSH is often implemented using GSSAPI. If Kerberos is enabled through SSH, the SSH daemon provides a means of access to the system's Kerberos implementation. Configuring these settings for the SSH daemon provides additional assurance that remote logon via SSH will not use unused methods of authentication, even in the event of misconfiguration elsewhere. | Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like Kerberos.
The default SSH configuration disallows authentication validation through Kerberos. The appropriate configuration is used if no value is set for KerberosAuthentication .
To explicitly disable Kerberos authentication, add or correct the following line in /etc/ssh/sshd_config :
KerberosAuthentication no |
To determine how the SSH daemon's KerberosAuthentication option is set, run the following command: $ sudo grep -i KerberosAuthentication /etc/ssh/sshd_config If a line indicating no is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000362-GPOS-00149 SRG-OS-000364-GPOS-00151 SRG-OS-000365-GPOS-00152 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000318 CCI-000368 CCI-001812 CCI-001813 CCI-001814 CCI-000366 |
CM-3 e CM-6 c CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_disable_root_login | medium | Disable SSH Root Login | Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging directly on as root. In addition, logging in with a user-specific account provides individual accountability of actions performed on the system and also helps to minimize direct attack attempts on root's password. | The root user should never be allowed to login to a
system directly over a network.
To disable root login via SSH, add or correct the following line in
/etc/ssh/sshd_config :
PermitRootLogin no |
To determine how the SSH daemon's PermitRootLogin option is set, run the following command: $ sudo grep -i PermitRootLogin /etc/ssh/sshd_config If a line indicating no is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000109-GPOS-00056 |
CCI-000366 CCI-000770 |
CM-6 b IA-2 (5) (b) |
xccdf_org.ssgproject.content_rule_sshd_disable_user_known_hosts | medium | Disable SSH Support for User Known Hosts | Configuring this setting for the SSH daemon provides additional assurance that remote login via SSH will require a password, even in the event of misconfiguration elsewhere. | SSH can allow system users to connect to systems if a cache of the remote
systems public keys is available. This should be disabled.
To ensure this behavior is disabled, add or correct the following line in /etc/ssh/sshd_config :
IgnoreUserKnownHosts yes |
To determine how the SSH daemon's IgnoreUserKnownHosts option is set, run the following command: $ sudo grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config If a line indicating yes is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_disable_x11_forwarding | medium | Disable X11 Forwarding | Disable X11 forwarding unless there is an operational requirement to use X11 applications directly. There is a small risk that the remote X11 servers of users who are logged in via SSH with X11 forwarding could be compromised by other users on the X11 server. Note that even if X11 forwarding is disabled, users can always install their own forwarders. | The X11Forwarding parameter provides the ability to tunnel X11 traffic
through the connection to enable remote graphic connections.
SSH has the capability to encrypt remote X11 connections when SSH's
X11Forwarding option is enabled.
The default SSH configuration disables X11Forwarding. The appropriate configuration is used if no value is set for X11Forwarding .
To explicitly disable X11 Forwarding, add or correct the following line in /etc/ssh/sshd_config :
X11Forwarding no |
To determine how the SSH daemon's X11Forwarding option is set, run the following command: $ sudo grep -i X11Forwarding /etc/ssh/sshd_config If a line indicating no is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_do_not_permit_user_env | medium | Do Not Allow SSH Environment Options | SSH environment options potentially allow users to bypass access restriction in some configurations. | Ensure that users are not able to override environment variables of the SSH daemon.
The default SSH configuration disables environment processing. The appropriate configuration is used if no value is set for PermitUserEnvironment .
To explicitly disable Environment options, add or correct the following /etc/ssh/sshd_config :
PermitUserEnvironment no |
To determine how the SSH daemon's PermitUserEnvironment option is set, run the following command: $ sudo grep -i PermitUserEnvironment /etc/ssh/sshd_config If a line indicating no is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_enable_strictmodes | medium | Enable Use of Strict Mode Checking | If other users have access to modify user-specific SSH configuration files, they may be able to log into the system as another user. | SSHs StrictModes option checks file and ownership permissions in
the user's home directory .ssh folder before accepting login. If world-
writable permissions are found, logon is rejected.
The default SSH configuration has StrictModes enabled. The appropriate
configuration is used if no value is set for StrictModes .
To explicitly enable StrictModes in SSH, add or correct the following line in
/etc/ssh/sshd_config :
StrictModes yes |
To determine how the SSH daemon's StrictModes option is set, run the following command: $ sudo grep -i StrictModes /etc/ssh/sshd_config If a line indicating yes is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_enable_warning_banner | medium | Enable SSH Warning Banner | The warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. Alternatively, systems whose ownership should not be obvious should ensure usage of a banner that does not provide easy attribution. | To enable the warning banner and ensure it is consistent
across the system, add or correct the following line in
/etc/ssh/sshd_config :
Banner /etc/issueAnother section contains information on how to create an appropriate system-wide warning banner. |
To determine how the SSH daemon's Banner option is set, run the following command: $ sudo grep -i Banner /etc/ssh/sshd_config If a line indicating /etc/issue is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000023-GPOS-00006 SRG-OS-000024-GPOS-00007 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 SRG-OS-000228-GPOS-00088 |
CCI-000048 CCI-000050 CCI-001384 CCI-001385 CCI-001386 CCI-001387 CCI-001388 |
AC-8 a AC-8 b AC-8 c AC-8 c AC-8 c AC-8 c AC-8 c |
xccdf_org.ssgproject.content_rule_sshd_print_last_log | medium | Enable SSH Print Last Log | Providing users feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use. | Ensure that SSH will display the date and time of the last successful account logon.
The default SSH configuration enables print of the date and time of the last login. The appropriate configuration is used if no value is set for PrintLastLog .
To explicitly enable LastLog in SSH, add or correct the following line in /etc/ssh/sshd_config :
PrintLastLog yes |
To determine how the SSH daemon's PrintLastLog option is set, run the following command: $ sudo grep -i PrintLastLog /etc/ssh/sshd_config If a line indicating yes is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_rekey_limit | medium | Force frequent session key renegotiation | By decreasing the limit based on the amount of data and enabling time-based limit, effects of potential attacks against encryption keys are limited. | The RekeyLimit parameter specifies how often
the session key of the is renegotiated, both in terms of
amount of data that may be transmitted and the time
elapsed.To decrease the default limits, add or correct the following line in /etc/ssh/sshd_config :
RekeyLimit |
To check if RekeyLimit is set correctly, run the following command: $ sudo grep RekeyLimit /etc/ssh/sshd_config If configured properly, output should be RekeyLimit Is it the case that it is commented out or is not set? |
SRG-OS-000033-GPOS-00014 |
CCI-000068 |
AC-17 (2) |
xccdf_org.ssgproject.content_rule_sshd_set_idle_timeout | medium | Set SSH Idle Timeout Interval | Terminating an idle ssh 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 let unattended. | SSH allows administrators to set an idle timeout interval. After this interval
has passed, the idle user will be automatically logged out.
To set an idle timeout interval, edit the following line in /etc/ssh/sshd_config as
follows:
ClientAliveInterval The timeout interval is given in seconds. For example, have a timeout of 10 minutes, set interval to 600. If a shorter timeout has already been set for the login shell, that value will preempt any SSH setting made in /etc/ssh/sshd_config . Keep in mind that
some processes may stop SSH from correctly detecting that the user is idle. |
Run the following command to see what the timeout interval is: $ sudo grep ClientAliveInterval /etc/ssh/sshd_config If properly configured, the output should be: ClientAliveInterval Is it the case that it is commented out or not configured properly? |
SRG-OS-000126-GPOS-00066 SRG-OS-000163-GPOS-00072 SRG-OS-000279-GPOS-00109 |
CCI-000879 CCI-001133 CCI-002361 |
MA-4 e SC-10 |
xccdf_org.ssgproject.content_rule_sshd_set_keepalive_0 | medium | Set SSH Client Alive Count Max to zero | This ensures a user login will be terminated as soon as the ClientAliveInterval
is reached. |
The SSH server sends at most ClientAliveCountMax messages
during a SSH session and waits for a response from the SSH client.
The option ClientAliveInterval configures timeout after
each ClientAliveCountMax message. If the SSH server does not
receive a response from the client, then the connection is considered idle
and terminated.
To ensure the SSH idle timeout occurs precisely when the
ClientAliveInterval is set, set the ClientAliveCountMax to
value of 0 in
/etc/ssh/sshd_config : |
To ensure ClientAliveInterval is set correctly, run the following command: $ sudo grep ClientAliveCountMax /etc/ssh/sshd_config If properly configured, the output should be: ClientAliveCountMax 0 In this case, the SSH idle timeout occurs precisely when the ClientAliveInterval is set. Is it the case that it is commented out or not configured properly? |
SRG-OS-000126-GPOS-00066 SRG-OS-000163-GPOS-00072 SRG-OS-000279-GPOS-00109 |
CCI-000879 CCI-001133 CCI-002361 |
MA-4 e SC-10 |
xccdf_org.ssgproject.content_rule_sshd_use_strong_rng | low | SSH server uses strong entropy to seed | SSH implementation in Oracle Linux 8 uses the openssl library, which doesn't use high-entropy sources by default. Randomness is needed to generate data-encryption keys, and as plaintext padding and initialization vectors in encryption algorithms, and high-quality entropy elliminates the possibility that the output of the random number generator used by SSH would be known to potential attackers. | To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
make sure that the file contains line
SSH_USE_STRONG_RNG=32 |
To determine whether the SSH service is configured to use strong entropy seed, run $ sudo grep SSH_USE_STRONG_RNG /etc/sysconfig/sshd If a line indicating that SSH_USE_STRONG_RNG is set to 32 is returned, then the option is set correctly. Is it the case that the SSH_USE_STRONG_RNG is not set to 32 in /etc/sysconfig/sshd? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sshd_x11_use_localhost | medium | Prevent remote hosts from connecting to the proxy display | When X11 forwarding is enabled, there may be additional exposure to the
server and client displays if the sshd proxy display is configured to listen
on the wildcard address. By default, sshd binds the forwarding server to the
loopback address and sets the hostname part of the DISPLAY
environment variable to localhost. This prevents remote hosts from
connecting to the proxy display. |
The SSH daemon should prevent remote hosts from connecting to the proxy
display.
The default SSH configuration for X11UseLocalhost is yes ,
which prevents remote hosts from connecting to the proxy display.
To explicitly prevent remote connections to the proxy display, add or correct the following line in /etc/ssh/sshd_config :
X11UseLocalhost yes
|
To determine how the SSH daemon's X11UseLocalhost option is set, run the following command: $ sudo grep -i X11UseLocalhost /etc/ssh/sshd_config If a line indicating yes is returned, then the required value is set. Is it the case that the display proxy is listening on wildcard address? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sssd_certificate_verification | medium | Certificate status checking in SSSD | Ensuring that multifactor solutions certificates are checked via Online Certificate Status Protocol (OCSP) ensures the security of the system. | 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.
Configuring certificate_verification to ocsp_dgst= ensures that certificates for
multifactor solutions are checked via Online Certificate Status Protocol (OCSP). |
Check to see if Online Certificate Status Protocol (OCSP) is enabled and using the proper digest value on the system with the following command: $ sudo grep certificate_verification /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf | grep -v "^#" If configured properly, output should look like certificate_verification = ocsp_dgst= Is it the case that certificate_verification in sssd is not configured? |
SRG-OS-000375-GPOS-00160 SRG-OS-000377-GPOS-00162 |
CCI-001948 CCI-001954 |
|
xccdf_org.ssgproject.content_rule_sssd_enable_certmap | medium | Enable Certmap in SSSD | 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. | SSSD should be configured to verify the certificate of the user or group. To set this up
ensure that section like certmap/testing.test/rule_name is setup in
/etc/sssd/sssd.conf . For example
[certmap/testing.test/rule_name] matchrule =<SAN>.*EDIPI@mil maprule = (userCertificate;binary={cert!bin}) domains = testing.test |
To verify Certmap is enabled in SSSD, run the following command: $ sudo cat /etc/sssd/sssd.conf If configured properly, output should contain section like the following [certmap/testing.test/rule_name] matchrule =<SAN>.*EDIPI@mil maprule = (userCertificate;binary={cert!bin}) domains = testing.test Is it the case that Certmap is not configured in SSSD? |
SRG-OS-000068-GPOS-00036 |
CCI-000187 |
IA-5 (2) |
xccdf_org.ssgproject.content_rule_sssd_enable_smartcards | medium | Enable Smartcards in SSSD | 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.
Multi-Factor Authentication (MFA) 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. |
SSSD should be configured to authenticate access to the system using smart cards.
To enable smart cards in SSSD, set pam_cert_auth to True under the
[pam] section in /etc/sssd/sssd.conf . For example:
[pam] pam_cert_auth = TrueAdd or update "pam_sss.so" line in auth section of "/etc/pam.d/system-auth" file to include "try_cert_auth" or "require_cert_auth" option, like in the following example: /etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_authAlso add or update "pam_sss.so" line in auth section of "/etc/pam.d/smartcard-auth" file to include the "allow_missing_name" option, like in the following example: /etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name |
To verify that smart cards are enabled in SSSD, run the following command: $ sudo grep pam_cert_auth /etc/sssd/sssd.conf If configured properly, output should be pam_cert_auth = True To verify that smart cards are enabled in PAM files, run the following command: $ sudo grep -e "auth.*pam_sss\.so.*\(allow_missing_name\|try_cert_auth\)" /etc/pam.d/smartcard-auth /etc/pam.d/system-auth If configured properly, output should be /etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name /etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth Is it the case that smart cards are not enabled in SSSD? |
SRG-OS-000377-GPOS-00162 SRG-OS-000105-GPOS-00052 SRG-OS-000106-GPOS-00053 SRG-OS-000107-GPOS-00054 SRG-OS-000108-GPOS-00055 |
CCI-001954 CCI-000765 CCI-000766 CCI-000767 CCI-000768 |
IA-2 (1) IA-2 (2) IA-2 (3) IA-2 (4) |
xccdf_org.ssgproject.content_rule_sssd_has_trust_anchor | medium | SSSD Has a Correct Trust Anchor | Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is 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. | SSSD must have acceptable trust anchor present. | Verify Oracle Linux 8 for PKI-based authentication has valid certificates by constructing a certification path (which includes status information) to an accepted trust anchor. Check that the system has a valid DoD root CA installed with the following command: $ sudo openssl x509 -text -in /etc/sssd/pki/sssd_auth_ca_db.pem Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha256WithRSAEncryption Issuer: C = US, O = U.S. Government, OU = DoD, OU = PKI, CN = DoD Root CA 3 Validity Not Before: Mar 20 18:46:41 2012 GMT Not After : Dec 30 18:46:41 2029 GMT Subject: C = US, O = U.S. Government, OU = DoD, OU = PKI, CN = DoD Root CA 3 Subject Public Key Info: Public Key Algorithm: rsaEncryption Is it the case that root CA file is not a DoD-issued certificate with a valid date and installed in the /etc/sssd/pki/sssd_auth_ca_db.pem location? |
SRG-OS-000066-GPOS-00034 |
CCI-000185 |
IA-5 (2) |
xccdf_org.ssgproject.content_rule_sssd_offline_cred_expiration | medium | Configure SSSD to Expire Offline Credentials | If cached authentication information is out-of-date, the validity of the authentication information may be questionable. | SSSD should be configured to expire offline credentials after 1 day.
Check if SSSD allows cached authentications with the following command:
$ sudo grep cache_credentials /etc/sssd/sssd.conf cache_credentials = trueIf "cache_credentials" is set to "false" or is missing no further checks are required. To configure SSSD to expire offline credentials, set offline_credentials_expiration to 1 under the [pam]
section in /etc/sssd/sssd.conf . For example:
[pam] offline_credentials_expiration = 1 |
Check if SSSD allows cached authentications with the following command: $ sudo grep cache_credentials /etc/sssd/sssd.conf cache_credentials = true If "cache_credentials" is set to "false" or is missing no further checks are required. To verify that SSSD expires offline credentials, run the following command: $ sudo grep offline_credentials_expiration /etc/sssd/sssd.conf If configured properly, output should be offline_credentials_expiration = 1 Is it the case that it does not exist or is not configured properly? |
SRG-OS-000383-GPOS-00166 |
CCI-002007 |
|
xccdf_org.ssgproject.content_rule_sudo_remove_no_authenticate | medium | Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate | 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 that the user re-authenticate. |
The sudo !authenticate option, when specified, allows a user to execute commands using
sudo without having to authenticate. This should be disabled by making sure that the
!authenticate option does not exist in /etc/sudoers configuration file or
any sudo configuration snippets in /etc/sudoers.d/ . |
To determine if !authenticate has not been configured for sudo, run the following command: $ sudo grep -r \!authenticate /etc/sudoers /etc/sudoers.d/ The command should return no output. Is it the case that !authenticate is specified in the sudo config files? |
SRG-OS-000373-GPOS-00156 SRG-OS-000373-GPOS-00157 SRG-OS-000373-GPOS-00158 |
CCI-002038 |
|
xccdf_org.ssgproject.content_rule_sudo_remove_nopasswd | medium | Ensure Users Re-Authenticate for Privilege Escalation - sudo NOPASSWD | 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 that the user re-authenticate. |
The sudo NOPASSWD tag, when specified, allows a user to execute
commands using sudo without having to authenticate. This should be disabled
by making sure that the NOPASSWD tag does not exist in
/etc/sudoers configuration file or any sudo configuration snippets
in /etc/sudoers.d/ . |
To determine if NOPASSWD has been configured for sudo, run the following command: $ sudo grep -ri nopasswd /etc/sudoers /etc/sudoers.d/ The command should return no output. Is it the case that nopasswd is specified in the sudo config files? |
SRG-OS-000373-GPOS-00156 SRG-OS-000373-GPOS-00157 SRG-OS-000373-GPOS-00158 |
CCI-002038 |
|
xccdf_org.ssgproject.content_rule_sudo_require_reauthentication | medium | The operating system must require Re-Authentication when using the sudo command. Ensure sudo timestamp_timeout is appropriate - sudo timestamp_timeout | 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 that the user re-authenticate. |
The sudo timestamp_timeout tag sets the amount of time sudo password prompt waits.
The default timestamp_timeout value is 5 minutes.
The timestamp_timeout should be configured by making sure that the
timestamp_timeout tag exists in
/etc/sudoers configuration file or any sudo configuration snippets
in /etc/sudoers.d/ .
If the value is set to an integer less than 0, the user's time stamp will not expire
and the user will not have to re-authenticate for privileged actions until the user's session is terminated. |
Verify the operating system requires re-authentication when using the "sudo" command to elevate privileges, run the following command: sudo grep -ri '^Defaults.*timestamp_timeout' /etc/sudoers /etc/sudoers.d The output should be: /etc/sudoers:Defaults timestamp_timeout=0 or "timestamp_timeout" is set to a positive number. If conflicting results are returned, this is a finding. Is it the case that timestamp_timeout is not set with the appropriate value for sudo? |
SRG-OS-000373-GPOS-00156 SRG-OS-000373-GPOS-00157 SRG-OS-000373-GPOS-00158 |
CCI-002038 |
|
xccdf_org.ssgproject.content_rule_sudo_restrict_privilege_elevation_to_authorized | medium | The operating system must restrict privilege elevation to authorized personnel | If the "sudoers" file is not configured correctly, any user defined on the system can initiate privileged actions on the target system. | The sudo command allows a user to execute programs with elevated
(administrator) privileges. It prompts the user for their password
and confirms your request to execute a command by checking a file,
called sudoers.
Restrict privileged actions by removing the following entries from the sudoers file:
ALL ALL=(ALL) ALL
ALL ALL=(ALL:ALL) ALL
|
Determine if "sudoers" file restricts sudo access run the following commands: $ sudo grep -PR '^\s*ALL\s+ALL\=\(ALL\)\s+ALL\s*$' /etc/sudoers /etc/sudoers.d/* $ sudo grep -PR '^\s*ALL\s+ALL\=\(ALL\:ALL\)\s+ALL\s*$' /etc/sudoers /etc/sudoers.d/* Is it the case that either of the commands returned a line? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sudoers_default_includedir | medium | Ensure sudo only includes the default configuration directory | Some sudo configurtion options allow users to run programs without re-authenticating.
Use of these configuration options makes it easier for one compromised accound to be used to
compromise other accounts. |
Administrators can configure authorized sudo users via drop-in files, and it is possible to include
other directories and configuration files from the file currently being parsed.
Make sure that /etc/sudoers only includes drop-in configuration files from /etc/sudoers.d ,
or that no drop-in file is included.
Either the /etc/sudoers should contain only one #includedir directive pointing to
/etc/sudoers.d , and no file in /etc/sudoers.d/ should include other files or directories;
Or the /etc/sudoers should not contain any #include ,
@include , #includedir or @includedir directives.
Note that the '#' character doesn't denote a comment in the configuration file. |
To determine whether sudo command includes configuration files from the appropriate directory, run the following command: $ sudo grep -rP '^[#@]include(dir)?' /etc/sudoers /etc/sudoers.d If only the line /etc/sudoers:#includedir /etc/sudoers.d is returned, then the drop-in include configuration is set correctly. Any other line returned is a finding. Is it the case that the /etc/sudoers doesn't include /etc/sudores.d or includes other directories?? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sudoers_validate_passwd | medium | Ensure invoking users password for privilege escalation when using sudo | If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt the invoking user for the "root" user password. | The sudoers security policy requires that users authenticate themselves before they can use sudo.
When sudoers requires authentication, it validates the invoking user's credentials.
The expected output for:
sudo cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)$' Defaults !targetpw Defaults !rootpw Defaults !runaspwor if cvtsudoers not supported: sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \; /etc/sudoers:Defaults !targetpw /etc/sudoers:Defaults !rootpw /etc/sudoers:Defaults !runaspw |
Run the following command to Verify that the sudoers security policy is configured to use the invoking user's password for privilege escalation: sudo cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)' or if cvtsudoers not supported: sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \; If no results are returned, this is a finding. If conflicting results are returned, this is a finding. If "Defaults !targetpw" is not defined, this is a finding. If "Defaults !rootpw" is not defined, this is a finding. If "Defaults !runaspw" is not defined, this is a finding. Is it the case that invoke user passwd when using sudo? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-002227 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_crypto_fips_enabled | high | Set kernel parameter 'crypto.fips_enabled' to 1 | 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. | System running in FIPS mode is indicated by kernel parameter
'crypto.fips_enabled' . This parameter should be set to 1 in FIPS mode.
To enable FIPS mode, run the following command:
fips-mode-setup --enableTo enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot parameters during system installation so key generation is done with FIPS-approved algorithms and continuous monitoring tests in place. |
To verify that kernel parameter 'crypto.fips_enabled' is set properly, run the following command: sysctl crypto.fips_enabled The output should contain the following: crypto.fips_enabled = 1 Is it the case that crypto.fips_enabled is not 1? |
SRG-OS-000033-GPOS-00014 SRG-OS-000120-GPOS-00061 SRG-OS-000125-GPOS-00065 SRG-OS-000250-GPOS-00093 SRG-OS-000423-GPOS-00187 SRG-OS-000481-GPOS-00481 SRG-OS-000396-GPOS-00176 SRG-OS-000478-GPOS-00223 SRG-OS-000393-GPOS-00173 SRG-OS-000394-GPOS-00174 |
CCI-000068 CCI-000803 CCI-000877 CCI-001453 CCI-002418 CCI-002450 CCI-002890 CCI-003123 |
AC-17 (2) IA-7 MA-4 c AC-17 (2) |
xccdf_org.ssgproject.content_rule_sysctl_fs_protected_hardlinks | medium | Enable Kernel Parameter to Enforce DAC on Hardlinks | By enabling this kernel parameter, users can no longer create soft or hard links to
files which they do not own. Disallowing such hardlinks mitigate vulnerabilities
based on insecure file system accessed by privileged programs, avoiding an
exploitation vector exploiting unsafe use of open() or creat() . |
To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : fs.protected_hardlinks = 1 |
The runtime status of the fs.protected_hardlinks kernel parameter can be queried by running the following command: $ sysctl fs.protected_hardlinks 1. Is it the case that the correct value is not returned? |
SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 |
CCI-002165 |
|
xccdf_org.ssgproject.content_rule_sysctl_fs_protected_symlinks | medium | Enable Kernel Parameter to Enforce DAC on Symlinks | By enabling this kernel parameter, symbolic links are permitted to be followed
only when outside a sticky world-writable directory, or when the UID of the
link and follower match, or when the directory owner matches the symlink's owner.
Disallowing such symlinks helps mitigate vulnerabilities based on insecure file system
accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of
open() or creat() . |
To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : fs.protected_symlinks = 1 |
The runtime status of the fs.protected_symlinks kernel parameter can be queried by running the following command: $ sysctl fs.protected_symlinks 1. Is it the case that the correct value is not returned? |
SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 |
CCI-002165 |
|
xccdf_org.ssgproject.content_rule_sysctl_kernel_core_pattern | medium | Disable storing core dumps | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems. | To set the runtime status of the kernel.core_pattern kernel parameter, run the following command: $ sudo sysctl -w kernel.core_pattern=|/bin/falseTo make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.core_pattern = |/bin/false |
The runtime status of the kernel.core_pattern kernel parameter can be queried by running the following command: $ sysctl kernel.core_pattern |/bin/false. Is it the case that the returned line does not have a value of "|/bin/false", or a line is not returned and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_kernel_dmesg_restrict | low | Restrict Access to Kernel Message Buffer | Unprivileged access to the kernel syslog can expose sensitive kernel address information. | To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.dmesg_restrict=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.dmesg_restrict = 1 |
The runtime status of the kernel.dmesg_restrict kernel parameter can be queried by running the following command: $ sysctl kernel.dmesg_restrict 1. Is it the case that the correct value is not returned? |
SRG-OS-000138-GPOS-00069 SRG-OS-000206-GPOS-00084 |
CCI-001090 CCI-001314 |
SC-4 SI-11 c |
xccdf_org.ssgproject.content_rule_sysctl_kernel_kexec_load_disabled | medium | Disable Kernel Image Loading | Disabling kexec_load allows greater control of the kernel memory. It makes it impossible to load another kernel image after it has been disabled. | To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.kexec_load_disabled=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.kexec_load_disabled = 1 |
The runtime status of the kernel.kexec_load_disabled kernel parameter can be queried by running the following command: $ sysctl kernel.kexec_load_disabled 1. Is it the case that the correct value is not returned? |
SRG-OS-000366-GPOS-00153 |
CCI-001749 |
|
xccdf_org.ssgproject.content_rule_sysctl_kernel_kptr_restrict | medium | Restrict Exposed Kernel Pointer Addresses Access | Exposing kernel pointers (through procfs or seq_printf() ) exposes kernel
writeable structures which may contain functions pointers. If a write vulnerability
occurs in the kernel, allowing write access to any of this structure, the kernel can
be compromised. This option disallow any program without the CAP_SYSLOG capability
to get the addresses of kernel pointers by replacing them with 0. |
To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.kptr_restrict = |
The runtime status of the kernel.kptr_restrict kernel parameter can be queried by running the following command: $ sysctl kernel.kptr_restrict The output of the command should indicate either: kernel.kptr_restrict = 1 or: kernel.kptr_restrict = 2 The output of the command should not indicate: kernel.kptr_restrict = 0 The preferable way how to assure the runtime compliance is to have correct persistent configuration, and rebooting the system. The persistent kernel parameter configuration is performed by specifying the appropriate assignment in any file located in the /etc/sysctl.d directory. Verify that there is not any existing incorrect configuration by executing the following command: $ grep -r '^\s*kernel.kptr_restrict\s*=' /etc/sysctl.conf /etc/sysctl.d The command should not find any assignments other than: kernel.kptr_restrict = 1 or: kernel.kptr_restrict = 2 Conflicting assignments are not allowed. Is it the case that the kernel.kptr_restrict is not set to 1 or 2 or is configured to be 0? |
SRG-OS-000433-GPOS-00192 SRG-OS-000433-GPOS-00193 SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-002824 CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_kernel_perf_event_paranoid | low | Disallow kernel profiling by unprivileged users | Kernel profiling can reveal sensitive information about kernel behaviour. | To set the runtime status of the kernel.perf_event_paranoid kernel parameter, run the following command: $ sudo sysctl -w kernel.perf_event_paranoid=2To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.perf_event_paranoid = 2 |
The runtime status of the kernel.perf_event_paranoid kernel parameter can be queried by running the following command: $ sysctl kernel.perf_event_paranoid 2. Is it the case that the correct value is not returned? |
SRG-OS-000138-GPOS-00069 |
CCI-001090 |
SC-4 |
xccdf_org.ssgproject.content_rule_sysctl_kernel_randomize_va_space | medium | Enable Randomized Layout of Virtual Address Space | Address space layout randomization (ASLR) makes it more difficult for an attacker to predict the location of attack code they have introduced into a process's address space during an attempt at exploitation. Additionally, ASLR makes it more difficult for an attacker to know the location of existing code in order to re-purpose it using return oriented programming (ROP) techniques. | To set the runtime status of the kernel.randomize_va_space kernel parameter, run the following command: $ sudo sysctl -w kernel.randomize_va_space=2To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.randomize_va_space = 2 |
The runtime status of the kernel.randomize_va_space kernel parameter can be queried by running the following command: $ sysctl kernel.randomize_va_space 2. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 SRG-OS-000433-GPOS-00192 SRG-OS-000433-GPOS-00193 |
CCI-000366 CCI-002824 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_kernel_unprivileged_bpf_disabled | medium | Disable Access to Network bpf() Syscall From Unprivileged Processes | Loading and accessing the packet filters programs and maps using the bpf() syscall has the potential of revealing sensitive information about the kernel state. | To set the runtime status of the kernel.unprivileged_bpf_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.unprivileged_bpf_disabled=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.unprivileged_bpf_disabled = 1 |
The runtime status of the kernel.unprivileged_bpf_disabled kernel parameter can be queried by running the following command: $ sysctl kernel.unprivileged_bpf_disabled 1. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_kernel_yama_ptrace_scope | medium | Restrict usage of ptrace to descendant processes | Unrestricted usage of ptrace allows compromised binaries to run ptrace on another processes of the user. Like this, the attacker can steal sensitive information from the target processes (e.g. SSH sessions, web browser, ...) without any additional assistance from the user (i.e. without resorting to phishing). | To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : kernel.yama.ptrace_scope = 1 |
The runtime status of the kernel.yama.ptrace_scope kernel parameter can be queried by running the following command: $ sysctl kernel.yama.ptrace_scope 1. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_core_bpf_jit_harden | medium | Harden the operation of the BPF just-in-time compiler | When hardened, the extended Berkeley Packet Filter just-in-time compiler
will randomize any kernel addresses in the BPF programs and maps,
and will not expose the JIT addresses in /proc/kallsyms . |
To set the runtime status of the net.core.bpf_jit_harden kernel parameter, run the following command: $ sudo sysctl -w net.core.bpf_jit_harden=2To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.core.bpf_jit_harden = 2 |
The runtime status of the net.core.bpf_jit_harden kernel parameter can be queried by running the following command: $ sysctl net.core.bpf_jit_harden 2. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_accept_redirects | medium | Disable Accepting ICMP Redirects for All IPv4 Interfaces | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages modify the
host's route table and are unauthenticated. An illicit ICMP redirect
message could result in a man-in-the-middle attack.
This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless absolutely required." |
To set the runtime status of the net.ipv4.conf.all.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.conf.all.accept_redirects = 0 |
The runtime status of the net.ipv4.conf.all.accept_redirects kernel parameter can be queried by running the following command: $ sysctl net.ipv4.conf.all.accept_redirects 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001503 CCI-001551 |
CM-6 b CM-6 d AC-4 |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_accept_source_route | medium | Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv4 Interfaces | Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router,
which can be used to bypass network security measures. This requirement
applies only to the forwarding of source-routerd traffic, such as when IPv4
forwarding is enabled and the system is functioning as a router.
Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
To set the runtime status of the net.ipv4.conf.all.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.conf.all.accept_source_route = 0 |
The runtime status of the net.ipv4.conf.all.accept_source_route kernel parameter can be queried by running the following command: $ sysctl net.ipv4.conf.all.accept_source_route 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_rp_filter | medium | Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces | Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface they were received on. It should not be used on systems which are routers for complicated networks, but is helpful for end hosts and routers serving small networks. | To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.conf.all.rp_filter = 1 |
The runtime status of the net.ipv4.conf.all.rp_filter parameter can be queried by running the following command: $ sysctl net.ipv4.conf.all.rp_filter The output of the command should indicate either: net.ipv4.conf.all.rp_filter = 1 or: net.ipv4.conf.all.rp_filter = 2 The output of the command should not indicate: net.ipv4.conf.all.rp_filter = 0 The preferable way how to assure the runtime compliance is to have correct persistent configuration, and rebooting the system. The persistent sysctl parameter configuration is performed by specifying the appropriate assignment in any file located in the /etc/sysctl.d directory. Verify that there is not any existing incorrect configuration by executing the following command: $ grep -r '^\s*net.ipv4.conf.all.rp_filter\s*=' /etc/sysctl.conf /etc/sysctl.d The command should not find any assignments other than: net.ipv4.conf.all.rp_filter = 1 or: net.ipv4.conf.all.rp_filter = 2 Conflicting assignments are not allowed. Is it the case that the net.ipv4.conf.all.rp_filter is not set to 1 or 2 or is configured to be 0? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001551 |
CM-6 b AC-4 |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_send_redirects | medium | Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.
The ability to send ICMP redirects is only appropriate for systems acting as routers. |
To set the runtime status of the net.ipv4.conf.all.send_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.send_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.conf.all.send_redirects = 0 |
The runtime status of the net.ipv4.conf.all.send_redirects kernel parameter can be queried by running the following command: $ sysctl net.ipv4.conf.all.send_redirects 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_accept_redirects | medium | Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv4 Interfaces | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages modify the
host's route table and are unauthenticated. An illicit ICMP redirect
message could result in a man-in-the-middle attack.
This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless absolutely required. |
To set the runtime status of the net.ipv4.conf.default.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.conf.default.accept_redirects = 0 |
The runtime status of the net.ipv4.conf.default.accept_redirects kernel parameter can be queried by running the following command: $ sysctl net.ipv4.conf.default.accept_redirects 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001551 |
CM-6 b AC-4 |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_accept_source_route | medium | Disable Kernel Parameter for Accepting Source-Routed Packets on IPv4 Interfaces by Default | Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router,
which can be used to bypass network security measures.
Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required, such as when IPv4 forwarding is enabled and the system is legitimately functioning as a router. |
To set the runtime status of the net.ipv4.conf.default.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.conf.default.accept_source_route = 0 |
The runtime status of the net.ipv4.conf.default.accept_source_route kernel parameter can be queried by running the following command: $ sysctl net.ipv4.conf.default.accept_source_route 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001551 |
CM-6 b AC-4 |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_send_redirects | medium | Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces by Default | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.
The ability to send ICMP redirects is only appropriate for systems acting as routers. |
To set the runtime status of the net.ipv4.conf.default.send_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.send_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.conf.default.send_redirects = 0 |
The runtime status of the net.ipv4.conf.default.send_redirects kernel parameter can be queried by running the following command: $ sysctl net.ipv4.conf.default.send_redirects 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_icmp_echo_ignore_broadcasts | medium | Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests on IPv4 Interfaces | Responding to broadcast (ICMP) echoes facilitates network mapping
and provides a vector for amplification attacks.
Ignoring ICMP echo requests (pings) sent to broadcast or multicast addresses makes the system slightly more difficult to enumerate on the network. |
To set the runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.icmp_echo_ignore_broadcasts = 1 |
The runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter can be queried by running the following command: $ sysctl net.ipv4.icmp_echo_ignore_broadcasts 1. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_ip_forward | medium | Disable Kernel Parameter for IP Forwarding on IPv4 Interfaces | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this capability is used when not required, system network information may be unnecessarily transmitted across the network. | To set the runtime status of the net.ipv4.ip_forward kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.ip_forward=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.ip_forward = 0 |
The runtime status of the net.ipv4.ip_forward kernel parameter can be queried by running the following command: $ sysctl net.ipv4.ip_forward 0. The ability to forward packets is only appropriate for routers. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_ra | medium | Configure Accepting Router Advertisements on All IPv6 Interfaces | An illicit router advertisement message could result in a man-in-the-middle attack. | To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv6.conf.all.accept_ra = 0 |
The runtime status of the net.ipv6.conf.all.accept_ra kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.all.accept_ra 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_redirects | medium | Disable Accepting ICMP Redirects for All IPv6 Interfaces | An illicit ICMP redirect message could result in a man-in-the-middle attack. | To set the runtime status of the net.ipv6.conf.all.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv6.conf.all.accept_redirects = 0 |
The runtime status of the net.ipv6.conf.all.accept_redirects kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.all.accept_redirects 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001551 |
CM-6 b AC-4 |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_source_route | medium | Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv6 Interfaces | Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and
the system is functioning as a router.
Accepting source-routed packets in the IPv6 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
To set the runtime status of the net.ipv6.conf.all.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv6.conf.all.accept_source_route = 0 |
The runtime status of the net.ipv6.conf.all.accept_source_route kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.all.accept_source_route 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_forwarding | medium | Disable Kernel Parameter for IPv6 Forwarding | IP forwarding permits the kernel to forward packets from one network interface to another. The ability to forward packets between two networks is only appropriate for systems acting as routers. | To set the runtime status of the net.ipv6.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.forwarding=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv6.conf.all.forwarding = 0 |
The runtime status of the net.ipv6.conf.all.forwarding kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.all.forwarding 0. The ability to forward packets is only appropriate for routers. Is it the case that IP forwarding value is "1" and the system is not router? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_ra | medium | Disable Accepting Router Advertisements on all IPv6 Interfaces by Default | An illicit router advertisement message could result in a man-in-the-middle attack. | To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv6.conf.default.accept_ra = 0 |
The runtime status of the net.ipv6.conf.default.accept_ra kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.default.accept_ra 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_redirects | medium | Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv6 Interfaces | An illicit ICMP redirect message could result in a man-in-the-middle attack. | To set the runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv6.conf.default.accept_redirects = 0 |
The runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.default.accept_redirects 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 CCI-001551 |
CM-6 b AC-4 |
xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_source_route | medium | Disable Kernel Parameter for Accepting Source-Routed Packets on IPv6 Interfaces by Default | Source-routed packets allow the source of the packet to suggest routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and the system is functioning as a router. Accepting source-routed packets in the IPv6 protocol has few legitimate uses. It should be disabled unless it is absolutely required. | To set the runtime status of the net.ipv6.conf.default.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv6.conf.default.accept_source_route = 0 |
The runtime status of the net.ipv6.conf.default.accept_source_route kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.default.accept_source_route 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces | medium | Disable the use of user namespaces | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or system 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. User namespaces are used primarily for Linux containers. The value 0 disallows the use of user namespaces. | To set the runtime status of the user.max_user_namespaces kernel parameter,
run the following command:
$ sudo sysctl -w user.max_user_namespaces=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d :
user.max_user_namespaces = 0When containers are deployed on the machine, the value should be set to large non-zero value. |
Verify that Oracle Linux 8 disables the use of user namespaces with the following commands: Note: User namespaces are used primarily for Linux containers. If containers are in use, this requirement is not applicable. The runtime status of the user.max_user_namespaces kernel parameter can be queried by running the following command: $ sysctl user.max_user_namespaces 0. Is it the case that the correct value is not returned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_tftpd_uses_secure_mode | high | Ensure tftp Daemon Uses Secure Mode | Using the -s option causes the TFTP service to only serve files from the
given directory. Serving files from an intentionally-specified directory
reduces the risk of sharing files which should remain private. |
If running the tftp service is necessary, it should be configured
to change its root directory at startup. To do so, ensure
/etc/xinetd.d/tftp includes -s as a command line argument, as shown in
the following example:
server_args = -s |
If TFTP is not installed, this is not applicable. To determine if TFTP is installed, run the following command: $ rpm -qa | grep tftp Verify tftp is configured by with the -s option by running the following command: grep "server_args" /etc/xinetd.d/tftp server_args = -s Is it the case that "server_args" line does not have a "-s" option, and a subdirectory is not assigned? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_usbguard_generate_policy | medium | Generate USBGuard Policy | The usbguard must be configured to allow connected USB devices to work
properly, avoiding the system to become inaccessible. |
By default USBGuard when enabled prevents access to all USB devices and this lead to inaccessible system if they use USB mouse/keyboard. To prevent this scenario, the initial policy configuration must be generated based on current connected USB devices. | Verify the USBGuard has a policy configured with the following command: $ sudo usbguard list-rules If the command does not return results or an error is returned, ask the SA to indicate how unauthorized peripherals are being blocked. Is it the case that there is no evidence that unauthorized peripherals are being blocked before establishing a connection? |
SRG-OS-000378-GPOS-00163 |
CCI-000416 CCI-001958 |
CM-8 (3) (a) |
xccdf_org.ssgproject.content_rule_vlock_installed | medium | Check that vlock is installed to allow session locking | 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 must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system. | The Oracle Linux 8 operating system must have vlock installed to allow for session locking.
The kbd package can be installed with the following command:
$ sudo yum install kbd |
Run the following command to determine if the kbd package is installed: $ rpm -q kbd Is it the case that the package is not installed? |
SRG-OS-000028-GPOS-00009 SRG-OS-000030-GPOS-00011 SRG-OS-000031-GPOS-00012 |
CCI-000056 CCI-000058 CCI-000060 |
AC-11 b AC-11 a AC-11 (1) |
xccdf_org.ssgproject.content_rule_wireless_disable_interfaces | medium | Deactivate Wireless Network Interfaces | The use of wireless networking can introduce many different attack vectors into the organization's network. Common attack vectors such as malicious association and ad hoc networks will allow an attacker to spoof a wireless access point (AP), allowing validated systems to connect to the malicious AP and enabling the attacker to monitor and record network traffic. These malicious APs can also serve to create a man-in-the-middle attack or be used to create a denial of service to valid network resources. | Deactivating wireless network interfaces should prevent normal usage of the wireless
capability.
Configure the system to disable all wireless network interfaces with the following command: $ sudo nmcli radio all off |
Verify that there are no wireless interfaces configured on the system with the following command: $ sudo nmcli device The output should only contain wireless devices in unavailable state, like in the following example: wlp0s20f3 wifi unavailable -- Is it the case that wireless interfaces are not active? |
SRG-OS-000423-GPOS-00187 SRG-OS-000481-GPOS-00481 SRG-OS-000424-GPOS-00188 SRG-OS-000300-GPOS-00118 SRG-OS-000299-GPOS-00117 |
CCI-000085 CCI-002418 CCI-002421 CCI-001443 CCI-001444 |
AC-19 c AC-18 (1) AC-18 (1) |
xccdf_org.ssgproject.content_rule_xwindows_remove_packages | medium | Disable graphical user interface | Unnecessary service packages must not be installed to decrease the attack surface of the system. X windows has a long history of security vulnerabilities and should not be installed unless approved and documented. | By removing the following packages, the system no longer has X Windows installed.
xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
If X Windows is not installed then the system cannot boot into graphical user mode.
This prevents the system from being accidentally or maliciously booted into a graphical.target
mode. To do so, run the following command:
sudo yum remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland |
To ensure the X Windows package group is removed, run the following command: $ rpm -qi xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland For each package mentioned above you should receive following line: package <package> is not installed Is it the case that xorg related packages are not removed and run level is not correctly configured? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |
xccdf_org.ssgproject.content_rule_xwindows_runlevel_target | medium | Disable X Windows Startup By Setting Default Target | Services that are not required for system and application processes must not be active to decrease the attack surface of the system. X windows has a long history of security vulnerabilities and should not be used unless approved and documented. | Systems that do not require a graphical user interface should only boot by
default into multi-user.target mode. This prevents accidental booting of the system
into a graphical.target mode. Setting the system's default target to
multi-user.target will prevent automatic startup of the X server. To do so, run:
$ systemctl set-default multi-user.targetYou should see the following output: Removed symlink /etc/systemd/system/default.target. Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target. |
Verify the default target is multi-user, run the following command: $ systemctl get-default multi-user.target Is it the case that the system default target is not set to "multi-user.target" and the Information System Security Officer (ISSO) lacks a documented requirement for a graphical user interface? |
SRG-OS-000360-GPOS-00147 SRG-OS-000480-GPOS-00225 SRG-OS-000480-GPOS-00226 SRG-OS-000480-GPOS-00227 SRG-OS-000480-GPOS-00228 SRG-OS-000480-GPOS-00229 SRG-OS-000480-GPOS-00230 SRG-OS-000480-GPOS-00232 |
CCI-000366 |
CM-6 b |