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_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_admin | medium | Never Automatically Remove or Disable Emergency Administrator Accounts | Emergency accounts are different from infrequently used accounts (i.e., local logon accounts used by the organization's system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. To address access requirements the SUSE operating system can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements. | Emergency accounts are privileged accounts that are established in response
to crisis situations where the need for rapid account activation is
required. Therefore, emergency account activation may bypass normal account
authorization processes. If these accounts are automatically disabled,
system maintenance during emergencies may not be possible, thus adversely
affecting system availability.
Check to see if an emergency administrator account password or account expires with the following command:
# sudo chage -l [Emergency_Administrator] Password expires:neverIf Password expires or Account expires is set to anything other than never , this is a finding. |
Check to see if an emergency administrator account password or account expires with the following command: # sudo chage -l [Emergency_Administrator] Password expires:never If Password expires or Account expires is set to anything other than never, this is a finding. Is it the case that any emergency administrator account or account password has an expiration date set? |
SRG-OS-000123-GPOS-00064 |
CCI-001682 |
AC-2 (2) |
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 SUSE Linux Enterprise 15 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_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 SUSE Linux Enterprise 15 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_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_pam_unix_remember | medium | Limit Password Reuse | 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_unix or pam_pwhistory PAM modules. |
To verify the password reuse setting is compliant, run the following command: $ grep remember /etc/pam.d/system-auth The output should show the following at the end of the line: remember= Is it the case that the value of remember is not equal to or greater than the expected value? |
SRG-OS-000077-GPOS-00045 |
CCI-000200 |
IA-5 (1) (e) |
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_faildelay_delay | medium | Enforce Delay After Failed Logon Attempts | Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account. | To configure the system to introduce a delay after failed logon attempts,
add or correct the pam_faildelay settings in
/etc/pam.d/common-auth to make sure its delay parameter
is at least or greater. For example:
auth required pam_faildelay.so delay= |
Verify that the SUSE Linux Enterprise 15 operating system enforces a minimum delay betweeen logon prompts following a failed logon attempt. # grep pam_faildelay /etc/pam.d/common-auth auth required pam_faildelay.so delay= If the value of delay is not set to or greater, "delay" is commented out, "delay" is missing, or the "pam_faildelay" line is missing completely, this is a finding. Is it the case that the value of delay is not set properly or the line is commented or missing? |
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_passwords_pam_tally2 | medium | Set Deny 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-force
attacks, is reduced. Limits are imposed by locking the account.
To configure the operating system to lock an account after three
unsuccessful consecutive access attempts using pam_tally2.so ,
modify the content of both /etc/pam.d/common-auth and
/etc/pam.d/common-account as follows:
|
The SUSE Linux Enterprise 15 operating system must lock an account after - at most - consecutive invalid access attempts. | Check that the systems locks a user account after - at most - consecutive failed login attempts with the following command: # grep pam_tally2.so /etc/pam.d/common-auth auth required pam_tally2.so onerr=fail deny= If no line is returned, the line is commented out, or the line is missing "onerr=fail", this is a finding. If the line has "deny" set to a value outside of the range 1-, this is a finding. Check that the system resets the failed login attempts counter after a successful login using the following command: # grep pam_tally2.so /etc/pam.d/common-account account required pam_tally2.so deny= If the account option is missing, or commented out, this is a finding. Is it the case that the account option is missing or commented out? |
SRG-OS-000021-GPOS-00005 |
CCI-000044 |
AC-7 a |
xccdf_org.ssgproject.content_rule_accounts_tmout | medium | Set Interactive Session Timeout | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. | Setting the TMOUT option in /etc/profile ensures that
all user sessions will terminate based on inactivity.
The value of TMOUT should be exported and read only.
The TMOUT
setting in /etc/profile.d/autologout.sh should read as follows:
TMOUT=readonly TMOUT export TMOUT |
Run the following command to ensure the TMOUT value is configured for all users on the system: $ sudo grep TMOUT /etc/profile.d/autologout.sh The output should return the following: TMOUT= readonly TMOUT export TMOUT Is it the case that TMOUT is not set or its value is greater than expected setting? |
SRG-OS-000029-GPOS-00010 SRG-OS-000163-GPOS-00072 SRG-OS-000279-GPOS-00109 |
CCI-000057 CCI-001133 CCI-002361 |
AC-11 a SC-10 |
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_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_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+selinux+xattrs+sha512 /usr/sbin/auditd p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 /usr/sbin/ausearch p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 /usr/sbin/aureport p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 /usr/sbin/autrace p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 /usr/sbin/audispd p+i+n+u+g+s+b+acl+selinux+xattrs+sha512 /usr/sbin/augenrules p+i+n+u+g+s+b+acl+selinux+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_periodic_cron_checking | medium | Configure Periodic Execution of AIDE | By default, AIDE does not install itself for periodic execution. Periodically
running AIDE is necessary to reveal unexpected changes in installed files.
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. |
At a minimum, AIDE should be configured to run a weekly scan.
To implement a daily execution of AIDE at 4:05am using cron, add the following line to /etc/crontab :
05 4 * * * root /usr/bin/aide --checkTo implement a weekly execution of AIDE at 4:05am using cron, add the following line to /etc/crontab :
05 4 * * 0 root /usr/bin/aide --checkAIDE can be executed periodically through other means; this is merely one example. The usage of cron's special time codes, such as @daily and
@weekly is acceptable. |
Verify the operating system routinely checks the baseline configuration for unauthorized changes. 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/bin/aide --check NOTE: The usage of special cron times, such as @daily or @weekly, is acceptable. Is it the case that AIDE is not configured to scan periodically? |
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_apparmor_configured | medium | Ensure AppArmor is Active and Configured | Using a whitelist provides a configuration management method for allowing
the execution of only authorized software. Using only authorized software
decreases risk by limiting the number of potential vulnerabilities. The organization must identify authorized software programs and permit execution of authorized software by adding each authorized program to the "pam_apparmor" exception policy. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. Verification of whitelisted software occurs prior to execution or at system startup. Users' home directories/folders may contain information of a sensitive nature. Nonprivileged users should coordinate any sharing of information with a System Administrator (SA) through shared resources. Apparmor can confine users to their home directory, not allowing them to make any changes outside of their own home directories. Confining users to their home directory will minimize the risk of sharing information. |
Verify that the Apparmor tool is configured to
control whitelisted applications and user home directory access
control. The apparmor service can be enabled with the following command:
$ sudo systemctl enable apparmor.service |
Run the following command to determine the current status of the apparmor service: $ sudo systemctl is-active apparmor If the service is running, it should return the following: active Is it the case that it is not? |
SRG-OS-000368-GPOS-00154 SRG-OS-000370-GPOS-00155 SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 SRG-OS-000326-GPOS-00126 SRG-OS-000324-GPOS-00125 |
CCI-001764 CCI-001774 CCI-002165 CCI-002233 CCI-002235 |
|
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 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 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 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 |
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_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_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_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 |
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 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 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 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 |
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_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_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_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 |
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 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 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 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 |
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_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_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_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 |
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_dac_modification_umount | medium | Record Events that Modify the System's Discretionary Access Controls - umount | 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 system umount
changes. 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 umount -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 umount -F auid>=1000 -F auid!=unset -F key=perm_mod |
Verify that SUSE Linux Enterprise 15 generates an audit record for all uses of the "umount" and system call. To determine if the system is configured to audit calls to the "umount" system call, run the following command: $ sudo grep "umount" /etc/audit/audit.* If the system is configured to audit this activity, it will return a line like the following. -a always,exit -F arch=b32 -S umount -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-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-000172 CCI-002884 |
AU-3 AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_umount2 | medium | Record Events that Modify the System's Discretionary Access Controls - umount2 | 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 system umount2
changes. 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 umount2 -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 umount2 -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 umount2 -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 umount2 -F auid>=1000 -F auid!=unset -F key=perm_mod |
To determine if the system is configured to audit calls to the umount2 system call, run the following command: $ sudo grep "umount2" /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-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-000169 CCI-000172 CCI-002884 |
AU-3 AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_enable_syscall_auditing | medium | Remove Default Configuration to Disable Syscall Auditing | Audit rules for syscalls do not take effect unless this line is removed. | By default, SUSE Linux Enterprise 15 ships an audit rule to disable syscall
auditing for performance reasons.
To make sure that syscall auditing works, this line must be removed from
/etc/audit/rules.d/audit.rules and /etc/audit/audit.rules :
-a task,never |
To check for the offending line, run the following command: $ grep task,never /etc/audit/{rules.d,.}/audit.rules There must not be any output, or else these lines must be removed from the matching files. Is it the case that syscall auditing is still disabled? |
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_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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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_chmod | medium | Record Any Attempts to Run chmod | 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 chmod 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/chmod -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/chmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
To verify that execution of the command is being audited, run the following command: $ sudo grep "path=/usr/bin/chmod" /etc/audit/audit.rules /etc/audit/rules.d/* The output should return something similar to: -a always,exit -F path=/usr/bin/chmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged Is it the case that ? |
SRG-OS-000037-GPOS-00015 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-000169 CCI-000172 CCI-002884 |
AU-3 AU-12 a AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_execution_rm | medium | Record Any Attempts to Run rm | 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 rm 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/rm -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/rm -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
To verify that execution of the command is being audited, run the following command: $ sudo grep "path=/usr/bin/rm" /etc/audit/audit.rules /etc/audit/rules.d/* The output should return something similar to: -a always,exit -F path=/usr/bin/rm -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged Is it the case that ? |
SRG-OS-000037-GPOS-00015 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-000169 CCI-000172 CCI-002884 |
AU-3 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 SUSE Linux Enterprise 15 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_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 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 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 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 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_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 SUSE Linux Enterprise 15 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_login_events_tallylog | medium | Record Attempts to Alter Logon and Logout Events - tallylog | 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/tallylog -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/tallylog -p wa -k logins |
Verify SUSE Linux Enterprise 15 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/tallylog" with the following command: $ sudo auditctl -l | grep /var/log/tallylog -w /var/log/tallylog -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-000172 CCI-002884 CCI-000126 |
AU-12 c AU-2 d |
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 SUSE Linux Enterprise 15 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_chfn | medium | Ensure auditd Collects Information on the Use of Privileged Commands - chfn | 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 :
-a always,exit -F path=/usr/bin/chfn -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/chfn -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
To verify that auditing of privileged command use is configured, run the following command: $ sudo grep chfn /etc/audit/audit.rules /etc/audit/rules.d/* It should return a relevant line in the audit rules. 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-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-000172 CCI-002884 |
AU-3 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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_insmod | medium | Ensure auditd Collects Information on the Use of Privileged Commands - insmod | 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 :
-w /sbin/insmod -p x -k modules |
To verify that auditing of privileged command use is configured, run the following command: sudo auditctl -l | grep -w '/sbin/insmod' If the system is configured to audit the execution of the module management program "insmod", the command will return a line. 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-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-000172 CCI-002884 |
AU-3 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 SUSE Linux Enterprise 15 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_modprobe | medium | Ensure auditd Collects Information on the Use of Privileged Commands - modprobe | 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 :
-w /sbin/modprobe -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 /sbin/modprobe -p x -k modules |
To verify that auditing of privileged command use is configured, run the following command: sudo auditctl -l | grep -w '/sbin/modprobe' -w /sbin/modprobe -p x -k modules It should return a relevant line in the audit rules. 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-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-000172 CCI-002884 |
AU-3 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 SUSE Linux Enterprise 15 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=/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=/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
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_passmass | medium | Ensure auditd Collects Information on the Use of Privileged Commands - passmass | 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/passmass -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/passmass -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
To verify that auditing of privileged command use is configured, run the following command: $ sudo grep passmass /etc/audit/audit.rules /etc/audit/rules.d/* It should return a relevant line in the audit rules. 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-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-000172 CCI-002884 |
AU-3 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 SUSE Linux Enterprise 15 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_rmmod | medium | Ensure auditd Collects Information on the Use of Privileged Commands - rmmod | 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 :
-w /sbin/rmmod -p x -k modules |
To verify that auditing of privileged command use is configured, run the following command: sudo auditctl -l | grep -w '/sbin/rmmod' If the system is configured to audit the execution of the module management program "rmmod", the command will return a line. 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-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-000172 CCI-002884 |
AU-3 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 SUSE Linux Enterprise 15 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/lib/ssh/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/lib/ssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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_sudoedit | medium | Ensure auditd Collects Information on the Use of Privileged Commands - sudoedit | 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/sudoedit -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/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
Verify that SUSE Linux Enterprise 15 is configured to audit the execution of the "sudoedit" command with the following command: $ sudo auditctl -l | grep sudoedit -a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudoedit 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_unix2_chkpwd | medium | Ensure auditd Collects Information on the Use of Privileged Commands - unix2_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=/sbin/unix2_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=/sbin/unix2_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
To verify that auditing of privileged command use is configured, run the following command: $ sudo grep unix2_chkpwd /etc/audit/audit.rules /etc/audit/rules.d/* It should return a relevant line in the audit rules. 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_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 SUSE Linux Enterprise 15 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_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 SUSE Linux Enterprise 15 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_session_events_btmp | medium | Record Attempts to Alter Process and Session Initiation Information btmp | 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 process 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 such process information:
-w /var/log/btmp -p wa -k sessionIf 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 attempted manual
edits of files involved in storing such process information:
-w /var/log/btmp -p wa -k session |
Check that the file is being audited by running the following command: sudo auditctl -l | grep -w '/var/log/btmp' Is it the case that Audit rule is not present? |
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-000172 |
AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_session_events_utmp | medium | Record Attempts to Alter Process and Session Initiation Information utmp | 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 process 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 such process information:
-w /run/utmp -p wa -k sessionIf 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 attempted manual
edits of files involved in storing such process information:
-w /run/utmp -p wa -k session |
To Check the file is being audited by performing the following command sudo auditctl -l | grep -w '/run/utmp' Is it the case that Audit rule is not present? |
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-000172 |
AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_session_events_wtmp | medium | Record Attempts to Alter Process and Session Initiation Information wtmp | 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 process 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 such process information:
-w /var/log/wtmp -p wa -k sessionIf 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 attempted manual
edits of files involved in storing such process information:
-w /var/log/wtmp -p wa -k session |
Check that the file is being audited by performing the following command: sudo auditctl -l | grep -w '/var/log/wtmp' Is it the case that Audit rule is not present? |
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-000172 |
AU-12 c |
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 -F euid=0 -k setuid -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -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 SUSE Linux Enterprise 15 audits the execution of privileged functions. Check if SUSE Linux Enterprise 15 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 -F euid=0 -k setuid -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -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_sysadmin_actions | medium | Ensure auditd Collects System Administrator Actions | 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. | 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 actions -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 -p wa -k actions -w /etc/sudoers.d/ -p wa -k actions |
To verify that auditing is configured for system administrator actions, run the following command: $ sudo auditctl -l | grep "watch=/etc/sudoers\|watch=/etc/sudoers.d\|-w /etc/sudoers\|-w /etc/sudoers.d" Is it the case that there is not output? |
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_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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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_rename | medium | Record Unsuccessful Delete Attempts to Files - rename | Unsuccessful attempts to delete files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | The audit system should collect unsuccessful file deletion
attempts 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 .
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.
-a always,exit -F arch=b32 -S rename -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b32 -S rename -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-deleteIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S rename -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b64 -S rename -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete |
Verify SUSE Linux Enterprise 15 generates an audit record for unsuccessful attempts to use the rename 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 rename /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 rename /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S rename -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S rename -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b32 -S rename -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S rename -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete 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-000172 CCI-002884 |
AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_renameat | medium | Record Unsuccessful Delete Attempts to Files - renameat | Unsuccessful attempts to delete files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
The operating system must generate audit records for all uses of the renameat system call.
Without generating audit records 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).
Add or update the following lines to /etc/audit/rules.d/audit.rules to configure the operating system to generate
an audit record for all uses of the renameat system call:
-a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k perm_mod -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k perm_mod |
Verify SUSE Linux Enterprise 15 generates an audit record for unsuccessful attempts to use the renameat 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 renameat /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 renameat /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S renameat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S renameat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b32 -S renameat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S renameat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete 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-000172 CCI-002884 |
AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_renameat2 | medium | Record Unsuccessful Delete Attempts to Files - renameat2 | Unsuccessful attempts to delete files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. | The operating system must generate audit records for all uses of the renameat2 system call.
Without generating audit records 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).
Add or update the following lines to /etc/audit/rules.d/audit.rules to configure the operating system to generate
an audit record for all uses of the renameat2 system call:
-a always,exit -F arch=b32 -S renameat2 -F auid>=1000 -F auid!=-1 -k perm_mod -a always,exit -F arch=b64 -S renameat2 -F auid>=1000 -F auid!=-1 -k perm_mod |
To determine if the system is configured to audit unsuccessful calls to the renameat2 system call, run the following command: $ sudo grep "renameat2" /etc/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-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-000172 |
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 SUSE Linux Enterprise 15 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_unsuccessful_file_modification_unlink | medium | Record Unsuccessful Delete Attempts to Files - unlink | Unsuccessful attempts to delete files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
The operating system must generate audit records for all uses of the unlink system call.
Without generating audit records 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).
Add or update the following lines to /etc/audit/rules.d/audit.rules to configure the operating system to generate
an audit record for all uses of the unlink system call:
-a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=-1 -k perm_mod -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=-1 -k perm_mod |
Verify SUSE Linux Enterprise 15 generates an audit record for unsuccessful attempts to use the unlink 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 unlink /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 unlink /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S unlink -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S unlink -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b32 -S unlink -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S unlink -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete 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-000172 CCI-002884 |
AU-12 c |
xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_unlinkat | medium | Record Unsuccessful Delete Attempts to Files - unlinkat | Unsuccessful attempts to delete files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
The operating system must generate audit records for all uses of the unlinkat system call.
Without generating audit records 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).
Add or update the following lines to /etc/audit/rules.d/audit.rules to configure the operating system to generate
an audit record for all uses of the unlinkat system call:
-a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=-1 -k perm_mod -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=-1 -k perm_mod |
Verify SUSE Linux Enterprise 15 generates an audit record for unsuccessful attempts to use the unlinkat 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 unlinkat /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 unlinkat /etc/audit/audit.rules The output should be the following: -a always,exit -F arch=b32 -S unlinkat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S unlinkat -F exit=-EPERM -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b32 -S unlinkat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete -a always,exit -F arch=b64 -S unlinkat -F exit=-EACCES -F auid>=1000 -F auid!=unset -k unsuccessful-delete 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-000172 CCI-002884 |
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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 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_audispd_disk_full_action | medium | Configure audispd's Plugin disk_full_action When Disk Is Full | Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records. | Configure the action the operating system takes if the disk the audit records
are written to becomes full. Edit the file /etc/audit/audisp-remote.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 and
halt . For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. |
Inspect /etc/audit/audisp-remote.conf and locate the following line to determine if the system is configured to either send to syslog, switch to single user mode, or halt when the disk is full: $ sudo grep -i disk_full_action /etc/audit/audisp-remote.conf The output should return something similar to: disk_full_action = single Acceptable values also include syslog and halt. Is it the case that the system is not configured to switch to single user mode for corrective action? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
xccdf_org.ssgproject.content_rule_auditd_audispd_encrypt_sent_records | medium | Encrypt Audit Records Sent With audispd Plugin | 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. | Configure the operating system to encrypt the transfer of off-loaded audit
records onto a different system or media from the system being audited.
Uncomment the enable_krb5 option in /etc/audit/audisp-remote.conf, and set it with the following line: enable_krb5 = yes |
To verify the audispd plugin encrypts audit records off-loaded onto a different system or media from the system being audited, run the following command: $ sudo grep -i enable_krb5 /etc/audit/audisp-remote.conf The output should return the following: enable_krb5 = yes Is it the case that audispd is not encrypting audit records when sent over the network? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
xccdf_org.ssgproject.content_rule_auditd_audispd_network_failure_action | medium | Configure audispd's Plugin network_failure_action On Network Failure | Taking appropriate action when there is an error sending audit records to a remote system will minimize the possibility of losing audit records. | Configure the action the operating system takes if there is an error sending
audit records to a remote system. Edit the file /etc/audit/audisp-remote.conf .
Add or modify the following line, substituting ACTION appropriately:
network_failure_action = ACTIONSet this value to single to cause the system to switch to single user
mode for corrective action. Acceptable values also include syslog and
halt . For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined.
This profile configures the action to be . |
Inspect /etc/audit/audisp-remote.conf and locate the following line to determine if the system is configured to perform a correct action according to the policy: $ sudo grep -i network_failure_action /etc/audit/audisp-remote.conf The output should return: network_failure_action = Is it the case that the system is not configured to switch to single user mode for corrective action? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
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 ,
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 SUSE Linux Enterprise 15 takes the appropriate action when the audit storage volume is full. Check that SUSE Linux Enterprise 15 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 SUSE Linux Enterprise 15 "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 | 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 SIZE_in_MB appropriately:
space_left = SIZE_in_MBSet this value to the appropriate size in Megabytes 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 SIZE_in_MB Is it the case that the system is not configured a specfic size in MB to notify administrators of an issue? |
SRG-OS-000343-GPOS-00134 |
CCI-001855 |
|
xccdf_org.ssgproject.content_rule_banner_etc_gdm_banner | medium | Modify the System GUI 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 GUI system login banner edit /etc/gdm/banner .
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/gdm/banner Is it the case that it does not display the required banner? |
SRG-OS-000024-GPOS-00007 |
CCI-000050 |
AC-8 b |
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_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 SUSE Linux Enterprise 15 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_clean_components_post_updating | low | Ensure zypper 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. |
zypper should be configured to remove previous software components after
new versions have been installed. To configure zypper to remove the
previous software components after updating, set the solver.upgradeRemoveDroppedPackages
to 1 in /etc/zypp/zypp.conf . |
Verify SUSE Linux Enterprise 15 removes all software components after updated versions have been installed. To verify that solver.upgradeRemoveDroppedPackages is configured properly, run the following command: $ grep -i upgradeRemoveDroppedPackages /etc/zypp/zypp.conf The output should return something similar to: solver.upgradeRemoveDroppedPackages=true Is it the case that 'solver.upgradeRemoveDroppedPackages is not enabled or configured correctly'? |
SRG-OS-000437-GPOS-00194 |
CCI-002617 |
|
xccdf_org.ssgproject.content_rule_cracklib_accounts_password_pam_dcredit | medium | Set Password Strength Minimum Digit Characters | Requiring digits makes password guessing attacks more difficult by ensuring a larger search space. | The pam_cracklib 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_cracklib will grant +1 additional length credit for
each digit. Add dcredit=-1 after pam_cracklib.so to require use of
a digit in passwords. |
To check how many digits are required in a password, run the following command: # grep pam_cracklib /etc/pam.d/common-password password requisite pam_cracklib.so dcredit= The dcredit parameter (as a negative number) will indicate how many digits are required. The DoD requires at least one digit in a password. This would appear as dcredit=-1. Is it the case that dcredit is not found or not set to the required value? |
SRG-OS-000071-GPOS-00039 |
CCI-000194 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_cracklib_accounts_password_pam_difok | medium | Set Password Strength Minimum Different Characters | 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_cracklib module's difok parameter controls requirements for
usage of different characters during a password change. The number of
changed characters refers to the number of changes required with respect to
the total number of positions in the current password. In other words,
characters may be the same within the two passwords; however, the positions
of the like characters must be different.
Make sure the difok parameter for the pam_cracklib module is
configured to greater than or equal to . |
To check how many characters must differ during a password change, run the following command: # grep pam_cracklib.so /etc/pam.d/common-password password requisite pam_cracklib.so difok= The difok parameter will indicate how many characters must differ. The DoD requires at least eight characters differ during a password change. This would appear as difok=8. Is it the case that difok is not found or not set to the required value? |
SRG-OS-000072-GPOS-00040 |
CCI-000195 |
IA-5 (1) (b) |
xccdf_org.ssgproject.content_rule_cracklib_accounts_password_pam_lcredit | medium | Set Password Strength Minimum Lowercase Characters | Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space. | The pam_cracklib 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_cracklib will grant +1
additional length credit for each lowercase character.
Add lcredit=-1 after pam_cracklib.so to require use of a
lowercase character in passwords. |
Check that the operating system enforces password complexity by requiring that at least one lower-case character be used by using the following command: # grep pam_cracklib.so /etc/pam.d/common-password password requisite pam_cracklib.so lcredit= If the command does not return anything, the returned line is commented out, or has a second column value different from "requisite", or does not contain lcredit=, this is a finding. The DoD and FISMA require at least one lowercase character in a password. This would appear as lcredit=-1. Is it the case that lcredit is not found or not set to the required value? |
SRG-OS-000070-GPOS-00038 |
CCI-000193 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_cracklib_accounts_password_pam_minlen | medium | Set Password Minimum Length | 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_cracklib module's minlen parameter controls requirements for
minimum characters required in a password. Add minlen=
to set minimum password length requirements. |
To check how many characters are required in a password, run the following command: $ grep pam_cracklib.so /etc/pam.d/common-password Your output should contain minlen= Is it the case that minlen is not found or not set to the required value (or higher)? |
SRG-OS-000078-GPOS-00046 |
CCI-000205 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_cracklib_accounts_password_pam_ocredit | medium | Set Password Strength Minimum Special Characters | Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space. | The pam_cracklib 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_cracklib will grant +1
additional length credit for each special character.
Make sure the ocredit parameter for the pam_cracklib module is
set to less than or equal to . For example, ocredit= . |
To check how many special characters are required in a password, run the following command: # grep pam_cracklib.so /etc/pam.d/common-password password requisite pam_cracklib.so ocredit= The ocredit parameter (as a negative number) will indicate how many special characters are required. The DoD and FISMA require at least one special character in a password. This would appear as ocredit=-1. Is it the case that ocredit is not found or not set to the required value? |
SRG-OS-000266-GPOS-00101 |
CCI-001619 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_cracklib_accounts_password_pam_retry | medium | Set Password Retry Limit | To reduce opportunities for successful guesses and brute-force attacks. | The pam_cracklib module's retry parameter controls the maximum
number of times to prompt the user for the password before returning
with error. Make sure it is configured with a value that is no more than
. For example, retry=1 . |
Check the password retry limit with the following command: # grep pam_cracklib.so /etc/pam.d/common-password password requisite pam_cracklib.so retry= If the command does not return anything, or the returned line is commented out, this is a finding. If the value of retry is greater than , this is a finding. Is it the case that retry is not found or not set to the required value (or lower)? |
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_cracklib_accounts_password_pam_ucredit | medium | Set Password Strength Minimum Uppercase Characters | Requiring a minimum number of uppercase characters makes password guessing attacks more difficult by ensuring a larger search space. | The pam_cracklib 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_cracklib will grant +1
additional length credit for each uppercase character.
Add ucredit=-1 after pam_cracklib.so to require use of an upper
case character in passwords. |
To check how many uppercase characters are required in a password, run the following command: grep pam_cracklib.so /etc/pam.d/common-password password requisite pam_cracklib.so ucredit= The ucredit parameter (as a negative number) will indicate how many uppercase characters are required. The DoD and FISMA require at least one uppercase character in a password. 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 |
CCI-000192 |
IA-5 (1) (a) |
xccdf_org.ssgproject.content_rule_dconf_db_up_to_date | high | Make sure that the dconf databases are up-to-date with regards to respective keyfiles | Unlike text-based keyfiles, the binary database is impossible to check by OVAL. Therefore, in order to evaluate dconf configuration, both have to be true at the same time - configuration files have to be compliant, and the database needs to be more recent than those keyfiles, which gives confidence that it reflects them. | By default, DConf uses a binary database as a data backend.
The system-level database is compiled from keyfiles in the /etc/dconf/db/
directory by the dconf updatecommand. More specifically, content present in the following directories: /etc/dconf/db/gdm.d /etc/dconf/db/local.d |
In order to be sure that the databases are up-to-date, run the dconf update command as the administrator. Is it the case that The system-wide dconf databases are up-to-date with regards to respective keyfiles? |
|||
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/gdm.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/gdm.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/gdm.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/gdm.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_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/gdm.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/gdm.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/gdm.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/gdm.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_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,
run the following command to configure the SUSE operating system to allow the user to lock the GUI:
gsettings set org.gnome.desktop.lockdown disable-lock-screen falseValidate that disable-lock-screen has been set to false with the command:
gsettings get org.gnome.desktop.lockdown disable-lock-screen |
To check the status of the idle screen lock activation, run the following command: gsettings get org.gnome.desktop.lockdown disable-lock-screen If the result is "true", this is a finding. Configure the SUSE operating system to allow the user to lock the GUI. Run the following command to configure the SUSE operating system to allow the user to lock the GUI: gsettings set org.gnome.desktop.lockdown disable-lock-screen false 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_mode_blank | medium | Implement Blank Screensaver | Setting the screensaver mode to blank-only conceals the contents of the display from passersby. |
On SUSE users should set the screensaver to use publicly viewable images or blank screen
by doing the following:
Find the Settings menu and then navigate to the Background selection section
- Click "Activities" on the top left.
- Click "Show Applications" at the bottom of the Activities menu.
- Click the "Settings" icon.
- Click "Background" from left hand menu.
- Select image and set the Lock Screen image to the user's choice.
- Exit Settings Dialog.
To set the screensaver mode in the GNOME3 desktop to a blank screen,
add or set picture-uri to string '' in
/etc/dconf/db/local.d/00-security-settings . For example:
[org/gnome/desktop/screensaver] picture-uri=string ''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/desktop/screensaver/picture-uriAfter the settings have been set, run dconf update . |
To ensure the screensaver is configured to be blank, run the following command: $ gsettings get org.gnome.desktop.screensaver picture-uri If properly configured, the output should be ''. To ensure that users cannot set the screensaver background, run the following: $ grep picture-uri /etc/dconf/db/local.d/locks/* If properly configured, the output should be /org/gnome/desktop/screensaver/picture-uri Is it the case that it is not set or configured properly? |
SRG-OS-000031-GPOS-00012 |
CCI-000060 |
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_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_dir_system_commands_group_root_owned | medium | Verify that system commands directories have root as a group owner | 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 commands are stored in the following directories:
by default:
/bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbinAll these directories should have root user as a group owner.
If any system command directory is not group owned by a user other than root
correct its ownership with the following command:
$ sudo chgrp root DIR |
System commands are stored in the following directories: /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin For each of these directories, run the following command to find directories not owned by root: $ sudo find -L $DIR ! -group root -type d -exec chgrp root {} \; Is it the case that any of these directories are not group owned by root? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
xccdf_org.ssgproject.content_rule_dir_system_commands_root_owned | medium | Verify that system commands directories have root ownership | 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 commands are stored in the following directories by default:
/bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbinAll these directories should be owned by the root user.
If any system command directory is not owned by a user other than root
correct its ownership with the following command:
$ sudo chown root DIR |
System commands are stored in the following directories: /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin For each of these directories, run the following command to find directories not owned by root: $ sudo find -L $DIR ! -user root -type d Is it the case that any of these directories are not owned by root? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
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_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/login 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/login session required pam_lastlog.so showfailed Is it the case that "pam_lastlog" is missing from "/etc/pam.d/login" 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_dconf_user_profile | high | Configure GNOME3 DConf User Profile | Failure to have a functional DConf profile prevents GNOME3 configuration settings from being enforced for all users and allows various security risks. | By default, DConf provides a standard user profile. This profile contains a list
of DConf configuration databases. The user profile and database always take the
highest priority. As such the DConf User profile should always exist and be
configured correctly.
To make sure that the user profile is configured correctly, the /etc/dconf/profile/gdm
should be set as follows:
user-db:user system-db:gdm |
To verify that the DConf User profile is configured correctly, run the following command: $ cat /etc/dconf/profile/gdm The output should show the following: user-db:user system-db:gdm Is it the case that DConf User profile does not exist or is not configured correctly? |
|||
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. | SUSE Linux Enterprise 15 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.
Detailed information on encrypting partitions using LUKS or LUKS ciphers can be found on the SUSE Linux Enterprise 15 Documentation web site: https://www.suse.com/documentation/sled-12/book_security/data/sec_security_cryptofs_y2.html . |
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 zypper 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 zypper to check package signatures before installing
them, ensure the following line appears in /etc/zypp/zypp.conf in
the [main] section:
gpgcheck=1 |
To determine whether zypper is configured to use gpgcheck, inspect /etc/zypp/zypp.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_rtc_utc_configuration | high | Ensure real-time clock is set to UTC | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the operating system include date and time. Time is commonly expressed in UTC, a modern continuation of GMT, or local time with an offset from UTC. | Ensure that the system real-time clock (RTC) is set to Coordinated Universal Time (UTC). | To verify that the system real-time clock is set to UTC or GMT, run the following command: # timedatectl status | grep -i "time zone" # Time zone: UTC (UTC, +0000) If "Timezone" is not set to UTC, this is a finding. Fix Text: Configure the SUSE operating system is configured to use UTC. To configure the system time zone to use UTC or GMT, run the following command, replacing [ZONE] with "UTC" or "GMT". # sudo timedatectl set-timezone [ZONE] Is it the case that the system real-time clock is not configured to use UTC as its time base? |
SRG-OS-000359-GPOS-00146 |
CCI-001890 |
|
xccdf_org.ssgproject.content_rule_file_etc_security_opasswd | medium | Verify Permissions and Ownership of Old Passwords File | The /etc/security/opasswd file stores old passwords to prevent
password reuse. Protection of this file is critical for system security. |
To properly set the owner of /etc/security/opasswd , run the command: $ sudo chown root /etc/security/opasswdTo properly set the group owner of /etc/security/opasswd , run the command: $ sudo chgrp root /etc/security/opasswdTo properly set the permissions of /etc/security/opasswd , run the command: $ sudo chmod 0600 /etc/security/opasswd |
To check the ownership of /etc/security/opasswd, run the command: $ ls -lL /etc/security/opasswd If properly configured, the output should indicate the following owner: root To check the group ownership of /etc/security/opasswd, run the command: $ ls -lL /etc/security/opasswd If properly configured, the output should indicate the following group-owner: root To check the permissions of /etc/security/opasswd, run the command: $ ls -l /etc/security/opasswd If properly configured, the output should indicate the following permissions: 0600 Is it the case that /etc/security/opasswd does not have an owner of root and /etc/security/opasswd does not have a group owner of root and /etc/security/opasswd does not have unix mode 0600? |
SRG-OS-000077-GPOS-00045 |
CCI-000200 |
IA-5 (1) (e) |
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_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_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_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_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_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_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_local_var_log_messages | medium | Verify that local /var/log/messages is not world-readable | The /var/log/messages file contains system error messages. Only
authorized personnel should be aware of errors and the details of the
errors. Error messages are an indicator of an organization's operational
state or can identify the SUSE operating system or platform. Additionally,
Personally Identifiable Information (PII) and operational information must
not be revealed through error messages to unauthorized personnel or their
designated representatives. |
Files containing sensitive informations should be protected by restrictive
permissions. Most of the time, there is no need that these files need to be read by any non-root user
To properly set the permissions of /var/log/messages , run the command:
$ sudo chmod 0640 /var/log/messagesCheck that "permissions.local" file contains the correct permissions rules with the following command: # grep -i messages /etc/permissions.local /var/log/messages root:root 640 |
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----- Check that permissions.local file contains the correct permissions rules with the following command: # grep -i messages /etc/permissions.local /var/log/messages root:root 640 If the command does not return any or different output, this is a finding. Run the following command to correct the permissions after adding the missing entry: # sudo chkstat --set --system Is it the case that Make sure /var/log/messages is not world-readable? |
SRG-OS-000206-GPOS-00084 |
CCI-001314 |
SI-11 c |
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_system_commands_dirs | medium | Verify that system commands are protected from unauthorized access | 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 commands 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 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 755 FILE |
System commands are stored in the following directories by default: /bin /sbin /usr/bin /usr/local/bin /usr/local/sbin /usr/sbin To find system commands that have mode 0755 or less permissive, run the following command for each directory DIR which contains system executables: $ sudo find -L DIR -perm /022 -type f Is it the case that any system commands are found to be group or world writable? |
SRG-OS-000259-GPOS-00100 |
CCI-001499 |
CM-5 (6) |
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_gnome_gdm_disable_unattended_automatic_login | high | Disable GDM Unattended or 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 or unattended login. 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 DISPLAYMANAGER_AUTOLOGIN=""
or DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" in the
/etc/sysconfig/displaymanager . For example:
DISPLAYMANAGER_AUTOLOGIN="" DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" |
To verify that automatic or unattended logins are disabled, run the following command: grep -i ^DISPLAYMANAGER_AUTOLOGIN /etc/sysconfig/displaymanager The output should show the following: DISPLAYMANAGER_AUTOLOGIN="" DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" Is it the case that GDM allows users to automatically login or unattended 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_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-mkpasswd-pbkdf2When prompted, enter the password that was selected. Using the hash from the output, modify the /etc/grub.d/40_custom
file with the following content:
set superusers="boot" password_pbkdf2 boot grub.pbkdf2.sha512.VeryLongStringNOTE: the bootloader superuser account and password MUST differ from the root account and password. Once the superuser password has been added, update the grub.cfg file by running:
grub2-mkconfig -o /boot/grub2/grub2.cfg |
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_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-mkpasswd-pbkdf2When prompted, enter the password that was selected. Using the hash from the output, modify the /etc/grub.d/40_custom
file with the following content:
set superusers="boot" password_pbkdf2 boot grub.pbkdf2.sha512.VeryLongStringNOTE: the bootloader superuser account and password MUST differ from the root account and password. Once the superuser password has been added, update the grub.cfg file by running:
grub2-mkconfig -o /boot/grub2/grub2.cfg |
To verify the boot loader superuser password has been set, run the following command: $ sudo grep "^[\s]*GRUB2_PASSWORD=grub\.pbkdf2\.sha512.*$" /boot/grub2/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_gui_login_dod_acknowledgement | medium | Display the Standard Mandatory DoD Notice and Consent Banner until Explicit Acknowledgement | 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. |
Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The banner must be acknowledged by the user prior to allowing the user access to the SUSE operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for the SUSE operating system: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.Check the configuration by running the following command: # more /etc/gdm/XsessionThe beginning of the file must contain the following text immediately after #!/bin/sh :
if ! zenity --text-info \ --title "Consent" \ --filename=/etc/gdm/banner \ --no-markup \ --checkbox="Accept." 10 10; then sleep 1; exit 1; fi |
Verify the SUSE operating system displays the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on via the local GUI. Note: If GNOME is not installed, this requirement is Not Applicable. Check the configuration by running the following command: # more /etc/gdm/Xsession The beginning of the file must contain the following text immediately after #!/bin/sh: if ! zenity --text-info \ --title "Consent" \ --filename=/etc/gdm/banner \ --no-markup \ --checkbox="Accept." 10 10; then sleep 1; exit 1; fi If the beginning of the file does not contain the above text immediately after the line (#!/bin/sh), this is a finding. Is it the case that the GNOME environment does not display the standard mandatory DoD notice and consent banner? |
SRG-OS-000023-GPOS-00006 SRG-OS-000024-GPOS-00007 |
CCI-000048 CCI-000050 |
AC-8 a AC-8 b |
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 pam_pkcs11 package can be installed with the following command:
$ sudo zypper install pam_pkcs11The mozilla-nss package can be installed with the following command:
$ sudo zypper install mozilla-nssThe mozilla-nss-tools package can be installed with the following command:
$ sudo zypper install mozilla-nss-toolsThe pcsc-ccid package can be installed with the following command:
$ sudo zypper install pcsc-ccidThe pcsc-lite package can be installed with the following command:
$ sudo zypper install pcsc-liteThe pcsc-tools package can be installed with the following command:
$ sudo zypper install pcsc-toolsThe opensc package can be installed with the following command:
$ sudo zypper install opensc |
Check that SUSE Linux Enterprise 15 has the packages for smart card support installed. Run the following command to determine if the pam_pkcs11 package is installed: $ rpm -q pam_pkcs11 Run the following command to determine if the mozilla-nss package is installed: $ rpm -q mozilla-nss Run the following command to determine if the mozilla-nss-tools package is installed: $ rpm -q mozilla-nss-tools Run the following command to determine if the pcsc-ccid package is installed: $ rpm -q pcsc-ccid Run the following command to determine if the pcsc-lite package is installed: $ rpm -q pcsc-lite Run the following command to determine if the pcsc-tools package is installed: $ rpm -q pcsc-tools Run the following command to determine if the opensc package is installed: $ rpm -q opensc 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. SUSE Linux Enterprise is supported by SUSE. As the SUSE Linux Enterprise vendor, SUSE is responsible for providing security patches. | To verify that the installed operating system is supported, run the following command: $ grep -i "suse" /etc/os-release SUSE Linux Enterprise 15 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_is_fips_mode_enabled | high | Verify '/proc/sys/crypto/fips_enabled' exists | 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. | On a system where FIPS 140-2 mode is enabled, /proc/sys/crypto/fips_enabled must exist.
To verify FIPS mode, run the following command:
cat /proc/sys/crypto/fips_enabled |
To verify /proc/sys/crypto/fips_enabled exists, run the following command: cat /proc/sys/crypto/fips_enabled The output should be: 1 Is it the case that the command 'cat /proc/sys/crypto/fips_enabled' returns nothing or '0' or the file does not exist? |
SRG-OS-000396-GPOS-00176 SRG-OS-000478-GPOS-00223 |
CCI-002450 |
|
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/trueThis 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. 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_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_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_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_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
password authentication configurations in /etc/pam.d/
to prevent logins with empty passwords. |
To verify that null passwords cannot be used, run the following command: $ grep pam_unix.so /etc/pam.d/* | grep nullok 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_shelllogin_for_systemaccounts | medium | Ensure that System Accounts Do Not Run a Shell Upon Login | Ensuring shells are not given to system accounts upon login makes it more difficult for attackers to make use of system accounts. | Some accounts are not associated with a human user of the system, and exist to
perform some administrative function. Should an attacker be able to log into
these accounts, they should not be granted access to a shell.
The login shell for each local account is stored in the last field of each line in /etc/passwd . System accounts are those user accounts with a user ID
less than UID_MIN, where value of UID_MIN directive is set in
/etc/login.defs configuration file. In the default configuration UID_MIN is set
to 1000, thus system accounts are those user accounts with a user ID less than
1000. The user ID is stored in the third field. If any system account
SYSACCT (other than root) has a login shell, disable it with the
command: $ sudo usermod -s /sbin/nologin SYSACCT |
To obtain a listing of all users, their UIDs, and their shells, run the command: $ awk -F: '{print $1 ":" $3 ":" $7}' /etc/passwd Identify the system accounts from this listing. These will primarily be the accounts with UID numbers less than UID_MIN, other than root. Value of the UID_MIN directive is set in /etc/login.defs configuration file. In the default configuration UID_MIN is set to 1000. Is it the case that any system account (other than root) has a login shell? |
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_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_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 zypper 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-audispd-plugins_installed | medium | Ensure the default plugins for the audit dispatcher are Installed | 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 audit-audispd-plugins package should be installed. | Is it the case that the package is not installed? |
SRG-OS-000342-GPOS-00133 SRG-OS-000479-GPOS-00224 |
CCI-001851 |
|
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_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. SUSE Linux Enterprise 15 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 zypper 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_pam_apparmor_installed | medium | Install the pam_apparmor Package | Protection of system integrity using AppArmor depends on this package being installed. | The pam_apparmor package can be installed with the following command:
$ sudo zypper install pam_apparmor |
Run the following command to determine if the pam_apparmor package is installed: $ rpm -q pam_apparmor Is it the case that the package is not installed? |
SRG-OS-000368-GPOS-00154 SRG-OS-000370-GPOS-00155 SRG-OS-000312-GPOS-00122 SRG-OS-000312-GPOS-00123 SRG-OS-000312-GPOS-00124 SRG-OS-000326-GPOS-00126 SRG-OS-000324-GPOS-00125 |
CCI-001764 CCI-001774 CCI-002165 CCI-002233 CCI-002235 |
|
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 zypper remove 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_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 zypper remove 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_pam_disable_automatic_configuration | medium | The PAM configuration should not be changed automatically |
pam-config is a command line utility that automatically generates
a system PAM configuration as packages are installed, updated or removed
from the system. pam-config removes configurations for PAM modules
and parameters that it does not know about. It may render ineffective PAM
configuration by the system administrator and thus impact system security. |
Verify the SUSE operating system is configured to not overwrite Pluggable Authentication Modules (PAM) configuration on package changes. | Check that soft links between PAM configuration files are removed with the following command: # find /etc/pam.d/ -type l -iname "common-*" If any results are returned, this is a finding. 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_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_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_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_permissions_local_audit_binaries | medium | Verify Permissions of Local Logs of audit Tools | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. SUSE operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys to make access decisions regarding the access to audit tools. | The SUSE operating system audit tools must have the proper permissions
configured to protect against unauthorized access.
Check that "permissions.local" file contains the correct permissions rules
with the following command:
grep "^/usr/sbin/au" /etc/permissions.local /usr/sbin/audispd root:root 0750 /usr/sbin/auditctl root:root 0750 /usr/sbin/auditd root:root 0750 /usr/sbin/ausearch root:root 0755 /usr/sbin/aureport root:root 0755 /usr/sbin/autrace root:root 0750 /usr/sbin/augenrules root:root 0750Audit 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. |
Check that permissions.local file contains the correct permissions rules with the following command: grep "^/usr/sbin/au" /etc/permissions.local /usr/sbin/audispd root:root 0750 /usr/sbin/auditctl root:root 0750 /usr/sbin/auditd root:root 0750 /usr/sbin/ausearch root:root 0755 /usr/sbin/aureport root:root 0755 /usr/sbin/autrace root:root 0750 /usr/sbin/augenrules root:root 0750 If the command does not return all the above lines, the missing ones need to be added. Run the following command to correct the permissions after adding missing entries: # sudo chkstat --set --system Is it the case that ? |
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_permissions_local_var_log | medium | Verify permissions of log files | The SUSE Linux Enterprise 15 must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. | Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization. Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. | Verify the operating system has all system log files under the /var/log directory with a permission set to 640, by using the following command: sudo find /var/log -perm /137 -type f -exec stat -c "%n %a" {} \; Is it the case that not all log files have permission 640 or stricter? |
SRG-OS-000205-GPOS-00083 |
CCI-001312 |
SI-11 b |
xccdf_org.ssgproject.content_rule_permissions_local_var_log_audit | medium | Verify that Local Logs of the audit Daemon are not World-Readable | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. | Files containing sensitive informations should be protected by restrictive
permissions. Most of the time, there is no need that these files need to bei
read by any non-root user.
Check that "permissions.local" file contains the correct permissions rules with the following command:
# grep -i audit /etc/permissions.local /var/log/audit/ root:root 600 /var/log/audit/audit.log root:root 600 /etc/audit/audit.rules root:root 640 /etc/audit/rules.d/audit.rules root:root 640 |
Check that permissions.local file contains the correct permissionsi rules with the following command: # grep -i audit /etc/permissions.local /var/log/audit/ root:root 600 /var/log/audit/audit.log root:root 600 /etc/audit/audit.rules root:root 640 /etc/audit/rules.d/audit.rules root:root 640 If the command does not return all the above lines, the missing ones need to be added. Run the following command to correct the permissions after adding missing entries: # sudo chkstat --set --system Is it the case that ? |
SRG-OS-000059-GPOS-00029 |
CCI-000164 |
AU-9 |
xccdf_org.ssgproject.content_rule_postfix_client_configure_mail_alias | medium | Configure System to Forward All Mail For The Root Account | A number of system services utilize email messages sent to the root user to notify system administrators of active or impending issues. These messages must be forwarded to at least one monitored email address. | Make sure that mails delivered to root user are forwarded to a monitored
email address. Make sure that the address
is a valid email address
reachable from the system in question. Use the following command to
configure the alias:
$ sudo echo "root: " >> /etc/aliases $ sudo newaliases |
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 root user: $ sudo postmap -q root hash:/etc/aliases The output should return an alias. Is it the case that the alias is not set? |
SRG-OS-000046-GPOS-00022 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-000139 CCI-000366 |
AU-5 a CM-6 b |
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_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 configured for online updates, invoking the following command will list available
security updates:
$ sudo zypper refresh && sudo zypper list-patches -g security 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_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_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_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_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_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/common-password", 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 required 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/common-password 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/common-password password required 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_smartcard_configure_ca | medium | Configure Smart Card Certificate Authority Validation | 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 do certificate status checking for PKI
authentication. Modify all of the cert_policy lines in
/etc/pam_pkcs11/pam_pkcs11.conf to include ca like so:
cert_policy = ca, ocsp_on, signature; |
To verify the operating system implements certificate status checking for PKI authentication, run the following command: $ sudo grep -i cert_policy /etc/pam_pkcs11/pam_pkcs11.conf The output should return multiple lines similiar to the following: cert_policy = ca, ocsp_on, signature; cert_policy = ca, ocsp_on, signature; cert_policy = ca, ocsp_on, signature; Is it the case that ca is not configured? |
SRG-OS-000066-GPOS-00034 SRG-OS-000384-GPOS-00167 |
CCI-000185 CCI-001991 |
IA-5 (2) |
xccdf_org.ssgproject.content_rule_smartcard_configure_cert_checking | medium | Configure Smart Card Certificate Status Checking | 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 do certificate status checking for PKI
authentication. Modify all of the cert_policy lines in
/etc/pam_pkcs11/pam_pkcs11.conf to include ocsp_on like so:
cert_policy = ca, ocsp_on, signature; |
To verify the operating system implements certificate status checking for PKI authentication, run the following command: $ sudo grep -i cert_policy /etc/pam_pkcs11/pam_pkcs11.conf The output should return multiple lines similiar to the following: cert_policy = ca, ocsp_on, signature; cert_policy = ca, ocsp_on, signature; cert_policy = ca, ocsp_on, signature; Is it the case that ocsp_on is not configured? |
SRG-OS-000375-GPOS-00160 SRG-OS-000376-GPOS-00161 SRG-OS-000377-GPOS-00162 |
CCI-001948 CCI-001953 CCI-001954 |
|
xccdf_org.ssgproject.content_rule_smartcard_pam_enabled | medium | Enable Smart Card Logins in PAM | Smart card login provides two-factor authentication stronger than that provided by a username and password combination. Smart cards leverage PKI (public key infrastructure) in order to provide and verify credentials. 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. | This requirement only applies to components where this is specific to the
function of the device or has the concept of an organizational user (e.g.,
VPN, proxy capability). This does not apply to authentication for the
purpose of configuring the device itself (management).
Check that the pam_pkcs11.so option is configured in the
etc/pam.d/common-auth file with the following command:
# grep pam_pkcs11.so /etc/pam.d/common-auth auth sufficient pam_pkcs11.soFor general information about enabling smart card authentication, consult the documentation at: |
Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management). Check that the pam_pkcs11.so option is configured in the etc/pam.d/common-auth file with the following command: # grep pam_pkcs11.so /etc/pam.d/common-auth auth sufficient pam_pkcs11.so If pam_pkcs11.so is not set in etc/pam.d/common-auth this is a finding. Is it the case that non-exempt accounts are not using CAC authentication? |
SRG-OS-000105-GPOS-00052 SRG-OS-000106-GPOS-00053 SRG-OS-000107-GPOS-00054 SRG-OS-000108-GPOS-00055 SRG-OS-000068-GPOS-00036 SRG-OS-000375-GPOS-00160 SRG-OS-000376-GPOS-00161 SRG-OS-000377-GPOS-00162 |
CCI-000765 CCI-000766 CCI-000767 CCI-000768 CCI-000187 CCI-001948 CCI-001953 CCI-001954 |
IA-2 (1) IA-2 (2) IA-2 (3) IA-2 (4) 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_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_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_set_loglevel_verbose | medium | Set SSH Daemon LogLevel to VERBOSE | SSH provides several logging levels with varying amounts of verbosity. DEBUG is specifically
not recommended other than strictly for debugging SSH communications since it provides
so much data that it is difficult to identify important security information. INFO or
VERBOSE level is the basic level that only records login activity of SSH users. In many
situations, such as Incident Response, it is important to determine when a particular user was active
on a system. The logout record can eliminate those users who disconnected, which helps narrow the
field. |
The VERBOSE parameter configures the SSH daemon to record login and logout activity.
To specify the log level in
SSH, add or correct the following line in
/etc/ssh/sshd_config :
LogLevel VERBOSE |
To determine how the SSH daemon's LogLevel option is set, run the following command: $ sudo grep -i LogLevel /etc/ssh/sshd_config If a line indicating VERBOSE is returned, then the required value is set. Is it the case that the required value is not set? |
SRG-OS-000032-GPOS-00013 |
CCI-000067 |
AC-17 (1) |
xccdf_org.ssgproject.content_rule_sshd_use_approved_ciphers_ordered_stig | medium | Use Only FIPS 140-2 Validated Ciphers | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore
cannot be relied upon to provide confidentiality or integrity, and system data may be compromised.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets industry and government requirements. For government systems, this allows Security Levels 1, 2, 3, or 4 for use on SUSE Linux Enterprise 15. |
Limit the ciphers to those algorithms which are FIPS-approved.
The following line in /etc/ssh/sshd_config
demonstrates use of FIPS-approved ciphers:
Ciphers aes256-ctr,aes192-ctr,aes128-ctrThis rule ensures that there are configured ciphers mentioned above (or their subset), keeping the given order of algorithms. |
Only FIPS ciphers should be used. To verify that only FIPS-approved ciphers are in use, run the following command: $ sudo grep Ciphers /etc/ssh/sshd_config The output should contain only following ciphers (or a subset) in the exact order: aes256-ctr,aes192-ctr,aes128-ctr Is it the case that FIPS ciphers are not configured or the enabled ciphers are not FIPS-approved? |
SRG-OS-000033-GPOS-00014 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-000120-GPOS-00061 SRG-OS-000125-GPOS-00065 SRG-OS-000393-GPOS-00173 SRG-OS-000394-GPOS-00174 |
CCI-000068 CCI-000366 CCI-000803 CCI-000877 CCI-002890 CCI-003123 |
AC-17 (2) CM-6 b IA-7 MA-4 c |
xccdf_org.ssgproject.content_rule_sshd_use_approved_macs_ordered_stig | medium | Use Only FIPS 140-2 Validated MACs | DoD Information Systems are required to use FIPS-approved cryptographic hash functions. The only SSHv2 hash algorithms meeting this requirement is SHA2. | Limit the MACs to those hash algorithms which are FIPS-approved.
The following line in /etc/ssh/sshd_config
demonstrates use of FIPS-approved MACs:
MACs hmac-sha2-512,hmac-sha2-256This rule ensures that there are configured MACs mentioned above (or their subset), keeping the given order of algorithms. |
Only FIPS-approved MACs should be used. To verify that only FIPS-approved MACs are in use, run the following command: $ sudo grep -i macs /etc/ssh/sshd_config The output should contain only following MACs (or a subset) in the exact order: MACs Is it the case that MACs option is commented out or not using FIPS-approved hash algorithms? |
SRG-OS-000033-GPOS-00014 SRG-OS-000120-GPOS-00061 SRG-OS-000125-GPOS-00065 SRG-OS-000250-GPOS-00093 SRG-OS-000394-GPOS-00174 |
CCI-000068 CCI-000803 CCI-000877 CCI-001453 CCI-003123 |
AC-17 (2) IA-7 MA-4 c AC-17 (2) |
xccdf_org.ssgproject.content_rule_sssd_memcache_timeout | medium | Configure SSSD's Memory Cache to Expire | If cached authentication information is out-of-date, the validity of the authentication information may be questionable. | SSSD's memory cache should be configured to set to expire records after
seconds.
To configure SSSD to expire memory cache, set memcache_timeout to
under the
[nss] section in /etc/sssd/sssd.conf .
For example:
[nss] memcache_timeout = |
To verify that SSSD's in-memory cache expires after a day, run the following command: $ sudo grep memcache_timeout /etc/sssd/sssd.conf If configured properly, output should be memcache_timeout = . 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_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.
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 |
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_authentication | medium | Ensure Users Re-Authenticate for Privilege Escalation - sudo | 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 and !authenticate option, when
specified, allows a user to execute commands using sudo without having to
authenticate. This should be disabled by making sure that
NOPASSWD and/or !authenticate do not exist in
/etc/sudoers configuration file or any sudo configuration snippets
in /etc/sudoers.d/ ." |
To determine if NOPASSWD or !authenticate have been configured for sudo, run the following command: $ sudo grep -ri "nopasswd\|\!authenticate" /etc/sudoers /etc/sudoers.d/ The command should return no output. Is it the case that nopasswd and/or !authenticate is enabled in sudo? |
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_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_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_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_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_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_ipv4_tcp_syncookies | medium | Enable Kernel Parameter to Use TCP Syncookies on Network Interfaces | A TCP SYN flood attack can cause a denial of service by filling a system's TCP connection table with connections in the SYN_RCVD state. Syncookies can be used to track a connection when a subsequent ACK is received, verifying the initiator is attempting a valid connection and is not a flood source. This feature is activated when a flood condition is detected, and enables the system to continue servicing valid connection requests. | To set the runtime status of the net.ipv4.tcp_syncookies kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.tcp_syncookies=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d : net.ipv4.tcp_syncookies = 1 |
The runtime status of the net.ipv4.tcp_syncookies kernel parameter can be queried by running the following command: $ sysctl net.ipv4.tcp_syncookies 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 SRG-OS-000142-GPOS-00071 |
CCI-000366 CCI-001095 |
CM-6 b SC-5 (2) |
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_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_net_ipv6_conf_default_forwarding | medium | Disable Kernel Parameter for IPv6 Forwarding by default | 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.default.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.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.default.forwarding = 0 |
The runtime status of the net.ipv6.conf.default.forwarding kernel parameter can be queried by running the following command: $ sysctl net.ipv6.conf.default.forwarding 0. The ability to forward packets is only appropriate for routers. Is it the case that IPv6 Forwading is not disabled? |
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_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 SUSE Linux Enterprise 15 operating system must have vlock installed to allow for session locking.
The kbd package can be installed with the following command:
$ sudo zypper 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 wireless network interfaces by issuing the following command for every active <WIFI-INTERFACE> in the system:
$ sudo wicked ifdown <WIFI-INTERFACE>Also remove the configuration files for every wifi adapter from /etc/wicked/ifconfig/<WIFI-INTERFACE>.xml to prevent future
connections. |
Verify that there are no wireless interfaces configured on the system with the following command: # wicked show all lo up link: #1, state up type: loopback config: compat:suse:/etc/sysconfig/network/ifcfg-lo leases: ipv4 static granted leases: ipv6 static granted addr: ipv4 127.0.0.1/8 [static] addr: ipv6 ::1/128 [static] wlan0 up link: #3, state up, mtu 1500 type: wireless, hwaddr 06:00:00:00:00:02 config: wicked:xml:/etc/wicked/ifconfig/wlan0.xml leases: ipv4 dhcp granted addr: ipv4 10.0.0.101/16 [dhcp] route: ipv4 default via 10.0.0.1 proto dhcp The output should not contain any interfaces of type wireless in state up. If a wireless interface is configured it must be documented and approved by the local Authorizing Official. 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) |