| CCE-80206-6 |
Disable debug-shell SystemD Service |
disable |
via systemctl |
SystemD's debug-shell service is intended to diagnose SystemD related boot issues with various systemctl commands. Once enabled and following a system reboot, the root shell will be available on tty9 which is access by pressing CTRL-ALT-F9. The debug-shell service should only be used for SystemD related issues and should otherwise be disabled. By default, the debug-shell SystemD service is already disabled. The debug-shell service can be disabled with the following command: $ sudo systemctl disable debug-shell.service The debug-shell service can be masked with the following command: $ sudo systemctl mask debug-shell.service |
This prevents attackers with physical access from trivially bypassing security on the machine through valid troubleshooting configurations and gaining root access when the system is rebooted. |
medium |
NaN |
FIA_UAU.1 |
NaN |
SRG-OS-000324-GPOS-00125 |
Protect Physical Console Access |
| CCE-27287-2 |
Require Authentication for Single User Mode |
verify |
via systemctl |
Single-user mode is intended as a system recovery method, providing a single user root access to the system by providing a boot option at startup. By default, no authentication is performed if single-user mode is selected. By default, single-user mode is protected by requiring a password and is set in /usr/lib/systemd/system/rescue.service. |
This prevents attackers with physical access from trivially bypassing security on the machine and gaining root access. Such accesses are further prevented by configuring the bootloader password. |
medium |
AC-3,CM-6(a),IA-2 |
FIA_UAU.1 |
1.4.3 |
SRG-OS-000080-GPOS-00048 |
Protect Physical Console Access |
| CCE-27511-5 |
Disable Ctrl-Alt-Del Reboot Activation |
disable |
via systemctl |
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.target or 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. |
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. |
high |
AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000324-GPOS-00125,SRG-OS-000480-GPOS-00227 |
Protect Physical Console Access |
| CCE-82185-0 |
Require Authentication for Emergency Systemd Target |
verify |
via systemctl |
Emergency mode is intended as a system recovery method, providing a single user root access to the system during a failed boot sequence. By default, Emergency mode is protected by requiring a password and is set in /usr/lib/systemd/system/emergency.service. |
This prevents attackers with physical access from trivially bypassing security on the machine and gaining root access. Such accesses are further prevented by configuring the bootloader password. |
medium |
AC-3,CM-6(a),IA-2 |
FIA_UAU.1 |
1.4.3 |
SRG-OS-000080-GPOS-00048 |
Protect Physical Console Access |
| CCE-27335-9 |
Verify that Interactive Boot is Disabled |
disable |
via grub |
Red Hat Enterprise Linux 7 systems support an "interactive boot" option that can be used to prevent services from being started. On a Red Hat Enterprise Linux 7 system, interactive boot can be enabled by providing a 1, yes, true, or on value to the systemd.confirm_spawn kernel argument in /etc/default/grub. Remove any instance of systemd.confirm_spawn=(1|yes|true|on) from the kernel arguments in that file to disable interactive boot. It is also required to change the runtime configuration, run: /sbin/grubby --update-kernel=ALL --remove-args="systemd.confirm_spawn" |
Using interactive boot, the console user could disable auditing, firewalls, or other services, weakening system security. |
medium |
CM-6(a),SC-2(1) |
FIA_UAU.1 |
NaN |
SRG-OS-000480-GPOS-00227 |
Protect Physical Console Access |
| CCE-80449-2 |
Disable Ctrl-Alt-Del Burst Action |
CtrlAltDelBurstAction=none |
via /etc/systemd/system.conf |
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 |
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. |
high |
AC-6(1),CM-6(a),CM-6(a) |
NaN |
NaN |
SRG-OS-000324-GPOS-00125 |
Protect Physical Console Access |
| CCE-80568-9 |
Install the opensc Package For Multifactor Authentication |
install |
via yum |
The opensc package can be installed with the following command: $ sudo yum install opensc |
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. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000375-GPOS-00160 |
Hardware Tokens for Authentication |
| CCE-82347-6 |
Install the pcsc-lite package |
install |
via yum |
The pcsc-lite package can be installed with the following command: $ sudo yum install pcsc-lite |
The pcsc-lite package must be installed if it is to be available for multifactor authentication using smartcards. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000375-GPOS-00160 |
Hardware Tokens for Authentication |
| CCE-80569-7 |
Enable the pcscd Service |
enable |
via systemctl |
The pcscd service can be enabled with the following command: $ sudo systemctl enable pcscd.service |
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. |
medium |
CM-6(a),IA-2(1),IA-2(11),IA-2(2),IA-2(3),IA-2(4),IA-2(6),IA-2(7) |
NaN |
NaN |
SRG-OS-000375-GPOS-00160 |
Hardware Tokens for Authentication |
| CCE-80567-1 |
Configure NSS DB To Use opensc |
opensc |
via pkcs11-switch |
The opensc module should be configured for use over the Coolkey PKCS#11 module in the NSS database. To configure the NSS database ot use the opensc module, run the following command: $ sudo pkcs11-switch opensc |
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. |
medium |
CM-6(a),IA-2(1),IA-2(11),IA-2(2),IA-2(3),IA-2(4),IA-2(6),IA-2(7) |
NaN |
NaN |
SRG-OS-000104-GPOS-00051,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000108-GPOS-00055,SRG-OS-000108-GPOS-00057,SRG-OS-000108-GPOS-00058,SRG-OS-000109-GPOS-00056 |
Hardware Tokens for Authentication |
| CCE-80519-2 |
Install Smart Card Packages For Multifactor Authentication |
install |
via yum |
Configure the operating system to implement multifactor authentication by installing the required packages with the following command: The esc pam_pkcs11 package can be installed with the following command: $ sudo yum install esc pam_pkcs11 |
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. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000105-GPOS-00052,SRG-OS-000375-GPOS-00160,SRG-OS-000375-GPOS-00161,SRG-OS-000377-GPOS-00162 |
Hardware Tokens for Authentication |
| CCE-80520-0 |
Configure Smart Card Certificate Status Checking |
ocsp_on |
via /etc/pam_pkcs11/pam_pkcs11.conf |
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; |
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. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000375-GPOS-00160,SRG-OS-000376-GPOS-00161,SRG-OS-000377-GPOS-00162,SRG-OS-000384-GPOS-00167 |
Hardware Tokens for Authentication |
| CCE-81002-8 |
Force opensc To Use Defined Smart Card Driver |
True |
via /etc/opensc-ARCH.conf |
The OpenSC smart card tool can auto-detect smart card drivers; however by forcing the smart card driver in use by your organization, opensc will no longer autodetect or use other drivers unless specified. This helps to prevent users from using unauthorized smart cards. The default smart card driver for this profile is . To force the OpenSC driver, edit the /etc/opensc-ARCH.conf (where ARCH is the architecture of your operating system) file. Look for a line similar to: # force_card_driver = customcos; and change it to: force_card_driver = ; |
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. Forcing the smart card driver in use by your organization helps to prevent users from using unauthorized smart cards. |
medium |
CM-6(a),IA-2(1),IA-2(11),IA-2(2),IA-2(3),IA-2(4),IA-2(6),IA-2(7) |
NaN |
NaN |
SRG-OS-000104-GPOS-00051,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000108-GPOS-00055,SRG-OS-000108-GPOS-00057,SRG-OS-000108-GPOS-00058,SRG-OS-000109-GPOS-00056 |
Hardware Tokens for Authentication |
| CCE-80565-5 |
Configure opensc Smart Card Drivers |
cac |
via /etc/opensc-ARCH.conf |
The OpenSC smart card tool can auto-detect smart card drivers; however, setting the smart card drivers in use by your organization helps to prevent users from using unauthorized smart cards. The default smart card driver for this profile is . To configure the OpenSC driver, edit the /etc/opensc-ARCH.conf (where ARCH is the architecture of your operating system) file. Look for a line similar to: # card_drivers = old, internal; and change it to: card_drivers = ; |
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. Configuring the smart card driver in use by your organization helps to prevent users from using unauthorized smart cards. |
medium |
CM-6(a),IA-2(1),IA-2(11),IA-2(2),IA-2(3),IA-2(4),IA-2(6),IA-2(7) |
NaN |
NaN |
SRG-OS-000104-GPOS-00051,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000108-GPOS-00055,SRG-OS-000108-GPOS-00057,SRG-OS-000108-GPOS-00058,SRG-OS-000109-GPOS-00056 |
Hardware Tokens for Authentication |
| CCE-80207-4 |
Enable Smart Card Login |
enable manually |
via authconfig |
To enable smart card authentication, consult the documentation at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/smartcards.html#authconfig-smartcards For guidance on enabling SSH to authenticate against a Common Access Card (CAC), consult documentation at: https://access.redhat.com/solutions/82273 |
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. |
medium |
CM-6(a),IA-2(1),IA-2(11),IA-2(2),IA-2(3),IA-2(4),IA-2(6),IA-2(7) |
NaN |
NaN |
SRG-OS-000104-GPOS-00051,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000108-GPOS-00055,SRG-OS-000108-GPOS-00057,SRG-OS-000108-GPOS-00058,SRG-OS-000109-GPOS-00056,SRG-OS-000376-GPOS-00161,SRG-OS-000377-GPOS-00162 |
Hardware Tokens for Authentication |
| CCE-27351-6 |
Install the screen Package |
install |
via yum |
To enable console screen locking, install the screen package. The screen package can be installed with the following command: $ sudo yum install screen Instruct users to begin new terminal sessions with the following command: $ screen The console can now be locked with the following key combination: ctrl+a x |
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not logout because of the temporary nature of the absence. Rather than relying on the user to manually lock their operation system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. The screen package allows for a session lock to be implemented and configured. |
medium |
CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure Console Screen Locking |
| CCE-80526-7 |
User Initialization Files Must Be Group-Owned By The Primary User |
USER GID |
via chgrp |
Change the group owner of interactive users files to the group found in /etc/passwd for the user. To change the group owner of a local interactive user home directory, use the following command: $ sudo chgrp USER_GROUP /home/USER/.INIT_FILE |
Local initialization files for interactive users are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80201-7 |
Ensure that User Home Directories are not Group-Writable or World-Readable |
750 |
via chmod |
For each human user of the system, view the permissions of the user's home directory: # ls -ld /home/USER Ensure that the directory is not group-writable and that it is not world-readable. If necessary, repair the permissions: # chmod g-w /home/USER # chmod o-rwx /home/USER |
User home directories contain many configuration files which affect the behavior of a user's account. No user should ever have write permission to another user's home directory. Group shared directories can be configured in sub-directories or elsewhere in the filesystem if they are needed. Typically, user home directories should not be world-readable, as it would disclose file names to other users. If a subset of users need read access to one another's home directories, this can be provided using groups or ACLs. |
medium |
AC-6(1),CM-6(a),CM-6(a) |
NaN |
NaN |
NaN |
Secure Session Configuration Files for Login Accounts |
| CCE-80528-3 |
All Interactive Users Must Have A Home Directory Defined |
True |
via usermod |
Assign home directories to all interactive users that currently do not have a home directory assigned. |
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. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80532-5 |
All Interactive User Home Directories Must Be Group-Owned By The Primary User |
USER GID |
via chgrp |
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/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. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80525-9 |
Ensure All User Initialization Files Have Mode 0740 Or Less Permissive |
740 |
via chmod |
Set the mode of the user initialization files to 0740 with the following command: $ sudo chmod 0740 /home/USER/.INIT_FILE |
Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80531-7 |
All Interactive User Home Directories Must Be Owned By The Primary User |
User UID |
via chown |
Change the owner of interactive users home directories to that correct owner. To change the owner of a interactive users home directory, use the following command: $ sudo chown USER /home/USER |
If a local interactive user does not own their home directory, unauthorized users could access or modify the user's files, and the users may not be able to access their own files. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80534-1 |
All User Files and Directories In The Home Directory Must Be Group-Owned By The Primary User |
USER GID |
via chgrp |
Change the group of a local interactive users files and directories to a group that the interactive user is a member of. To change the group owner of a local interactive users files and directories, use the following command: $ sudo chgrp USER_GROUP /home/USER/FILE_DIR |
If a local interactive users files are group-owned by a group of which the user is not a member, unintended users may be able to access them. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80434-4 |
Ensure Home Directories are Created for New Users |
yes |
via /etc/login.defs |
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 |
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. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80352-8 |
Ensure the Logon Failure Delay is Set Correctly in login.defs |
3 |
via /etc/login.defs |
To ensure the logon failure delay controlled by /etc/login.defs is set properly, add or correct the FAIL_DELAY setting in /etc/login.defs to read as follows: FAIL_DELAY |
Increasing the time between a failed authentication attempt and re-prompting to enter credentials helps to slow a single-threaded brute force attack. |
medium |
AC-7(b),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00226 |
Secure Session Configuration Files for Login Accounts |
| CCE-80530-9 |
All Interactive User Home Directories Must Have mode 0750 Or Less Permissive |
750 |
via chmod |
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 |
Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-82041-5 |
Limit the Number of Concurrent Login Sessions Allowed Per User |
10 |
via /etc/security/limits.conf |
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 |
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. |
low |
AC-10,CM-6(a) |
NaN |
NaN |
SRG-OS-000027-GPOS-00008 |
Secure Session Configuration Files for Login Accounts |
| CCE-80524-2 |
Ensure that Users Path Contains Only Local Directories |
Verify |
via PATH |
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. |
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). |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80529-1 |
All Interactive Users Home Directories Must Exist |
USERNAME |
via mkdir |
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 |
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. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80523-4 |
User Initialization Files Must Not Run World-Writable Programs |
750 |
via chmod |
Set the mode on files being executed by the user initialization files with the following command: $ sudo chmod 0755 FILE |
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. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80533-3 |
All User Files and Directories In The Home Directory Must Be Owned By The Primary User |
User UID |
via chown |
Change the owner of a interactive users files and directories to that owner. To change the of a local interactive users files and directories, use the following command: $ sudo chown -R USER /home/USER |
If local interactive users do not own the files in their directories, unauthorized users may be able to access them. Additionally, if files are not owned by the user, this could be an indication of system compromise. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80527-5 |
User Initialization Files Must Be Owned By the Primary User |
User UID |
via chown |
Set the owner of the user initialization files for interactive users to the primary owner with the following command: $ sudo chown USER /home/USER/.* |
Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-80535-8 |
All User Files and Directories In The Home Directory Must Have Mode 0750 Or Less Permissive |
750 |
via chmod |
Set the mode on files and directories in the local interactive user home directory with the following command: $ sudo chmod 0750 /home/USER/FILE_DIR |
If a local interactive user files have excessive permissions, unintended users may be able to access or modify them. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Secure Session Configuration Files for Login Accounts |
| CCE-27557-8 |
Set Interactive Session Timeout |
600 |
TMOUT |
Setting the TMOUT option in /etc/profile ensures that all user sessions will terminate based on inactivity. The TMOUT setting in /etc/profile should read as follows: TMOUT= |
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. |
medium |
AC-12,AC-2(5),CM-6(a),SC-10 |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000163-GPOS-00072 |
Secure Session Configuration Files for Login Accounts |
| CCE-80536-6 |
Ensure the Default Umask is Set Correctly For Interactive Users |
remove |
via rm |
Remove the UMASK environment variable from all interactive users initialization files. |
The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 700 or less permissive. Although umask can be represented as a four-digit number, the first digit representing special access modes is typically ignored or required to be 0. This requirement applies to the globally configured system defaults and the local interactive user defaults for each account on the system. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Ensure that Users Have Sensible Umask Values |
| CCE-80204-1 |
Ensure the Default Umask is Set Correctly in /etc/profile |
“077” |
via UMASK |
To ensure the default umask controlled by /etc/profile is set properly, add or correct the umask setting in /etc/profile to read as follows: umask |
The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read or written to by unauthorized users. |
unknown |
AC-6(1),CM-6(a) |
NaN |
5.4.4 |
SRG-OS-000480-GPOS-00228 |
Ensure that Users Have Sensible Umask Values |
| CCE-80202-5 |
Ensure the Default Bash Umask is Set Correctly |
“077” |
via UMASK |
To ensure the default umask for users of the Bash shell is set properly, add or correct the umask setting in /etc/bashrc to read as follows: umask |
The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read or written to by unauthorized users. |
unknown |
AC-6(1),CM-6(a) |
NaN |
5.4.4 |
SRG-OS-000480-GPOS-00228 |
Ensure that Users Have Sensible Umask Values |
| CCE-80205-8 |
Ensure the Default Umask is Set Correctly in login.defs |
“077” |
via UMASK |
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 |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00228 |
Ensure that Users Have Sensible Umask Values |
| CCE-80203-3 |
Ensure the Default C Shell Umask is Set Correctly |
“077” |
via UMASK |
To ensure the default umask for users of the C shell is set properly, add or correct the umask setting in /etc/csh.cshrc to read as follows: umask |
The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read or written to by unauthorized users. |
unknown |
AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00228 |
Ensure that Users Have Sensible Umask Values |
| CCE-80199-3 |
Ensure that Root's Path Does Not Include Relative Paths or Null Directories |
disable |
via PATH |
Ensure that none of the directories in root's path is equal to a single . character, or that it contains any instances that lead to relative path traversal, such as .. or beginning a path without the slash (/) character. Also ensure that there are no "empty" elements in the path, such as in these examples: PATH=:/bin PATH=/bin: PATH=/bin::/sbin These empty elements have the same effect as a single . character. |
Including these entries increases the risk that root could execute code from an untrusted location. |
unknown |
CM-6(a),CM-6(a) |
NaN |
NaN |
NaN |
Ensure that No Dangerous Directories Exist in Root's Path |
| CCE-80200-9 |
Ensure that Root's Path Does Not Include World or Group-Writable Directories |
go-w |
via chmod |
For each element in root's path, run: # ls -ld DIR and ensure that write permissions are disabled for group and other. |
Such entries increase the risk that root could execute code provided by unprivileged users, and potentially malicious code. |
medium |
CM-6(a),CM-6(a) |
NaN |
NaN |
NaN |
Ensure that No Dangerous Directories Exist in Root's Path |
| CCE-27275-7 |
Ensure PAM Displays Last Logon/Access Notification |
pam_succeed_if.so service !~ gdm* service !~ su* quiet session [default=1] pam_lastlog.so nowtmp showfailed session optional pam_lastlog.so silent noupdate showfailed |
via pam_lastlog |
To configure the system to notify users of last logon/access using pam_lastlog, add or correct the pam_lastlog settings in /etc/pam.d/postlogin to read as follows: session [success=1 default=ignore] pam_succeed_if.so service !~ gdm* service !~ su* quiet session [default=1] pam_lastlog.so nowtmp showfailed session optional pam_lastlog.so silent noupdate showfailed |
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. |
low |
AC-9(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Protect Accounts by Configuring PAM |
| CCE-27360-7 |
Ensure PAM Enforces Password Requirements - Minimum Special Characters |
True |
via /etc/security/pwquality.conf |
The pam_pwquality module's ocredit= parameter controls requirements for usage of special (or "other") characters in a password. When set to a negative number, any password will be required to contain that many special characters. When set to a positive number, pam_pwquality will grant +1 additional length credit for each special character. Modify the ocredit setting in /etc/security/pwquality.conf to equal to require use of a special character in passwords. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possble combinations that need to be tested before the password is compromised. Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space. |
medium |
CM-6(a),IA-5(1)(a),IA-5(4),IA-5(c) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000266-GPOS-00101 |
Set Password Quality Requirements with pam_pwquality |
| CCE-27345-8 |
Ensure PAM Enforces Password Requirements - Minimum Lowercase Characters |
True |
via /etc/security/pwquality.conf |
The pam_pwquality module's lcredit parameter controls requirements for usage of lowercase letters in a password. When set to a negative number, any password will be required to contain that many lowercase characters. When set to a positive number, pam_pwquality will grant +1 additional length credit for each lowercase character. Modify the lcredit setting in /etc/security/pwquality.conf to require the use of a lowercase character in passwords. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possble combinations that need to be tested before the password is compromised. Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space. |
medium |
CM-6(a),IA-5(1)(a),IA-5(4),IA-5(c) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000070-GPOS-00038 |
Set Password Quality Requirements with pam_pwquality |
| CCE-27160-1 |
Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session |
3 |
via /etc/security/pwquality.conf |
To configure the number of retry prompts that are permitted per-session: Edit the pam_pwquality.so statement in /etc/pam.d/system-auth to show retry=, or a lower value if site policy is more restrictive. The DoD requirement is a maximum of 3 prompts per session. |
Setting the password retry prompts that are permitted on a per-session basis to a low value requires some software, such as SSH, to re-connect. This can slow down and draw additional attention to some types of password-guessing attacks. Note that this is different from account lockout, which is provided by the pam_faillock module. |
medium |
AC-7(a),CM-6(a),IA-5(4) |
FMT_MOF_EXT.1 |
6.3.2 |
SRG-OS-000480-GPOS-00225 |
Set Password Quality Requirements with pam_pwquality |
| CCE-27512-3 |
Ensure PAM Enforces Password Requirements - Maximum Consecutive Repeating Characters from Same Character Class |
4 |
via /etc/security/pwquality.conf |
The pam_pwquality module's maxclassrepeat parameter controls requirements for consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords which contain more than that number of consecutive characters from the same character class. Modify the maxclassrepeat setting in /etc/security/pwquality.conf to equal to prevent a run of ( + 1) or more identical characters. |
Use of a complex password helps to increase the time and resources required to comrpomise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex a password, the greater the number of possible combinations that need to be tested before the password is compromised. |
medium |
CM-6(a),IA-5(1)(a),IA-5(4),IA-5(c) |
NaN |
NaN |
SRG-OS-000072-GPOS-00040 |
Set Password Quality Requirements with pam_pwquality |
| CCE-27200-5 |
Ensure PAM Enforces Password Requirements - Minimum Uppercase Characters |
True |
via /etc/security/pwquality.conf |
The pam_pwquality module's ucredit= parameter controls requirements for usage of uppercase letters in a password. When set to a negative number, any password will be required to contain that many uppercase characters. When set to a positive number, pam_pwquality will grant +1 additional length credit for each uppercase character. Modify the ucredit setting in /etc/security/pwquality.conf to require the use of an uppercase character in passwords. |
Use of a complex password helps to increase the time and resources reuiqred to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. |
medium |
CM-6(a),IA-5(1)(a),IA-5(4),IA-5(c) |
FMT_MOF_EXT.1 |
6.3.2 |
SRG-OS-000069-GPOS-00037 |
Set Password Quality Requirements with pam_pwquality |
| CCE-82020-9 |
Ensure PAM Enforces Password Requirements - Minimum Different Characters |
8 |
via /etc/security/pwquality.conf |
The pam_pwquality module's difok parameter sets the number of characters in a password that must not be present in and old password during a password change. Modify the difok setting in /etc/security/pwquality.conf to equal to require differing characters when changing passwords. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute–force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring a minimum number of different characters during password changes ensures that newly changed passwords should not resemble previously compromised ones. Note that passwords which are changed on compromised systems will still be compromised, however. |
medium |
CM-6(a),IA-5(1)(b),IA-5(4),IA-5(c) |
NaN |
NaN |
SRG-OS-000072-GPOS-00040 |
Set Password Quality Requirements with pam_pwquality |
| CCE-27293-0 |
Ensure PAM Enforces Password Requirements - Minimum Length |
16 |
via /etc/security/pwquality.conf |
The pam_pwquality module's minlen parameter controls requirements for minimum characters required in a password. Add minlen= after pam_pwquality to set minimum password length requirements. |
The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromose the password. |
medium |
CM-6(a),IA-5(1)(a),IA-5(4),IA-5(c) |
FMT_MOF_EXT.1 |
6.3.2 |
SRG-OS-000078-GPOS-00046 |
Set Password Quality Requirements with pam_pwquality |
| CCE-82055-5 |
Set Password Maximum Consecutive Repeating Characters |
4 |
via /etc/security/pwquality.conf |
The pam_pwquality module's maxrepeat parameter controls requirements for consecutive repeating characters. When set to a positive number, it will reject passwords which contain more than that number of consecutive characters. Modify the maxrepeat setting in /etc/security/pwquality.conf to equal to prevent a run of ( + 1) or more identical characters. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks. |
medium |
CM-6(a),IA-5(4),IA-5(c) |
NaN |
NaN |
SRG-OS-000072-GPOS-00040 |
Set Password Quality Requirements with pam_pwquality |
| CCE-27214-6 |
Ensure PAM Enforces Password Requirements - Minimum Digit Characters |
True |
via /etc/security/pwquality.conf |
The pam_pwquality module's dcredit parameter controls requirements for usage of digits in a password. When set to a negative number, any password will be required to contain that many digits. When set to a positive number, pam_pwquality will grant +1 additional length credit for each digit. Modify the dcredit setting in /etc/security/pwquality.conf to require the use of a digit in passwords. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring digits makes password guessing attacks more difficult by ensuring a larger search space. |
medium |
CM-6(a),IA-5(1)(a),IA-5(4),IA-5(c) |
FMT_MOF_EXT.1 |
6.3.2 |
SRG-OS-000071-GPOS-00039 |
Set Password Quality Requirements with pam_pwquality |
| CCE-82045-6 |
Ensure PAM Enforces Password Requirements - Minimum Different Categories |
3 |
via /etc/security/pwquality.conf |
The pam_pwquality module's minclass parameter controls requirements for usage of different character classes, or types, of character that must exist in a password before it is considered valid. For example, setting this value to three (3) requires that any password must have characters from at least three different categories in order to be approved. The default value is zero (0), meaning there are no required classes. There are four categories available: * Upper-case characters * Lower-case characters * Digits * Special characters (for example, punctuation) Modify the minclass setting in /etc/security/pwquality.conf entry to require differing categories of characters when changing passwords. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring a minimum number of character categories makes password guessing attacks more difficult by ensuring a larger search space. |
medium |
CM-6(a),IA-5(1)(a),IA-5(4),IA-5(c) |
NaN |
NaN |
SRG-OS-000072-GPOS-00040 |
Set Password Quality Requirements with pam_pwquality |
| CCE-82038-1 |
Set Password Hashing Algorithm in /etc/libuser.conf |
sha512 |
/etc/libuser.conf |
In /etc/libuser.conf, add or correct the following line in its [defaults] section to ensure the system will use the SHA-512 algorithm for password hashing: crypt_style = 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. 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. |
medium |
CM-6(a),IA-5(1)(c),IA-5(c) |
NaN |
NaN |
SRG-OS-000073-GPOS-00041 |
Set Password Hashing Algorithm |
| CCE-82043-1 |
Set PAM's Password Hashing Algorithm |
sha512 |
via system_auth |
The PAM system service can be configured to only store encrypted representations of passwords. In /etc/pam.d/system-auth, the password section of the file controls which PAM modules execute during a password change. Set the pam_unix.so module in the password section to include the argument sha512, as shown below: password sufficient pam_unix.so sha512 other arguments... This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default. |
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. |
medium |
CM-6(a),IA-5(1)(c),IA-5(c) |
NaN |
NaN |
SRG-OS-000073-GPOS-00041 |
Set Password Hashing Algorithm |
| CCE-82050-6 |
Set Password Hashing Algorithm in /etc/login.defs |
sha512 |
via /etc/login.defs |
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 |
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. |
medium |
CM-6(a),IA-5(1)(c),IA-5(c) |
NaN |
6.3.1 |
SRG-OS-000073-GPOS-00041 |
Set Password Hashing Algorithm |
| CCE-27350-8 |
Set Deny For Failed Password Attempts |
3 |
via pam_faillock |
To configure the system to lock out accounts after a number of incorrect login attempts using pam_faillock.so, modify the content of both /etc/pam.d/system-auth and /etc/pam.d/password-auth as follows: add the following line immediately before the pam_unix.so statement in the AUTH section: auth required pam_faillock.so preauth silent deny= unlock_time= fail_interval= add the following line immediately after the pam_unix.so statement in the AUTH section: auth [default=die] pam_faillock.so authfail deny= unlock_time= fail_interval= add the following line immediately before the pam_unix.so statement in the ACCOUNT section: account required pam_faillock.so |
Locking out user accounts after a number of incorrect attempts prevents direct password guessing attacks. |
medium |
AC-7(a),CM-6(a) |
FIA_AFL.1 |
5.3.2 |
SRG-OS-000021-GPOS-00005,SRG-OS-000329-GPOS-00128 |
Set Lockouts for Failed Password Attempts |
| CCE-27297-1 |
Set Interval For Counting Failed Password Attempts |
604800 |
via pam_faillock |
Utilizing pam_faillock.so, the fail_interval directive configures the system to lock out an account after a number of incorrect login attempts within a specified time period. Modify the content of both /etc/pam.d/system-auth and /etc/pam.d/password-auth as follows: Add the following line immediately before the pam_unix.so statement in the AUTH section: auth required pam_faillock.so preauth silent deny= unlock_time= fail_interval= Add the following line immediately after the pam_unix.so statement in the AUTH section: auth [default=die] pam_faillock.so authfail deny= unlock_time= fail_interval= Add the following line immediately before the pam_unix.so statement in the ACCOUNT section: account required pam_faillock.so |
By limiting the number of failed logon attempts the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
medium |
AC-7(a),CM-6(a) |
FIA_AFL.1 |
NaN |
SRG-OS-000021-GPOS-00005,SRG-OS-000329-GPOS-00128 |
Set Lockouts for Failed Password Attempts |
| CCE-82030-8 |
Limit Password Reuse |
5 |
via pam_unix.so or pam_pwhistory.so |
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. In the file /etc/pam.d/system-auth, append remember= to the line which refers to the pam_unix.so or pam_pwhistory.somodule, as shown below: for the pam_unix.so case: password sufficient pam_unix.so ...existing_options... remember= for the pam_pwhistory.so case: password requisite pam_pwhistory.so ...existing_options... remember= The DoD STIG requirement is 5 passwords. |
Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user. |
medium |
IA-5(1)(e),IA-5(f) |
NaN |
5.3.3 |
SRG-OS-000077-GPOS-00045 |
Set Lockouts for Failed Password Attempts |
| CCE-80353-6 |
Configure the root Account for Failed Password Attempts |
even_root_deny |
via pam_faillock |
To configure the system to lock out the root account after a number of incorrect login attempts using pam_faillock.so, modify the content of both /etc/pam.d/system-auth and /etc/pam.d/password-auth as follows: Modify the following line in the AUTH section to add even_deny_root: auth required pam_faillock.so preauth silent even_deny_root deny= unlock_time= fail_interval=Modify the following line in the AUTH section to add even_deny_root: auth [default=die] pam_faillock.so authfail even_deny_root deny= unlock_time= fail_interval= |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
medium |
AC-7(b),CM-6(a),IA-5(c) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000021-GPOS-00005,SRG-OS-000329-GPOS-00128 |
Set Lockouts for Failed Password Attempts |
| CCE-26884-7 |
Set Lockout Time for Failed Password Attempts |
0 |
via pam_faillock |
To configure the system to lock out accounts after a number of incorrect login attempts and require an administrator to unlock the account using pam_faillock.so, modify the content of both /etc/pam.d/system-auth and /etc/pam.d/password-auth as follows: add the following line immediately before the pam_unix.so statement in the AUTH section: auth required pam_faillock.so preauth silent deny= unlock_time= fail_interval= add the following line immediately after the pam_unix.so statement in the AUTH section: auth [default=die] pam_faillock.so authfail deny= unlock_time= fail_interval= add the following line immediately before the pam_unix.so statement in the ACCOUNT section: account required pam_faillock.so If unlock_time is set to 0, manual intervention by an administrator is required to unlock a user. |
Locking out user accounts after a number of incorrect attempts prevents direct password guessing attacks. Ensuring that an administrator is involved in unlocking locked accounts draws appropriate attention to such situations. |
medium |
AC-7(b),CM-6(a) |
FIA_AFL.1 |
5.3.2 |
SRG-OS-000021-GPOS-00005,SRG-OS-000329-GPOS-00128 |
Set Lockouts for Failed Password Attempts |
| CCE-27503-2 |
All GIDs referenced in /etc/passwd must be defined in /etc/group |
verify |
via /etc/passwd and /etc/group |
Add a group to the system for each GID referenced without a corresponding group. |
If a user is assigned the Group Identifier (GID) of a group not existing on the system, and a group with the Gruop Identifier (GID) is subsequently created, the user may have unintended rights to any files associated with the group. |
low |
CM-6(a),IA-2 |
NaN |
NaN |
SRG-OS-000104-GPOS-00051 |
Verify Proper Storage and Existence of Password Hashes |
| CCE-80211-6 |
Verify No netrc Files Exist |
verify |
via rm |
The .netrc files contain login information used to auto-login into FTP servers and reside in the user's home directory. These files may contain unencrypted passwords to remote FTP servers making them susceptible to access by unauthorized users and should not be used. Any .netrc files should be removed. |
Unencrypted passwords for remote FTP servers may be stored in .netrc files. |
medium |
CM-6(a),IA-5(1)(c),IA-5(7),IA-5(h) |
NaN |
NaN |
NaN |
Verify Proper Storage and Existence of Password Hashes |
| CCE-83388-9 |
Ensure there are no legacy + NIS entries in /etc/group |
verify |
via /etc/group |
The + character in /etc/group file marks a place where entries from a network information service (NIS) should be directly inserted. |
Using this method to include entries into /etc/group is considered legacy and should be avoided. These entries may provide a way for an attacker to gain access to the system. |
medium |
NaN |
NaN |
6.2.4 |
NaN |
Verify Proper Storage and Existence of Password Hashes |
| CCE-27286-4 |
Prevent Login to Accounts With Empty Password |
remove |
via /etc/pam.d/system-auth |
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 option in /etc/pam.d/system-auth to prevent logins with empty 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. |
high |
CM-6(a),IA-5(1)(a),IA-5(c) |
FIA_UAU.1 |
NaN |
SRG-OS-000480-GPOS-00227 |
Verify Proper Storage and Existence of Password Hashes |
| CCE-82889-7 |
Ensure there are no legacy + NIS entries in /etc/passwd |
verify |
via /etc/passwd |
The + character in /etc/passwd file marks a place where entries from a network information service (NIS) should be directly inserted. |
Using this method to include entries into /etc/passwd is considered legacy and should be avoided. These entries may provide a way for an attacker to gain access to the system. |
medium |
NaN |
NaN |
6.2.2 |
NaN |
Verify Proper Storage and Existence of Password Hashes |
| CCE-27352-4 |
Verify All Account Password Hashes are Shadowed |
verify |
via /etc/passwd |
If any password hashes are stored in /etc/passwd (in the second field, instead of an x or *), the cause of this misconfiguration should be investigated. The account should have its password reset and the hash should be properly stored, or the account should be deleted entirely. |
The hashes for all user account passwords should be stored in the file /etc/shadow and never in /etc/passwd, which is readable by all users. |
medium |
CM-6(a),IA-5(h) |
NaN |
NaN |
NaN |
Verify Proper Storage and Existence of Password Hashes |
| CCE-83390-5 |
Ensure there are no legacy + NIS entries in /etc/shadow |
verify |
via /etc/shadow |
The + character in /etc/shadow file marks a place where entries from a network information service (NIS) should be directly inserted. |
Using this method to include entries into /etc/shadow is considered legacy and should be avoided. These entries may provide a way for an attacker to gain access to the system. |
medium |
NaN |
NaN |
6.2.3 |
NaN |
Verify Proper Storage and Existence of Password Hashes |
| CCE-82049-8 |
Set Password Minimum Length in login.defs |
16 |
via /etc/login.defs |
To specify password length requirements for new accounts, edit the file /etc/login.defs and add or correct the following line: PASS_MIN_LEN The DoD requirement is 15. The FISMA requirement is 12. The profile requirement is . If a program consults /etc/login.defs and also another PAM module (such as pam_pwquality) during a password change operation, then the most restrictive must be satisfied. See PAM section for more information about enforcing password quality requirements. |
Requiring a minimum password length makes password cracking attacks more difficult by ensuring a larger search space. However, any security benefit from an onerous requirement must be carefully weighed against usability problems, support costs, or counterproductive behavior that may result. |
medium |
CM-6(a),IA-5(1)(a),IA-5(f) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000078-GPOS-00046 |
Set Password Expiration Parameters |
| CCE-80521-8 |
Set Existing Passwords Minimum Age |
True |
via chage |
Configure non-compliant accounts to enforce a 24 hours/1 day minimum password lifetime by running the following command: $ sudo chage -m 1 USER |
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. |
medium |
CM-6(a),IA-5(1)(d),IA-5(f) |
NaN |
NaN |
SRG-OS-000075-GPOS-00043 |
Set Password Expiration Parameters |
| CCE-80522-6 |
Set Existing Passwords Maximum Age |
60 |
via chage |
Configure non-compliant accounts to enforce a 60-day maximum password lifetime restriction by running the following command: $ sudo chage -M 60 USER |
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. |
medium |
CM-6(a),IA-5(1)(d),IA-5(f) |
NaN |
NaN |
SRG-OS-000076-GPOS-00044 |
Set Password Expiration Parameters |
| CCE-82016-7 |
Set Password Warning Age |
7 |
via /etc/login.defs |
To specify how many days prior to password expiration that a warning will be issued to users, edit the file /etc/login.defs and add or correct the following line: PASS_WARN_AGE The DoD requirement is 7. The profile requirement is . |
Setting the password warning age enables users to make the change at a practical time. |
medium |
CM-6(a),IA-5(1)(d),IA-5(f) |
NaN |
NaN |
NaN |
Set Password Expiration Parameters |
| CCE-82036-5 |
Set Password Minimum Age |
True |
via /etc/login.defs |
To specify password minimum age for new accounts, edit the file /etc/login.defs and add or correct the following line: PASS_MIN_DAYS A value of 1 day is considered sufficient for many environments. The DoD requirement is 1. The profile requirement is . |
Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse. Setting the minimum password age protects against users cycling back to a favorite password after satisfying the password reuse requirement. |
medium |
CM-6(a),IA-5(1)(d),IA-5(f) |
NaN |
NaN |
SRG-OS-000075-GPOS-00043 |
Set Password Expiration Parameters |
| CCE-27051-2 |
Set Password Maximum Age |
60 |
via /etc/login.defs |
To specify password maximum age for new accounts, edit the file /etc/login.defs and add or correct the following line: PASS_MAX_DAYS A value of 180 days is sufficient for many environments. The DoD requirement is 60. The profile requirement is . |
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. |
medium |
CM-6(a),IA-5(1)(d),IA-5(f) |
NaN |
NaN |
SRG-OS-000076-GPOS-00044 |
Set Password Expiration Parameters |
| CCE-80650-5 |
Ensure that System Accounts Are Locked |
-l SYSACCT |
via passwd |
Some accounts are not associated with a human user of the system, and exist to perform some administrative function. An attacker should not be able to log into these accounts. System accounts are those user accounts with a user ID less than UID_MIN, where value of the UID_MIN directive is set in /etc/login.defs configuration file. In the default configuration UID_MIN is set to 500, thus system accounts are those user accounts with a user ID less than 500. If any system account SYSACCT (other than root) has an unlocked password, disable it with the command: $ sudo passwd -l SYSACCT |
Disabling authentication for default system accounts makes it more difficult for attackers to make use of them to compromise a system.false |
medium |
AC-6,CM-6(a) |
NaN |
NaN |
NaN |
Restrict Root Logins |
| CCE-27318-5 |
Restrict Virtual Console Root Logins |
disable |
via /etc/securetty |
To restrict root logins through the (deprecated) virtual console devices, ensure lines of this form do not appear in /etc/securetty: vc/1 vc/2 vc/3 vc/4 |
Preventing direct root login to virtual console devices helps ensure accountability for actions taken on the system using the root account. |
medium |
AC-6,CM-6(a) |
NaN |
NaN |
SRG-OS-000324-GPOS-00125 |
Restrict Root Logins |
| CCE-80210-8 |
Root Path Must Be Vendor Default |
verify |
via PATH |
Assuming root shell is bash, edit the following files: ~/.profile ~/.bashrc Change any PATH variables to the vendor default for root and remove any empty PATH entries or references to relative paths. |
The root account's executable search path must be the vendor default, and must contain only absolute paths. |
unknown |
CM-6(a) |
NaN |
NaN |
NaN |
Restrict Root Logins |
| CCE-80209-0 |
Restrict Web Browser Use for Administrative Accounts |
restrict |
via network |
Enforce policy requiring administrative accounts use web browsers only for local service administration. |
If a browser vulnerability is exploited while running with administrative privileges, the entire system could be compromised. Specific exceptions for local service administration should be documented in site-defined policy. |
unknown |
NaN |
NaN |
NaN |
NaN |
Restrict Root Logins |
| CCE-27294-8 |
Direct root Logins Not Allowed |
“” |
via /etc/securetty |
To further limit access to the root account, administrators can disable root logins at the console by editing the /etc/securetty file. This file lists all devices the root user is allowed to login to. If the file does not exist at all, the root user can login through any communication device on the system, whether via the console or via a raw network interface. This is dangerous as user can login to the system as root via Telnet, which sends the password in plain text over the network. By default, Red Hat Enterprise Linux 7's /etc/securetty file only allows the root user to login at the console physically attached to the system. To prevent root from logging in, remove the contents of this file. To prevent direct root logins, remove the contents of this file by typing the following command: $ sudo echo > /etc/securetty |
Disabling direct root logins ensures proper accountability and multifactor authentication to privileged accounts. Users will first login, then escalate to privileged (root) access via su / sudo. This is required for FISMA Low and FISMA Moderate systems. |
medium |
CM-6(a),IA-2 |
NaN |
NaN |
NaN |
Restrict Root Logins |
| CCE-27268-2 |
Restrict Serial Port Root Logins |
ttyS0 ttyS1 |
via /etc/securetty |
To restrict root logins on serial ports, ensure lines of this form do not appear in /etc/securetty: ttyS0 ttyS1 |
Preventing direct root login to serial port interfaces helps ensure accountability for actions taken on the systems using the root account. |
medium |
AC-6,CM-6(a) |
NaN |
NaN |
NaN |
Restrict Root Logins |
| CCE-82015-9 |
Ensure that System Accounts Do Not Run a Shell Upon Login |
/sbin/nologin |
via usermod |
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 |
Ensuring shells are not given to system accounts upon login makes it more difficult for attackers to make use of system accounts. |
medium |
AC-6,CM-6(a) |
NaN |
5.4.2 |
NaN |
Restrict Root Logins |
| CCE-82054-8 |
Verify Only Root Has UID 0 |
verify |
via /etc/passwd |
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. |
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. |
high |
AC-6(5),IA-2,IA-4(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Restrict Root Logins |
| CCE-80208-2 |
Ensure All Accounts on the System Have Unique Names |
verify |
via getent |
Ensure accounts on the system have unique names. To ensure all accounts have unique names, run the following command: $ sudo getent passwd | awk -F: '{ print $1}' | uniq -d If a username is returned, change or delete the username. |
Unique usernames allow for accountability on the system. |
medium |
NaN |
NaN |
NaN |
NaN |
Set Account Expiration Parameters |
| CCE-81000-2 |
Assign Expiration Date to Temporary Accounts |
-E YYYY-MM-DD USER |
via chage |
Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts. In the event temporary or emergency accounts are required, configure the system to terminate them after a documented time period. For every temporary and emergency 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. |
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. |
unknown |
AC-2(2),AC-2(3),CM-6(a) |
NaN |
NaN |
SRG-OS-000002-GPOS-00002,SRG-OS-000123-GPOS-00064 |
Set Account Expiration Parameters |
| CCE-27355-7 |
Set Account Expiration Following Inactivity |
35 |
via /etc/default/useradd |
To specify the number of days after a password expires (which signifies inactivity) until an account is permanently disabled, add or correct the following lines in /etc/default/useradd, substituting NUM_DAYS appropriately: INACTIVE= A value of 35 is recommended; however, this profile expects that the value is set to . If a password is currently on the verge of expiration, then 35 days remain until the account is automatically disabled. However, if the password will not expire for another 60 days, then 95 days could elapse until the account would be automatically disabled. See the useradd man page for more information. Determining the inactivity timeout must be done with careful consideration of the length of a "normal" period of inactivity for users in the particular environment. Setting the timeout too low incurs support costs and also has the potential to impact availability of the system to legitimate users. |
Disabling inactive accounts ensures that accounts which may not have been responsibly removed are not available to attackers who may have compromised their credentials. |
medium |
AC-2(3),CM-6(a),IA-4(e) |
NaN |
NaN |
SRG-OS-000118-GPOS-00060 |
Set Account Expiration Parameters |
| CCE-83717-9 |
Verify ownership of System Login Banner |
root |
via chown |
To properly set the owner of /etc/issue, run the command: $ sudo chown root /etc/issue |
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. Proper ownership will ensure that only root user can modify the banner. |
medium |
NaN |
NaN |
1.7.1.5 |
NaN |
Warning Banners for System Accesses |
| CCE-83394-7 |
Modify the System Message of the Day Banner |
configure text |
via /etc/motd |
To configure the system message banner edit /etc/motd. 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: -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. OR: I've read & consent to terms in IS user agreem't. |
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. |
medium |
NaN |
NaN |
NaN |
NaN |
Warning Banners for System Accesses |
| CCE-83337-6 |
Verify permissions on Message of the Day Banner |
644 |
via chmod |
To properly set the permissions of /etc/motd, run the command: $ sudo chmod 0644 /etc/motd |
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. Proper permissions will ensure that only root user can modify the banner. |
medium |
NaN |
NaN |
1.7.1.4 |
NaN |
Warning Banners for System Accesses |
| CCE-83737-7 |
Verify ownership of Message of the Day Banner |
root |
via chown |
To properly set the owner of /etc/motd, run the command: $ sudo chown root /etc/motd |
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. Proper ownership will ensure that only root user can modify the banner. |
medium |
NaN |
NaN |
1.7.1.4 |
NaN |
Warning Banners for System Accesses |
| CCE-27303-7 |
Modify the System Login Banner |
configure text |
via /etc/issue |
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: -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. OR: I've read & consent to terms in IS user agreem't. |
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. |
medium |
AC-8(a),AC-8(c) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007 |
Warning Banners for System Accesses |
| CCE-83347-5 |
Verify permissions on System Login Banner |
644 |
via chmod |
To properly set the permissions of /etc/issue, run the command: $ sudo chmod 0644 /etc/issue |
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. Proper permissions will ensure that only root user can modify the banner. |
medium |
NaN |
NaN |
1.7.1.5 |
NaN |
Warning Banners for System Accesses |
| CCE-83727-8 |
Verify Group Ownership of Message of the Day Banner |
root |
via chgrp |
To properly set the group owner of /etc/motd, run the command: $ sudo chgrp root /etc/motd |
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. Proper group ownership will ensure that only root user can modify the banner. |
medium |
NaN |
NaN |
1.7.1.4 |
NaN |
Warning Banners for System Accesses |
| CCE-83707-0 |
Verify Group Ownership of System Login Banner |
root |
via chgrp |
To properly set the group owner of /etc/issue, run the command: $ sudo chgrp root /etc/issue |
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. Proper group ownership will ensure that only root user can modify the banner. |
medium |
NaN |
NaN |
1.7.1.5 |
NaN |
Warning Banners for System Accesses |
| CCE-26892-0 |
Set the GNOME3 Login Warning Banner Text |
configure text |
via dconf db config files |
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-text After 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. |
An appropriate warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. |
medium |
AC-8(a),AC-8(c) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007,SRG-OS-000228-GPOS-00088 |
Implement a GUI Warning Banner |
| CCE-26970-4 |
Enable GNOME3 Login Warning Banner |
True |
via dconf db config files |
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=true 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-enable After the settings have been set, run dconf update. The banner text must also be set. |
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. |
medium |
AC-8(a),AC-8(b),AC-8(c) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007,SRG-OS-000228-GPOS-00088 |
Implement a GUI Warning Banner |
| CCE-82954-9 |
Install audispd-plugins Package |
install |
via yum |
The audispd-plugins package can be installed with the following command: $ sudo yum install audispd-plugins |
audispd-plugins provides plugins for the real-time interface to the audit subsystem, audispd. These plugins can do things like relay events to remote machines or analyze events for suspicious behavior. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000342-GPOS-00133 |
System Accounting with auditd |
| CCE-81042-4 |
Ensure the audit Subsystem is Installed |
install |
via yum |
The audit package should be 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. |
medium |
AC-7(a),AU-12(2),AU-14,AU-2(a),AU-7(1),AU-7(2),CM-6(a) |
NaN |
NaN |
SRG-OS-000122-GPOS-00063,SRG-OS-000480-GPOS-00227 |
System Accounting with auditd |
| CCE-27407-6 |
Enable auditd Service |
enable |
via systemctl |
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 |
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. |
high |
AC-2(g),AC-6(9),AU-10,AU-12(c),AU-14(1),AU-2(d),AU-3,CM-6(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000038-GPOS-00016,SRG-OS-000039-GPOS-00017,SRG-OS-000040-GPOS-00018,SRG-OS-000042-GPOS-00021,SRG-OS-000254-GPOS-00095,SRG-OS-000255-GPOS-00096,SRG-OS-000365-GPOS-00152 |
System Accounting with auditd |
| CCE-27212-0 |
Enable Auditing for Processes Which Start Prior to the Audit Daemon |
audit=1 |
via grub |
To ensure all processes can be audited, even those which start prior to the audit daemon, add the argument audit=1 to the default GRUB 2 command line for the Linux operating system in /etc/default/grub, so that the line looks similar to GRUB_CMDLINE_LINUX="... audit=1 ..." In case the GRUB_DISABLE_RECOVERY is set to true, then the parameter should be added to the GRUB_CMDLINE_LINUX_DEFAULT instead. |
Each process on the system carries an "auditable" flag which indicates whether its activities can be audited. Although auditd takes care of enabling this for all processes which launch after it does, adding the kernel argument ensures it is set for every process during boot. |
medium |
AC-17(1),AU-10,AU-14(1),CM-6(a),IR-5(1) |
NaN |
NaN |
SRG-OS-000254-GPOS-00095 |
System Accounting with auditd |
| CCE-82156-1 |
Extend Audit Backlog Limit for the Audit Daemon |
8192 |
via grub |
To improve the kernel capacity to queue all log events, even those which occurred prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default GRUB 2 command line for the Linux operating system in /etc/default/grub, in the manner below: GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=VolGroup/LogVol06 rd.lvm.lv=VolGroup/lv_swap rhgb quiet rd.shell=0 audit=1 audit_backlog_limit=8192" |
audit_backlog_limit sets the queue length for audit events awaiting transfer to the audit daemon. Until the audit daemon is up and running, all log messages are stored in this queue. If the queue is overrun during boot process, the action defined by audit failure flag is taken. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000254-GPOS-00095 |
System Accounting with auditd |
| CCE-82370-8 |
Configure audit according to OSPP requirements |
audit enabled |
via /etc/audit/audit.rules or auditctl |
Configure audit to meet requirements for Operating System Protection Profile (OSPP) v4.2.1. Audit defines groups of rules in /usr/share/doc/audit/rules to satisfy specific policies. To fulfill requirements for compliance with OSPP v4.2.1, the following files are necessary: /usr/share/doc/audit-VERSION/rules/10-base-config.rules/usr/share/doc/audit-VERSION/rules/11-loginuid.rules/usr/share/doc/audit-VERSION/rules/30-ospp-v42.rules/usr/share/doc/audit-VERSION/rules/43-module-load.rules Copy the files from /usr/share/doc/audit/rules to /etc/audit/rules.d: cp /usr/share/doc/audit*/rules/{10-base-config,11-loginuid,30-ospp-v42,43-module-load}.rules /etc/audit/rules.d/ |
The audit rules defined in /usr/share/doc/audit/rules are the recommended way to meet compliance with OSPP v4.2.1. |
medium |
NONE |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000004-GPOS-00004,SRG-OS-000064-GPOS-00033,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000327-GPOS-00127,SRG-OS-000365-GPOS-00152,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-000474-GPOS-00219,SRG-OS-000475-GPOS-00220,SRG-OS-000476-GPOS-00221,SRG-OS-000477-GPOS-00222 |
System Accounting with auditd |
| CCE-80433-6 |
Record Events that Modify User/Group Information - /etc/group |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.5 |
SRG-OS-000004-GPOS-00004 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-80432-8 |
Record Events that Modify User/Group Information - /etc/gshadow |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.5 |
SRG-OS-000004-GPOS-00004 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27205-4 |
System Audit Logs Must Have Mode 0640 or Less Permissive |
600 |
via chmod |
If log_group in /etc/audit/auditd.conf is set to a group other than the root group account, change the mode of the audit log files with the following command: $ sudo chmod 0640 audit_file Otherwise, change the mode of the audit log files with the following command: $ sudo chmod 0600 audit_file |
If users can write to audit logs, audit trails can be modified or destroyed. |
medium |
AC-6(1),AU-9(4),CM-6(a) |
NaN |
NaN |
SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029,SRG-OS-000206-GPOS-00084 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27192-4 |
Record Events that Modify User/Group Information |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 -w /etc/passwd -p wa -k audit_rules_usergroup_modification -w /etc/gshadow -p wa -k audit_rules_usergroup_modification -w /etc/shadow -p wa -k audit_rules_usergroup_modification -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/group -p wa -k audit_rules_usergroup_modification -w /etc/passwd -p wa -k audit_rules_usergroup_modification -w /etc/gshadow -p wa -k audit_rules_usergroup_modification -w /etc/shadow -p wa -k audit_rules_usergroup_modification -w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
5.2.5 |
SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000239-GPOS-00089,SRG-OS-000241-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000476-GPOS-00221 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-80997-0 |
Shutdown System When Auditing Failures Occur |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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: -f 2 If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to the top of the /etc/audit/audit.rules file: -f 2 |
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. |
medium |
AU-5(b),CM-6(a),SC-24 |
NaN |
NaN |
SRG-OS-000046-GPOS-00022,SRG-OS-000047-GPOS-00023 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-80431-0 |
Record Events that Modify User/Group Information - /etc/shadow |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.5 |
SRG-OS-000004-GPOS-00004 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-80430-2 |
Record Events that Modify User/Group Information - /etc/security/opasswd |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.5 |
SRG-OS-000004-GPOS-00004 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27097-5 |
Make the auditd Configuration Immutable |
audit enabled |
via /etc/audit/audit.rules or auditctl |
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d in order to make the auditd configuration immutable: -e 2 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 in order to make the auditd configuration immutable: -e 2 With this setting, a reboot will be required to change any audit rules. |
Making the audit configuration immutable prevents accidental as well as malicious modification of the audit rules, although it may be problematic if legitimate changes are needed during system operation |
medium |
AC-6(9),CM-6(a) |
NaN |
4.1.18 |
NaN |
Configure auditd Rules for Comprehensive Auditing |
| CCE-80435-1 |
Record Events that Modify User/Group Information - /etc/passwd |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.5 |
SRG-OS-000004-GPOS-00004,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-000476-GPOS-00221 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27301-1 |
Record Attempts to Alter Process and Session Initiation Information |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/run/utmp -p wa -k session -w /var/log/btmp -p wa -k session -w /var/log/wtmp -p wa -k session 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 watch for attempted manual edits of files involved in storing such process information: -w /var/run/utmp -p wa -k session -w /var/log/btmp -p wa -k session -w /var/log/wtmp -p wa -k session |
Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27076-9 |
Record Events that Modify the System's Network Environment |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S sethostname,setdomainname -F key=audit_rules_networkconfig_modification -w /etc/issue -p wa -k audit_rules_networkconfig_modification -w /etc/issue.net -p wa -k audit_rules_networkconfig_modification -w /etc/hosts -p wa -k audit_rules_networkconfig_modification -w /etc/sysconfig/network -p wa -k audit_rules_networkconfig_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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S sethostname,setdomainname -F key=audit_rules_networkconfig_modification -w /etc/issue -p wa -k audit_rules_networkconfig_modification -w /etc/issue.net -p wa -k audit_rules_networkconfig_modification -w /etc/hosts -p wa -k audit_rules_networkconfig_modification -w /etc/sysconfig/network -p wa -k audit_rules_networkconfig_modification |
The network environment should not be modified by anything other than administrator action. Any change to network parameters should be audited. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Configure auditd Rules for Comprehensive Auditing |
| CCE-82071-2 |
Record Access Events to Audit Log Directory |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect access events to read audit log directory. The following audit rule will assure that access to audit log directory are collected. -a always,exit -F dir=/var/log/audit/ -F perm=r -F auid>=1000 -F auid!=unset -F key=access-audit-trail If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rule 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 rule to /etc/audit/audit.rules file. |
Attempts to read the logs should be recorded, suspicious access to audit log files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise.' |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Configure auditd Rules for Comprehensive Auditing |
| CCE-80125-8 |
System Audit Logs Must Be Owned By Root |
root |
via chown |
All audit logs must be owned by root user and group. By default, the path for audit log is /var/log/audit/. To properly set the owner of /var/log/audit, run the command: $ sudo chown root /var/log/audit To properly set the owner of /var/log/audit/*, run the command: $ sudo chown root /var/log/audit/* |
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. |
medium |
AC-6(1),AU-9(4),CM-6(a) |
NaN |
NaN |
SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029,SRG-OS-000206-GPOS-00084 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27447-2 |
Ensure auditd Collects Information on Exporting to Media (successful) |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=export 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, 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 |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
5.2.13 |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27461-3 |
Ensure auditd Collects System Administrator Actions |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 actions 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: -w /etc/sudoers -p wa -k actions -w /etc/sudoers.d/ -p wa -k 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. |
medium |
AC-2(7)(b),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27168-4 |
Record Events that Modify the System's Mandatory Access Controls |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/selinux/ -p wa -k MAC-policy 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: -w /etc/selinux/ -p wa -k MAC-policy |
The system's mandatory access policy (SELinux) should not be arbitrarily changed by anything other than administrator action. All changes to MAC policy should be audited. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Configure auditd Rules for Comprehensive Auditing |
| CCE-27389-6 |
Record Events that Modify the System's Discretionary Access Controls - fsetxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If 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 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 fsetxattr -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 fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27356-5 |
Record Events that Modify the System's Discretionary Access Controls - fchown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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_mod If 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 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 fchown -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 fchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27387-0 |
Record Events that Modify the System's Discretionary Access Controls - fchownat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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_mod If 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 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 fchownat -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 fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27393-8 |
Record Events that Modify the System's Discretionary Access Controls - fchmod |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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_mod If 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 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 fchmod -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 fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27410-0 |
Record Events that Modify the System's Discretionary Access Controls - lremovexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27367-2 |
Record Events that Modify the System's Discretionary Access Controls - removexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27353-2 |
Record Events that Modify the System's Discretionary Access Controls - fremovexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27280-7 |
Record Events that Modify the System's Discretionary Access Controls - lsetxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If 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 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 lsetxattr -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 lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27213-8 |
Record Events that Modify the System's Discretionary Access Controls - setxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod If 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 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 setxattr -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 setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27388-8 |
Record Events that Modify the System's Discretionary Access Controls - fchmodat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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_mod If 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 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 fchmodat -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 fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27364-9 |
Record Events that Modify the System's Discretionary Access Controls - chown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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_mod If 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 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 chown -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 chown -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27339-1 |
Record Events that Modify the System's Discretionary Access Controls - chmod |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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_mod If 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 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 chmod -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 chmod -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-27083-5 |
Record Events that Modify the System's Discretionary Access Controls - lchown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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_mod If 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 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 lchown -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 lchown -F auid>=1000 -F auid!=unset -F key=perm_mod |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000474-GPOS-00219 |
Record Events that Modify the System's Discretionary Access Controls |
| CCE-80402-1 |
Ensure auditd Collects Information on the Use of Privileged Commands - sudoedit |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80404-7 |
Ensure auditd Collects Information on the Use of Privileged Commands - chsh |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80398-1 |
Ensure auditd Collects Information on the Use of Privileged Commands - chage |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-82074-6 |
Ensure auditd Collects Information on the Use of Privileged Commands - usernetctl |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/usernetctl -F auid>=1000 -F auid!=unset -F key=privileged If 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/usernetctl -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Record Information on the Use of Privileged Commands |
| CCE-80411-2 |
Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80397-3 |
Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80396-5 |
Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80401-3 |
Ensure auditd Collects Information on the Use of Privileged Commands - sudo |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-27437-3 |
Ensure auditd Collects Information on the Use of Privileged Commands |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. To find the relevant setuid / setgid programs, run the following command for each local partition PART: $ sudo find PART -xdev -type f -perm -4000 -o -type f -perm -2000 2>/dev/null 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 for each setuid / setgid program on the system, replacing the SETUID_PROG_PATH part with the full path of that setuid / setgid program in the list: -a always,exit -F path=SETUID_PROG_PATH -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged If 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 for each setuid / setgid program on the system, replacing the SETUID_PROG_PATH part with the full path of that setuid / setgid program in the list: -a always,exit -F path=SETUID_PROG_PATH -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
5.2.10 |
SRG-OS-000327-GPOS-00127 |
Record Information on the Use of Privileged Commands |
| CCE-80405-4 |
Ensure auditd Collects Information on the Use of Privileged Commands - umount |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80400-5 |
Ensure auditd Collects Information on the Use of Privileged Commands - su |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80409-6 |
Ensure auditd Collects Information on the Use of Privileged Commands - pt_chown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/libexec/pt_chown -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/libexec/pt_chown -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80410-4 |
Ensure auditd Collects Information on the Use of Privileged Commands - crontab |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80395-7 |
Ensure auditd Collects Information on the Use of Privileged Commands - passwd |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80408-8 |
Ensure auditd Collects Information on the Use of Privileged Commands - ssh-keysign |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80406-2 |
Ensure auditd Collects Information on the Use of Privileged Commands - postdrop |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-82200-7 |
Ensure auditd Collects Information on the Use of Privileged Commands - newgidmap |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/newgidmap -F auid>=1000 -F auid!=unset -F key=privileged If 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/newgidmap -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Record Information on the Use of Privileged Commands |
| CCE-80399-9 |
Ensure auditd Collects Information on the Use of Privileged Commands - userhelper |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-81060-6 |
Ensure auditd Collects Information on the Use of Privileged Commands - at |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/at -F auid>=1000 -F auid!=unset -F key=privileged If 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/at -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Record Information on the Use of Privileged Commands |
| CCE-81064-8 |
Ensure auditd Collects Information on the Use of Privileged Commands - mount |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172 |
Record Information on the Use of Privileged Commands |
| CCE-81070-5 |
Ensure auditd Collects Information on the Use of Privileged Commands - newuidmap |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/newuidmap -F auid>=1000 -F auid!=unset -F key=privileged If 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/newuidmap -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Record Information on the Use of Privileged Commands |
| CCE-80407-0 |
Ensure auditd Collects Information on the Use of Privileged Commands - postqueue |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect the execution of privileged commands for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F auid!=unset -F key=privileged If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules: -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80403-9 |
Ensure auditd Collects Information on the Use of Privileged Commands - newgrp |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged If 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 auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 |
Record Information on the Use of Privileged Commands |
| CCE-80413-8 |
Ensure auditd Collects File Deletion Events by User - renameat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete 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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete |
Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.14 |
SRG-OS-000392-GPOS-00172,SRG-OS-000466-GPOS-00210,SRG-OS-000467-GPOS-00211,SRG-OS-000468-GPOS-00212 |
Record File Deletion Events by User |
| CCE-27206-2 |
Ensure auditd Collects File Deletion Events by User |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum the audit system should collect file deletion events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S rmdir,unlink,unlinkat,rename,renameat -F auid>=1000 -F auid!=unset -F key=delete 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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S rmdir,unlink,unlinkat,rename -S renameat -F auid>=1000 -F auid!=unset -F key=delete |
Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.14 |
NaN |
Record File Deletion Events by User |
| CCE-80996-2 |
Ensure auditd Collects File Deletion Events by User - unlink |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete 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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete |
Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.14 |
SRG-OS-000392-GPOS-00172,SRG-OS-000466-GPOS-00210,SRG-OS-000467-GPOS-00211,SRG-OS-000468-GPOS-00212 |
Record File Deletion Events by User |
| CCE-80412-0 |
Ensure auditd Collects File Deletion Events by User - rmdir |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete 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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete |
Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.14 |
SRG-OS-000392-GPOS-00172,SRG-OS-000466-GPOS-00210,SRG-OS-000467-GPOS-00211,SRG-OS-000468-GPOS-00212 |
Record File Deletion Events by User |
| CCE-80995-4 |
Ensure auditd Collects File Deletion Events by User - rename |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete 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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete |
Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.14 |
SRG-OS-000392-GPOS-00172,SRG-OS-000466-GPOS-00210,SRG-OS-000467-GPOS-00211,SRG-OS-000468-GPOS-00212 |
Record File Deletion Events by User |
| CCE-80662-0 |
Ensure auditd Collects File Deletion Events by User - unlinkat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete 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, setting ARCH to either b32 or b64 as appropriate for your system: -a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete |
Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.14 |
SRG-OS-000392-GPOS-00172,SRG-OS-000466-GPOS-00210,SRG-OS-000467-GPOS-00211,SRG-OS-000468-GPOS-00212 |
Record File Deletion Events by User |
| CCE-80393-2 |
Record Any Attempts to Run chcon |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 auid>=1000 -F auid!=unset -F key=privileged 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 path=/usr/bin/chcon -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000392-GPOS-00172,SRG-OS-000463-GPOS-00207,SRG-OS-000465-GPOS-00209 |
Record Execution Attempts to Run SELinux Privileged Commands |
| CCE-82362-5 |
Record Any Attempts to Run seunshare |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect any execution attempt of the seunshare command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/seunshare -F auid>=1000 -F auid!=unset -F key=privileged 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 path=/usr/sbin/seunshare -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
NaN |
Record Execution Attempts to Run SELinux Privileged Commands |
| CCE-80394-0 |
Record Any Attempts to Run restorecon |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect any execution attempt of the restorecon command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/restorecon -F auid>=1000 -F auid!=unset -F key=privileged 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 path=/usr/sbin/restorecon -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000392-GPOS-00172,SRG-OS-000463-GPOS-00207,SRG-OS-000465-GPOS-00209 |
Record Execution Attempts to Run SELinux Privileged Commands |
| CCE-80391-6 |
Record Any Attempts to Run semanage |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect any execution attempt of the semanage command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=unset -F key=privileged 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 path=/usr/sbin/semanage -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-2(4),AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000392-GPOS-00172,SRG-OS-000463-GPOS-00207,SRG-OS-000465-GPOS-00209 |
Record Execution Attempts to Run SELinux Privileged Commands |
| CCE-80660-4 |
Record Any Attempts to Run setfiles |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect any execution attempt of the setfiles command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=unset -F key=privileged 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 path=/usr/sbin/setfiles -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
SRG-OS-000392-GPOS-00172,SRG-OS-000463-GPOS-00207,SRG-OS-000465-GPOS-00209 |
Record Execution Attempts to Run SELinux Privileged Commands |
| CCE-80392-4 |
Record Any Attempts to Run setsebool |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect any execution attempt of the setsebool command for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F auid!=unset -F key=privileged 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 path=/usr/sbin/setsebool -F auid>=1000 -F auid!=unset -F key=privileged |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000392-GPOS-00172,SRG-OS-000463-GPOS-00207,SRG-OS-000465-GPOS-00209 |
Record Execution Attempts to Run SELinux Privileged Commands |
| CCE-81127-3 |
Record Successful Creation Attempts to Files - openat O_CREAT |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The openat syscall can be used to create new files when O_CREAT flag is specified. The following audit rules will assure that successful attempts to create a file via openat syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S openat -F a2&0100 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-create If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F a2&0100 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-create |
Successful 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. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-80390-8 |
Record Unsuccessful Access Attempts to Files - ftruncate |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F exiu=-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 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 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=access If 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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81134-9 |
Record Successful Creation Attempts to Files - open O_CREAT |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The open syscall can be used to create new files when O_CREAT flag is specified. The following audit rules will assure that successful attempts to create a file via open syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open -F a2&0100 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-create If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F a2&0100 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-create |
Successful 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. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-80388-2 |
Record Unsuccessful Access Attempts to Files - open_by_handle_at |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=access If 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=access 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 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=access If 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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81098-6 |
Record Unsuccessul Permission Changes to Files - removexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 removexattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S removexattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S removexattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S removexattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81102-6 |
Record Unsuccessul Permission Changes to Files - fremovexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 fremovexattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S fremovexattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fremovexattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S fremovexattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81094-5 |
Record Unsuccessul Permission Changes to Files - lsetxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 lsetxattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S lsetxattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lsetxattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S lsetxattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82094-4 |
Record Successful Delete Attempts to Files - renameat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion 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 renameat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S renameat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete 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 renameat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S renameat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete |
File deletion attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82091-0 |
Record Successful Delete Attempts to Files - rename |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion 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 rename -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S rename -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete 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 success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S rename -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete |
File deletion attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82004-3 |
Record Successful Access Attempts to Files - ftruncate |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access 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 ftruncate -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access |
File access attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82012-6 |
Record Successful Access Attempts to Files - open_by_handle_at |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access 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 open_by_handle_at -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access |
File access attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81140-6 |
Record Successful Creation Attempts to Files - open_by_handle_at O_TRUNC_WRITE |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect detailed file access records for all users and root. The open_by_handle_at syscall can be used to modify files if called for write operation with the O_TRUNC_WRITE flag. The following audit rules will assure that successful attempts to create a file via open_by_handle_at syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open_by_handle_at -F a2&01003 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-modification If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F a2&01003 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-modification |
Successful 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. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82112-4 |
Record Successful Permission Changes to Files - fsetxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 fsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81084-6 |
Record Unsuccessul Ownership Changes to Files - fchownat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file ownership change 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 fchownat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S fchownat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchownat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S fchownat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change ownership of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82115-7 |
Record Successful Permission Changes to Files - removexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S removexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S removexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 removexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S removexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81100-0 |
Record Unsuccessul Permission Changes to Files - lremovexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 lremovexattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S lremovexattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lremovexattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S lremovexattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81106-7 |
Record Unsuccessul Delete Attempts to Files - unlink |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 unlink -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b32 -S unlink -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S unlink -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b64 -S unlink -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82085-2 |
Record Successful Delete Attempts to Files - unlink |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion 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 unlink -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S unlink -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete 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 unlink -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S unlink -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete |
File deletion attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81119-0 |
Record Unsuccessful Creation Attempts to Files - open O_CREAT |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unauthorized file accesses for all users and root. The open syscall can be used to create new files when O_CREAT flag is specified. The following auidt rules will asure that unsuccessful attempts to create a file via open syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open -F a1&0100 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-create -a always,exit -F arch=b32 -S open -F a1&0100 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-create If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F a1&0100 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-create -a always,exit -F arch=b64 -S open -F a1&0100 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-create |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82082-9 |
Record Unsuccessul Delete Attempts to Files - renameat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 renameat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b32 -S renameat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S renameat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b64 -S renameat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81088-7 |
Record Unsuccessul Permission Changes to Files - fchmod |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 fchmod -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S fchmod -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchmod -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S fchmod -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81080-4 |
Record Unsuccessul Ownership Changes to Files - fchown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file ownership change 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 fchown -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S fchown -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchown -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S fchown -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change ownership of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82106-6 |
Record Successful Permission Changes to Files - setxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S setxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S setxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 setxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S setxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File deletion attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81104-2 |
Record Unsuccessul Delete Attempts to Files - unlinkat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 unlinkat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b32 -S unlinkat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S unlinkat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete -a always,exit -F arch=b64 -S unlinkat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccessful-delete |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82100-9 |
Record Successful Permission Changes to Files - fchmod |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 fchmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81092-9 |
Record Unsuccessul Permission Changes to Files - setxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 setxattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S setxattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S setxattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S setxattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82097-7 |
Record Successful Permission Changes to Files - chmod |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S chmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S chmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 chmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S chmod -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82121-5 |
Record Successful Permission Changes to Files - fremovexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 fremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81123-2 |
Record Unsuccessful Modification Attempts to Files - openat O_TRUNC_WRITE |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect detailed unauthorized file accesses for all users and root. The openat syscall can be used to modify files if called for write operation of with O_TRUNC_WRITE flag. The following auidt rules will asure that unsuccessful attempts to modify a file via openat syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S openat -F a2&01003 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification -a always,exit -F arch=b32 -S openat -F a2&01003 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F a2&01003 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification -a always,exit -F arch=b64 -S openat -F a2&01003 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-80386-6 |
Record Unsuccessful Access Attempts to Files - open |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=access If 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 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 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=access If 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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82118-1 |
Record Successful Permission Changes to Files - lremovexattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S lremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 lremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lremovexattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81117-4 |
Record Unsuccessful Creation Attempts to Files - open_by_handle_at O_CREAT |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unauthorized file accesses for all users and root. The open_by_handle_at syscall can be used to create new files when O_CREAT flag is specified. The following auidt rules will asure that unsuccessful attempts to create a file via open_by_handle_at syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open_by_handle_at -F a2&0100 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-create -a always,exit -F arch=b32 -S open_by_handle_at -F a2&0100 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-create If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F a2&0100 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-create -a always,exit -F arch=b64 -S open_by_handle_at -F a2&0100 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-create |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81146-3 |
Record Successful Access Attempts to Files - open |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access 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 open -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access |
File access attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-80387-4 |
Record Unsuccessful Access Attempts to Files - openat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=access If 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 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 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=access If 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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81086-1 |
Record Unsuccessul Permission Changes to Files - chmod |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 chmod -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S chmod -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S chmod -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S chmod -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81125-7 |
Record Unsuccessful Modification Attempts to Files - open_by_handle_at O_TRUNC_WRITE |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect detailed unauthorized file accesses for all users and root. The open_by_handle_at syscall can be used to modify files if called for write operation of with O_TRUNC_WRITE flag. The following auidt rules will asure that unsuccessful attempts to modify a file via open_by_handle_at syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open_by_handle_at -F a2&01003 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification -a always,exit -F arch=b32 -S open_by_handle_at -F a2&01003 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F a2&01003 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification -a always,exit -F arch=b64 -S open_by_handle_at -F a2&01003 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82088-6 |
Record Successful Delete Attempts to Files - unlinkat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file deletion 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 unlinkat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S unlinkat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete 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 unlinkat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S unlinkat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-delete |
File deletion attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81115-8 |
Record Unsuccessful Creation Attempts to Files - openat O_CREAT |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unauthorized file accesses for all users and root. The openat syscall can be used to create new files when O_CREAT flag is specified. The following auidt rules will asure that unsuccessful attempts to create a file via openat syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S openat -F a2&0100 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-create -a always,exit -F arch=b32 -S openat -F a2&0100 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-create If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F a2&0100 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-create -a always,exit -F arch=b64 -S openat -F a2&0100 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-create |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82133-0 |
Record Successful Ownership Changes to Files - fchownat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file ownership 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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchownat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchownat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 fchownat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchownat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File ownership attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81078-8 |
Record Unsuccessul Ownership Changes to Files - lchown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file ownership change 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 lchown -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S lchown -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lchown -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S lchown -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change ownership of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-80385-8 |
Record Unsuccessful Access Attempts to Files - creat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=access If 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 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 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=access If 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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81090-3 |
Record Unsuccessul Permission Changes to Files - fchmodat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 fchmodat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S fchmodat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchmodat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S fchmodat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82124-9 |
Record Successful Ownership Changes to Files - lchown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file ownership 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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S lchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 lchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File ownership attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-80389-0 |
Record Unsuccessful Access Attempts to Files - truncate |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=access If 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 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 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=access If 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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82103-3 |
Record Successful Permission Changes to Files - fchmodat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchmodat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchmodat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 fchmodat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchmodat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81137-2 |
Record Successful Creation Attempts to Files - openat O_TRUNC_WRITE |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect detailed file access records for all users and root. The openat syscall can be used to modify files if called for write operation with the O_TRUNC_WRITE flag. The following audit rules will assure that successful attempts to create a file via openat syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S openat -F a2&01003 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-modification If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F a2&01003 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-modification |
Successful 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. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81096-0 |
Record Unsuccessul Permission Changes to Files - fsetxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file permission change 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 fsetxattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S fsetxattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fsetxattr -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S fsetxattr -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change permissions of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82109-0 |
Record Successful Permission Changes to Files - lsetxattr |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S lsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 lsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S lsetxattr -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File permission changes could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82130-6 |
Record Successful Ownership Changes to Files - chown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file ownership 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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S chown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S chown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 chown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S chown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File ownership attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-27347-4 |
Ensure auditd Collects Unauthorized Access Attempts to Files (unsuccessful) |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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,open,openat,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 creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat,open,openat,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 creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access 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 creat,open,openat,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 creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat,open,openat,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 creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
5.2.10 |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81149-7 |
Record Successful Access Attempts to Files - creat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access 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 creat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access |
File access attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82009-2 |
Record Successful Access Attempts to Files - openat |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access 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 openat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access |
File access attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81143-0 |
Record Successful Creation Attempts to Files - open O_TRUNC_WRITE |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect detailed file access records for all users and root. The open syscall can be used to modify files if called for write operation with the O_TRUNC_WRITE flag. The following audit rules will assure that successful attempts to create a file via open syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open -F a2&01003 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-modification If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F a2&01003 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-modification |
Successful 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. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82127-2 |
Record Successful Ownership Changes to Files - fchown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
At a minimum, the audit system should collect file ownership 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 lines to a file with suffix .rules in the directory /etc/audit/rules.d: -a always,exit -F arch=b32 -S fchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change 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 fchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S fchown -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-perm-change |
File ownership attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-82001-9 |
Record Successful Access Attempts to Files - truncate |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access 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 truncate -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-access |
File access attempts could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81108-3 |
Record Unsuccessul Delete Attempts to Files - rename |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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-delete If 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 |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81131-5 |
Record Successful Creation Attempts to Files - open_by_handle_at O_CREAT |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The open_by_handle_at syscall can be used to create new files when O_CREAT flag is specified. The following audit rules will assure that successful attempts to create a file via open_by_handle_at syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open_by_handle_at -F a2&0100 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-create If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F a2&0100 -F success=1 -F auid>=1000 -F auid!=unset -F key=successful-create |
Successful 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. |
medium |
NaN |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81082-0 |
Record Unsuccessul Ownership Changes to Files - chown |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect unsuccessful file ownership change 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 chown -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b32 -S chown -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S chown -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change -a always,exit -F arch=b64 -S chown -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-perm-change |
Unsuccessful attempts to change ownership of files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-81121-6 |
Record Unsuccessful Modification Attempts to Files - open O_TRUNC_WRITE |
audit enabled |
via /etc/audit/audit.rules or auditctl |
The audit system should collect detailed unauthorized file accesses for all users and root. The open syscall can be used to modify files if called for write operation of with O_TRUNC_WRITE flag. The following auidt rules will asure that unsuccessful attempts to modify a file via open syscall are collected. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the rules below 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 rules below to /etc/audit/audit.rules file. -a always,exit -F arch=b32 -S open -F a1&01003 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification -a always,exit -F arch=b32 -S open -F a1&01003 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification If the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F a1&01003 -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification -a always,exit -F arch=b64 -S open -F a1&01003 -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=unsuccesful-modification |
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. |
medium |
AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.10 |
SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000458-GPOS-00203,SRG-OS-000461-GPOS-00205 |
Record Unauthorized Access Attempts Events to Files (unsuccessful) |
| CCE-80414-6 |
Ensure auditd Collects Information on Kernel Module Loading - init_module |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=modules Place 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. |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.17 |
SRG-OS-000471-GPOS-00216,SRG-OS-000477-GPOS-00222 |
Record Information on Kernel Modules Loading and Unloading |
| CCE-27129-6 |
Ensure auditd Collects Information on Kernel Module Loading and Unloading |
audit enabled |
via /etc/audit/audit.rules or auditctl |
To capture kernel module loading and unloading events, use following lines, 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,finit_module,delete_module -F key=modules The place to add the lines depends on a way auditd daemon is configured. If it is configured to use the augenrules program (the default), add the 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, add the lines to file /etc/audit/audit.rules. |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
5.2.17 |
NaN |
Record Information on Kernel Modules Loading and Unloading |
| CCE-80415-3 |
Ensure auditd Collects Information on Kernel Module Unloading - delete_module |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=modules Place 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. |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.17 |
SRG-OS-000471-GPOS-00216,SRG-OS-000477-GPOS-00222 |
Record Information on Kernel Modules Loading and Unloading |
| CCE-80547-3 |
Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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=modules 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 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 |
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. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.17 |
SRG-OS-000471-GPOS-00216,SRG-OS-000477-GPOS-00222 |
Record Information on Kernel Modules Loading and Unloading |
| CCE-27219-5 |
Record Attempts to Alter Time Through clock_settime |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 clock_settime -F a0=0x0 -F key=time-change If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change 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 clock_settime -F a0=0x0 -F key=time-change If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls: -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=audit_time_rules |
Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Records Events that Modify Date and Time Information |
| CCE-27216-1 |
Record attempts to alter time through settimeofday |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 settimeofday -F key=audit_time_rules If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S settimeofday -F key=audit_time_rules 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 settimeofday -F key=audit_time_rules If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S settimeofday -F key=audit_time_rules The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls: -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=audit_time_rules |
Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Records Events that Modify Date and Time Information |
| CCE-27310-2 |
Record Attempts to Alter the localtime File |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/localtime -p wa -k audit_time_rules 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: -w /etc/localtime -p wa -k audit_time_rules The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport and should always be used. |
Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Records Events that Modify Date and Time Information |
| CCE-27290-6 |
Record attempts to alter time through adjtimex |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 adjtimex -F key=audit_time_rules If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S adjtimex -F key=audit_time_rules 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 adjtimex -F key=audit_time_rules If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S adjtimex -F key=audit_time_rules The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls: -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=audit_time_rules |
Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Records Events that Modify Date and Time Information |
| CCE-27299-7 |
Record Attempts to Alter Time Through stime |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 for both 32 bit and 64 bit systems: -a always,exit -F arch=b32 -S stime -F key=audit_time_rules Since the 64 bit version of the "stime" system call is not defined in the audit lookup table, the corresponding "-F arch=b64" form of this rule is not expected to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule form itself is sufficient for both 32 bit and 64 bit systems). 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 for both 32 bit and 64 bit systems: -a always,exit -F arch=b32 -S stime -F key=audit_time_rules Since the 64 bit version of the "stime" system call is not defined in the audit lookup table, the corresponding "-F arch=b64" form of this rule is not expected to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule form itself is sufficient for both 32 bit and 64 bit systems). The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined system calls: -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=audit_time_rules |
Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Records Events that Modify Date and Time Information |
| CCE-27204-7 |
Record Attempts to Alter Logon and Logout Events |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 logins -w /var/run/faillock -p wa -k logins -w /var/log/lastlog -p wa -k logins 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 watch for unattempted manual edits of files involved in storing logon events: -w /var/log/tallylog -p wa -k logins -w /var/run/faillock -p wa -k logins -w /var/log/lastlog -p wa -k logins |
Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
NaN |
NaN |
NaN |
Record Attempts to Alter Logon and Logout Events |
| CCE-80384-1 |
Record Attempts to Alter Logon and Logout Events - lastlog |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 logins 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 watch for unattempted manual edits of files involved in storing logon events: -w /var/log/lastlog -p wa -k logins |
Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
4.1.8 |
SRG-OS-000392-GPOS-00172,SRG-OS-000470-GPOS-00214,SRG-OS-000473-GPOS-00218 |
Record Attempts to Alter Logon and Logout Events |
| CCE-80994-7 |
Record Attempts to Alter Logon and Logout Events - tallylog |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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 logins 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 watch for unattempted manual edits of files involved in storing logon events: -w /var/log/tallylog -p wa -k logins |
Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
5.2.8 |
SRG-OS-000392-GPOS-00172,SRG-OS-000470-GPOS-00214,SRG-OS-000473-GPOS-00218 |
Record Attempts to Alter Logon and Logout Events |
| CCE-80383-3 |
Record Attempts to Alter Logon and Logout Events - faillock |
audit enabled |
via /etc/audit/audit.rules or auditctl |
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/run/faillock -p wa -k logins 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 watch for unattempted manual edits of files involved in storing logon events: -w /var/run/faillock -p wa -k logins |
Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. |
medium |
AC-6(9),AU-12(c),AU-2(d),CM-6(a) |
FAU_GEN.1.1.c |
4.1.8 |
SRG-OS-000392-GPOS-00172,SRG-OS-000470-GPOS-00214,SRG-OS-000473-GPOS-00218 |
Record Attempts to Alter Logon and Logout Events |
| CCE-80646-3 |
Configure auditd Disk Error Action on Disk Error |
single |
via /etc/audit/auditd.conf |
The auditd service can be configured to take an action when there is a disk error. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting ACTION appropriately: disk_error_action = ACTION Set this value to single to cause the system to switch to single-user mode for corrective action. Acceptable values also include syslog, exec, single, and halt. For certain systems, the need for availability outweighs the need to log all actions, and a different setting should be determined. Details regarding all possible values for ACTION are described in the auditd.conf man page. |
Taking appropriate action in case of disk errors will minimize the possibility of losing audit records. |
medium |
AU-5(1),AU-5(2),AU-5(4),AU-5(b),CM-6(a) |
NaN |
NaN |
NaN |
Configure auditd Data Retention |
| CCE-27319-3 |
Configure auditd Max Log File Size |
6 |
via /etc/audit/auditd.conf |
Determine the amount of audit data (in megabytes) which should be retained in each log file. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting the correct value of for STOREMB: max_log_file = STOREMB Set the value to 6 (MB) or higher for general-purpose systems. Larger values, of course, support retention of even more audit data. |
The total storage for audit log files must be large enough to retain log information over the period required. This is a function of the maximum log file size and the number of logs retained. |
medium |
AU-11,CM-6(a) |
NaN |
NaN |
NaN |
Configure auditd Data Retention |
| CCE-27348-2 |
Configure auditd Number of Logs Retained |
5 |
via /etc/audit/auditd.conf |
Determine how many log files auditd should retain when it rotates logs. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting NUMLOGS with the correct value of : num_logs = NUMLOGS Set the value to 5 for general-purpose systems. Note that values less than 2 result in no log rotation. |
The total storage for audit log files must be large enough to retain log information over the period required. This is a function of the maximum log file size and the number of logs retained. |
medium |
AU-11,CM-6(a) |
NaN |
NaN |
NaN |
Configure auditd Data Retention |
| CCE-80539-0 |
Configure audispd's Plugin disk_full_action When Disk Is Full |
manually |
via /etc/audisp/audisp-remote.conf |
Configure the action the operating system takes if the disk the audit records are written to becomes full. Edit the file /etc/audisp/audisp-remote.conf. Add or modify the following line, substituting ACTION appropriately: disk_full_action = ACTION Set 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. |
Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records. |
medium |
AU-5(1),AU-5(2),AU-5(4),AU-5(b),CM-6(a) |
NaN |
NaN |
SRG-OS-000342-GPOS-00133 |
Configure auditd Data Retention |
| CCE-27370-6 |
Configure auditd admin_space_left Action on Low Disk Space |
single |
via /etc/audit/auditd.conf |
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: admin_space_left_action = ACTION Set this value to single to cause the system to switch to single user mode for corrective action. Acceptable values also include suspend 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. |
Administrators should be made aware of an inability to record audit records. If a separate partition or logical volume of adequate size is used, running low on space for audit records should never occur. |
medium |
AU-5(1),AU-5(2),AU-5(4),AU-5(b),CM-6(a) |
NaN |
NaN |
SRG-OS-000343-GPOS-00134 |
Configure auditd Data Retention |
| CCE-80540-8 |
Encrypt Audit Records Sent With audispd Plugin |
yes |
via /etc/audisp/audisp-remote.conf |
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/audisp/audisp-remote.conf, and set it with the following line: enable_krb5 = yes |
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. |
medium |
AU-9(3),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 |
Configure auditd Data Retention |
| CCE-27331-8 |
Configure auditd flush priority |
manually |
via /etc/audit/auditd.conf |
The auditd service can be configured to synchronously write audit event data to disk. Add or correct the following line in /etc/audit/auditd.conf to ensure that audit event data is fully synchronized with the log files on the disk: flush = |
Audit data should be synchronously written to disk to ensure log integrity. These parameters assure that all audit event data is fully synchronized with the log files on the disk. |
medium |
AU-11,CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure auditd Data Retention |
| CCE-80537-4 |
Configure auditd space_left on Low Disk Space |
manually |
via /etc/audit/auditd.conf |
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_MB Set this value to the appropriate size in Megabytes cause the system to notify the user of an issue. |
Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption. |
medium |
AU-5(1),AU-5(2),AU-5(4),AU-5(b),CM-6(a) |
NaN |
NaN |
SRG-OS-000343-GPOS-00134 |
Configure auditd Data Retention |
| CCE-82358-3 |
Set number of records to cause an explicit flush to audit logs |
50 |
via /etc/audit/auditd.conf |
To configure Audit daemon to issue an explicit flush to disk command after writing 50 records, set freq to 50 in /etc/audit/auditd.conf. |
If option freq isn't set to 50, the flush to disk may happen after higher number of records, increasing the danger of audit loss. |
medium |
NaN |
FAU_GEN.1 |
NaN |
SRG-OS-000051-GPOS-00024 |
Configure auditd Data Retention |
| CCE-82357-5 |
Resolve information before writing to audit logs |
ENRICHED |
via /etc/audit/auditd.conf |
To configure Audit daemon to resolve all uid, gid, syscall, architecture, and socket address information before writing the events to disk, set log_format to ENRICHED in /etc/audit/auditd.conf. |
If option log_format isn't set to ENRICHED, the audit records will be stored in a format exactly as the kernel sends them. |
medium |
NaN |
FAU_GEN.1 |
NaN |
SRG-OS-000255-GPOS-00096 |
Configure auditd Data Retention |
| CCE-80538-2 |
Configure audispd's Plugin network_failure_action On Network Failure |
install |
via /etc/audisp/audisp-remote.conf |
Configure the action the operating system takes if there is an error sending audit records to a remote system. Edit the file /etc/audisp/audisp-remote.conf. Add or modify the following line, substituting ACTION appropriately: network_failure_action = ACTION Set 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. |
Taking appropriate action when there is an error sending audit records to a remote system will minimize the possibility of losing audit records. |
medium |
AU-5(1),AU-5(2),AU-5(4),AU-5(b),CM-6(a) |
NaN |
NaN |
SRG-OS-000342-GPOS-00133 |
Configure auditd Data Retention |
| CCE-27341-7 |
Configure auditd to use audispd's syslog plugin |
yes |
/etc/audisp/plugins.d/syslog.conf |
To configure the auditd service to use the syslog plug-in of the audispd audit event multiplexor, set the active line in /etc/audisp/plugins.d/syslog.conf to yes. Restart the auditd service: $ sudo service auditd restart |
The auditd service does not include the ability to send audit records to a centralized server for management directly. It does, however, include a plug-in for audit event multiplexor (audispd) to pass audit records to the local syslog server |
medium |
AU-4(1),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 |
Configure auditd Data Retention |
| CCE-27394-6 |
Configure auditd mail_acct Action on Low Disk Space |
configure |
via /etc/audit/auditd.conf |
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 = |
Email sent to the root account is typically aliased to the administrators of the system, who can take appropriate action. |
medium |
AU-5(2),AU-5(a),CM-6(a),IA-5(1) |
NaN |
NaN |
SRG-OS-000343-GPOS-00134 |
Configure auditd Data Retention |
| CCE-27231-0 |
Configure auditd max_log_file_action Upon Reaching Maximum Log Size |
single |
via /etc/audit/auditd.conf |
The default action to take when the logs reach their maximum size is to rotate the log files, discarding the oldest one. To configure the action taken by auditd, add or correct the line in /etc/audit/auditd.conf: max_log_file_action = ACTION Possible values for ACTION are described in the auditd.conf man page. These include: syslogsuspendrotatekeep_logs Set the ACTION to rotate to ensure log rotation occurs. This is the default. The setting is case-insensitive. |
Automatically rotating logs (by setting this to rotate) minimizes the chances of the system unexpectedly running out of disk space by being overwhelmed with log data. However, for systems that must never discard log data, or which use external processes to transfer it and reclaim space, keep_logs can be employed. |
medium |
AU-5(1),AU-5(2),AU-5(4),AU-5(b),CM-6(a) |
NaN |
NaN |
NaN |
Configure auditd Data Retention |
| CCE-82356-7 |
Write Audit Logs to the Disk |
yes |
via /etc/audit/auditd.conf |
To configure Audit daemon to write Audit logs to the disk, set write_logs to yes in /etc/audit/auditd.conf. This is the default setting. |
If write_logs isn't set to yes, the Audit logs will not be written to the disk. |
medium |
NaN |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure auditd Data Retention |
| CCE-27375-5 |
Configure auditd space_left Action on Low Disk Space |
single |
via /etc/audit/auditd.conf |
The auditd service can be configured to take an action when disk space starts to run low. Edit the file /etc/audit/auditd.conf. Modify the following line, substituting ACTION appropriately: space_left_action = ACTION Possible values for ACTION are described in the auditd.conf man page. These include: syslogemailexecsuspendsinglehalt Set this to email (instead of the default, which is suspend) as it is more likely to get prompt attention. Acceptable values also include suspend, single, and halt. |
Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption. |
medium |
AU-5(1),AU-5(2),AU-5(4),AU-5(b),CM-6(a) |
NaN |
NaN |
SRG-OS-000343-GPOS-00134 |
Configure auditd Data Retention |
| CCE-80541-6 |
Configure audispd Plugin To Send Logs To Remote Server |
configure |
via /etc/audit/auditd.conf |
Configure the audispd plugin to off-load audit records onto a different system or media from the system being audited. Set the remote_server option in /etc/audisp/audisp-remote.conf with an IP address or hostname of the system that the audispd plugin should send audit records to. For example remote_server = |
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. |
medium |
NaN |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 |
Configure auditd Data Retention |
| CCE-82355-9 |
Include Local Events in Audit Logs |
yes |
via /etc/audit/auditd.conf |
To configure Audit daemon to include local events in Audit logs, set local_events to yes in /etc/audit/auditd.conf. This is the default setting. |
If option local_events isn't set to yes only events from network will be aggregated. |
medium |
NaN |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000062-GPOS-00031 |
Configure auditd Data Retention |
| CCE-82359-1 |
Set hostname as computer node name in audit logs |
hostname |
via /etc/audit/auditd.conf |
To configure Audit daemon to use value returned by gethostname syscall as computer node name in the audit events, set name_format to hostname in /etc/audit/auditd.conf. |
If option name_format is left at its default value of none, audit events from different computers may be hard to distinguish. |
medium |
NaN |
FAU_GEN.1 |
NaN |
SRG-OS-000039-GPOS-00017,SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 |
Configure auditd Data Retention |
| CCE-82213-0 |
Install sudo Package |
install |
via yum |
The sudo package can be installed with the following command: $ sudo yum install sudo |
sudo is a program designed to allow a system administrator to give limited root privileges to users and log root activity. The basic philosophy is to give as few privileges as possible but still allow system users to get their work done. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000324-GPOS-00125 |
Sudo |
| CCE-82349-2 |
Only the VDSM User Can Use sudo NOPASSWD |
disable |
via sysctl |
The sudo NOPASSWD tag, when specified, allows a user to execute commands using sudo without having to authenticate. Only the vdsm user should have this capability in any sudo configuration snippets in /etc/sudoers.d/. |
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. |
medium |
NaN |
NaN |
NaN |
NaN |
Sudo |
| CCE-82278-3 |
Ensure Users Re-Authenticate for Privilege Escalation - sudo |
disable |
via sysctl |
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/." |
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. |
medium |
CM-6(a),IA-11 |
NaN |
NaN |
NaN |
Sudo |
| CCE-80351-0 |
Ensure Users Re-Authenticate for Privilege Escalation - sudo NOPASSWD |
enable |
via sysctl |
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/. |
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. |
medium |
CM-6(a),IA-11 |
NaN |
NaN |
SRG-OS-000373-GPOS-00156,SRG-OS-000373-GPOS-00157,SRG-OS-000373-GPOS-00158 |
Sudo |
| CCE-80350-2 |
Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate |
remove |
via /etc/sudoers or /etc/sudoers.d/ |
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/. |
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. |
medium |
CM-6(a),IA-11 |
NaN |
NaN |
SRG-OS-000373-GPOS-00156,SRG-OS-000373-GPOS-00157,SRG-OS-000373-GPOS-00158 |
Sudo |
| CCE-26989-4 |
Ensure gpgcheck Enabled In Main yum Configuration |
True |
via /etc/yum.conf |
The gpgcheck option controls whether RPM packages' signatures are always checked prior to installation. To configure yum to check package signatures before installing them, ensure the following line appears in /etc/yum.conf in the [main] section: gpgcheck=1 |
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). |
high |
CM-11(a),CM-11(b),CM-5(3),CM-6(a),SA-12,SA-12(10),SC-12,SC-12(3),SI-7 |
FPT_TUD_EXT.1,FPT_TUD_EXT.2 |
NaN |
SRG-OS-000366-GPOS-00153 |
Updating Software |
| CCE-80346-0 |
Ensure yum Removes Previous Package Versions |
True |
via /etc/yum.conf |
yum should be configured to remove previous software components after new versions have been installed. To configure yum to remove the previous software components after updating, set the clean_requirements_on_remove to 1 in /etc/yum.conf. |
Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by some adversaries. |
low |
CM-11(a),CM-11(b),CM-6(a),SI-2(6) |
NaN |
NaN |
SRG-OS-000437-GPOS-00194 |
Updating Software |
| CCE-80347-8 |
Ensure gpgcheck Enabled for Local Packages |
True |
via /etc/yum.conf |
yum should be configured to verify the signature(s) of local packages prior to installation. To configure yum to verify signatures of local packages, set the localpkg_gpgcheck to 1 in /etc/yum.conf. |
Changes to any software components can have significant effects to the overall security of the operating system. This requirement ensures the software has not been tampered and has been provided by a trusted vendor. Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization. |
high |
CM-11(a),CM-11(b),CM-5(3),CM-6(a),SA-12,SA-12(10) |
FPT_TUD_EXT.1,FPT_TUD_EXT.2 |
NaN |
SRG-OS-000366-GPOS-00153 |
Updating Software |
| CCE-26876-3 |
Ensure gpgcheck Enabled for All yum Package Repositories |
0 |
via /etc/yum.conf |
To ensure signature checking is not disabled for any repos, remove any lines from files in /etc/yum.repos.d of the form: gpgcheck=0 |
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)." |
high |
CM-11(a),CM-11(b),CM-5(3),CM-6(a),SA-12,SA-12(10),SC-12,SC-12(3),SI-7 |
FPT_TUD_EXT.1,FPT_TUD_EXT.2 |
NaN |
SRG-OS-000366-GPOS-00153 |
Updating Software |
| CCE-26957-1 |
Ensure Red Hat GPG Key Installed |
import |
via rpm |
To ensure the system can cryptographically verify base software packages come from Red Hat (and to connect to the Red Hat Network to receive them), the Red Hat GPG key must properly be installed. To install the Red Hat GPG key, run: $ sudo subscription-manager register If the system is not connected to the Internet or an RHN Satellite, then install the Red Hat GPG key from trusted media such as the Red Hat installation CD-ROM or DVD. Assuming the disc is mounted in /media/cdrom, use the following command as the root user to import it into the keyring: $ sudo rpm --import /media/cdrom/RPM-GPG-KEY Alternatively, the key may be pre-loaded during the RHEL installation. In such cases, the key can be installed by running the following command: sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release |
Changes to 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. The Red Hat GPG key is necessary to cryptographically verify packages are from Red Hat. |
high |
CM-5(3),CM-6(a),SC-12,SC-12(3),SI-7 |
FPT_TUD_EXT.1,FPT_TUD_EXT.2 |
NaN |
SRG-OS-000366-GPOS-00153 |
Updating Software |
| CCE-80348-6 |
Ensure gpgcheck Enabled for Repository Metadata |
True |
via /etc/yum.conf |
Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components of local packages without verification of the repository metadata. Check that yum verifies the repository metadata prior to install with the following command. This should be configured by setting repo_gpgcheck to 1 in /etc/yum.conf. |
Changes to any software components can have significant effects to the overall security of the operating system. This requirement ensures the software has not been tampered and has been provided by a trusted vendor. Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. NOTE: For U.S. Military systems, this requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved Certificate Authority. |
high |
CM-11(a),CM-11(b),CM-5(3),CM-6(a),SA-12,SA-12(10),SC-12,SC-12(3),SI-7 |
NaN |
NaN |
SRG-OS-000366-GPOS-00153 |
Updating Software |
| CCE-26895-3 |
Ensure Software Patches Installed |
update |
via yum |
If the system is joined to the Red Hat Network, a Red Hat Satellite Server, or a yum server, run the following command to install updates: $ sudo yum update If the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded from the Red Hat Network and installed using rpm. NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy dictates. |
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. |
high |
CM-6(a),SI-2(5),SI-2(c) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000480-GPOS-00227 |
Updating Software |
| CCE-27128-8 |
Encrypt Partitions |
partition |
via /etc/crypttab |
Red Hat Enterprise Linux 7 natively supports partition encryption through the Linux Unified Key Setup-on-disk-format (LUKS) technology. The easiest way to encrypt a partition is during installation time. For manual installations, select the Encrypt checkbox during partition creation to encrypt the partition. When this option is selected the system will prompt for a passphrase to use in decrypting the partition. The passphrase will subsequently need to be entered manually every time the system boots. For automated/unattended installations, it is possible to use Kickstart by adding the --encrypted and --passphrase= options to the definition of each partition to be encrypted. For example, the following line would encrypt the root partition: part / --fstype=ext4 --size=100 --onpart=hda1 --encrypted --passphrase=PASSPHRASE Any PASSPHRASE is stored in the Kickstart in plaintext, and the Kickstart must then be protected accordingly. Omitting the --passphrase= option from the partition definition will cause the installer to pause and interactively ask for the passphrase during installation. By default, the Anaconda installer uses aes-xts-plain64 cipher with a minimum 512 bit key size which should be compatible with FIPS enabled. Detailed information on encrypting partitions using LUKS or LUKS ciphers can be found on the Red Hat Enterprise Linux 7 Documentation web site: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Encryption.html. |
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. |
high |
AU-9(3),CM-6(a),SC-13,SC-28,SC-28(1) |
NaN |
NaN |
SRG-OS-000185-GPOS-00079,SRG-OS-000404-GPOS-00183,SRG-OS-000405-GPOS-00184 |
Disk Partitioning |
| CCE-80144-9 |
Ensure /home Located On Separate Partition |
partition |
via /etc/fstab |
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. |
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. |
low |
CM-6(a),SC-5(2) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disk Partitioning |
| CCE-82053-0 |
Ensure /tmp Located On Separate Partition |
partition |
via /etc/fstab |
The /tmp directory is a world-writable directory used for temporary file storage. Ensure it has its own partition or logical volume at installation time, or migrate it using LVM. |
The /tmp partition is used as temporary storage by many programs. Placing /tmp in its own partition enables the setting of more restrictive mount options, which can help protect programs which use it. |
low |
CM-6(a),SC-5(2) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disk Partitioning |
| CCE-82353-4 |
Ensure /var/tmp Located On Separate Partition |
partition |
via /etc/fstab |
The /var/tmp directory is a world-writable directory used for temporary file storage. Ensure it has its own partition or logical volume at installation time, or migrate it using LVM. |
The /var/tmp partition is used as temporary storage by many programs. Placing /var/tmp in its own partition enables the setting of more restrictive mount options, which can help protect programs which use it. |
low |
NaN |
NaN |
NaN |
NaN |
Disk Partitioning |
| CCE-82014-2 |
Ensure /var Located On Separate Partition |
partition |
via /etc/fstab |
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. |
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. |
low |
CM-6(a),SC-5(2) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disk Partitioning |
| CCE-82034-0 |
Ensure /var/log Located On Separate Partition |
partition |
via /etc/fstab |
System logs are stored in the /var/log directory. Ensure that it has its own partition or logical volume at installation time, or migrate it using LVM. |
Placing /var/log in its own partition enables better separation between log files and other files in /var/. |
medium |
AU-4,CM-6(a),SC-5(2) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disk Partitioning |
| CCE-82035-7 |
Ensure /var/log/audit Located On Separate Partition |
partition |
via /etc/fstab |
Audit logs are stored in the /var/log/audit directory. Ensure that it has its own partition or logical volume at installation time, or migrate it later using LVM. Make absolutely certain that it is large enough to store all audit logs that will be created by the auditing daemon. |
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. |
low |
AU-4,CM-6(a),SC-5(2) |
NaN |
NaN |
SRG-OS-000341-GPOS-00132,SRG-OS-000480-GPOS-00227 |
Disk Partitioning |
| CCE-27078-5 |
Disable Prelinking |
disable |
via prelink |
The prelinking feature changes binaries in an attempt to decrease their startup time. In order to disable it, change or add the following line inside the file /etc/sysconfig/prelink: PRELINKING=no Next, run the following command to return binaries to a normal, non-prelinked state: $ sudo /usr/sbin/prelink -ua |
Because the prelinking feature changes binaries, it can interfere with the operation of certain software and/or modes such as AIDE, FIPS, etc. |
medium |
CM-6(a),SC-13 |
NaN |
1.5.4 |
NaN |
System and Software Integrity |
| CCE-27096-7 |
Install AIDE |
install |
via yum |
The aide package can be installed with the following command: $ sudo yum install aide |
The AIDE package must be installed if it is to be available for integrity checking. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000363-GPOS-00150 |
Verify Integrity with AIDE |
| CCE-27220-3 |
Build and Test AIDE Database |
enable aide |
via aide |
Run the following command to generate a new database: $ sudo /usr/sbin/aide --init By default, the database will be written to the file /var/lib/aide/aide.db.new.gz. Storing the database, the configuration file /etc/aide.conf, and the binary /usr/sbin/aide (or hashes of these files), in a secure location (such as on read-only media) provides additional assurance about their integrity. The newly-generated database can be installed as follows: $ sudo cp /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz To initiate a manual check, run the following command: $ sudo /usr/sbin/aide --check If this check produces any unexpected output, investigate. |
For AIDE to be effective, an initial database of "known-good" information about files must be captured and it should be able to be verified against the installed files. |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
Verify Integrity with AIDE |
| CCE-80374-2 |
Configure Notification of Post-AIDE Scan Details |
configure |
via cron |
AIDE should notify appropriate personnel of the details of a scan after the scan has been run. If AIDE has already been configured for periodic execution in /etc/crontab, append the following line to the existing AIDE line: | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost Otherwise, add the following line to /etc/crontab: 05 4 * * * root /usr/sbin/aide --check | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost AIDE can be executed periodically through other means; this is merely one example. |
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. |
medium |
CM-3(5),CM-6(a) |
NaN |
NaN |
SRG-OS-000363-GPOS-00150 |
Verify Integrity with AIDE |
| CCE-80375-9 |
Configure AIDE to Verify Access Control Lists (ACLs) |
configure |
via aide |
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+sha256 AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. |
ACLs can provide permissions beyond those permitted through the file mode and must be verified by the file integrity tools. |
low |
CM-6(a),SI-7,SI-7(1) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Verify Integrity with AIDE |
| CCE-80377-5 |
Configure AIDE to Use FIPS 140-2 for Validating Hashes |
FIPSR+sha512 |
via aide |
By default, the sha512 option is added to the NORMAL ruleset in AIDE. If using a custom ruleset or the sha512 option is missing, add sha512 to the appropriate ruleset. For example, add sha512 to the following line in /etc/aide.conf: NORMAL = FIPSR+sha512 AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. |
File integrity tools use cryptographic hashes for verifying file contents and directories have not been altered. These hashes must be FIPS 140-2 approved cryptographic hashes. |
medium |
CM-6(a),SI-7,SI-7(1) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Verify Integrity with AIDE |
| CCE-26952-2 |
Configure Periodic Execution of AIDE |
enable cron |
via cron |
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/sbin/aide --check To implement a weekly execution of AIDE at 4:05am using cron, add the following line to /etc/crontab: 05 4 * * 0 root /usr/sbin/aide --check AIDE 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. |
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. |
medium |
CM-6(a),SI-7,SI-7(1) |
NaN |
NaN |
SRG-OS-000363-GPOS-00150,SRG-OS-000446-GPOS-00200 |
Verify Integrity with AIDE |
| CCE-80376-7 |
Configure AIDE to Verify Extended Attributes |
configure |
via aide |
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+sha256 AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. |
Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications. |
medium |
CM-6(a),SI-7,SI-7(1) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Verify Integrity with AIDE |
| CCE-80545-7 |
Verify and Correct Ownership with RPM |
verify |
via rpm |
The RPM package management system can check file ownership permissions of installed software packages, including many that are important to system security. After locating a file with incorrect permissions, which can be found with rpm -Va | awk '{ if (substr($0,6,1)=="U" || substr($0,7,1)=="G") print $NF }' run the following command to determine which package owns it: $ rpm -qf FILENAME Next, run the following command to reset its permissions to the correct values: $ sudo rpm --setugids PACKAGENAME |
Ownership of binaries and configuration files that is incorrect could allow an unauthorized user to gain privileges that they should not have. The ownership set by the vendor should be maintained. Any deviations from this baseline should be investigated. |
high |
AU-9(3),CM-6(c),CM-6(d),SI-7,SI-7(1),SI-7(6) |
NaN |
1.7.1.4,1.7.1.5,1.7.1.6,6.1.1,6.1.2,6.1.3,6.1.4,6.1.5,6.1.6,6.1.7,6.1.8,6.1.9 |
SRG-OS-000257-GPOS-00098,SRG-OS-000278-GPOS-00108 |
Verify Integrity with RPM |
| CCE-27209-6 |
Verify and Correct File Permissions with RPM |
verify |
via rpm |
The RPM package management system can check file access permissions of installed software packages, including many that are important to system security. Verify that the file permissions of system files and commands match vendor values. Check the file permissions with the following command: $ sudo rpm -Va | awk '{ if (substr($0,2,1)=="M") print $NF }' Output indicates files that do not match vendor defaults. After locating a file with incorrect permissions, run the following command to determine which package owns it: $ rpm -qf FILENAME Next, run the following command to reset its permissions to the correct values: $ sudo rpm --setperms PACKAGENAME |
Permissions on system binaries and configuration files that are too generous could allow an unauthorized user to gain privileges that they should not have. The permissions set by the vendor should be maintained. Any deviations from this baseline should be investigated. |
high |
AU-9(3),CM-6(a),CM-6(c),CM-6(d),SI-7,SI-7(1),SI-7(6) |
NaN |
1.7.1.4,1.7.1.5,1.7.1.6,6.1.1,6.1.2,6.1.3,6.1.4,6.1.5,6.1.6,6.1.7,6.1.8,6.1.9 |
SRG-OS-000256-GPOS-00097,SRG-OS-000257-GPOS-00098,SRG-OS-000258-GPOS-00099,SRG-OS-000278-GPOS-00108 |
Verify Integrity with RPM |
| CCE-27157-7 |
Verify File Hashes with RPM |
verify |
via rpm |
Without cryptographic integrity protections, system executables and files can be altered by unauthorized users without detection. The RPM package management system can check the hashes of installed software packages, including many that are important to system security. To verify that the cryptographic hash of system files and commands matches vendor values, run the following command to list which files on the system have hashes that differ from what is expected by the RPM database: $ rpm -Va --noconfig | grep '^..5' A "c" in the second column indicates that a file is a configuration file, which may appropriately be expected to change. If the file was not expected to change, investigate the cause of the change using audit logs or other means. The package can then be reinstalled to restore the file. Run the following command to determine which package owns the file: $ rpm -qf FILENAME The package can be reinstalled from a yum repository using the command: $ sudo yum reinstall PACKAGENAME Alternatively, the package can be reinstalled from trusted media using the command: $ sudo rpm -Uvh PACKAGENAME |
The hashes of important files like system executables should match the information given by the RPM database. Executables with erroneous hashes could be a sign of nefarious activity on the system. |
high |
AU-9(3),CM-6(c),CM-6(d),SI-7,SI-7(1),SI-7(6) |
NaN |
1.2.6 |
SRG-OS-000480-GPOS-00227 |
Verify Integrity with RPM |
| CCE-80358-5 |
Install the dracut-fips Package |
install |
via yum |
To enable FIPS, the system requires that the dracut-fips package be installed. The dracut-fips package can be installed with the following command: $ sudo yum install dracut-fips |
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. |
medium |
CM-6(a),IA-7,SC-12,SC-12(2),SC-12(3),SC-13 |
NaN |
NaN |
SRG-OS-000033-GPOS-00014,SRG-OS-000396-GPOS-00176,SRG-OS-000478-GPOS-00223 |
Federal Information Processing Standard (FIPS) |
| CCE-80359-3 |
Enable FIPS Mode in GRUB2 |
True |
via grub |
To ensure FIPS mode is enabled, install package dracut-fips, and rebuild initramfs by running the following commands: $ sudo yum install dracut-fips dracut -f After the dracut command has been run, add the argument fips=1 to the default GRUB 2 command line for the Linux operating system in /etc/default/grub, in the manner below: GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=VolGroup/LogVol06 rd.lvm.lv=VolGroup/lv_swap rhgb quiet rd.shell=0 fips=1" Finally, rebuild the grub.cfg file by using the grub2-mkconfig -o command as follows: On BIOS-based machines, issue the following command as root: ~]# grub2-mkconfig -o /boot/grub2/grub.cfgOn UEFI-based machines, issue the following command as root: ~]# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg |
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. |
high |
CM-6(a),IA-7,SC-12,SC-12(2),SC-12(3),SC-13 |
NaN |
NaN |
SRG-OS-000033-GPOS-00014,SRG-OS-000185-GPOS-00079,SRG-OS-000396-GPOS-00176,SRG-OS-000405-GPOS-00184,SRG-OS-000478-GPOS-00223 |
Federal Information Processing Standard (FIPS) |
| CCE-80657-0 |
The Installed Operating System Is FIPS 140-2 Certified |
verify |
via NIST FIPS validation URL |
To enable processing of sensitive information the operating system must provide certified cryptographic modules compliant with FIPS 140-2 standard. Red Hat Enterprise Linux is supported by Red Hat, Inc. As the Red Hat Enterprise Linux vendor, Red Hat, Inc. is responsible for maintaining government certifications and standards. |
The Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB 140-2) is a computer security standard. The standard specifies security requirements for cryptographic modules used to protect sensitive unclassified information. Refer to the full FIPS 140-2 standard at http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf for further details on the requirements. FIPS 140-2 validation is required by U.S. law when information systems use cryptography to protect sensitive government information. In order to achieve FIPS 140-2 certification, cryptographic modules are subject to extensive testing by independent laboratories, accredited by National Institute of Standards and Technology (NIST). |
high |
CM-6(a),IA-7,SC-12,SC-12(2),SC-12(3),SC-13 |
NaN |
NaN |
NaN |
Operating System Vendor Support and Certification |
| CCE-26818-5 |
Install Intrusion Detection Software |
install |
via SELinux |
The base Red Hat Enterprise Linux 7 platform already includes a sophisticated auditing system that can detect intruder activity, as well as SELinux, which provides host-based intrusion prevention capabilities by confining privileged programs and user sessions which may become compromised. |
Host-based intrusion detection tools provide a system-level defense when an intruder gains access to a system or network. |
high |
CM-6(a) |
NaN |
NaN |
NaN |
Endpoint Protection Software |
| CCE-27140-3 |
Install Virus Scanning Software |
install |
via rpm |
Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems. The virus scanning software should be configured to perform scans dynamically on accessed files. If this capability is not available, the system must be configured to scan, at a minimum, all altered files on the system on a daily basis. If the system processes inbound SMTP mail, the virus scanner must be configured to scan all received mail. |
Virus scanning software can be used to detect if a system has been compromised by computer viruses, as well as to limit their spread to other systems. |
high |
CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Endpoint Protection Software |
| CCE-80128-2 |
Enable nails Service |
enable |
via systemctl |
The nails service is used to run McAfee VirusScan Enterprise for Linux and McAfee Host-based Security System (HBSS) services. The nails service can be enabled with the following command: $ sudo systemctl enable nails.service |
Virus scanning software can be used to detect if a system has been compromised by computer viruses, as well as to limit their spread to other systems. |
medium |
CM-6(a),SC-28,SI-3(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
McAfee Endpoint Security Software |
| CCE-80129-0 |
Virus Scanning Software Definitions Are Updated |
verify |
via ls |
Ensure virus definition files are no older than 7 days or their last release. |
Virus scanning software can be used to detect if a system has been compromised by computer viruses, as well as to limit their spread to other systems. |
medium |
CM-6(a),SC-28,SI-3(2),SI-3(a),SI-3(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
McAfee Endpoint Security Software |
| CCE-80127-4 |
Install McAfee Virus Scanning Software |
install |
via rpm |
Install McAfee VirusScan Enterprise for Linux antivirus software which is provided for DoD systems and uses signatures to search for the presence of viruses on the filesystem. |
Virus scanning software can be used to detect if a system has been compromised by computer viruses, as well as to limit their spread to other systems. |
high |
CM-6(a),SC-28,SI-3(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
McAfee Endpoint Security Software |
| CCE-80367-6 |
Install the McAfee Runtime Libraries and Linux Agent |
install |
via rpm |
Install the McAfee Runtime Libraries (MFErt) and Linux Agent (MFEcma). |
The McAfee Runtime Libraries (MFErt) and Linux Agent (MFEcma) are dependencies for VirusScan Enterprise for Linux (VSEL) and Host-based Security System (HBSS) to run. |
medium |
NaN |
NaN |
NaN |
NaN |
McAfee Endpoint Security Software |
| CCE-80126-6 |
Install the Asset Configuration Compliance Module (ACCM) |
install |
via rpm |
Install the Asset Configuration Compliance Module (ACCM). |
Without a host-based intrusion detection tool, there is no system-level defense when an intruder gains access to a system or network. Additionally, a host-based intrusion prevention tool can provide methods to immediately lock out detected intrusion attempts. |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
McAfee Host-Based Intrusion Detection Software (HBSS) |
| CCE-80368-4 |
Install the Host Intrusion Prevention System (HIPS) Module |
install |
via rpm |
Install the McAfee Host Intrusion Prevention System (HIPS) Module if it is absolutely necessary. If SELinux is enabled, do not install or enable this module. |
Without a host-based intrusion detection tool, there is no system-level defense when an intruder gains access to a system or network. Additionally, a host-based intrusion prevention tool can provide methods to immediately lock out detected intrusion attempts. |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
McAfee Host-Based Intrusion Detection Software (HBSS) |
| CCE-80369-2 |
Install the Policy Auditor (PA) Module |
install |
via rpm |
Install the Policy Auditor (PA) Module. |
Without a host-based intrusion detection tool, there is no system-level defense when an intruder gains access to a system or network. Additionally, a host-based intrusion prevention tool can provide methods to immediately lock out detected intrusion attempts. |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
McAfee Host-Based Intrusion Detection Software (HBSS) |
| CCE-82882-2 |
Install rear Package |
install |
via yum |
The rear package can be installed with the following command: $ sudo yum install rear |
rear contains the Relax-and-Recover (ReaR) utility. ReaR produces a bootable image of a system and restores from backup using this image. |
medium |
NaN |
NaN |
NaN |
NaN |
System Tooling / Utilities |
| CCE-82980-4 |
Install libcap-ng-utils Package |
install |
via yum |
The libcap-ng-utils package can be installed with the following command: $ sudo yum install libcap-ng-utils |
libcap-ng-utils contains applications to analyze the posix posix capabilities of all the programs running on a system. libcap-ng-utils also lets system operators set the file system based capabilities. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000445-GPOS-00199 |
System Tooling / Utilities |
| CCE-82966-3 |
Install tar Package |
install |
via yum |
The tar package can be installed with the following command: $ sudo yum install tar |
The GNU tar program saves many files together into one archive and can restore individual files (or all of the files) from the archive. tar includes multivolume support, automatic archive compression/decompression, the the ability to perform incremental and full backups. If |
medium |
NaN |
NaN |
NaN |
NaN |
System Tooling / Utilities |
| CCE-82219-7 |
Install openscap-scanner Package |
install |
via yum |
The openscap-scanner package can be installed with the following command: $ sudo yum install openscap-scanner |
openscap-scanner contains the oscap command line tool. This tool is a configuration and vulnerability scanner, capable of performing compliance checking using SCAP content. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000191-GPOS-00080,SRG-OS-000480-GPOS-00227 |
System Tooling / Utilities |
| CCE-82996-0 |
Install cryptsetup-luks Package |
install |
via yum |
The cryptsetup-luks package can be installed with the following command: $ sudo yum install cryptsetup-luks |
LUKS is the upcoming standard for Linux hard disk encryption. By providing a standard on-disk format, it does not only facilitate compatibility among distributions, but also provide secure management of multiple user passwords. In contrast to existing solution, LUKS stores all necessary setup information in the partition header, enabling the user to transport or migrate their data seamlessly. LUKS for dm-crypt is implemented in cryptsetup. cryptsetup-luks is intended as a complete replacement for the original cryptsetup. It provides all the functionality of the original version plus all LUKS features, that are accessible by luks* action. |
medium |
NaN |
NaN |
NaN |
NaN |
System Tooling / Utilities |
| CCE-82957-2 |
Install vim Package |
install |
via yum |
The vim package can be installed with the following command: $ sudo yum install vim |
Vim (Vi IMproved) is an almost compatible version of the UNIX editor vi. |
low |
NaN |
NaN |
NaN |
NaN |
System Tooling / Utilities |
| CCE-82951-5 |
Install scap-security-guide Package |
install |
via yum |
The scap-security-guide package can be installed with the following command: $ sudo yum install scap-security-guide |
The scap-security-guide package provides a guide for configuration of the system from the final system's security point of view. The guidance is specified in the Security Content Automation Protocol (SCAP) format and constitutes a catalog of practical hardening advice, linked to government requirements where applicable. The SCAP Security Guide project bridges the gap between generalized policy requirements and specific implementation guidelines. A system administrator can use the oscap CLI tool from the openscap-scanner package, or the SCAP Workbench GUI tool from the scap-workbench package, to verify that the system conforms to provided guidelines. Refer to the scap-security-guide(8) manual page for futher information. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
System Tooling / Utilities |
| CCE-82638-8 |
Install subscription-manager Package |
install |
via yum |
The subscription-manager package can be installed with the following command: $ sudo yum install subscription-manager |
Red Hat Subscription Manager is a local service which tracks installed products and subscriptions on a local system to help manage subscription assignments. It communicates with the backend subscription service (the Customer Portal or an on-premise server such as Subscription Asset Manager) and works with content management tools such as yum. |
medium |
NaN |
FPT_TUD_EXT.1,FPT_TUD_EXT.2 |
NaN |
SRG-OS-000366-GPOS-00153 |
System Tooling / Utilities |
| CCE-82990-3 |
Install binutils Package |
install |
via yum |
The binutils package can be installed with the following command: $ sudo yum install binutils |
binutils is a collection of binary utilities required for foundational system operator activities, such as ld, nm, objcopy and readelf. |
medium |
NaN |
NaN |
NaN |
NaN |
System Tooling / Utilities |
| CCE-82969-7 |
Install rng-tools Package |
install |
via yum |
The rng-tools package can be installed with the following command: $ sudo yum install rng-tools |
rng-tools provides hardware random number generator tools, such as those used in the formation of x509/PKI certificates. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
System Tooling / Utilities |
| CCE-82940-8 |
Uninstall geolite2-city Package |
remove |
via yum |
The geolite2-city package can be removed with the following command: $ sudo yum erase geolite2-city |
geolite2-city is part of the GeoLite2 database packages, offering geolocation databases and tooling. |
low |
NaN |
NaN |
NaN |
NaN |
System Tooling / Utilities |
| CCE-82927-5 |
Uninstall abrt-addon-kerneloops Package |
remove |
via yum |
The abrt-addon-kerneloops package can be removed with the following command: $ sudo yum erase abrt-addon-kerneloops |
abrt-addon-kerneloops contains plugins for collecting kernel crash information and reporter plugin which sends this information to a specified server, usually to kerneloops.org. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82911-9 |
Uninstall abrt-plugin-sosreport Package |
remove |
via yum |
The abrt-plugin-sosreport package can be removed with the following command: $ sudo yum erase abrt-plugin-sosreport |
abrt-plugin-sosreport provides a plugin to include an sosreport in an ABRT report. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82908-5 |
Uninstall abrt-cli Package |
remove |
via yum |
The abrt-cli package can be removed with the following command: $ sudo yum erase abrt-cli |
abrt-cli contains a command line client for controlling abrt daemon over sockets. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82920-0 |
Uninstall abrt-addon-ccpp Package |
remove |
via yum |
The abrt-addon-ccpp package can be removed with the following command: $ sudo yum erase abrt-addon-ccpp |
abrt-addon-ccpp contains hooks for C/C++ crashed programs and abrt's C/C++ analyzer plugin. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82917-6 |
Uninstall abrt-plugin-rhtsupport Package |
remove |
via yum |
The abrt-plugin-rhtsupport package can be removed with the following command: $ sudo yum erase abrt-plugin-rhtsupport |
abrt-plugin-rhtsupport is a ABRT plugin to report bugs into the Red Hat Support system. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82937-4 |
Uninstall geolite2-country Package |
remove |
via yum |
The geolite2-country package can be removed with the following command: $ sudo yum erase geolite2-country |
geolite2-country is part of the GeoLite2 database packages, offering geolocation databases and tooling. |
low |
NaN |
NaN |
NaN |
NaN |
System Tooling / Utilities |
| CCE-82930-9 |
Uninstall krb5-workstation Package |
remove |
via yum |
The krb5-workstation package can be removed with the following command: $ sudo yum erase krb5-workstation |
Kerberos is a network authentication system. The krb5-workstation package contains the basic Kerberos programs (kinit, klist, kdestroy, kpasswd). Currently, Kerberos does not utilize FIPS 140-2 cryptography and is not permitted on Government networks, nor is it permitted in many regulatory environments such as HIPAA. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049,SRG-OS-000120-GPOS-00061 |
System Tooling / Utilities |
| CCE-82905-1 |
Uninstall tuned Package |
remove |
via yum |
The tuned package can be removed with the following command: $ sudo yum erase tuned |
tuned contains a daemon that tunes the system settings dynamically. It does so by monitoring the usage of several system components periodically. Based on that information, components will then be put into lower or higher power savings modes to adapt to the current usage. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82944-0 |
Uninstall gssproxy Package |
remove |
via yum |
The gssproxy package can be removed with the following command: $ sudo yum erase gssproxy |
gssproxy is a proxy for GSS API credential handling. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82924-2 |
Uninstall abrt-addon-python Package |
remove |
via yum |
The abrt-addon-python package can be removed with the following command: $ sudo yum erase abrt-addon-python |
abrt-addon-python contains python hook and python analyzer plugin for handling uncaught exceptions in python programs. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82947-3 |
Uninstall iprutils Package |
remove |
via yum |
The iprutils package can be removed with the following command: $ sudo yum erase iprutils |
iprutils provides a suite of utlilities to manage and configure SCSI devices supported by the ipr SCSI storage device driver. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82914-3 |
Uninstall abrt-plugin-logger Package |
remove |
via yum |
The abrt-plugin-logger package can be removed with the following command: $ sudo yum erase abrt-plugin-logger |
abrt-plugin-logger is an ABRT plugin which writes a report to a specified file. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
System Tooling / Utilities |
| CCE-82348-4 |
Remove the GDM Package Group |
remove |
via yum |
By removing the gdm package, the system no longer has GNOME installed installed. If X Windows is not installed then the system cannot boot into graphical user mode. This prevents the system from being accidentally or maliciously booted into a graphical.target mode. To do so, run the following command: $ sudo yum remove gdm |
Unnecessary service packages must not be installed to decrease the attack surface of the system. A graphical environment is unnecessary for certain types of systems including a virtualization hypervisor. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
GNOME Desktop Environment |
| CCE-81004-4 |
Make sure that the dconf databases are up-to-date with regards to respective keyfiles |
update |
via dconf |
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 update command. |
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. |
high |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
GNOME Desktop Environment |
| CCE-27446-4 |
Configure GNOME3 DConf User Profile |
configure |
via /etc/dconf/profile/user |
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/user should be set as follows: user-db:user system-db:local system-db:site system-db:distro |
Failure to have a functional DConf profile prevents GNOME3 configuration settings from being enforced for all users and allows various security risks. |
high |
NaN |
NaN |
NaN |
NaN |
GNOME Desktop Environment |
| CCE-80108-4 |
Enable the GNOME3 Login Smartcard Authentication |
True |
via dconf db config files |
In the default graphical environment, smart card authentication can be enabled on the login screen by setting enable-smartcard-authentication to true. To enable, add or edit enable-smartcard-authentication to /etc/dconf/db/gdm.d/00-security-settings. For example: [org/gnome/login-screen] enable-smartcard-authentication=true 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/enable-smartcard-authentication After the settings have been set, run dconf update. |
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. |
medium |
IA-2(11),IA-2(3),IA-2(4),IA-2(8),IA-2(9) |
NaN |
NaN |
SRG-OS-000375-GPOS-00160,SRG-OS-000375-GPOS-00161,SRG-OS-000377-GPOS-00162 |
Configure GNOME Login Screen |
| CCE-80109-2 |
Set the GNOME3 Login Number of Failures |
3 |
via dconf db config files |
In the default graphical environment, the GNOME3 login screen and be configured to restart the authentication process after a configured number of attempts. This can be configured by setting allowed-failures to 3 or less. To enable, add or edit allowed-failures to /etc/dconf/db/gdm.d/00-security-settings. For example: [org/gnome/login-screen] allowed-failures=3 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/allowed-failures After the settings have been set, run dconf update. |
Setting the password retry prompts that are permitted on a per-session basis to a low value requires some software, such as SSH, to re-connect. This can slow down and draw additional attention to some types of password-guessing attacks. |
medium |
NaN |
FMT_MOF_EXT.1 |
NaN |
NaN |
Configure GNOME Login Screen |
| CCE-80107-6 |
Disable the GNOME3 Login Restart and Shutdown Buttons |
True |
via dconf db config files |
In the default graphical environment, users logging directly into the system are greeted with a login screen that allows any user, known or unknown, the ability the ability to shutdown or restart the system. This functionality should be disabled by setting disable-restart-buttons to true. To disable, add or edit disable-restart-buttons to /etc/dconf/db/gdm.d/00-security-settings. For example: [org/gnome/login-screen] disable-restart-buttons=true 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/disable-restart-buttons After the settings have been set, run dconf update. |
A user who is at the console can reboot the system at the login screen. If restart or shutdown buttons are pressed at the login screen, this can create the risk of short-term loss of availability of systems due to reboot. |
high |
AC-6(1),CM-6(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure GNOME Login Screen |
| CCE-80105-0 |
Disable GDM Guest Login |
0 |
via /etc/gdm/custom.conf |
The GNOME Display Manager (GDM) can allow users to login without credentials which can be useful for public kiosk scenarios. Allowing users to login without credentials or "guest" account access has inherent security risks and should be disabled. To do disable timed logins or guest account access, set the TimedLoginEnable to false in the [daemon] section in /etc/gdm/custom.conf. For example: [daemon] TimedLoginEnable=false |
Failure to restrict system access to authenticated users negatively impacts operating system security. |
high |
CM-6(a),CM-7(a),CM-7(b),IA-2 |
FIA_UAU.1 |
NaN |
SRG-OS-000480-GPOS-00229 |
Configure GNOME Login Screen |
| CCE-80106-8 |
Disable the GNOME3 Login User List |
True |
via dconf db config files |
In the default graphical environment, users logging directly into the system are greeted with a login screen that displays all known users. This functionality should be disabled by setting disable-user-list to true. To disable, add or edit disable-user-list to /etc/dconf/db/gdm.d/00-security-settings. For example: [org/gnome/login-screen] disable-user-list=true 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/disable-user-list After the settings have been set, run dconf update. |
Leaving the user list enabled is a security risk since it allows anyone with physical access to the system to quickly enumerate known user accounts without logging in. |
medium |
AC-23,CM-6(a) |
NaN |
NaN |
NaN |
Configure GNOME Login Screen |
| CCE-80104-3 |
Disable GDM Automatic Login |
0 |
via /etc/gdm/custom.conf |
The GNOME Display Manager (GDM) can allow users to automatically login without user interaction or credentials. User should always be required to authenticate themselves to the system that they are authorized to use. To disable user ability to automatically login to the system, set the AutomaticLoginEnable to false in the [daemon] section in /etc/gdm/custom.conf. For example: [daemon] AutomaticLoginEnable=false |
Failure to restrict system access to authenticated users negatively impacts operating system security. |
high |
AC-6(1),CM-6(a),CM-7(b) |
FIA_UAU.1 |
NaN |
SRG-OS-000480-GPOS-00229 |
Configure GNOME Login Screen |
| CCE-80120-9 |
Require Credential Prompting for Remote Access in GNOME3 |
vnc |
via dconf db config files |
By default, GNOME does not require credentials when using Vino for remote access. To configure the system to require remote credentials, add or set authentication-methods to ['vnc'] in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/Vino] authentication-methods=['vnc'] 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/Vino/authentication-methods After the settings have been set, run dconf update. |
Username and password prompting is required for remote access. Otherwise, non-authorized and nefarious users can access the system freely. |
medium |
NaN |
NaN |
NaN |
NaN |
GNOME Remote Access Settings |
| CCE-80121-7 |
Require Encryption for Remote Access in GNOME3 |
True |
via dconf db config files |
By default, GNOME requires encryption when using Vino for remote access. To prevent remote access encryption from being disabled, add or set require-encryption to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/Vino] require-encryption=true 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/Vino/require-encryption After the settings have been set, run dconf update. |
Open X displays allow an attacker to capture keystrokes and to execute commands remotely. |
medium |
AC-17(2),AC-17(a),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
GNOME Remote Access Settings |
| CCE-80119-1 |
Disable WIFI Network Notification in GNOME3 |
True |
via dconf db config files |
By default, GNOME disables WIFI notification. This should be permanently set so that users do not connect to a wireless network when the system finds one. While useful for mobile devices, this setting should be disabled for all other systems. To configure the system to disable the WIFI notication, add or set suppress-wireless-networks-available to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/nm-applet] suppress-wireless-networks-available=true 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/nm-applet/suppress-wireless-networks-available After the settings have been set, run dconf update. |
Wireless network connections should not be allowed to be configured by general users on a given system as it could open the system to backdoor attacks. |
medium |
NaN |
NaN |
NaN |
NaN |
GNOME Network Settings |
| CCE-80118-3 |
Disable WIFI Network Connection Creation in GNOME3 |
True |
via dconf db config files |
GNOME allows users to create ad-hoc wireless connections through the NetworkManager applet. Wireless connections should be disabled by adding or setting disable-wifi-create to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/nm-applet] disable-wifi-create=true 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/nm-applet/disable-wifi-create After the settings have been set, run dconf update. |
Wireless network connections should not be allowed to be configured by general users on a given system as it could open the system to backdoor attacks. |
medium |
NaN |
NaN |
NaN |
NaN |
GNOME Network Settings |
| CCE-80122-5 |
Disable GNOME3 Automounting |
0 |
via dconf db config files |
The system's default desktop environment, GNOME3, will mount devices and removable media (such as DVDs, CDs and USB flash drives) whenever they are inserted into the system. To disable automount and autorun within GNOME3, add or set automount to false, automount-open to false, and autorun-never to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/media-handling] automount=false automount-open=false autorun-never=true 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/media-handling/automount /org/gnome/desktop/media-handling/automount-open /org/gnome/desktop/media-handling/autorun-never After the settings have been set, run dconf update. |
Disabling automatic mounting in GNOME3 can prevent the introduction of malware via removable media. It will, however, also prevent desktop users from legitimate use of removable media. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
GNOME Media Settings |
| CCE-80123-3 |
Disable All GNOME3 Thumbnailers |
True |
via dconf db config files |
The system's default desktop environment, GNOME3, uses a number of different thumbnailer programs to generate thumbnails for any new or modified content in an opened folder. To disable the execution of these thumbnail applications, add or set disable-all to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/thumbnailers] disable-all=true 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/thumbnailers/disable-all After the settings have been set, run dconf update. This effectively prevents an attacker from gaining access to a system through a flaw in GNOME3's Nautilus thumbnail creators. |
An attacker with knowledge of a flaw in a GNOME3 thumbnailer application could craft a malicious file to exploit this flaw. Assuming the attacker could place the malicious file on the local filesystem (via a web upload for example) and assuming a user browses the same location using Nautilus, the malicious file would exploit the thumbnailer with the potential for malicious code execution. It is best to disable these thumbnailer applications unless they are explicitly required. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
GNOME Media Settings |
| CCE-80116-7 |
Disable Power Settings in GNOME3 |
0 |
via dconf db config files |
By default, GNOME enables a power profile designed for mobile devices with battery usage. While useful for mobile devices, this setting should be disabled for all other systems. To configure the system to disable the power setting, add or set active to false in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/settings-daemon/plugins/power] active=false Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/settings-daemon/plugins/power After the settings have been set, run dconf update. |
Power settings should not be enabled on systems that are not mobile devices. Enabling power settings on non-mobile devices could have unintended processing consequences on standard systems. |
medium |
NaN |
NaN |
NaN |
NaN |
GNOME System Settings |
| CCE-80115-9 |
Disable User Administration in GNOME3 |
True |
via dconf db config files |
By default, GNOME will allow all users to have some administratrion capability. This should be disabled so that non-administrative users are not making configuration changes. To configure the system to disable user administration capability in the Graphical User Interface (GUI), add or set user-administration-disabled to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/lockdown] user-administration-disabled=true 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/lockdown/user-administration-disabled After the settings have been set, run dconf update. |
Allowing all users to have some administratrive capabilities to the system through the Graphical User Interface (GUI) when they would not have them otherwise could allow unintended configuration changes as well as a nefarious user the capability to make system changes such as adding new accounts, etc. |
high |
NaN |
FMT_MOD_EXT.1 |
NaN |
NaN |
GNOME System Settings |
| CCE-80124-1 |
Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3 |
'’ |
via dconf db config files |
By default, GNOME will reboot the system if the Ctrl-Alt-Del key sequence is pressed. To configure the system to ignore the Ctrl-Alt-Del key sequence from the Graphical User Interface (GUI) instead of rebooting the system, add or set logout to '' in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/settings-daemon/plugins/media-keys] logout='' Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/settings-daemon/plugins/media-keys/logout After the settings have been set, run dconf update. |
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. |
high |
AC-6(1),CM-6(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
GNOME System Settings |
| CCE-80117-5 |
Disable Geolocation in GNOME3 |
0 |
via dconf db config files |
GNOME allows the clock and applications to track and access location information. This setting should be disabled as applications should not track system location. To configure the system to disable location tracking, add or set enabled to false in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/system/location] enabled=false To configure the clock to disable location tracking, add or set geolocation to false in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/clocks] geolocation=false 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/system/location/enabled /org/gnome/clocks/geolocation After the settings have been set, run dconf update. |
Power settings should not be enabled on systems that are not mobile devices. Enabling power settings on non-mobile devices could have unintended processing consequences on standard systems. |
medium |
NaN |
NaN |
NaN |
NaN |
GNOME System Settings |
| CCE-80563-0 |
Ensure Users Cannot Change GNOME3 Screensaver Lock After Idle Period |
/org/gnome/desktop/screensaver/lock-enabled |
via dconf db config files |
If not already configured, ensure that users cannot change GNOME3 screensaver lock settings by adding /org/gnome/desktop/screensaver/lock-enabled to /etc/dconf/db/local.d/00-security-settings. For example: /org/gnome/desktop/screensaver/lock-enabled After the settings have been set, run dconf update. |
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. |
medium |
CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure GNOME Screen Locking |
| CCE-80564-8 |
Ensure Users Cannot Change GNOME3 Screensaver Idle Activation |
/org/gnome/desktop/screensaver/idle-activation-enabled |
via dconf db config files |
If not already configured, ensure that users cannot change GNOME3 screensaver lock settings by adding /org/gnome/desktop/screensaver/idle-activation-enabled to /etc/dconf/db/local.d/00-security-settings. For example: /org/gnome/desktop/screensaver/idle-activation-enabled After the settings have been set, run dconf update. |
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. |
medium |
CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure GNOME Screen Locking |
| CCE-80114-2 |
Disable Full User Name on Splash Shield |
0 |
via dconf db config files |
By default when the screen is locked, the splash shield will show the user's full name. This should be disabled to prevent casual observers from seeing who has access to the system. This can be disabled by adding or setting show-full-name-in-top-bar to false in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/screensaver] show-full-name-in-top-bar=false 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/show-full-name-in-top-bar After the settings have been set, run dconf update. |
Setting the splash screen to not reveal the logged in user's name conceals who has access to the system from passersby. |
medium |
NaN |
FMT_MOF_EXT.1 |
NaN |
NaN |
Configure GNOME Screen Locking |
| CCE-80371-8 |
Ensure Users Cannot Change GNOME3 Screensaver Settings |
/org/gnome/desktop/screensaver/lock-delay |
via dconf db config files |
If not already configured, ensure that users cannot change GNOME3 screensaver lock settings by adding /org/gnome/desktop/screensaver/lock-delay to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/desktop/screensaver/lock-delay After the settings have been set, run dconf update. |
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not logout because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the session lock. As such, users should not be allowed to change session settings. |
medium |
CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure GNOME Screen Locking |
| CCE-80111-8 |
Enable GNOME3 Screensaver Idle Activation |
True |
via dconf db config files |
To activate the screensaver in the GNOME3 desktop after a period of inactivity, add or set idle-activation-enabled to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/screensaver] idle-activation-enabled=true Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/desktop/screensaver/idle-activation-enabled After the settings have been set, run dconf update. |
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not logout because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the session lock. Enabling idle activation of the screensaver ensures the screensaver will be activated after the idle delay. Applications requiring continuous, real-time screen display (such as network management products) require the login session does not have administrator rights and the display station is located in a controlled-access area. |
medium |
AC-11(a),CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure GNOME Screen Locking |
| CCE-80113-4 |
Implement Blank Screensaver |
'’ |
via dconf db config files |
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='' 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-uri After the settings have been set, run dconf update. |
Setting the screensaver mode to blank-only conceals the contents of the display from passersby. |
medium |
AC-11(1),CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
NaN |
Configure GNOME Screen Locking |
| CCE-80110-0 |
Set GNOME3 Screensaver Inactivity Timeout |
900 |
via dconf db config files |
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 Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/desktop/session/idle-delay After the settings have been set, run dconf update. |
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. |
medium |
AC-11(a),CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure GNOME Screen Locking |
| CCE-80370-0 |
Set GNOME3 Screensaver Lock Delay After Activation Period |
0 |
via dconf db config files |
To activate the locking delay of the screensaver in the GNOME3 desktop when the screensaver is activated, add or set lock-delay to uint32 in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/screensaver] lock-delay=uint32 Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/desktop/screensaver/lock-delay After the settings have been set, run dconf update. |
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. |
medium |
AC-11(a),CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure GNOME Screen Locking |
| CCE-80544-0 |
Ensure Users Cannot Change GNOME3 Session Idle Settings |
/org/gnome/desktop/session/idle-delay |
via dconf db config files |
If not already configured, ensure that users cannot change GNOME3 session idle settings by adding /org/gnome/desktop/session/idle-delay to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example: /org/gnome/desktop/session/idle-delay After the settings have been set, run dconf update. |
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not logout because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the session lock. As such, users should not be allowed to change session settings. |
medium |
CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000029-GPOS-00010 |
Configure GNOME Screen Locking |
| CCE-80112-6 |
Enable GNOME3 Screensaver Lock After Idle Period |
True |
via dconf db config files |
To activate locking of the screensaver in the GNOME3 desktop when it is activated, add or set lock-enabled to true in /etc/dconf/db/local.d/00-security-settings. For example: [org/gnome/desktop/screensaver] lock-enabled=true 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/lock-enabled After the settings have been set, run dconf update. |
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. |
medium |
CM-6(a) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000028-GPOS-00009,SRG-OS-000030-GPOS-00011 |
Configure GNOME Screen Locking |
| CCE-82351-8 |
IOMMU configuration directive |
off |
grub |
On x86 architecture supporting VT-d, the IOMMU manages the access control policy between the hardware devices and some of the system critical units such as the memory. |
On x86 architectures, activating the I/OMMU prevents the system from arbritrary accesses potentially made by hardware devices. |
unknown |
NaN |
NaN |
NaN |
NaN |
GRUB2 bootloader configuration |
| CCE-80517-6 |
Boot Loader Is Not Installed On Removeable Media |
hd0,msdos1 |
via grub |
The system must not allow removable media to be used as the boot loader. Remove alternate methods of booting the system from removable media. usb0, cd, fd0, etc. are some examples of removeable media which should not exist in the line: set root='hd0,msdos1' |
Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000364-GPOS-00151 |
GRUB2 bootloader configuration |
| CCE-82023-3 |
Verify /boot/grub2/grub.cfg Group Ownership |
root |
via chgrp |
The file /boot/grub2/grub.cfg should be group-owned by the root group to prevent destruction or modification of the file. To properly set the group owner of /boot/grub2/grub.cfg, run the command: $ sudo chgrp root /boot/grub2/grub.cfg |
The root group is a highly-privileged group. Furthermore, the group-owner of this file should not have any access privileges anyway. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
GRUB2 bootloader configuration |
| CCE-82039-9 |
Verify /boot/grub2/grub.cfg Permissions |
600 |
via chmod |
File permissions for /boot/grub2/grub.cfg should be set to 600. To properly set the permissions of /boot/grub2/grub.cfg, run the command: $ sudo chmod 600 /boot/grub2/grub.cfg |
Proper permissions ensure that only the root user can modify important boot parameters. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
GRUB2 bootloader configuration |
| CCE-83541-3 |
Set the UEFI Boot Loader Admin Username to a Non-Default Value |
unique name that is not root, admin, or administrator |
via grub |
The grub2 boot loader should have a superuser account and password protection enabled to protect boot-time settings. To maximize the protection, select a password-protected superuser account with unique name, and modify the /etc/grub.d/01_users configuration file to reflect the account name change. It is highly suggested not to use common administrator account names like root, admin, or administrator for the grub2 superuser account. Change the superuser to a different username (The default is 'root'). $ sed -i 's/\(set superuser=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users Once the superuser account has been added, update the grub.cfg file by running: grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg |
Having a non-default grub superuser username makes password-guessing attacks less effective. For more information on how to configure the grub2 superuser account and password, please refer to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-working_with_the_grub_2_boot_loader#sec-Protecting_GRUB_2_with_a_Password. |
low |
CM-6(a) |
FIA_UAU.1 |
1.4.2 |
SRG-OS-000080-GPOS-00048 |
GRUB2 bootloader configuration |
| CCE-82026-6 |
Verify /boot/grub2/grub.cfg User Ownership |
root |
via chown |
The file /boot/grub2/grub.cfg should be owned by the root user to prevent destruction or modification of the file. To properly set the owner of /boot/grub2/grub.cfg, run the command: $ sudo chown root /boot/grub2/grub.cfg |
Only root should be able to modify important boot parameters. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
GRUB2 bootloader configuration |
| CCE-80354-4 |
Set the UEFI Boot Loader Password |
configure |
via grub2-setpassword |
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-setpassword When prompted, enter the password that was selected. Once the superuser password has been added, update the grub.cfg file by running: grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg |
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. |
medium |
CM-6(a) |
FIA_UAU.1 |
1.4.2 |
SRG-OS-000080-GPOS-00048 |
GRUB2 bootloader configuration |
| CCE-83562-9 |
Set the Boot Loader Admin Username to a Non-Default Value |
unique name that is not root, admin, or administrator |
via grub |
The grub2 boot loader should have a superuser account and password protection enabled to protect boot-time settings. To maximize the protection, select a password-protected superuser account with unique name, and modify the /etc/grub.d/01_users configuration file to reflect the account name change. Do not to use common administrator account names like root, admin, or administrator for the grub2 superuser account. Change the superuser to a different username (The default is 'root'). $ sed -i 's/\(set superuser=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users Once the superuser account has been added, update the grub.cfg file by running: grub2-mkconfig -o /boot/grub2/grub.cfg |
Having a non-default grub superuser username makes password-guessing attacks less effective. |
low |
CM-6(a) |
FIA_UAU.1 |
1.4.2 |
SRG-OS-000080-GPOS-00048 |
GRUB2 bootloader configuration |
| CCE-80518-4 |
UEFI Boot Loader Is Not Installed On Removeable Media |
hd0,msdos1 |
via grub |
The system must not allow removable media to be used as the boot loader. Remove alternate methods of booting the system from removable media. usb0, cd, fd0, etc. are some examples of removeable media which should not exist in the line: set root='hd0,msdos1' |
Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000364-GPOS-00151 |
GRUB2 bootloader configuration |
| CCE-27309-4 |
Set Boot Loader Password in grub2 |
configure |
via grub2-setpassword |
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-setpassword When prompted, enter the password that was selected. Once the superuser password has been added, update the grub.cfg file by running: grub2-mkconfig -o /boot/grub2/grub.cfg |
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. |
high |
CM-6(a) |
FIA_UAU.1 |
NaN |
SRG-OS-000080-GPOS-00048 |
GRUB2 bootloader configuration |
| CCE-82977-0 |
Install policycoreutils Package |
install |
via yum |
The policycoreutils package can be installed with the following command: $ sudo yum install policycoreutils |
Security-enhanced Linux is a feature of the Linux kernel and a number of utilities with enhanced security functionality designed to add mandatory access controls to Linux. The Security-enhanced Linux kernel contains new architectural components originally developed to improve security of the Flask operating system. These architectural components provide general support for the enforcement of many kinds of mandatory access control policies, including those based on the concepts of Type Enforcement, Role-based Access Control, and Multi-level Security. policycoreutils contains the policy core utilities that are required for basic operation of an SELinux-enabled system. These utilities include load_policy to load SELinux policies, setfiles to label filesystems, newrole to switch roles, and run_init to run /etc/init.d scripts in the proper context. |
high |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
SELinux |
| CCE-82876-4 |
Install libselinux Package |
install |
via yum |
The libselinux package can be installed with the following command: $ sudo yum install libselinux |
Security-enhanced Linux is a feature of the Linux kernel and a number of utilities with enhanced security functionality designed to add mandatory access controls to Linux. The libselinux package contains the core library of the Security-enhanced Linux system. |
high |
NaN |
NaN |
1.6.2 |
NaN |
SELinux |
| CCE-80444-3 |
Uninstall setroubleshoot Package |
remove |
via yum |
The SETroubleshoot service notifies desktop users of SELinux denials. The service provides information around configuration errors, unauthorized intrusions, and other potential errors. The setroubleshoot package can be removed with the following command: $ sudo yum erase setroubleshoot |
The SETroubleshoot service is an unnecessary daemon to have running on a server, especially if X Windows is removed or disabled. |
low |
NaN |
NaN |
NaN |
NaN |
SELinux |
| CCE-80445-0 |
Uninstall mcstrans Package |
remove |
via yum |
The mcstransd daemon provides category label information to client processes requesting information. The label translations are defined in /etc/selinux/targeted/setrans.conf. The mcstrans package can be removed with the following command: $ sudo yum erase mcstrans |
Since this service is not used very often, disable it to reduce the amount of potentially vulnerable code running on the system. NOTE: This rule was added in support of the CIS RHEL6 v1.2.0 benchmark. Please note that Red Hat does not feel this rule is security relevant. |
low |
NaN |
NaN |
1.6.1.5 |
NaN |
SELinux |
| CCE-80543-2 |
Map System Users To The Appropriate SELinux Role |
configure |
via semanage |
Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. All administrators must be mapped to the sysadm_u or staff_u users with the appropriate domains (sysadm_t and staff_t). $ sudo semanage login -m -s sysadm_u USER or $ sudo semanage login -m -s staff_u USER All authorized non-administrative users must be mapped to the user_u role or the appropriate domain (user_t). $ sudo semanage login -m -s user_u USER |
Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000324-GPOS-00125 |
SELinux |
| CCE-27279-9 |
Configure SELinux Policy |
targeting |
via /etc/selinux/config |
The SELinux targeted policy is appropriate for general-purpose desktops and servers, as well as systems in many other roles. To configure the system to use this policy, add or correct the following line in /etc/selinux/config: SELINUXTYPE= Other policies, such as mls, provide additional security labeling and greater confinement but are not compatible with many general-purpose use cases. |
Setting the SELinux policy to targeted or a more specialized policy ensures the system will confine processes that are likely to be targeted for exploitation, such as network or system services. Note: During the development or debugging of SELinux modules, it is common to temporarily place non-production systems in permissive mode. In such temporary cases, SELinux policies should be developed, and once work is completed, the system should be reconfigured to . |
high |
AC-3,AC-3(3)(a),AU-9,SC-7(21) |
NaN |
NaN |
SRG-OS-000445-GPOS-00199 |
SELinux |
| CCE-27288-0 |
Ensure No Daemons are Unconfined by SELinux |
verify |
via ps |
Daemons for which the SELinux policy does not contain rules will inherit the context of the parent process. Because daemons are launched during startup and descend from the init process, they inherit the initrc_t context. To check for unconfined daemons, run the following command: $ sudo ps -eZ | egrep "initrc" | egrep -vw "tr|ps|egrep|bash|awk" | tr ':' ' ' | awk '{ print $NF }' It should produce no output in a well-configured system. |
Daemons which run with the initrc_t context may cause AVC denials, or allow privileges that the daemon does not require. |
medium |
AC-3(3)(a),AC-6,CM-6(a),CM-7(a),CM-7(b) |
NaN |
1.7.1.5 |
NaN |
SELinux |
| CCE-27334-2 |
Ensure SELinux State is Enforcing |
Enforcing |
via /etc/selinux/config |
The SELinux state should be set to at system boot time. In the file /etc/selinux/config, add or correct the following line to configure the system to boot into enforcing mode: SELINUX= |
Setting the SELinux state to enforcing ensures SELinux is able to confine potentially compromised processes to the security policy, which is designed to prevent them from causing damage to the system or further elevating their privileges. |
high |
AC-3,AC-3(3)(a),AU-9,SC-7(21) |
NaN |
NaN |
SRG-OS-000445-GPOS-00199 |
SELinux |
| CCE-26961-3 |
Ensure SELinux Not Disabled in /etc/default/grub |
verify |
via /etc/default/grub |
SELinux can be disabled at boot time by an argument in /etc/default/grub. Remove any instances of selinux=0 from the kernel arguments in that file to prevent SELinux from being disabled at boot. |
Disabling a major host protection feature, such as SELinux, at boot time prevents it from confining system services at boot time. Further, it increases the chances that it will remain off during system operation. |
medium |
AC-3,AC-3(3)(a) |
NaN |
NaN |
NaN |
SELinux |
| CCE-27326-8 |
Ensure No Device Files are Unlabeled by SELinux |
verify |
via find |
Device files, which are used for communication with important system resources, should be labeled with proper SELinux types. If any device files carry the SELinux type device_t or unlabeled_t, report the bug so that policy can be corrected. Supply information about what the device is and what programs use it. To check for incorrectly labeled device files, run following commands: $ sudo find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n" $ sudo find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n" It should produce no output in a well-configured system. |
If a device file carries the SELinux type device_t or unlabeled_t, then SELinux cannot properly restrict access to the device file. |
medium |
AC-3(3)(a),AC-6,CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
SELinux |
| CCE-80423-7 |
Disable the antivirus_use_jit SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean antivirus_use_jit is disabled. If this setting is enabled, it should be disabled. To disable the antivirus_use_jit SELinux boolean, run the following command: $ sudo setsebool -P antivirus_use_jit off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82337-7 |
Disable the xguest_connect_network SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xguest_connect_network is enabled. This setting should be disabled as guest users should not be able to configure NetworkManager. To disable the xguest_connect_network SELinux boolean, run the following command: $ sudo setsebool -P xguest_connect_network off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82298-1 |
Enable the logadm_exec_content SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean logadm_exec_content is enabled. If this setting is disabled, it should be enabled. To enable the logadm_exec_content SELinux boolean, run the following command: $ sudo setsebool -P logadm_exec_content on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82314-6 |
disable the selinuxuser_execstack SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_execstack is enabled. This setting should be disabled as unconfined executables should not be able to make their stack executable. To disable the selinuxuser_execstack SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_execstack off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82306-2 |
Enable the secadm_exec_content SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean secadm_exec_content is enabled. If this setting is disabled, it should be enabled. To enable the secadm_exec_content SELinux boolean, run the following command: $ sudo setsebool -P secadm_exec_content on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82325-2 |
Disable the ssh_chroot_rw_homedirs SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean ssh_chroot_rw_homedirs is disabled. If this setting is enabled, it should be disabled. To disable the ssh_chroot_rw_homedirs SELinux boolean, run the following command: $ sudo setsebool -P ssh_chroot_rw_homedirs off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82308-8 |
Disable the secure_mode_insmod SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean secure_mode_insmod is disabled. If this setting is enabled, it should be disabled. To disable the secure_mode_insmod SELinux boolean, run the following command: $ sudo setsebool -P secure_mode_insmod off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80424-5 |
Enable the auditadm_exec_content SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean auditadm_exec_content is enabled. If this setting is disabled, it should be enabled. To enable the auditadm_exec_content SELinux boolean, run the following command: $ sudo setsebool -P auditadm_exec_content on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82322-9 |
Disable the selinuxuser_tcp_server SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_tcp_server is disabled. If this setting is enabled, it should be disabled. To disable the selinuxuser_tcp_server SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_tcp_server off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80422-9 |
Enable the antivirus_can_scan_system SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean antivirus_can_scan_system is disabled. This setting should be enabled as it allows antivirus programs to read non-security files on a system. To enable the antivirus_can_scan_system SELinux boolean, run the following command: $ sudo setsebool -P antivirus_can_scan_system on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82286-6 |
Enable the cron_userdomain_transition SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean cron_userdomain_transition is enabled. This setting should be enabled as end user cron jobs run in their default associated user domain(s) instead of the general cronjob domain. To enable the cron_userdomain_transition SELinux boolean, run the following command: $ sudo setsebool -P cron_userdomain_transition on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82301-3 |
Enable the login_console_enabled SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean login_console_enabled is enabled. If this setting is disabled, it should be enabled as it allows login from /dev/console to a console session. To enable the login_console_enabled SELinux boolean, run the following command: $ sudo setsebool -P login_console_enabled on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82299-9 |
Disable the logging_syslogd_can_sendmail SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean logging_syslogd_can_sendmail is disabled. If this setting is enabled, it should be disabled. To disable the logging_syslogd_can_sendmail SELinux boolean, run the following command: $ sudo setsebool -P logging_syslogd_can_sendmail off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80420-3 |
Disable the abrt_handle_event SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean abrt_handle_event is disabled. If this setting is enabled, it should be disabled. To disable the abrt_handle_event SELinux boolean, run the following command: $ sudo setsebool -P abrt_handle_event off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82294-0 |
Disable the gpg_web_anon_write SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean gpg_web_anon_write is disabled. If this setting is enabled, it should be disabled. To disable the gpg_web_anon_write SELinux boolean, run the following command: $ sudo setsebool -P gpg_web_anon_write off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82333-6 |
Disable the xdm_bind_vnc_tcp_port SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xdm_bind_vnc_tcp_port is disabled. If this setting is enabled, it should be disabled. To disable the xdm_bind_vnc_tcp_port SELinux boolean, run the following command: $ sudo setsebool -P xdm_bind_vnc_tcp_port off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82288-2 |
Disable the daemons_use_tcp_wrapper SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean daemons_use_tcp_wrapper is disabled. If this setting is enabled, it should be disabled. To disable the daemons_use_tcp_wrapper SELinux boolean, run the following command: $ sudo setsebool -P daemons_use_tcp_wrapper off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82328-6 |
Enable the staff_exec_content SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean staff_exec_content is enabled. If this setting is disabled, it should be enabled. To enable the staff_exec_content SELinux boolean, run the following command: $ sudo setsebool -P staff_exec_content on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82284-1 |
Disable the cron_can_relabel SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean cron_can_relabel is disabled. If this setting is enabled, it should be disabled. To disable the cron_can_relabel SELinux boolean, run the following command: $ sudo setsebool -P cron_can_relabel off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82310-4 |
Disable the secure_mode_policyload SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean secure_mode_policyload is disabled. If this setting is enabled, it should be disabled. To disable the secure_mode_policyload SELinux boolean, run the following command: $ sudo setsebool -P secure_mode_policyload off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82285-8 |
Disable the cron_system_cronjob_use_shares SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean cron_system_cronjob_use_shares is disabled. If this setting is enabled, it should be disabled. To disable the cron_system_cronjob_use_shares SELinux boolean, run the following command: $ sudo setsebool -P cron_system_cronjob_use_shares off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82326-0 |
Disable the ssh_keysign SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean ssh_keysign is disabled. If this setting is enabled, it should be disabled. To disable the ssh_keysign SELinux boolean, run the following command: $ sudo setsebool -P ssh_keysign off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82338-5 |
Disable the xguest_exec_content SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xguest_exec_content is enabled. This setting should be disabled as guest users should not be able to run executables. To disable the xguest_exec_content SELinux boolean, run the following command: $ sudo setsebool -P xguest_exec_content off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82320-3 |
Disable the selinuxuser_rw_noexattrfile SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_rw_noexattrfile is enabled. This setting should be disabled as users should not be able to read/write files on filesystems that do not have extended attributes e.g. FAT, CDROM, FLOPPY, etc. To disable the selinuxuser_rw_noexattrfile SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_rw_noexattrfile off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82332-8 |
Enable the user_exec_content SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean user_exec_content is enabled. If this setting is disabled, it should be enabled. To enable the user_exec_content SELinux boolean, run the following command: $ sudo setsebool -P user_exec_content on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82311-2 |
Configure the selinuxuser_direct_dri_enabled SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_direct_dri_enabled is enabled. If XWindows is not installed or used on the system, this setting should be disabled. Otherwise, enable it. To disable the selinuxuser_direct_dri_enabled SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_direct_dri_enabled off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80421-1 |
Disable the abrt_upload_watch_anon_write SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean abrt_upload_watch_anon_write is enabled. This setting should be disabled as it allows the Automatic Bug Report Tool (ABRT) to modify public files used for public file transfer services. To disable the abrt_upload_watch_anon_write SELinux boolean, run the following command: $ sudo setsebool -P abrt_upload_watch_anon_write off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82287-4 |
Disable the daemons_dump_core SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean daemons_dump_core is disabled. If this setting is enabled, it should be disabled. To disable the daemons_dump_core SELinux boolean, run the following command: $ sudo setsebool -P daemons_dump_core off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82335-1 |
Disable the xdm_sysadm_login SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xdm_sysadm_login is disabled. If this setting is enabled, it should be disabled. To disable the xdm_sysadm_login SELinux boolean, run the following command: $ sudo setsebool -P xdm_sysadm_login off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82305-4 |
Disable the polyinstantiation_enabled SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean polyinstantiation_enabled is disabled. If this setting is enabled, it should be disabled. To disable the polyinstantiation_enabled SELinux boolean, run the following command: $ sudo setsebool -P polyinstantiation_enabled off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80428-6 |
Disable the awstats_purge_apache_log_files SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean awstats_purge_apache_log_files is disabled. If this setting is enabled, it should be disabled. To disable the awstats_purge_apache_log_files SELinux boolean, run the following command: $ sudo setsebool -P awstats_purge_apache_log_files off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82327-8 |
Disable the ssh_sysadm_login SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean ssh_sysadm_login is disabled. If this setting is enabled, it should be disabled. To disable the ssh_sysadm_login SELinux boolean, run the following command: $ sudo setsebool -P ssh_sysadm_login off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82331-0 |
Disable the use_ecryptfs_home_dirs SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean use_ecryptfs_home_dirs is disabled. If this setting is enabled, it should be disabled. To disable the use_ecryptfs_home_dirs SELinux boolean, run the following command: $ sudo setsebool -P use_ecryptfs_home_dirs off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82339-3 |
Disable the xguest_mount_media SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xguest_mount_media is enabled. This setting should be disabled as guest users should not be able to mount any media. To disable the xguest_mount_media SELinux boolean, run the following command: $ sudo setsebool -P xguest_mount_media off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80419-5 |
Disable the abrt_anon_write SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean abrt_anon_write is disabled. If this setting is enabled, it should be disabled. To disable the abrt_anon_write SELinux boolean, run the following command: $ sudo setsebool -P abrt_anon_write off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82290-8 |
Disable the deny_execmem SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean deny_execmem is disabled. If this setting is enabled, it should be disabled. To disable the deny_execmem SELinux boolean, run the following command: $ sudo setsebool -P deny_execmem off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82300-5 |
Enable the logging_syslogd_use_tty SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean logging_syslogd_use_tty is enabled. If this setting is disabled, it should be enabled as it allows syslog the ability to read/write to terminal. To enable the logging_syslogd_use_tty SELinux boolean, run the following command: $ sudo setsebool -P logging_syslogd_use_tty on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82323-7 |
Disable the selinuxuser_udp_server SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_udp_server is disabled. If this setting is enabled, it should be disabled. To disable the selinuxuser_udp_server SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_udp_server off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80427-8 |
Disable the authlogin_yubikey SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean authlogin_yubikey is disabled. If this setting is enabled, it should be disabled. To disable the authlogin_yubikey SELinux boolean, run the following command: $ sudo setsebool -P authlogin_yubikey off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80425-2 |
Disable the authlogin_nsswitch_use_ldap SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean authlogin_nsswitch_use_ldap is disabled. If this setting is enabled, it should be disabled. To disable the authlogin_nsswitch_use_ldap SELinux boolean, run the following command: $ sudo setsebool -P authlogin_nsswitch_use_ldap off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82295-7 |
Disable the guest_exec_content SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean guest_exec_content is enabled. This setting should be disabled as no guest accounts should be used. To disable the guest_exec_content SELinux boolean, run the following command: $ sudo setsebool -P guest_exec_content off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82340-1 |
Disable the xguest_use_bluetooth SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xguest_use_bluetooth is enabled. This setting should be disabled as guests users should not be able to access or use bluetooth. To disable the xguest_use_bluetooth SELinux boolean, run the following command: $ sudo setsebool -P xguest_use_bluetooth off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82334-4 |
Disable the xdm_exec_bootloader SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xdm_exec_bootloader is disabled. If this setting is enabled, it should be disabled. To disable the xdm_exec_bootloader SELinux boolean, run the following command: $ sudo setsebool -P xdm_exec_bootloader off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82319-5 |
Disable the selinuxuser_postgresql_connect_enabled SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_postgresql_connect_enabled is disabled. If this setting is enabled, it should be disabled. To disable the selinuxuser_postgresql_connect_enabled SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_postgresql_connect_enabled off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82346-8 |
Disable the xserver_object_manager SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xserver_object_manager is disabled. If this setting is enabled, it should be disabled. To disable the xserver_object_manager SELinux boolean, run the following command: $ sudo setsebool -P xserver_object_manager off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82291-6 |
Disable the deny_ptrace SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean deny_ptrace is disabled. If this setting is enabled, it should be disabled. To disable the deny_ptrace SELinux boolean, run the following command: $ sudo setsebool -P deny_ptrace off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82289-0 |
Disable the daemons_use_tty SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean daemons_use_tty is disabled. If this setting is enabled, it should be disabled. To disable the daemons_use_tty SELinux boolean, run the following command: $ sudo setsebool -P daemons_use_tty off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82321-1 |
Disable the selinuxuser_share_music SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_share_music is disabled. If this setting is enabled, it should be disabled. To disable the selinuxuser_share_music SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_share_music off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82293-2 |
Disable the domain_kernel_load_modules SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean domain_kernel_load_modules is disabled. If this setting is enabled, it should be disabled. To disable the domain_kernel_load_modules SELinux boolean, run the following command: $ sudo setsebool -P domain_kernel_load_modules off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82307-0 |
Disable the secure_mode SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean secure_mode is disabled. If this setting is enabled, it should be disabled. To disable the secure_mode SELinux boolean, run the following command: $ sudo setsebool -P secure_mode off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82329-4 |
Enable the sysadm_exec_content SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean sysadm_exec_content is enabled. If this setting is disabled, it should be enabled. To enable the sysadm_exec_content SELinux boolean, run the following command: $ sudo setsebool -P sysadm_exec_content on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82296-5 |
Enable the kerberos_enabled SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean kerberos_enabled is enabled. If this setting is disabled, it should be enabled to allow confined applications to run with Kerberos. To enable the kerberos_enabled SELinux boolean, run the following command: $ sudo setsebool -P kerberos_enabled on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82341-9 |
Disable the xserver_clients_write_xshm SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xserver_clients_write_xshm is disabled. If this setting is enabled, it should be disabled. To disable the xserver_clients_write_xshm SELinux boolean, run the following command: $ sudo setsebool -P xserver_clients_write_xshm off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82324-5 |
Disable the selinuxuser_use_ssh_chroot SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_use_ssh_chroot is disabled. If this setting is enabled, it should be disabled. To disable the selinuxuser_use_ssh_chroot SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_use_ssh_chroot off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80426-0 |
Disable the authlogin_radius SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean authlogin_radius is disabled. If this setting is enabled, it should be disabled. To disable the authlogin_radius SELinux boolean, run the following command: $ sudo setsebool -P authlogin_radius off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82292-4 |
Enable the domain_fd_use SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean domain_fd_use is enabled. If this setting is disabled, it should be enabled. To enable the domain_fd_use SELinux boolean, run the following command: $ sudo setsebool -P domain_fd_use on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82312-0 |
Disable the selinuxuser_execheap SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_execheap is disabled. If this setting is enabled, it should be disabled. To disable the selinuxuser_execheap SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_execheap off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82313-8 |
Enable the selinuxuser_execmod SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean selinuxuser_execmod is enabled. If this setting is disabled, it should be enabled. To enable the selinuxuser_execmod SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_execmod on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82303-9 |
Disable the mock_enable_homedirs SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean mock_enable_homedirs is disabled. If this setting is enabled, it should be disabled. To disable the mock_enable_homedirs SELinux boolean, run the following command: $ sudo setsebool -P mock_enable_homedirs off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82317-9 |
Disable the selinuxuser_mysql_connect_enabled SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean selinuxuser_mysql_connect_enabled is disabled. If this setting is enabled, it should be disabled. To disable the selinuxuser_mysql_connect_enabled SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_mysql_connect_enabled off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82342-7 |
Disable the xserver_execmem SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xserver_execmem is disabled. If this setting is enabled, it should be disabled. To disable the xserver_execmem SELinux boolean, run the following command: $ sudo setsebool -P xserver_execmem off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82336-9 |
Disable the xdm_write_home SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean xdm_write_home is disabled. If this setting is enabled, it should be disabled. To disable the xdm_write_home SELinux boolean, run the following command: $ sudo setsebool -P xdm_write_home off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82318-7 |
Enable the selinuxuser_ping SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean selinuxuser_ping is enabled. If this setting is disabled, it should be enabled as it allows confined users to use ping and traceroute which is helpful for network troubleshooting. To enable the selinuxuser_ping SELinux boolean, run the following command: $ sudo setsebool -P selinuxuser_ping on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80418-7 |
Enable the fips_mode SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean fips_mode is enabled. This allows all SELinux domains to execute in fips_mode. If this setting is disabled, it should be enabled. To enable the fips_mode SELinux boolean, run the following command: $ sudo setsebool -P fips_mode on |
NaN |
medium |
CM-6(a),IA-7,SC-12,SC-12(2),SC-12(3),SC-13 |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82330-2 |
Enable the unconfined_login SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean unconfined_login is enabled. If this setting is disabled, it should be enabled. To enable the unconfined_login SELinux boolean, run the following command: $ sudo setsebool -P unconfined_login on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82304-7 |
Enable the mount_anyfile SELinux Boolean |
on |
via setsebool |
By default, the SELinux boolean mount_anyfile is enabled. If this setting is disabled, it should be enabled to allow any file or directory to be mounted. To enable the mount_anyfile SELinux boolean, run the following command: $ sudo setsebool -P mount_anyfile on |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80429-4 |
Disable the boinc_execmem SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean boinc_execmem is enabled. This setting should be disabled. To disable the boinc_execmem SELinux boolean, run the following command: $ sudo setsebool -P boinc_execmem off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-82302-1 |
Disable the mmap_low_allowed SELinux Boolean |
off |
via setsebool |
By default, the SELinux boolean mmap_low_allowed is disabled. If this setting is enabled, it should be disabled. To disable the mmap_low_allowed SELinux boolean, run the following command: $ sudo setsebool -P mmap_low_allowed off |
NaN |
medium |
NaN |
NaN |
NaN |
NaN |
SELinux - Booleans |
| CCE-80438-5 |
Configure Multiple DNS Servers in /etc/resolv.conf |
configure |
via /etc/resolv.conf |
Multiple Domain Name System (DNS) Servers should be configured in /etc/resolv.conf. This provides redundant name resolution services in the event that a domain server crashes. To configure the system to contain as least 2 DNS servers, add a corresponding nameserver ip_address entry in /etc/resolv.conf for each DNS server where ip_address is the IP address of a valid DNS server. For example: search example.com nameserver 192.168.0.1 nameserver 192.168.0.2 |
To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging. |
low |
CM-6(a),SC-20(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Configuration and Firewalls |
| CCE-82178-5 |
Prevent non-Privileged Users from Modifying Network Interfaces using nmcli |
configure |
via polkit-1 |
By default, non-privileged users are given permissions to modify networking interfaces and configurations using the nmcli command. Non-privileged users should not be making configuration changes to network configurations. To ensure that non-privileged users do not have permissions to make changes to the network configuration using nmcli, create the following configuration in /etc/polkit-1/localauthority/20-org.d/10-nm-harden-access.pkla: [Disable General User Access to NetworkManager] Identity=default Action=org.freedesktop.NetworkManager.* ResultAny=no ResultInactive=no ResultActive=auth_admin |
Allowing non-privileged users to make changes to network settings can allow untrusted access, prevent system availability, and/or can lead to a compromise or attack. |
medium |
AC-18(4),CM-6(a) |
NaN |
NaN |
NaN |
Network Configuration and Firewalls |
| CCE-80357-7 |
Disable Client Dynamic DNS Updates |
disable |
via ifcfg |
Dynamic DNS allows clients to dynamically update their own DNS records. The updates are transmitted by unencrypted means which can reveal information to a potential malicious user. If the system does not require Dynamic DNS, remove all DHCP_HOSTNAME references from the /etc/sysconfig/network-scripts/ifcfg-interface scripts. If dhclient is used, remove all send host-name hostname references from the /etc/dhclient.conf configuration file and/or any reference from the /etc/dhcp directory. |
Dynamic DNS updates transmit unencrypted information about a system including its name and address and should not be used unless needed. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Configuration and Firewalls |
| CCE-80174-6 |
Ensure System is Not Acting as a Network Sniffer |
disable |
via ip |
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 PROMISC Promiscuous mode of an interface can be disabled with the following command: $ sudo ip link set dev device_name multicast off promisc off |
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. |
medium |
CM-6(a),CM-7(2),CM-7(a),CM-7(b),MA-3 |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Configuration and Firewalls |
| CCE-80173-8 |
Disable Zeroconf Networking |
disable |
via /etc/sysconfig/network |
Zeroconf networking allows the system to assign itself an IP address and engage in IP communication without a statically-assigned address or even a DHCP server. Automatic address assignment via Zeroconf (or DHCP) is not recommended. To disable Zeroconf automatic route assignment in the 169.254.0.0 subnet, add or correct the following line in /etc/sysconfig/network: NOZEROCONF=yes |
Zeroconf addresses are in the network 169.254.0.0. The networking scripts add entries to the system's routing table for these addresses. Zeroconf address assignment commonly occurs when the system is configured to use DHCP but fails to receive an address assignment from the DHCP server. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Network Configuration and Firewalls |
| CCE-82983-8 |
Install iptables Package |
install |
via yum |
The iptables package can be installed with the following command: $ sudo yum install iptables |
iptables controls the Linux kernel network packet filtering code. iptables allows system operators to set up firewalls and IP masquerading, etc. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
iptables and ip6tables |
| CCE-27328-4 |
Disable Bluetooth Service |
disable |
via systemctl |
The bluetooth service can be disabled with the following command: $ sudo systemctl disable bluetooth.service The bluetooth service can be masked with the following command: $ sudo systemctl mask bluetooth.service $ sudo service bluetooth stop |
Disabling the bluetooth service prevents the system from attempting connections to Bluetooth devices, which entails some security risk. Nevertheless, variation in this risk decision may be expected due to the utility of Bluetooth connectivity and its limited range. |
medium |
AC-18(3),AC-18(a),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
NaN |
Disable Wireless Through Software Configuration |
| CCE-27397-9 |
Disable WiFi or Bluetooth in BIOS |
install |
via yum |
Some machines that include built-in wireless support offer the ability to disable the device through the BIOS. This is hardware-specific; consult your hardware manual or explore the BIOS setup during boot. |
Disabling wireless support in the BIOS prevents easy activation of the wireless interface, generally requiring administrators to reboot the system first. |
unknown |
AC-18(3),AC-18(a),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
NaN |
Disable Wireless Through Software Configuration |
| CCE-27327-6 |
Disable Bluetooth Kernel Module |
disable |
via modprobe.d |
The kernel's module loading system can be configured to prevent loading of the Bluetooth module. Add the following to the appropriate /etc/modprobe.d configuration file to prevent the loading of the Bluetooth module: install bluetooth /bin/true |
If Bluetooth functionality must be disabled, preventing the kernel from loading the kernel module provides an additional safeguard against its activation. |
medium |
AC-18(3),AC-18(a),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
Disable Wireless Through Software Configuration |
| CCE-27358-1 |
Deactivate Wireless Network Interfaces |
disable |
via nmcli |
Deactivating wireless network interfaces should prevent normal usage of the wireless capability. Configure the system to disable all wireless network interfaces with the following command: $ sudo nmcli radio wifi off |
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. |
medium |
AC-18(3),AC-18(a),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
3.7 |
SRG-OS-000424-GPOS-00188 |
Disable Wireless Through Software Configuration |
| CCE-82024-1 |
Disable DCCP Support |
disable |
via modprobe.d |
The Datagram Congestion Control Protocol (DCCP) is a relatively new transport layer protocol, designed to support streaming media and telephony. To configure the system to prevent the dccp kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install dccp /bin/true |
Disabling DCCP protects the system against exploitation of any flaws in its implementation. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000096-GPOS-00050,SRG-OS-000378-GPOS-00163 |
Uncommon Network Protocols |
| CCE-82162-9 |
Disable ATM Support |
disable |
via modprobe.d |
The Asynchronous Transfer Mode (ATM) is a protocol operating on network, data link, and physical layers, based on virtual circuits and virtual paths. To configure the system to prevent the atm kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install atm /bin/true |
Disabling ATM protects the system against exploitation of any flaws in its implementation. |
medium |
NaN |
FMT_SMF_EXT.1 |
NaN |
SRG-OS-000095-GPOS-00049 |
Uncommon Network Protocols |
| CCE-83395-4 |
Disable TIPC Support |
disable |
via modprobe.d |
The Transparent Inter-Process Communication (TIPC) protocol is designed to provide communications between nodes in a cluster. To configure the system to prevent the tipc kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install tipc /bin/true |
Disabling TIPC protects the system against exploitation of any flaws in its implementation. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
FMT_SMF_EXT.1 |
NaN |
SRG-OS-000095-GPOS-00049 |
Uncommon Network Protocols |
| CCE-82869-9 |
Disable RDS Support |
disable |
via modprobe.d |
The Reliable Datagram Sockets (RDS) protocol is a transport layer protocol designed to provide reliable high-bandwidth, low-latency communications between nodes in a cluster. To configure the system to prevent the rds kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install rds /bin/true |
Disabling RDS protects the system against exploitation of any flaws in its implementation. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Uncommon Network Protocols |
| CCE-82044-9 |
Disable SCTP Support |
disable |
via modprobe.d |
The Stream Control Transmission Protocol (SCTP) is a transport layer protocol, designed to support the idea of message-oriented communication, with several streams of messages within one connection. To configure the system to prevent the sctp kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install sctp /bin/true |
Disabling SCTP protects the system against exploitation of any flaws in its implementation. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
Uncommon Network Protocols |
| CCE-82160-3 |
Disable IEEE 1394 (FireWire) Support |
disable |
via modprobe.d |
The IEEE 1394 (FireWire) is a serial bus standard for high-speed real-time communication. To configure the system to prevent the firewire-core kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install firewire-core /bin/true |
Disabling FireWire protects the system against exploitation of any flaws in its implementation. |
medium |
NaN |
FMT_SMF_EXT.1 |
NaN |
SRG-OS-000095-GPOS-00049 |
Uncommon Network Protocols |
| CCE-82164-5 |
Disable CAN Support |
disable |
via modprobe.d |
The Controller Area Network (CAN) is a serial communications protocol which was initially developed for automotive and is now also used in marine, industrial, and medical applications. To configure the system to prevent the can kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install can /bin/true |
Disabling CAN protects the system against exploitation of any flaws in its implementation. |
medium |
NaN |
FMT_SMF_EXT.1 |
NaN |
SRG-OS-000095-GPOS-00049 |
Uncommon Network Protocols |
| CCE-82999-4 |
Install firewalld Package |
install |
via yum |
The firewalld package can be installed with the following command: $ sudo yum install firewalld |
The firewalld package should be installed to provide access control methods. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000298-GPOS-00116,SRG-OS-000480-GPOS-00227 |
Inspect and Activate Default firewalld Rules |
| CCE-80998-8 |
Verify firewalld Enabled |
enable |
via systemctl |
The firewalld service can be enabled with the following command: $ sudo systemctl enable firewalld.service |
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. |
medium |
AC-4,CA-3(5),CM-6(a),CM-7(b),SC-7(21) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000480-GPOS-00227,SRG-OS-000480-GPOS-00231,SRG-OS-000480-GPOS-00232 |
Inspect and Activate Default firewalld Rules |
| CCE-80447-6 |
Configure the Firewalld Ports |
configure |
via firewall-cmd |
Configure the firewalld ports to allow approved services to have access to the system. To configure firewalld to open ports, run the following command: $ sudo firewall-cmd --permanent --add-port=port_number/tcp or $ sudo firewall-cmd --permanent --add-port=service_name Run the command list above for each of the ports listed below: To configure firewalld to allow access, run the following command(s): firewall-cmd --permanent --add-service=ssh |
In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems. Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. |
medium |
AC-4,CA-3(5),CM-6(a),CM-7(b),SC-7(21) |
NaN |
NaN |
SRG-OS-000096-GPOS-00050,SRG-OS-000297-GPOS-00115 |
Strengthen the Default Ruleset |
| CCE-27349-0 |
Set Default firewalld Zone for Incoming Packets |
drop |
via /etc/firewalld/firewalld.conf |
To set the default zone to drop for the built-in default zone which processes incoming IPv4 and IPv6 packets, modify the following line in /etc/firewalld/firewalld.conf to be: DefaultZone=drop |
In firewalld the default zone is applied only after all the applicable rules in the table are examined for a match. Setting the default zone to drop implements proper design for a firewall, i.e. any packets which are not explicitly permitted should not be accepted. |
medium |
CA-3(5),CM-6(a),CM-7(b),SC-7(23) |
FMT_MOF_EXT.1 |
NaN |
SRG-OS-000480-GPOS-00227 |
Strengthen the Default Ruleset |
| CCE-80542-4 |
Configure firewalld To Rate Limit Connections |
configure |
via firewall-cmd |
Create a direct firewall rule to protect against DoS attacks with the following command: $ sudo firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT_direct 0 -p tcp -m limit --limit 25/minute --limit-burst 100 -j INPUT_ZONES |
DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of the operating system to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks. |
medium |
CM-6(a),SC-5,SC-5(1),SC-5(2),SC-5(3)(a) |
NaN |
NaN |
SRG-OS-000420-GPOS-00186 |
Strengthen the Default Ruleset |
| CCE-82871-5 |
Disable IPv6 Networking Support Automatic Loading |
disable |
via modprobe.d |
To prevent the IPv6 kernel module (ipv6) from binding to the IPv6 networking stack, add the following line to /etc/modprobe.d/disabled.conf (or another file in /etc/modprobe.d): options ipv6 disable=1 This permits the IPv6 module to be loaded (and thus satisfy other modules that depend on it), while disabling support for the IPv6 protocol. |
Any unnecessary network stacks - including IPv6 - should be disabled, to reduce the vulnerability to exploitation. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable Support for IPv6 Unless Needed |
| CCE-82886-3 |
Ensure IPv6 is disabled through kernel boot parameter |
True |
via grub |
To disable IPv6 protocol support in the Linux kernel, add the argument ipv6.disable=1 to the default GRUB2 command line for the Linux operating system in /etc/default/grub, so that the line looks similar to GRUB_CMDLINE_LINUX="... ipv6.disable=1 ..." In case the GRUB_DISABLE_RECOVERY is set to true, then the parameter should be added to the GRUB_CMDLINE_LINUX_DEFAULT instead. Run one of following command to ensure that the configuration is applied when booting currently installed kernels: sudo grub2-mkconfig -o /boot/grub2/grub.cfg or sudo /sbin/grubby --update-kernel=ALL --args="ipv6.disable=1" |
Any unnecessary network stacks, including IPv6, should be disabled to reduce the vulnerability to exploitation. |
low |
NaN |
NaN |
3.3.3 |
NaN |
Disable Support for IPv6 Unless Needed |
| CCE-80176-1 |
Disable Interface Usage of IPv6 |
NETWORKING_IPV6=no IPV6INIT=no |
via /etc/sysconfig/network |
To disable interface usage of IPv6, add or correct the following lines in /etc/sysconfig/network: NETWORKING_IPV6=no IPV6INIT=no |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Support for IPv6 Unless Needed |
| CCE-80177-9 |
Disable Support for RPC IPv6 |
disable |
via netconfig |
RPC services for NFSv4 try to load transport modules for udp6 and tcp6 by default, even if IPv6 has been disabled in /etc/modprobe.d. To prevent RPC services such as rpc.mountd from attempting to start IPv6 network listeners, remove or comment out the following two lines in /etc/netconfig: udp6 tpi_clts v inet6 udp - - tcp6 tpi_cots_ord v inet6 tcp - - |
NaN |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable Support for IPv6 Unless Needed |
| CCE-80175-3 |
Disable IPv6 Networking Support Automatic Loading |
True |
via sysctl |
To disable support for (ipv6) add the following line to /etc/sysctl.d/ipv6.conf (or another file in /etc/sysctl.d): net.ipv6.conf.all.disable_ipv6 = 1 This disables IPv6 on all network interfaces as other services and system functionality require the IPv6 stack loaded to work. |
Any unnecessary network stacks - including IPv6 - should be disabled, to reduce the vulnerability to exploitation. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
3.3.3 |
NaN |
Disable Support for IPv6 Unless Needed |
| CCE-80184-5 |
Manually Assign Global IPv6 Address |
configure |
via ifcfg |
To manually assign an IP address for an interface, edit the file /etc/sysconfig/network-scripts/ifcfg-interface. Add or correct the following line (substituting the correct IPv6 address): IPV6ADDR=2001:0DB8::ABCD/64 Manually assigning an IP address is preferable to accepting one from routers or from the network otherwise. The example address here is an IPv6 address reserved for documentation purposes, as defined by RFC3849. |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure IPv6 Settings if Necessary |
| CCE-80183-7 |
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv6 Interfaces |
0 |
via sysctl |
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=0 To 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 |
An illicit ICMP redirect message could result in a man-in-the-middle attack. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
3.3.2 |
SRG-OS-000480-GPOS-00227 |
Configure IPv6 Settings if Necessary |
| CCE-80180-3 |
Configure Accepting Router Advertisements on All IPv6 Interfaces |
0 |
via sysctl |
To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.accept_ra = 0 |
An illicit router advertisement message could result in a man-in-the-middle attack. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure IPv6 Settings if Necessary |
| CCE-80355-1 |
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv6 Interfaces by Default |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure IPv6 Settings if Necessary |
| CCE-80181-1 |
Disable Accepting Router Advertisements on all IPv6 Interfaces by Default |
0 |
via sysctl |
To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.default.accept_ra = 0 |
An illicit router advertisement message could result in a man-in-the-middle attack. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure IPv6 Settings if Necessary |
| CCE-80179-5 |
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv6 Interfaces |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure IPv6 Settings if Necessary |
| CCE-80186-0 |
Manually Assign IPv6 Router Address |
configure |
via ifcfg |
Edit the file /etc/sysconfig/network-scripts/ifcfg-interface, and add or correct the following line (substituting your gateway IP as appropriate): IPV6_DEFAULTGW=2001:0DB8::0001 Router addresses should be manually set and not accepted via any auto-configuration or router advertisement. |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure IPv6 Settings if Necessary |
| CCE-80356-9 |
Disable Kernel Parameter for IPv6 Forwarding |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure IPv6 Settings if Necessary |
| CCE-80185-2 |
Use Privacy Extensions for Address |
configure |
via ifcfg |
To introduce randomness into the automatic generation of IPv6 addresses, add or correct the following line in /etc/sysconfig/network-scripts/ifcfg-interface: IPV6_PRIVACY=rfc3041 Automatically-generated IPv6 addresses are based on the underlying hardware (e.g. Ethernet) address, and so it becomes possible to track a piece of hardware over its lifetime using its traffic. If it is important for a system's IP address to not trivially reveal its hardware address, this setting should be applied. |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure IPv6 Settings if Necessary |
| CCE-80182-9 |
Disable Accepting ICMP Redirects for All IPv6 Interfaces |
0 |
via sysctl |
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=0 To 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 |
An illicit ICMP redirect message could result in a man-in-the-middle attack. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure IPv6 Settings if Necessary |
| CCE-80163-9 |
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv4 Interfaces |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-6(a),CM-7(a),CM-7(b),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80162-1 |
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv4 Interfaces by Default |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-7(a),CM-7(b),SC-5,SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80161-3 |
Enable Kernel Paremeter to Log Martian Packets on all IPv4 Interfaces by Default |
True |
via sysctl |
To set the runtime status of the net.ipv4.conf.default.log_martians kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.log_martians=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.log_martians = 1 |
The presence of "martian" packets (which have impossible addresses) as well as spoofed packets, source-routed packets, and redirects could be a sign of nefarious network activity. Logging these packets enables this activity to be detected. |
unknown |
CM-7(a),CM-7(b),SC-5(3)(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80164-7 |
Configure Kernel Parameter for Accepting Secure Redirects By Default |
0 |
via sysctl |
To set the runtime status of the net.ipv4.conf.default.secure_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.secure_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.secure_redirects = 0 |
Accepting "secure" ICMP redirects (from those gateways listed as default gateways) has few legitimate uses. It should be disabled unless it is absolutely required. |
medium |
CM-7(a),CM-7(b),SC-5,SC-7(a) |
NaN |
3.2.3 |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80165-4 |
Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests on IPv4 Interfaces |
True |
via sysctl |
To set the runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.icmp_echo_ignore_broadcasts = 1 |
Responding to broadcast (ICMP) echoes facilitates network mapping and provides a vector for amplification attacks. Ignoring ICMP echo requests (pings) sent to broadcast or multicast addresses makes the system slightly more difficult to enumerate on the network. |
medium |
CM-7(a),CM-7(b),SC-5 |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80166-2 |
Enable Kernel Parameter to Ignore Bogus ICMP Error Responses on IPv4 Interfaces |
True |
via sysctl |
To set the runtime status of the net.ipv4.icmp_ignore_bogus_error_responses kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.icmp_ignore_bogus_error_responses = 1 |
Ignoring bogus ICMP error responses reduces log size, although some activity would not be logged. |
unknown |
CM-7(a),CM-7(b),SC-5 |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-82893-9 |
Configure Kernel to Rate Limit Sending of Duplicate TCP Acknowledgments |
500 |
via sysctl |
Make sure that the system is configured to limit the maximal rate for sending duplicate acknowledgments in response to incoming TCP packets that are for an existing connection but that are invalid due to any of these reasons: (a) out-of-window sequence number, (b) out-of-window acknowledgment number, or (c) PAWS (Protection Against Wrapped Sequence numbers) check failure This measure protects against or limits effects of DoS attacks against the system. Set the system to implement rate-limiting measures by adding the following line to /etc/sysctl.conf or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value): net.ipv4.tcp_invalid_ratelimit = Issue the following command to make the changes take effect: # sysctl --system |
Denial of Service (DoS) is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This can help mitigate simple “ack loop” DoS attacks, wherein a buggy or malicious middlebox or man-in-the-middle can rewrite TCP header fields in manner that causes each endpoint to think that the other is sending invalid TCP segments, thus causing each side to send an unterminating stream of duplicate acknowledgments for invalid segments. |
medium |
SC-5 |
NaN |
NaN |
SRG-OS-000420-GPOS-00186 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80168-8 |
Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces by Default |
True |
via sysctl |
To set the runtime status of the net.ipv4.conf.default.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.rp_filter=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.rp_filter = 1 |
Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface they were received on. It should not be used on systems which are routers for complicated networks, but is helpful for end hosts and routers serving small networks. |
medium |
CM-6(a),CM-7(a),CM-7(b),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-27434-0 |
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv4 Interfaces |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-7(a),CM-7(b),SC-5CM-6(a),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80167-0 |
Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces |
True |
via sysctl |
To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.rp_filter = 1 |
Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface they were received on. It should not be used on systems which are routers for complicated networks, but is helpful for end hosts and routers serving small networks. |
medium |
CM-6(a),CM-7(a),CM-7(b),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-27495-1 |
Enable Kernel Parameter to Use TCP Syncookies on IPv4 Interfaces |
True |
via sysctl |
To set the runtime status of the net.ipv4.tcp_syncookies kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.tcp_syncookies=1 To 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 |
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. |
medium |
CM-6(a),CM-7(a),CM-7(b),SC-5(1),SC-5(2),SC-5(3)(a) |
NaN |
NaN |
SRG-OS-000142-GPOS-00071,SRG-OS-000420-GPOS-00186,SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80158-9 |
Disable Accepting ICMP Redirects for All IPv4 Interfaces |
0 |
via sysctl |
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=0 To 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 |
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." |
medium |
CM-6(a),CM-7(a),CM-7(b),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80159-7 |
Disable Kernel Parameter for Accepting Secure ICMP Redirects on all IPv4 Interfaces |
0 |
via sysctl |
To set the runtime status of the net.ipv4.conf.all.secure_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.secure_redirects=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.secure_redirects = 0 |
Accepting "secure" ICMP redirects (from those gateways listed as default gateways) has few legitimate uses. It should be disabled unless it is absolutely required. |
medium |
CM-6(a),CM-7(a),CM-7(b),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80160-5 |
Enable Kernel Parameter to Log Martian Packets on all IPv4 Interfaces |
True |
via sysctl |
To set the runtime status of the net.ipv4.conf.all.log_martians kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.log_martians=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.log_martians = 1 |
The presence of "martian" packets (which have impossible addresses) as well as spoofed packets, source-routed packets, and redirects could be a sign of nefarious network activity. Logging these packets enables this activity to be detected. |
unknown |
CM-7(a),CM-7(b),SC-5(3)(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Related Kernel Runtime Parameters for Hosts and Routers |
| CCE-80156-3 |
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-7(a),CM-7(b),SC-5CM-6(a),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Parameters for Hosts Only |
| CCE-80157-1 |
Disable Kernel Parameter for IP Forwarding on IPv4 Interfaces |
0 |
via sysctl |
To set the runtime status of the net.ipv4.ip_forward kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.ip_forward=0 To 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 |
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. |
medium |
CM-7(a),CM-7(b),SC-5CM-6(a),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Parameters for Hosts Only |
| CCE-80999-6 |
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces by Default |
0 |
via sysctl |
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=0 To 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 |
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. |
medium |
CM-7(a),CM-7(b),SC-5CM-6(a),SC-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Network Parameters for Hosts Only |
| CCE-80170-4 |
Install libreswan Package |
install |
via yum |
The Libreswan package provides an implementation of IPsec and IKE, which permits the creation of secure tunnels over untrusted networks. The libreswan package can be installed with the following command: $ sudo yum install libreswan |
Providing the ability for remote users or systems to initiate a secure VPN connection protects information when it is transmitted over a wide area network. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000120-GPOS-00061,SRG-OS-000480-GPOS-00227 |
IPSec Support |
| CCE-80171-2 |
Verify Any Configured IPSec Tunnel Connections |
verify |
via /etc/ipsec.conf |
Libreswan provides an implementation of IPsec and IKE, which permits the creation of secure tunnels over untrusted networks. As such, IPsec can be used to circumvent certain network requirements such as filtering. Verify that if any IPsec connection (conn) configured in /etc/ipsec.conf and /etc/ipsec.d exists is an approved organizational connection. |
IP tunneling mechanisms can be used to bypass network filtering. |
medium |
AC-17(a),AC-4,CM-6(a),MA-4(6),SC-8 |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
IPSec Support |
| CCE-82159-5 |
Disable vsyscalls |
none |
via grub |
To disable use of virtual syscalls, add the argument vsyscall=none to the default GRUB 2 command line for the Linux operating system in /etc/default/grub, in the manner below: GRUB_CMDLINE_LINUX="vsyscall=none" |
Virtual Syscalls provide an opportunity of attack for a user who has control of the return instruction pointer. |
medium |
CM-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Restrict Programs from Dangerous Execution Patterns |
| CCE-81056-4 |
Disable Kernel Image Loading |
True |
via sysctl |
To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.kexec_load_disabled=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kexec_load_disabled = 1 |
Disabling kexec_load allows greater control of the kernel memory. It makes it impossible to load another kernel image after it has been disabled. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Restrict Programs from Dangerous Execution Patterns |
| CCE-81053-1 |
Disallow kernel profiling by unprivileged users |
2 |
via sysctl |
To set the runtime status of the kernel.perf_event_paranoid kernel parameter, run the following command: $ sudo sysctl -w kernel.perf_event_paranoid=2 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.perf_event_paranoid = 2 |
Kernel profiling can reveal sensitive information about kernel behaviour. |
medium |
NaN |
FMT_SMF_EXT.1 |
NaN |
SRG-OS-000132-GPOS-00067 |
Restrict Programs from Dangerous Execution Patterns |
| CCE-27050-4 |
Restrict Access to Kernel Message Buffer |
True |
via sysctl |
To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.dmesg_restrict=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.dmesg_restrict = 1 |
Unprivileged access to the kernel syslog can expose sensitive kernel address information. |
medium |
SI-11(a),SI-11(b) |
NaN |
NaN |
SRG-OS-000132-GPOS-00067 |
Restrict Programs from Dangerous Execution Patterns |
| CCE-81058-0 |
Restrict usage of ptrace to descendant processes |
True |
via sysctl |
To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 |
Unrestricted usage of ptrace allows compromised binaries to run ptrace on another processes of the user. Like this, the attacker can steal sensitive information from the target processes (e.g. SSH sessions, web browser, ...) without any additional assistance from the user (i.e. without resorting to phishing). |
medium |
NaN |
NaN |
NaN |
SRG-OS-000132-GPOS-00067 |
Restrict Programs from Dangerous Execution Patterns |
| CCE-27211-2 |
Enable ExecShield via sysctl |
enable |
via grub |
By default on Red Hat Enterprise Linux 7 64-bit systems, ExecShield is enabled and can only be disabled if the hardware does not support ExecShield or is disabled in /etc/default/grub. For Red Hat Enterprise Linux 7 32-bit systems, sysctl can be used to enable ExecShield. |
ExecShield uses the segmentation feature on all x86 systems to prevent execution in memory higher than a certain address. It writes an address as a limit in the code segment descriptor, to control where code can be executed, on a per-process basis. When the kernel places a process's memory regions such as the stack and heap higher than this address, the hardware prevents execution in that address range. This is enabled by default on the latest Red Hat and Fedora systems if supported by the hardware. |
medium |
CM-6(a),SC-39 |
NaN |
1.5.2 |
SRG-OS-000433-GPOS-00192 |
Enable ExecShield |
| CCE-27127-0 |
Enable Randomized Layout of Virtual Address Space |
2 |
via sysctl |
To set the runtime status of the kernel.randomize_va_space kernel parameter, run the following command: $ sudo sysctl -w kernel.randomize_va_space=2 To 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 |
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. |
medium |
CM-6(a),SC-30,SC-30(2) |
NaN |
NaN |
SRG-OS-000433-GPOS-00193,SRG-OS-000480-GPOS-00227 |
Enable ExecShield |
| CCE-80659-6 |
Restrict Exposed Kernel Pointer Addresses Access |
True |
via sysctl |
To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kptr_restrict = 1 |
Exposing kernel pointers (through procfs or seq_printf()) exposes kernel writeable structures that can contain functions pointers. If a write vulnereability occurs in the kernel allowing a write access to any of this structure, the kernel can be compromise. This option disallow any program withtout the CAP_SYSLOG capability from getting the kernel pointers addresses, replacing them with 0. |
medium |
CM-6(a),SC-30,SC-30(2),SC-30(5) |
NaN |
NaN |
SRG-OS-000132-GPOS-00067 |
Enable ExecShield |
| CCE-27116-3 |
Install PAE Kernel on Supported 32-bit x86 Systems |
install |
via yum |
Systems that are using the 64-bit x86 kernel package do not need to install the kernel-PAE package because the 64-bit x86 kernel already includes this support. However, if the system is 32-bit and also supports the PAE and NX features as determined in the previous section, the kernel-PAE package should be installed to enable XD or NX support. The kernel-PAE package can be installed with the following command: $ sudo yum install kernel-PAE The installation process should also have configured the bootloader to load the new kernel at boot. Verify this after reboot and modify /etc/default/grub if necessary. |
On 32-bit systems that support the XD or NX bit, the vendor-supplied PAE kernel is required to enable either Execute Disable (XD) or No Execute (NX) support. |
unknown |
CM-6(a) |
NaN |
NaN |
NaN |
Enable Execute Disable (XD) or No Execute (NX) Support on x86 Systems |
| CCE-27099-1 |
Enable NX or XD Support in the BIOS |
configure |
via BIOS |
Reboot the system and enter the BIOS or Setup configuration menu. Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX) on AMD-based systems. |
Computers with the ability to prevent this type of code execution frequently put an option in the BIOS that will allow users to turn the feature on or off at will. |
unknown |
CM-6(a),SC-39 |
NaN |
NaN |
NaN |
Enable Execute Disable (XD) or No Execute (NX) Support on x86 Systems |
| CCE-26900-1 |
Disable Core Dumps for SUID programs |
0 |
via sysctl |
To set the runtime status of the fs.suid_dumpable kernel parameter, run the following command: $ sudo sysctl -w fs.suid_dumpable=0 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.suid_dumpable = 0 |
The core dump of a setuid program is more likely to contain sensitive data, as the program itself runs with greater privileges than the user who initiated execution of the program. Disabling the ability for any setuid program to write a core file decreases the risk of unauthorized access of such data. |
medium |
SI-11(a),SI-11(b) |
NaN |
NaN |
NaN |
Disable Core Dumps |
| CCE-80169-6 |
Disable Core Dumps for All Users |
0 |
via /etc/security/limits.conf |
To disable core dumps for all users, add the following line to /etc/security/limits.conf, or to a file within the /etc/security/limits.d/ directory: * hard core 0 |
A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems. |
unknown |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disable Core Dumps |
| CCE-82158-7 |
Enable page allocator poisoning |
True |
via grub |
To enable poisoning of free pages, add the argument page_poison=1 to the default GRUB 2 command line for the Linux operating system in /etc/default/grub, in the manner below: GRUB_CMDLINE_LINUX="page_poison=1" |
Poisoning writes an arbitrary value to freed pages, so any modification or reference to that page after being freed or before being initialized will be detected and prevented. This prevents many types of use-after-free vulnerabilities at little performance cost. Also prevents leak of data and detection of corrupted memory. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Memory Poisoning |
| CCE-82157-9 |
Enable SLUB/SLAB allocator poisoning |
P |
via grub |
To enable poisoning of SLUB/SLAB objects, add the argument slub_debug=P to the default GRUB 2 command line for the Linux operating system in /etc/default/grub, in the manner below: GRUB_CMDLINE_LINUX="slub_debug=P" |
Poisoning writes an arbitrary value to freed objects, so any modification or reference to that object after being freed or before being initialized will be detected and prevented. This prevents many types of use-after-free vulnerabilities at little performance cost. Also prevents leak of data and detection of corrupted memory. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000433-GPOS-00192 |
Memory Poisoning |
| CCE-27068-6 |
Set Daemon Umask |
“077” |
via /etc/init.d/functions |
The file /etc/init.d/functions includes initialization parameters for most or all daemons started at boot time. Many daemons on the system already individually restrict themselves to a umask of 077 in their own init scripts. By default, the umask of 022 is set which prevents creation of group- or world-writable files. To set the umask for daemons expected by the profile, edit the following line: umask |
The umask influences the permissions assigned to files created by a process at run time. An unnecessarily permissive umask could result in files being created with insecure permissions. |
unknown |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Daemon Umask |
| CCE-81029-1 |
Enable Kernel Parameter to Enforce DAC on Symlinks |
True |
via sysctl |
To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 |
By enabling this kernel parameter, symbolic links are permitted to be followed only when outside a sticky world-writable directory, or when the UID of the link and follower match, or when the directory owner matches the symlink's owner. Disallowing such symlinks helps mitigate vulnerabilities based on insecure file system accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of open() or creat(). |
unknown |
AC-6(1),CM-6(a) |
NaN |
1.6.1 |
SRG-OS-000324-GPOS-00125 |
Verify Permissions on Important Files and Directories |
| CCE-80135-7 |
Ensure All Files Are Owned by a Group |
verify |
via find |
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. |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.12 |
SRG-OS-000480-GPOS-00227 |
Verify Permissions on Important Files and Directories |
| CCE-80136-5 |
Ensure All World-Writable Directories Are Owned by a System Account |
verify |
via find |
All directories in local partitions which are world-writable should be owned by root or another system account. If any world-writable directories are not owned by a system account, this should be investigated. Following this, the files should be deleted or assigned to an appropriate group. |
Allowing a user account to own a world-writable directory is undesirable because it allows the owner of that directory to remove or replace any files that may be placed in the directory by other users. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Verify Permissions on Important Files and Directories |
| CCE-80130-8 |
Verify that All World-Writable Directories Have Sticky Bits Set |
+t |
via chmod |
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 |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Verify Permissions on Important Files and Directories |
| CCE-80132-4 |
Ensure All SGID Executables Are Authorized |
verify |
via rpm |
The SGID (set group id) bit should be set only on files that were installed via authorized means. A straightforward means of identifying unauthorized SGID files is determine if any were not installed as part of an RPM package, which is cryptographically verified. Investigate the origin of any unpackaged SGID files. This configuration check considers authorized SGID files which were installed via RPM. It is assumed that when an individual has sudo access to install an RPM and all packages are signed with an organizationally-recognized GPG key, the software should be considered an approved package on the system. Any SGID file not deployed through an RPM will be flagged for further review. |
Executable files with the SGID permission run with the privileges of the owner of the file. SGID files of uncertain provenance could allow for unprivileged users to elevate privileges. The presence of these files should be strictly controlled on the system. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.14 |
NaN |
Verify Permissions on Important Files and Directories |
| CCE-81026-7 |
Enable Kernel Parameter to Enforce DAC on Hardlinks |
True |
via sysctl |
To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1 To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 |
By enabling this kernel parameter, users can no longer create soft or hard links to files which they do not own. Disallowing such hardlinks mitigate vulnerabilities based on insecure file system accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of open() or creat(). |
unknown |
AC-6(1),CM-6(a) |
NaN |
1.6.1 |
SRG-OS-000324-GPOS-00125 |
Verify Permissions on Important Files and Directories |
| CCE-80133-2 |
Ensure All SUID Executables Are Authorized |
verify |
via rpm |
The SUID (set user id) bit should be set only on files that were installed via authorized means. A straightforward means of identifying unauthorized SUID files is determine if any were not installed as part of an RPM package, which is cryptographically verified. Investigate the origin of any unpackaged SUID files. This configuration check considers authorized SUID files which were installed via RPM. It is assumed that when an individual has sudo access to install an RPM and all packages are signed with an organizationally-recognized GPG key, the software should be considered an approved package on the system. Any SUID file not deployed through an RPM will be flagged for further review. |
Executable files with the SUID permission run with the privileges of the owner of the file. SUID files of uncertain provenance could allow for unprivileged users to elevate privileges. The presence of these files should be strictly controlled on the system. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.13 |
NaN |
Verify Permissions on Important Files and Directories |
| CCE-80131-6 |
Ensure No World-Writable Files Exist |
o-w |
via chmod |
It is generally a good idea to remove global (other) write access to a file when it is discovered. However, check with documentation for specific applications before making changes. Also, monitor for recurring world-writable files, as these may be symptoms of a misconfigured application or user account. Finally, this applies to real files and not virtual files that are a part of pseudo file systems such as sysfs or procfs. |
Data in world-writable files can be modified by any user on the system. In almost all circumstances, files can be configured using a combination of user and group permissions to support whatever legitimate access is needed without the risk caused by world-writable files. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.10 |
NaN |
Verify Permissions on Important Files and Directories |
| CCE-80134-0 |
Ensure All Files Are Owned by a User |
verify |
via find |
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. |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.11 |
SRG-OS-000480-GPOS-00227 |
Verify Permissions on Important Files and Directories |
| CCE-82350-0 |
Verify that local System.map file (if exists) is readable only by root |
600 |
via chmod |
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 /boot/System.map-*, run the command: $ sudo chmod 0600 /boot/System.map-* |
The System.map file contains information about kernel symbols and can give some hints to generate local exploitation. |
unknown |
NaN |
NaN |
NaN |
NaN |
Verify Permissions on Important Files and Directories |
| CCE-82031-6 |
Verify User Who Owns group File |
root |
via chown |
To properly set the owner of /etc/group, run the command: $ sudo chown root /etc/group |
The /etc/group file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.4 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82052-2 |
Verify User Who Owns passwd File |
root |
via chown |
To properly set the owner of /etc/passwd, run the command: $ sudo chown root /etc/passwd |
The /etc/passwd file contains information about the users that are configured on the system. Protection of this file is critical for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.2 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83534-8 |
Verify Group Who Owns Backup gshadow File |
root |
via chgrp |
To properly set the group owner of /etc/gshadow-, run the command: $ sudo chgrp root /etc/gshadow- |
The /etc/gshadow- file is a backup of /etc/gshadow, and as such, it contains group password hashes. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.9 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83414-3 |
Verify User Who Owns Backup shadow File |
root |
via chgrp |
To properly set the group owner of /etc/shadow-, run the command: $ sudo chgrp root /etc/shadow- |
The /etc/shadow- file is a backup file of /etc/shadow, and as such, it contains the list of local system accounts and password hashes. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.7 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82032-4 |
Verify Permissions on group File |
644 |
via chmod |
To properly set the permissions of /etc/passwd, run the command: $ sudo chmod 0644 /etc/passwd |
The /etc/group file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.4 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83416-8 |
Verify Permissions on Backup shadow File |
“0000” |
via chmod |
To properly set the permissions of /etc/shadow-, run the command: $ sudo chmod 0000 /etc/shadow- |
The /etc/shadow- file is a backup file of /etc/shadow, and as such, it contains the list of local system accounts and password hashes. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.7 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82195-9 |
Verify User Who Owns gshadow File |
root |
via chown |
To properly set the owner of /etc/gshadow, run the command: $ sudo chown root /etc/gshadow |
The /etc/gshadow file contains group password hashes. Protection of this file is critical for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.5 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82192-6 |
Verify Permissions on gshadow File |
“0000” |
via chmod |
To properly set the permissions of /etc/gshadow, run the command: $ sudo chmod 0000 /etc/gshadow |
The /etc/gshadow file contains group password hashes. Protection of this file is critical for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.5 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83474-7 |
Verify Group Who Owns Backup group File |
root |
via chgrp |
To properly set the group owner of /etc/group-, run the command: $ sudo chgrp root /etc/group- |
The /etc/group- file is a backup file of /etc/group, and as such, it contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
medium |
NaN |
NaN |
6.1.8 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82037-3 |
Verify Group Who Owns group File |
root |
via chgrp |
To properly set the group owner of /etc/group, run the command: $ sudo chgrp root /etc/group |
The /etc/group file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.4 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82042-3 |
Verify Permissions on shadow File |
“0000” |
via chmod |
To properly set the permissions of /etc/shadow, run the command: $ sudo chmod 0000 /etc/shadow |
The /etc/shadow file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security. Failure to give ownership of this file to root provides the designated owner with access to sensitive information which could weaken the system security posture. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.3 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83323-6 |
Verify Group Who Owns Backup passwd File |
root |
via chgrp |
To properly set the group owner of /etc/passwd-, run the command: $ sudo chgrp root /etc/passwd- |
The /etc/passwd- file is a backup file of /etc/passwd, and as such, it contains information about the users that are configured on the system. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.6 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83472-1 |
Verify User Who Owns Backup group File |
root |
via chown |
To properly set the owner of /etc/group-, run the command: $ sudo chown root /etc/group- |
The /etc/group- file is a backup file of /etc/group, and as such, it contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
medium |
NaN |
NaN |
6.1.8 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-26639-5 |
Verify Group Who Owns passwd File |
root |
via chgrp |
To properly set the group owner of /etc/passwd, run the command: $ sudo chgrp root /etc/passwd |
The /etc/passwd file contains information about the users that are configured on the system. Protection of this file is critical for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.2 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82025-8 |
Verify Group Who Owns gshadow File |
root |
via chgrp |
To properly set the group owner of /etc/gshadow, run the command: $ sudo chgrp root /etc/gshadow |
The /etc/gshadow file contains group password hashes. Protection of this file is critical for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.5 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83325-1 |
Verify User Who Owns Backup passwd File |
root |
via chown |
To properly set the owner of /etc/passwd-, run the command: $ sudo chown root /etc/passwd- |
The /etc/passwd- file is a backup file of /etc/passwd, and as such, it contains information about the users that are configured on the system. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.6 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82022-5 |
Verify User Who Owns shadow File |
root |
via chown |
To properly set the owner of /etc/shadow, run the command: $ sudo chown root /etc/shadow |
The /etc/shadow file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security. Failure to give ownership of this file to root provides the designated owner with access to sensitive information which could weaken the system security posture. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.3 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82051-4 |
Verify Group Who Owns shadow File |
root |
via chgrp |
To properly set the group owner of /etc/shadow, run the command: $ sudo chgrp root /etc/shadow |
The /etc/shadow file stores password hashes. Protection of this file is critical for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.3 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83331-9 |
Verify Permissions on Backup passwd File |
644 |
via chmod |
To properly set the permissions of /etc/passwd-, run the command: $ sudo chmod 0644 /etc/passwd- |
The /etc/passwd- file is a backup file of /etc/passwd, and as such, it contains information about the users that are configured on the system. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.6 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83532-2 |
Verify User Who Owns Backup gshadow File |
root |
via chown |
To properly set the owner of /etc/gshadow-, run the command: $ sudo chown root /etc/gshadow- |
The /etc/gshadow- file is a backup of /etc/gshadow, and as such, it contains group password hashes. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.9 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83482-0 |
Verify Permissions on Backup group File |
644 |
via chmod |
To properly set the permissions of /etc/group-, run the command: $ sudo chmod 0644 /etc/group- |
The /etc/group- file is a backup file of /etc/group, and as such, it contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
medium |
NaN |
NaN |
6.1.8 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82029-0 |
Verify Permissions on passwd File |
645 |
via chmod |
To properly set the permissions of /etc/passwd, run the command: $ sudo chmod 0644 /etc/passwd |
If the /etc/passwd file is writable by a group-owner or the world the risk of its compromise is increased. The file contains the list of accounts on the system and associated information, and protection of this file is critical for system security. |
medium |
AC-6(1),CM-6(a) |
NaN |
6.1.2 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83412-7 |
Verify Group Who Owns Backup shadow File |
root |
via chown |
To properly set the owner of /etc/shadow-, run the command: $ sudo chown root /etc/shadow- |
The /etc/shadow- file is a backup file of /etc/shadow, and as such, it contains the list of local system accounts and password hashes. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.7 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-83572-8 |
Verify Permissions on Backup gshadow File |
“0000” |
via chmod |
To properly set the permissions of /etc/gshadow-, run the command: $ sudo chmod 0000 /etc/gshadow- |
The /etc/gshadow- file is a backup of /etc/gshadow, and as such, it contains group password hashes. Protection of this file is critical for system security. |
medium |
NaN |
NaN |
6.1.9 |
NaN |
Verify Permissions on Files with Local Account Information and Credentials |
| CCE-82040-7 |
Verify that System Executables Have Restrictive Permissions |
go-w |
via chmod |
System executables are stored in the following directories by default: /bin /sbin /usr/bin /usr/libexec /usr/local/bin /usr/local/sbin /usr/sbin All 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 |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Verify File Permissions Within Some Important Directories |
| CCE-82021-7 |
Verify that Shared Library Files Have Root Ownership |
root |
via chown |
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/lib64 Kernel 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 |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Verify File Permissions Within Some Important Directories |
| CCE-82048-0 |
Verify that System Executables Have Root Ownership |
root |
via chown |
System executables are stored in the following directories by default: /bin /sbin /usr/bin /usr/libexec /usr/local/bin /usr/local/sbin /usr/sbin All 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 |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Verify File Permissions Within Some Important Directories |
| CCE-82033-2 |
Verify that Shared Library Files Have Restrictive Permissions |
go-w |
via chmod |
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/lib64 Kernel 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 |
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. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Verify File Permissions Within Some Important Directories |
| CCE-82144-7 |
Add nosuid Option to /var/log |
nosuid |
via /etc/fstab |
The nosuid mount option can be used to prevent execution of setuid programs in /var/log. The SUID and SGID permissions should not be required in directories containing log files. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /var/log. |
The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from partitions designated for log files. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80150-6 |
Add noexec Option to /tmp |
noexec |
via /etc/fstab |
The noexec mount option can be used to prevent binaries from being executed out of /tmp. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of /tmp. |
Allowing users to execute binaries from world-writable directories such as /tmp should never be necessary in normal operation and can expose the system to potential compromise. |
unknown |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80152-2 |
Add nodev Option to /dev/shm |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent creation of device files in /dev/shm. Legitimate character and block devices should not exist within temporary directories like /dev/shm. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /dev/shm. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80145-6 |
Add nodev Option to Non-Root Local Partitions |
nodev |
via /etc/fstab |
The nodev mount option prevents files from being interpreted as character or block devices. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of any non-root local partitions. |
The nodev mount option prevents files from being interpreted as character or block devices. The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails, for which it is not advised to set nodev on these filesystems. |
unknown |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
1.1.11 |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-82064-7 |
Add nodev Option to /var |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent device files from being created in /var. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /var. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80155-5 |
Bind Mount /var/tmp To /tmp |
bind |
via /etc/fstab |
The /var/tmp directory is a world-writable directory. Bind-mount it to /tmp in order to consolidate temporary storage into one location protected by the same techniques as /tmp. To do so, edit /etc/fstab and add the following line: /tmp /var/tmp none rw,nodev,noexec,nosuid,bind 0 0 See the mount(8) man page for further explanation of bind mounting. |
Having multiple locations for temporary storage is not required. Unless absolutely necessary to meet requirements, the storage location /var/tmp should be bind mounted to /tmp and thus share the same protections. |
unknown |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
1.1.6 |
NaN |
Restrict Partition Mount Options |
| CCE-80151-4 |
Add nosuid Option to /tmp |
nosuid |
via /etc/fstab |
The nosuid mount option can be used to prevent execution of setuid programs in /tmp. The SUID and SGID permissions should not be required in these world-writable directories. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /tmp. |
The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from temporary storage partitions. |
unknown |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-82153-8 |
Add nosuid Option to /var/tmp |
nosuid |
via /etc/fstab |
The nosuid mount option can be used to prevent execution of setuid programs in /var/tmp. The SUID and SGID permissions should not be required in these world-writable directories. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /var/tmp. |
The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from temporary storage partitions. |
unknown |
NaN |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-82146-2 |
Add noexec Option to /var/log/audit |
noexec |
via /etc/fstab |
The noexec mount option can be used to prevent binaries from being executed out of /var/log/audit. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of /var/log/audit. |
Allowing users to execute binaries from directories containing audit log files such as /var/log/audit should never be necessary in normal operation and can expose the system to potential compromise. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80147-2 |
Add noexec Option to Removable Media Partitions |
noexec |
via /etc/fstab |
The noexec mount option prevents the direct execution of binaries on the mounted filesystem. Preventing the direct execution of binaries from removable media (such as a USB key) provides a defense against malicious software that may be present on such untrusted media. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of any removable media partitions. |
Allowing users to execute binaries from removable media such as USB keys exposes the system to potential compromise. |
unknown |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
NaN |
Restrict Partition Mount Options |
| CCE-82150-4 |
Add noexec Option to /var/tmp |
noexec |
via /etc/fstab |
The noexec mount option can be used to prevent binaries from being executed out of /var/tmp. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of /var/tmp. |
Allowing users to execute binaries from world-writable directories such as /var/tmp should never be necessary in normal operation and can expose the system to potential compromise. |
unknown |
NaN |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80154-8 |
Add nosuid Option to /dev/shm |
nosuid |
via /etc/fstab |
The nosuid mount option can be used to prevent execution of setuid programs in /dev/shm. The SUID and SGID permissions should not be required in these world-writable directories. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /dev/shm. |
The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from temporary storage partitions. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80149-8 |
Add nodev Option to /tmp |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent device files from being created in /tmp. Legitimate character and block devices should not exist within temporary directories like /tmp. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /tmp. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
unknown |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80153-0 |
Add noexec Option to /dev/shm |
noexec |
via /etc/fstab |
The noexec mount option can be used to prevent binaries from being executed out of /dev/shm. It can be dangerous to allow the execution of binaries from world-writable temporary storage directories such as /dev/shm. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of /dev/shm. |
Allowing users to execute binaries from world-writable directories such as /dev/shm can expose the system to potential compromise. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-82076-1 |
Add nodev Option to /var/log |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent device files from being created in /var/log. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /var/log. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-82142-1 |
Add noexec Option to /var/log |
noexec |
via /etc/fstab |
The noexec mount option can be used to prevent binaries from being executed out of /var/log. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of /var/log. |
Allowing users to execute binaries from directories containing log files such as /var/log should never be necessary in normal operation and can expose the system to potential compromise. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-81047-3 |
Add nodev Option to /home |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent device files from being created in /home. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /home. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
unknown |
NaN |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80146-4 |
Add nodev Option to Removable Media Partitions |
nodev |
via /etc/fstab |
The nodev mount option prevents files from being interpreted as character or block devices. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of any removable media partitions. |
The only legitimate location for device files is the /dev directory located on the root partition. An exception to this is chroot jails, and it is not advised to set nodev on partitions which contain their root filesystems. |
low |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
NaN |
Restrict Partition Mount Options |
| CCE-82135-5 |
Add nodev Option to /boot |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent device files from being created in /boot. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /boot. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-81052-3 |
Add nodev Option to /var/tmp |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent device files from being created in /var/tmp. Legitimate character and block devices should not exist within temporary directories like /var/tmp. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /var/tmp. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
unknown |
NaN |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-80148-0 |
Add nosuid Option to Removable Media Partitions |
nosuid |
via yum |
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. |
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. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Restrict Partition Mount Options |
| CCE-82079-5 |
Add nodev Option to /var/log/audit |
nodev |
via /etc/fstab |
The nodev mount option can be used to prevent device files from being created in /var/log/audit. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /var/log/audit. |
The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-82138-9 |
Add nosuid Option to /boot |
nosuid |
via /etc/fstab |
The nosuid mount option can be used to prevent execution of setuid programs in /boot. The SUID and SGID permissions should not be required on the boot partition. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /boot. |
The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from boot partitions. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-81153-9 |
Add nosuid Option to /home |
nosuid |
via /etc/fstab |
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. |
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. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
1.1.3 |
SRG-OS-000368-GPOS-00154,SRG-OS-000480-GPOS-00227 |
Restrict Partition Mount Options |
| CCE-82148-8 |
Add nosuid Option to /var/log/audit |
nosuid |
via /etc/fstab |
The nosuid mount option can be used to prevent execution of setuid programs in /var/log/audit. The SUID and SGID permissions should not be required in directories containing audit log files. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /var/log/audit. |
The presence of SUID and SGID executables should be tightly controlled. Users should not be able to execute SUID or SGID binaries from partitions designated for audit log files. |
medium |
AC-6,AC-6(1),CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000368-GPOS-00154 |
Restrict Partition Mount Options |
| CCE-27498-5 |
Disable the Automounter |
disable |
via systemctl |
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 disable autofs.service The autofs service can be masked with the following command: $ sudo systemctl mask autofs.service |
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. |
medium |
CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000114-GPOS-00059,SRG-OS-000378-GPOS-00163,SRG-OS-000480-GPOS-00227 |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80143-1 |
Disable Mounting of udf |
disable |
via modprobe.d |
To configure the system to prevent the udf kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install udf /bin/true This effectively prevents usage of this uncommon filesystem. The udf filesystem type is the universal disk format used to implement the ISO/IEC 13346 and ECMA-167 specifications. This is an open vendor filesystem type for data storage on a broad range of media. This filesystem type is neccessary to support writing DVDs and newer optical disc formats. |
Removing support for unneeded filesystem types reduces the local attack surface of the system. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80138-1 |
Disable Mounting of freevxfs |
disable |
via modprobe.d |
To configure the system to prevent the freevxfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install freevxfs /bin/true This effectively prevents usage of this uncommon filesystem. |
Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
1.1.1.2 |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-26960-5 |
Disable Booting from USB Devices in Boot Firmware |
disable |
via BIOS |
Configure the system boot firmware (historically called BIOS on PC systems) to disallow booting from USB drives. |
Booting a system from a USB device would allow an attacker to circumvent any security measures provided by the operating system. Attackers could mount partitions and modify the configuration of the OS. |
unknown |
CM-6(a),CM-7(b),MP-7 |
NaN |
NaN |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-27277-3 |
Disable Modprobe Loading of USB Storage Driver |
disable |
via modprobe.d |
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 a file in the directory /etc/modprobe.d: install usb-storage /bin/true This 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. |
USB storage devices such as thumb drives can be used to introduce malicious software. |
medium |
CM-6(a),CM-7(a),CM-7(b),MP-7 |
NaN |
NaN |
SRG-OS-000114-GPOS-00059,SRG-OS-000378-GPOS-00163,SRG-OS-000480-GPOS-00227 |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-27194-0 |
Assign Password to Prevent Changes to Boot Firmware Configuration |
configure |
via BIOS |
Assign a password to the system boot firmware (historically called BIOS on PC systems) to require a password for any configuration changes. |
Assigning a password to the system boot firmware prevents anyone with physical access from configuring the system to boot from local media and circumvent the operating system's access controls. For systems in physically secure locations, such as a data center or Sensitive Compartmented Information Facility (SCIF), this risk must be weighed against the risk of administrative personnel being unable to conduct recovery operations in a timely fashion. |
unknown |
NaN |
NaN |
NaN |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80141-5 |
Disable Mounting of hfsplus |
disable |
via modprobe.d |
To configure the system to prevent the hfsplus kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install hfsplus /bin/true This effectively prevents usage of this uncommon filesystem. |
Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
1.1.1.5 |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80137-3 |
Disable Mounting of cramfs |
disable |
via modprobe.d |
To configure the system to prevent the cramfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install cramfs /bin/true This effectively prevents usage of this uncommon filesystem. The cramfs filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A cramfs image can be used without having to first decompress the image. |
Removing support for unneeded filesystem types reduces the local attack surface of the server. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80139-9 |
Disable Mounting of jffs2 |
disable |
via modprobe.d |
To configure the system to prevent the jffs2 kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install jffs2 /bin/true This effectively prevents usage of this uncommon filesystem. |
Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
1.1.1.3 |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-26548-8 |
Disable Kernel Support for USB via Bootloader Configuration |
nousb |
via grub |
All USB support can be disabled by adding the nousb argument to the kernel's boot loader configuration. To do so, append "nousb" to the kernel line in /etc/default/grub as shown: kernel /vmlinuz-VERSION ro vga=ext root=/dev/VolGroup00/LogVol00 rhgb quiet nousb |
Disabling the USB subsystem within the Linux kernel at system boot will protect against potentially malicious USB devices, although it is only practical in specialized systems. |
unknown |
CM-6(a),MP-7 |
NaN |
NaN |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80140-7 |
Disable Mounting of hfs |
disable |
via modprobe.d |
To configure the system to prevent the hfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install hfs /bin/true This effectively prevents usage of this uncommon filesystem. |
Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
1.1.1.4 |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-82169-4 |
Disable Mounting of vFAT filesystems |
disable |
via modprobe.d |
To configure the system to prevent the vfat kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install vfat /bin/true This effectively prevents usage of this uncommon filesystem. The vFAT filesystem format is primarily used on older windows systems and portable USB drives or flash modules. It comes in three types FAT12, FAT16, and FAT32 all of which are supported by the vfat kernel module. |
Removing support for unneeded filesystems reduces the local attack surface of the system. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80142-3 |
Disable Mounting of squashfs |
disable |
via modprobe.d |
To configure the system to prevent the squashfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d: install squashfs /bin/true This effectively prevents usage of this uncommon filesystem. The squashfs filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems (similar to cramfs). A squashfs image can be used without having to first decompress the image. |
Removing support for unneeded filesystem types reduces the local attack surface of the system. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict Dynamic Mounting and Unmounting of Filesystems |
| CCE-80187-8 |
Ensure rsyslog is Installed |
install |
via yum |
Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo yum install rsyslog |
The rsyslog package provides the rsyslog daemon, which provides system logging services. |
medium |
CM-6(a) |
NaN |
NaN |
SRG-OS-000051-GPOS-00024,SRG-OS-000479-GPOS-00224 |
Configure Syslog |
| CCE-80188-6 |
Enable rsyslog Service |
enable |
via systemctl |
The rsyslog service provides syslog-style logging by default on Red Hat Enterprise Linux 7. The rsyslog service can be enabled with the following command: $ sudo systemctl enable rsyslog.service |
The rsyslog service must be running in order to provide logging services, which are essential to system administration. |
medium |
AU-4(1),CM-6(a) |
NaN |
NaN |
NaN |
Configure Syslog |
| CCE-80198-5 |
Disable Logwatch on Clients if a Logserver Exists |
disable |
via rm |
Does your site have a central logserver which has been configured to report on logs received from all systems? If so: $ sudo rm /etc/cron.daily/0logwatch If no logserver exists, it will be necessary for each system to run Logwatch individually. Using a central logserver provides the security and reliability benefits discussed earlier, and also makes monitoring logs easier and less time-intensive for administrators. |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure Syslog |
| CCE-80380-9 |
Ensure cron Is Logging To Rsyslog |
cron.* |
/etc/rsyslog.conf |
Cron logging must be implemented to spot intrusions or trace cron job status. If cron is not logging to rsyslog, it can be implemented by adding the following to the RULES section of /etc/rsyslog.conf: cron.* /var/log/cron |
Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users. |
medium |
CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000480-GPOS-00227 |
Ensure Proper Configuration of Log Files |
| CCE-80191-0 |
Ensure System Log Files Have Correct Permissions |
600 |
via chmod |
The file permissions for all log files written by rsyslog should be set to 600, or more restrictive. These log files are determined by the second part of each Rule line in /etc/rsyslog.conf and typically all appear in /var/log. For each log file LOGFILE referenced in /etc/rsyslog.conf, run the following command to inspect the file's permissions: $ ls -l LOGFILE If the permissions are not 600 or more restrictive, run the following command to correct this: $ sudo chmod 0600 LOGFILE" |
Log files can contain valuable information regarding system configuration. If the system log files are not protected unauthorized users could change the logged data, eliminating their forensic value. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Ensure Proper Configuration of Log Files |
| CCE-80189-4 |
Ensure Log Files Are Owned By Appropriate User |
root |
via chown |
The owner of all log files written by rsyslog should be . These log files are determined by the second part of each Rule line in /etc/rsyslog.conf and typically all appear in /var/log. For each log file LOGFILE referenced in /etc/rsyslog.conf, run the following command to inspect the file's owner: $ ls -l LOGFILE If the owner is not , run the following command to correct this: $ sudo chown LOGFILE |
The log files generated by rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Log files should be protected from unauthorized access. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Ensure Proper Configuration of Log Files |
| CCE-80190-2 |
Ensure Log Files Are Owned By Appropriate Group |
root |
via chgrp |
The group-owner of all log files written by rsyslog should be . These log files are determined by the second part of each Rule line in /etc/rsyslog.conf and typically all appear in /var/log. For each log file LOGFILE referenced in /etc/rsyslog.conf, run the following command to inspect the file's group owner: $ ls -l LOGFILE If the owner is not , run the following command to correct this: $ sudo chgrp LOGFILE |
The log files generated by rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Log files should be protected from unauthorized access. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
NaN |
Ensure Proper Configuration of Log Files |
| CCE-80195-1 |
Ensure Logrotate Runs Periodically |
daily |
via /etc/logrotate.conf |
The logrotate utility allows for the automatic rotation of log files. The frequency of rotation is specified in /etc/logrotate.conf, which triggers a cron task. To configure logrotate to run daily, add or correct the following line in /etc/logrotate.conf: # rotate log files frequency daily |
Log files that are not properly rotated run the risk of growing so large that they fill up the /var/log partition. Valuable logging information could be lost if the /var/log partition becomes full. |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
Ensure All Logs are Rotated by logrotate |
| CCE-80197-7 |
Configure Logwatch SplitHosts Line |
yes |
via /etc/rsyslog.conf |
If SplitHosts is set, Logwatch will separate entries by hostname. This makes the report longer but significantly more usable. If it is not set, then Logwatch will not report which host generated a given log entry, and that information is almost always necessary SplitHosts = yes |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure Logwatch on the Central Log Server |
| CCE-80196-9 |
Configure Logwatch HostLimit Line |
no |
via /etc/rsyslog.conf |
On a central logserver, you want Logwatch to summarize all syslog entries, including those which did not originate on the logserver itself. The HostLimit setting tells Logwatch to report on all hosts, not just the one on which it is running. HostLimit = no |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure Logwatch on the Central Log Server |
| CCE-27343-3 |
Ensure Logs Sent To Remote Host |
enable |
via /etc/rsyslog.conf |
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. |
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. |
medium |
AU-4(1),AU-9(2),CM-6(a) |
FAU_GEN.1.1.c |
NaN |
SRG-OS-000480-GPOS-00227 |
Rsyslog Logs Sent To Remote Host |
| CCE-80193-6 |
Enable rsyslog to Accept Messages via TCP, if Acting As Log Server |
enable |
via /etc/rsyslog.conf |
The rsyslog daemon should not accept remote messages unless the system acts as a log server. If the system needs to act as a central log server, add the following lines to /etc/rsyslog.conf to enable reception of messages over TCP: $ModLoad imtcp $InputTCPServerRun 514 |
If the system needs to act as a log server, this ensures that it can receive messages over a reliable TCP connection. |
unknown |
AU-6(3),AU-6(4),CM-6(a) |
NaN |
4.2.1.5 |
NaN |
Configure rsyslogd to Accept Remote Messages If Acting as a Log Server |
| CCE-80194-4 |
Enable rsyslog to Accept Messages via UDP, if Acting As Log Server |
enable |
via /etc/rsyslog.conf |
The rsyslog daemon should not accept remote messages unless the system acts as a log server. If the system needs to act as a central log server, add the following lines to /etc/rsyslog.conf to enable reception of messages over UDP: $ModLoad imudp $UDPServerRun 514 |
Many devices, such as switches, routers, and other Unix-like systems, may only support the traditional syslog transmission over UDP. If the system must act as a log server, this enables it to receive their messages as well. |
unknown |
AU-6(3),AU-6(4),CM-6(a) |
NaN |
4.2.1.5 |
NaN |
Configure rsyslogd to Accept Remote Messages If Acting as a Log Server |
| CCE-80192-8 |
Ensure rsyslog Does Not Accept Remote Messages Unless Acting As Log Server |
disable |
via /etc/rsyslog.conf |
The rsyslog daemon should not accept remote messages unless the system acts as a log server. To ensure that it is not listening on the network, ensure the following lines are not found in /etc/rsyslog.conf: $ModLoad imtcp $InputTCPServerRun port $ModLoad imudp $UDPServerRun port $ModLoad imrelp $InputRELPServerRun port |
Any process which receives messages from the network incurs some risk of receiving malicious messages. This risk can be eliminated for rsyslog by configuring it not to listen on the network. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure rsyslogd to Accept Remote Messages If Acting as a Log Server |
| CCE-80338-7 |
Disable Avahi Server Software |
disable |
via systemctl |
The avahi-daemon service can be disabled with the following command: $ sudo systemctl disable avahi-daemon.service The avahi-daemon service can be masked with the following command: $ sudo systemctl mask avahi-daemon.service |
Because the Avahi daemon service keeps an open network port, it is subject to network attacks. Its functionality is convenient but is only appropriate if the local network can be trusted. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable Avahi Server if Possible |
| CCE-80341-1 |
Prevent Other Programs from Using Avahi's Port |
yes |
via /etc/avahi/avahi-daemon.conf |
To prevent other mDNS stacks from running, edit /etc/avahi/avahi-daemon.conf and ensure the following line appears in the [server] section: disallow-other-stacks=yes |
This helps ensure that only Avahi is responsible for mDNS traffic coming from that port on the system. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure Avahi if Necessary |
| CCE-82369-0 |
Disable Avahi Publishing |
yes |
via /etc/avahi/avahi-daemon.conf |
To prevent Avahi from publishing its records, edit /etc/avahi/avahi-daemon.conf and ensure the following line appears in the [publish] section: disable-publishing=yes |
This helps ensure that no record will be published by Avahi. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure Avahi if Necessary |
| CCE-80339-5 |
Serve Avahi Only via Required Protocol |
no |
via /etc/avahi/avahi-daemon.conf |
If you are using only IPv4, edit /etc/avahi/avahi-daemon.conf and ensure the following line exists in the [server] section: use-ipv6=no Similarly, if you are using only IPv6, disable IPv4 sockets with the line: use-ipv4=no |
NaN |
low |
CM-6(a) |
NaN |
NaN |
NaN |
Configure Avahi if Necessary |
| CCE-80340-3 |
Check Avahi Responses' TTL Field |
yes |
via /etc/avahi/avahi-daemon.conf |
To make Avahi ignore packets unless the TTL field is 255, edit /etc/avahi/avahi-daemon.conf and ensure the following line appears in the [server] section: check-response-ttl=yes |
This helps to ensure that only mDNS responses from the local network are processed, because the TTL field in a packet is decremented from its initial value of 255 whenever it is routed from one network to another. Although a properly-configured router or firewall should not allow mDNS packets into the local network at all, this option provides another check to ensure they are not permitted. |
low |
CM-6(a) |
NaN |
NaN |
NaN |
Configure Avahi if Necessary |
| CCE-80343-7 |
Restrict Information Published by Avahi |
configure |
via /etc/avahi/avahi-daemon.conf |
If it is necessary to publish some information to the network, it should not be joined by any extraneous information, or by information supplied by a non-trusted source on the system. Prevent user applications from using Avahi to publish services by adding or correcting the following line in the [publish] section: disable-user-service-publishing=yes Implement as many of the following lines as possible, to restrict the information published by Avahi. publish-addresses=no publish-hinfo=no publish-workstation=no publish-domain=no Inspect the files in the directory /etc/avahi/services/. Unless there is an operational need to publish information about each of these services, delete the corresponding file. |
These options prevent publishing attempts from succeeding, and can be applied even if publishing is disabled entirely via disable-publishing. Alternatively, these can be used to restrict the types of published information in the event that some information must be published. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure Avahi if Necessary |
| CCE-80286-8 |
Uninstall squid Package |
remove |
via yum |
The squid package can be removed with the following command: $ sudo yum erase squid |
If there is no need to make the proxy server software available, removing it provides a safeguard against its activation. |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Squid if Possible |
| CCE-80285-0 |
Disable Squid |
disable |
via systemctl |
The squid service can be disabled with the following command: $ sudo systemctl disable squid.service The squid service can be masked with the following command: $ sudo systemctl mask squid.service |
Running proxy server software provides a network-based avenue of attack, and should be removed if not needed. |
unknown |
NaN |
NaN |
2.2.13 |
NaN |
Disable Squid if Possible |
| CCE-80360-1 |
Install the Samba Common Package |
install |
via yum |
The samba-common package should be installed. The samba-common package can be installed with the following command: $ sudo yum install samba-common |
If the samba-common package is not installed, samba cannot be configured. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure Samba if Necessary |
| CCE-80279-3 |
Disable Root Access to SMB Shares |
disable |
via /etc/samba/smb.conf |
Administrators should not use administrator accounts to access Samba file and printer shares. Disable the root user and the wheel administrator group: [share] invalid users = root @wheel If administrator accounts cannot be disabled, ensure that local system passwords and Samba service passwords do not match. |
Typically, administrator access is required when Samba must create user and system accounts and shares. Domain member servers and standalone servers may not need administrator access at all. If that is the case, add the invalid users parameter to [global] instead. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure Samba if Necessary |
| CCE-80280-1 |
Require Client SMB Packet Signing, if using smbclient |
client signing = mandatory |
via /etc/samba/smb.conf |
To require samba clients running smbclient to use packet signing, add the following to the [global] section of the Samba configuration file, /etc/samba/smb.conf: client signing = mandatory Requiring samba clients such as smbclient to use packet signing ensures they can only communicate with servers that support packet signing. |
Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure Samba if Necessary |
| CCE-80281-9 |
Require Client SMB Packet Signing, if using mount.cifs |
sec=krb5i or sec=ntlmv2i |
via /etc/fstab |
Require packet signing of clients who mount Samba shares using the mount.cifs program (e.g., those who specify shares in /etc/fstab). To do so, ensure signing options (either sec=krb5i or sec=ntlmv2i) are used. See the mount.cifs(8) man page for more information. A Samba client should only communicate with servers who can support SMB packet signing. |
Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure Samba if Necessary |
| CCE-80278-5 |
Uninstall Samba Package |
remove |
via yum |
The samba package can be removed with the following command: $ sudo yum erase samba |
If there is no need to make the Samba software available, removing it provides a safeguard against its activation. |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Samba if Possible |
| CCE-80277-7 |
Disable Samba |
disable |
via systemctl |
The smb service can be disabled with the following command: $ sudo systemctl disable smb.service The smb service can be masked with the following command: $ sudo systemctl mask smb.service |
Running a Samba server provides a network-based avenue of attack, and should be disabled if not needed. |
low |
NaN |
NaN |
NaN |
NaN |
Disable Samba if Possible |
| CCE-83334-3 |
Ensure rsyncd service is diabled |
disable |
via systemctl |
The rsyncd service can be disabled with the following command: $ sudo systemctl disable rsyncd.service The rsyncd service can be masked with the following command: $ sudo systemctl mask rsyncd.service |
The rsyncd service presents a security risk as it uses unencrypted protocols for communication. |
medium |
NaN |
NaN |
2.2.21 |
NaN |
Obsolete Services |
| CCE-27274-0 |
Uninstall rsh Package |
remove |
via yum |
The rsh package contains the client commands for the rsh services |
These legacy clients contain numerous security exposures and have been replaced with the more secure SSH package. Even if the server is removed, it is best to ensure the clients are also removed to prevent users from inadvertently attempting to use these commands and therefore exposing their credentials. Note that removing the rsh package removes the clients for rsh,rcp, and rlogin. |
unknown |
NaN |
NaN |
2.3.2 |
NaN |
Rlogin, Rsh, and Rexec |
| CCE-27342-5 |
Uninstall rsh-server Package |
remove |
via yum |
The rsh-server package can be removed with the following command: $ sudo yum erase rsh-server |
The rsh-server service provides unencrypted remote access service which does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication. If a privileged user were to login using this service, the privileged user password could be compromised. The rsh-server package provides several obsolete and insecure network services. Removing it decreases the risk of those services' accidental (or intentional) activation. |
high |
CM-6(a),CM-7(a),CM-7(b),IA-5(1)(c) |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
Rlogin, Rsh, and Rexec |
| CCE-27336-7 |
Disable rlogin Service |
disable |
via systemctl |
The rlogin service, which is available with the rsh-server package and runs as a service through xinetd or separately as a systemd socket, should be disabled. If using xinetd, set disable to yes in /etc/xinetd.d/rlogin. The rlogin socket can be disabled with the following command: $ sudo systemctl disable rlogin.socket The rlogin socket can be masked with the following command: $ sudo systemctl mask .socket |
The rlogin service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. |
high |
CM-6(a),CM-7(a),CM-7(b),IA-5(1)(c) |
NaN |
2.2.17 |
NaN |
Rlogin, Rsh, and Rexec |
| CCE-27337-5 |
Disable rsh Service |
disable |
via systemctl |
The rsh service, which is available with the rsh-server package and runs as a service through xinetd or separately as a systemd socket, should be disabled. If using xinetd, set disable to yes in /etc/xinetd.d/rsh. The rsh socket can be disabled with the following command: $ sudo systemctl disable rsh.socket The rsh socket can be masked with the following command: $ sudo systemctl mask .socket |
The rsh service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. |
high |
CM-6(a),CM-7(a),CM-7(b),IA-5(1)(c) |
NaN |
2.2.17 |
NaN |
Rlogin, Rsh, and Rexec |
| CCE-27408-4 |
Disable rexec Service |
disable |
via systemctl |
The rexec service, which is available with the rsh-server package and runs as a service through xinetd or separately as a systemd socket, should be disabled. If using xinetd, set disable to yes in /etc/xinetd.d/rexec. The rexec socket can be disabled with the following command: $ sudo systemctl disable rexec.socket The rexec socket can be masked with the following command: $ sudo systemctl mask .socket |
The rexec service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. |
high |
CM-6(a),CM-7(a),CM-7(b),IA-5(1)(c) |
NaN |
2.2.17 |
NaN |
Rlogin, Rsh, and Rexec |
| CCE-80514-3 |
Remove User Host-Based Authentication Files |
delete |
via rm |
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 |
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. |
high |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Rlogin, Rsh, and Rexec |
| CCE-27406-8 |
Remove Rsh Trust Files |
delete |
via rm |
The files /etc/hosts.equiv and ~/.rhosts (in each user's home directory) list remote hosts and users that are trusted by the local system when using the rshd daemon. To remove these files, run the following command to delete them from any location: $ sudo rm /etc/hosts.equiv $ rm ~/.rhosts |
This action is only meaningful if .rhosts support is permitted through PAM. Trust files are convenient, but when used in conjunction with the R-services, they can allow unauthenticated access to a system. |
high |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Rlogin, Rsh, and Rexec |
| CCE-80513-5 |
Remove Host-Based Authentication Files |
delete |
via rm |
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 |
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. |
high |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Rlogin, Rsh, and Rexec |
| CCE-27361-5 |
Install tcp_wrappers Package |
install |
via yum |
When network services are using the xinetd service, the tcp_wrappers package should be installed. The tcp_wrappers package can be installed with the following command: $ sudo yum install tcp_wrappers |
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. |
medium |
CM-6(a) |
NaN |
3.4.1 |
SRG-OS-000480-GPOS-00227 |
Xinetd |
| CCE-27354-0 |
Uninstall xinetd Package |
remove |
via yum |
The xinetd package can be removed with the following command: $ sudo yum erase xinetd |
Removing the xinetd package decreases the risk of the xinetd service's accidental (or intentional) activation. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Xinetd |
| CCE-27443-1 |
Disable xinetd Service |
disable |
via systemctl |
The xinetd service can be disabled with the following command: $ sudo systemctl disable xinetd.service The xinetd service can be masked with the following command: $ sudo systemctl mask xinetd.service |
The xinetd service provides a dedicated listener service for some programs, which is no longer necessary for commonly-used network services. Disabling it ensures that these uncommon services are not running, and also prevents attacks against xinetd itself. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
2.1.7 |
NaN |
Xinetd |
| CCE-83824-3 |
Verify Group Ownership of /etc/hosts.allow |
root |
via chgrp |
To properly set the group owner of /etc/hosts.allow, run the command: $ sudo chgrp root /etc/hosts.allow |
The /etc/hosts.allow file is used to control access of clients to daemons in the server. Insecure groupownership of this file could allow users to grant clients unrestricted access or no access at all to services in the server. |
medium |
NaN |
NaN |
3.4.4 |
NaN |
Xinetd |
| CCE-83826-8 |
Verify Ownership of /etc/hosts.allow |
root |
via chown |
To properly set the owner of /etc/hosts.allow, run the command: $ sudo chown root /etc/hosts.allow |
The /etc/hosts.allow file is used to control access of clients to daemons in the server. Insecure groupownership of this file could allow users to grant clients unrestricted access or no access at all to services in the server. |
medium |
NaN |
NaN |
3.4.4 |
NaN |
Xinetd |
| CCE-84031-4 |
Verify Group Ownership of /etc/hosts.deny |
root |
via chgrp |
To properly set the group owner of /etc/hosts.deny, run the command: $ sudo chgrp root /etc/hosts.deny |
The /etc/hosts.deny file is used to control access of clients to daemons in the server. Insecure groupownership of this file could allow users to grant clients unrestricted access or no access at all to services in the server. |
medium |
NaN |
NaN |
3.4.5 |
NaN |
Xinetd |
| CCE-83391-3 |
Ensure /etc/hosts.deny is configured |
configure |
via /etc/hosts.deny |
The file /etc/hosts.deny together with /etc/hosts.allow provides a simple access control mechanism for network services supporting TCP wrappers. The following line in the file ensures that access to services supporting this mechanism is denied to any clients not mentioned in /etc/hosts.allow: ALL: ALL It is advised to inspect available network services which might be affected by modification of file mentioned above prior to performing the remediation of this rule. If there exist services which might be affected and access to them should not be blocked, modify the /etc/hosts.allow file appropriately before performing the remediation. |
Correct configuration in /etc/hosts.deny ensures that no explicitly mentioned clients will be able to connect to services supporting this access control mechanism. |
medium |
NaN |
NaN |
3.4.3 |
NaN |
Xinetd |
| CCE-84033-0 |
Verify Ownership of /etc/hosts.deny |
root |
via chown |
To properly set the owner of /etc/hosts.deny, run the command: $ sudo chown root /etc/hosts.deny |
The /etc/hosts.deny file is used to control access of clients to daemons in the server. Insecure groupownership of this file could allow users to grant clients unrestricted access or no access at all to services in the server. |
medium |
NaN |
NaN |
3.4.5 |
NaN |
Xinetd |
| CCE-83828-4 |
Verify Permissions on /etc/hosts.allow |
644 |
chmod |
To properly set the permissions of /etc/hosts.allow, run the command: $ sudo chmod 0644 /etc/hosts.allow |
The /etc/hosts.allow file is used to control access of clients to daemons in the server. Insecure groupownership of this file could allow users to grant clients unrestricted access or no access at all to services in the server. |
medium |
NaN |
NaN |
3.4.4 |
NaN |
Xinetd |
| CCE-84035-5 |
Verify Permissions on /etc/hosts.deny |
645 |
chmod |
To properly set the permissions of /etc/hosts.deny, run the command: $ sudo chmod 0644 /etc/hosts.deny |
The /etc/hosts.deny file is used to control access of clients to daemons in the server. Insecure groupownership of this file could allow users to grant clients unrestricted access or no access at all to services in the server. |
medium |
NaN |
NaN |
3.4.5 |
NaN |
Xinetd |
| CCE-27305-2 |
Remove telnet Clients |
remove |
via yum |
The telnet client allows users to start connections to other systems via the telnet protocol. |
The telnet protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow an unauthorized user to steal credentials. The ssh package provides an encrypted session and stronger security and is included in Red Hat Enterprise Linux 7. |
low |
NaN |
NaN |
NaN |
NaN |
Telnet |
| CCE-27165-0 |
Uninstall telnet-server Package |
remove |
via yum |
The telnet-server package can be removed with the following command: $ sudo yum erase telnet-server |
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. |
high |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
2.1.1 |
SRG-OS-000095-GPOS-00049 |
Telnet |
| CCE-27401-9 |
Disable telnet Service |
disable |
via systemctl |
The telnet service configuration file /etc/xinetd.d/telnet is not created automatically. If it was created manually, check the /etc/xinetd.d/telnet file and ensure that disable = no is changed to read disable = yes as follows below: # description: The telnet server serves telnet sessions; it uses \\ # unencrypted username/password pairs for authentication. service telnet { flags = REUSE socket_type = stream wait = no user = root server = /usr/sbin/in.telnetd log_on_failure += USERID disable = yes } If the /etc/xinetd.d/telnet file does not exist, make sure that the activation of the telnet service on system boot is disabled via the following command: The rexec socket can be disabled with the following command: $ sudo systemctl disable rexec.socket The rexec socket can be masked with the following command: $ sudo systemctl mask .socket |
The telnet protocol uses unencrypted network communication, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. The telnet protocol is also subject to man-in-the-middle attacks. |
high |
CM-6(a),CM-7(a),CM-7(b),IA-5(1)(c) |
NaN |
2.2.18 |
NaN |
Telnet |
| CCE-27399-5 |
Uninstall ypserv Package |
remove |
via yum |
The ypserv package can be removed with the following command: $ sudo yum erase ypserv |
The NIS service provides an unencrypted authentication service which does not provide for the confidentiality and integrity of user passwords or the remote session. Removing the ypserv package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services. |
high |
CM-6(a),CM-7(a),CM-7(b),IA-5(1)(c) |
NaN |
2.2.16 |
SRG-OS-000095-GPOS-00049 |
NIS |
| CCE-27396-1 |
Remove NIS Client |
remove |
via yum |
The Network Information Service (NIS), formerly known as Yellow Pages, is a client-server directory service protocol used to distribute system configuration files. The NIS client (ypbind) was used to bind a system to an NIS server and receive the distributed configuration files. |
The NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be removed. |
unknown |
NaN |
NaN |
NaN |
NaN |
NIS |
| CCE-27385-4 |
Disable ypbind Service |
disable |
via systemctl |
The ypbind service, which allows the system to act as a client in a NIS or NIS+ domain, should be disabled. The ypbind service can be disabled with the following command: $ sudo systemctl disable ypbind.service The ypbind service can be masked with the following command: $ sudo systemctl mask ypbind.service |
Disabling the ypbind service ensures the system is not acting as a client in a NIS or NIS+ domain. This service should be disabled unless in use. |
medium |
CM-6(a),CM-7(a),CM-7(b),IA-5(1)(c) |
NaN |
NaN |
NaN |
NIS |
| CCE-27210-4 |
Uninstall talk-server Package |
remove |
via yum |
The talk-server package can be removed with the following command: $ sudo yum erase talk-server |
The talk software presents a security risk as it uses unencrypted protocols for communications. Removing the talk-server package decreases the risk of the accidental (or intentional) activation of talk services. |
medium |
NaN |
NaN |
2.2.21 |
NaN |
Chat/Messaging Services |
| CCE-27432-4 |
Uninstall talk Package |
remove |
via yum |
The talk package contains the client program for the Internet talk protocol, which allows the user to chat with other users on different systems. Talk is a communication program which copies lines from one terminal to the terminal of another user. The talk package can be removed with the following command: $ sudo yum erase talk |
The talk software presents a security risk as it uses unencrypted protocols for communications. Removing the talk package decreases the risk of the accidental (or intentional) activation of talk client program. |
medium |
NaN |
NaN |
2.3.3 |
NaN |
Chat/Messaging Services |
| CCE-80443-5 |
Remove tftp Daemon |
remove |
via yum |
Trivial File Transfer Protocol (TFTP) is a simple file transfer protocol, typically used to automatically transfer configuration or boot files between systems. TFTP does not support authentication and can be easily hacked. The package tftp is a client program that allows for connections to a tftp server. |
It is recommended that TFTP be removed, unless there is a specific need for TFTP (such as a boot server). In that case, use extreme caution when configuring the services. |
low |
NaN |
NaN |
NaN |
NaN |
TFTP Server |
| CCE-80213-2 |
Uninstall tftp-server Package |
remove |
via yum |
The tftp-server package can be removed with the following command: $ sudo yum erase tftp-server |
Removing the tftp-server package decreases the risk of the accidental (or intentional) activation of tftp services. If TFTP is required for operational support (such as transmission of router configurations), its use must be documented with the Information Systems Securty Manager (ISSM), restricted to only authorized personnel, and have access control rules established. |
high |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
TFTP Server |
| CCE-80212-4 |
Disable tftp Service |
disable |
via systemctl |
The tftp service should be disabled. The tftp service can be disabled with the following command: $ sudo systemctl disable tftp.service The tftp service can be masked with the following command: $ sudo systemctl mask tftp.service |
Disabling the tftp service ensures the system is not acting as a TFTP server, which does not provide encryption or authentication. |
high |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
2.1.6 |
NaN |
TFTP Server |
| CCE-80214-0 |
Ensure tftp Daemon Uses Secure Mode |
configure |
via /etc/xinetd.d/tftp |
If running the tftp service is necessary, it should be configured to change its root directory at startup. To do so, ensure /etc/xinetd.d/tftp includes -s as a command line argument, as shown in the following example: server_args = -s |
Using the -s option causes the TFTP service to only serve files from the given directory. Serving files from an intentionally-specified directory reduces the risk of sharing files which should remain private. |
medium |
AC-6,CM-6(b),CM-7(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
TFTP Server |
| CCE-80288-4 |
Uninstall Sendmail Package |
remove |
via yum |
Sendmail is not the default mail transfer agent and is not installed by default. The sendmail package can be removed with the following command: $ sudo yum erase sendmail |
The sendmail software was not developed with security in mind and its design prevents it from being effectively contained by SELinux. Postfix should be used instead. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Mail Server Software |
| CCE-80287-6 |
Enable Postfix Service |
enable |
via systemctl |
The Postfix mail transfer agent is used for local mail delivery within the system. The default configuration only listens for connections to the default SMTP port (port 25) on the loopback interface (127.0.0.1). It is recommended to leave this service enabled for local mail delivery. The postfix service can be enabled with the following command: $ sudo systemctl enable postfix.service |
Local mail delivery is essential to some system maintenance and notification tasks. |
unknown |
NaN |
NaN |
NaN |
NaN |
Mail Server Software |
| CCE-80289-2 |
Disable Postfix Network Listening |
inet_interfaces = loopback-only |
via /etc/postfix/main.cf |
Edit the file /etc/postfix/main.cf to ensure that only the following inet_interfaces line appears: inet_interfaces = |
This ensures postfix accepts mail messages (such as cron job reports) from the local system only, and not from the network, which protects it from network attack. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure SMTP For Mail Clients |
| CCE-82380-7 |
Configure System to Forward All Mail For The Root Account |
root |
via /etc/aliases |
Set up an alias for root that forwards to a monitored email address: $ sudo echo "root: " >> /etc/aliases $ sudo newaliases |
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. |
low |
CM-6(a) |
NaN |
NaN |
NaN |
Configure SMTP For Mail Clients |
| CCE-80290-0 |
Configure SMTP Greeting Banner |
configure |
/etc/postfix/main.cf |
Edit /etc/postfix/main.cf, and add or correct the following line, substituting some other wording for the banner information if you prefer: smtpd_banner = $myhostname ESMTP |
The default greeting banner discloses that the listening mail process is Postfix. When remote mail senders connect to the MTA on port 25, they are greeted by an initial banner as part of the SMTP dialogue. This banner is necessary, but it frequently gives away too much information, including the MTA software which is in use, and sometimes also its version number. Remote mail senders do not need this information in order to send mail, so the banner should be changed to reveal only the hostname (which is already known and may be useful) and the word ESMTP, to indicate that the modern SMTP protocol variant is supported. |
low |
AC-8(a),AC-8(c) |
NaN |
NaN |
NaN |
Configure Postfix if Necessary |
| CCE-80512-7 |
Prevent Unrestricted Mail Relaying |
smtpd_client_restrictions = permit_mynetworks,reject |
/etc/postfix/main.cf |
Modify the /etc/postfix/main.cf file to restrict client connections to the local network with the following command: $ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject' |
If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Control Mail Relaying |
| CCE-80362-7 |
Install the SSSD Package |
install |
via yum |
The sssd package should be installed. The sssd package can be installed with the following command: $ sudo yum install sssd |
NaN |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
System Security Services Daemon |
| CCE-82993-7 |
Install sssd-ipa Package |
install |
via yum |
The sssd-ipa package can be installed with the following command: $ sudo yum install sssd-ipa |
sssd-ipa provides the IPA back end that the SSSD can utilize to fetch identity data from and authenticate against an IPA server. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
System Security Services Daemon |
| CCE-80363-5 |
Enable the SSSD Service |
enable |
via systemctl |
The SSSD service should be enabled. The sssd service can be enabled with the following command: $ sudo systemctl enable sssd.service |
NaN |
medium |
CM-6(a),IA-5(10) |
NaN |
NaN |
NaN |
System Security Services Daemon |
| CCE-80570-5 |
Enable Smartcards in SSSD |
True |
via /etc/sssd/sssd.conf |
SSSD should be configured to authenticate access to the system using smart cards. To enable smart cards in SSSD, set pam_cert_auth to true under the [pam] section in /etc/sssd/sssd.conf. For example: [pam] pam_cert_auth = true |
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. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000375-GPOS-00160 |
System Security Services Daemon |
| CCE-80366-8 |
Configure SSSD to Expire SSH Known Hosts |
180 |
via /etc/sssd/sssd.conf |
SSSD should be configured to expire keys from known SSH hosts after seconds. To configure SSSD to known SSH hosts, set ssh_known_hosts_timeout to under the [ssh] section in /etc/sssd/sssd.conf. For example: [ssh] ssh_known_hosts_timeout = |
If cached authentication information is out-of-date, the validity of the authentication information may be questionable. |
medium |
CM-6(a),IA-5(13) |
NaN |
NaN |
SRG-OS-000383-GPOS-00166 |
System Security Services Daemon |
| CCE-80365-0 |
Configure SSSD to Expire Offline Credentials |
True |
via /etc/sssd/sssd.conf |
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 |
If cached authentication information is out-of-date, the validity of the authentication information may be questionable. |
medium |
CM-6(a),IA-5(13) |
NaN |
NaN |
SRG-OS-000383-GPOS-00166 |
System Security Services Daemon |
| CCE-80364-3 |
Configure SSSD's Memory Cache to Expire |
300 |
via /etc/sssd/sssd.conf |
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 = |
If cached authentication information is out-of-date, the validity of the authentication information may be questionable. |
medium |
CM-6(a),IA-5(13) |
NaN |
NaN |
SRG-OS-000383-GPOS-00166 |
System Security Services Daemon |
| CCE-80437-7 |
Configure PAM in SSSD Services |
configure |
via /etc/sssd/sssd.conf |
SSSD should be configured to run SSSD pam services. To configure SSSD to known SSH hosts, add pam to services under the [sssd] section in /etc/sssd/sssd.conf. For example: [sssd] services = sudo, autofs, pam |
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. |
medium |
CM-6(a),IA-2(1) |
NaN |
NaN |
SRG-OS-000375-GPOS-00160,SRG-OS-000375-GPOS-00161,SRG-OS-000375-GPOS-00162 |
System Security Services Daemon |
| CCE-80546-5 |
Configure SSSD LDAP Backend to Use TLS For All Transactions |
True |
via /etc/sssd/sssd.conf |
The LDAP client should be configured to implement TLS for the integrity of all remote LDAP authentication sessions. If the id_provider is set to ldap or ipa in /etc/sssd/sssd.conf or any of the /etc/sssd/sssd.conf.d configuration files, ldap_id_use_start_tls must be set to true. To check if LDAP is configured to use TLS when id_provider is set to ldap or ipa, use the following command: $ sudo grep -i ldap_id_use_start_tls /etc/sssd/sssd.conf |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. The ssl directive specifies whether to use TLS or not. If not specified it will default to no. It should be set to start_tls rather than doing LDAP over SSL. |
high |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000250-GPOS-00093 |
System Security Services Daemon (SSSD) - LDAP |
| CCE-80515-0 |
Configure SSSD LDAP Backend Client CA Certificate Location |
configure |
via /etc/sssd/sssd.conf |
Configure SSSD to implement cryptography to protect the integrity of LDAP remote access sessions. By setting the ldap_tls_cacertdir option in /etc/sssd/sssd.conf to point to the path for the X.509 certificates used for peer authentication. ldap_tls_cacertdir /path/to/tls/cacert |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash. |
medium |
CM-6(a),SC-12(3) |
NaN |
NaN |
SRG-OS-000250-GPOS-00093 |
System Security Services Daemon (SSSD) - LDAP |
| CCE-80516-8 |
Configure SSSD LDAP Backend Client CA Certificate |
configure |
via /etc/sssd/sssd.conf |
Configure SSSD to implement cryptography to protect the integrity of LDAP remote access sessions. By setting the ldap_tls_cacert option in /etc/sssd/sssd.conf to point to the path for the X.509 certificates used for peer authentication. ldap_tls_cacert /path/to/tls/ca.cert |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash. |
medium |
CM-6(a),SC-12(3) |
NaN |
NaN |
SRG-OS-000250-GPOS-00093 |
System Security Services Daemon (SSSD) - LDAP |
| CCE-80301-5 |
Uninstall httpd Package |
remove |
via yum |
The httpd package can be removed with the following command: $ sudo yum erase httpd |
If there is no need to make the web server software available, removing it provides a safeguard against its activation. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable Apache if Possible |
| CCE-80300-7 |
Disable httpd Service |
disable |
via systemctl |
The httpd service can be disabled with the following command: $ sudo systemctl disable httpd.service The httpd service can be masked with the following command: $ sudo systemctl mask httpd.service |
Running web server software provides a network-based avenue of attack, and should be disabled if not needed. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable Apache if Possible |
| CCE-80551-5 |
Configure The Number of Allowed Simultaneous Requests |
100 |
via /etc/httpd/conf/httpd.conf |
The MaxKeepAliveRequests directive should be set and configured to or greater by setting the following in /etc/httpd/conf/httpd.conf: MaxKeepAliveRequests |
Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a web site, facilitating a denial of service attack. Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests per IP address and may include, where feasible, limiting parameter values associated with keepalive, (i.e., a parameter used to limit the amount of time a connection may be inactive). |
medium |
NaN |
NaN |
NaN |
NaN |
Secure Apache Configuration |
| CCE-80548-1 |
Configure Error Log Format |
configure |
via /etc/httpd/conf/httpd.conf |
LogFormat should be enabled and set to the following in /etc/httpd/conf/httpd.conf: LogFormat "a %A %h %H %l %m %s %t %u %U \"%{Referer}i\" \"%{User-Agent}i\"" combined |
The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as "not found" or "unauthorized" errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the ability of Web Administrators to detect or remediate problems. The LogFormat directive defines the format and information to be included in the access log entries. |
medium |
NaN |
NaN |
NaN |
NaN |
Secure Apache Configuration |
| CCE-80549-9 |
Enable HTTPD System Logging |
configure |
via /etc/httpd/conf/httpd.conf |
CustomLog should be enabled and set to the following in /etc/httpd/conf/httpd.conf: CustomLog "logs/access_log" combined |
The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as "not found" or "unauthorized" errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the ability of Web Administrators to detect or remediate problems. The CustomLog directive specifies the log file, syslog facility, or piped logging utility. |
medium |
NaN |
NaN |
NaN |
NaN |
Secure Apache Configuration |
| CCE-80550-7 |
Enable HTTPD LogLevel |
warn |
via /etc/httpd/conf/httpd.conf |
LogLevel should be enabled and set to . Add or edit the following in /etc/httpd/conf/httpd.conf: LogLevel |
The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as "not found" or "unauthorized" errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the ability of Web Administrators to detect or remediate problems. While the ErrorLog directive configures the error log file name, the LogLevel directive is used to configure the severity level for the error logs. The log level values are the standard syslog levels: emerg, alert, crit, error, warn, notice, info and debug. |
medium |
NaN |
NaN |
NaN |
NaN |
Secure Apache Configuration |
| CCE-81130-7 |
Enable HTTPD Error Logging |
configure |
via /etc/httpd/conf/httpd.conf |
ErrorLog should be enabled and set to the following in /etc/httpd/conf/httpd.conf: ErrorLog "logs/error_log" |
The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as "not found" or "unauthorized" errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the ability of Web Administrators to detect or remediate problems. |
medium |
NaN |
NaN |
NaN |
NaN |
Secure Apache Configuration |
| CCE-80302-3 |
Set httpd ServerTokens Directive to Prod |
Prod |
via /etc/httpd/conf/httpd.conf |
ServerTokens Prod restricts information in page headers, returning only the word "Apache." Add or correct the following directive in /etc/httpd/conf/httpd.conf: ServerTokens Prod |
Information disclosed to clients about the configuration of the web server and system could be used to plan an attack on the given system. This information disclosure should be restricted to a minimum. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict Web Server Information Leakage |
| CCE-80303-1 |
Set httpd ServerSignature Directive to Off |
Off |
via /etc/httpd/conf/httpd.conf |
ServerSignature Off restricts httpd from displaying server version number on error pages. Add or correct the following directive in /etc/httpd/conf/httpd.conf: ServerSignature Off |
Information disclosed to clients about the configuration of the web server and system could be used to plan an attack on the given system. This information disclosure should be restricted to a minimum. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict Web Server Information Leakage |
| CCE-80561-4 |
Scan All Uploaded Content for Malicious Software |
configure |
via A/V software |
Install anti-virus software on the system and set it to automatically scan new files that are introduced to the web server. |
Remote web authors should not be able to upload files to the Document Root directory structure without virus checking and checking for malicious or mobile code. A remote web user, whose agency has a Memorandum of Agreement (MOA) with the hosting agency and has submitted a DoD form 2875 (System Authorization Access Request (SAAR)) or an equivalent document, will be allowed to post files to a temporary location on the server. All posted files to this temporary location will be scanned for viruses and content checked for malicious or mobile code. Only files free of viruses and malicious or mobile code will be posted to the appropriate DocumentRoot directory. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure Operating System to Protect Web Server |
| CCE-80562-2 |
HTTPD Log Files Must Be Owned By Root |
root |
via chown |
All httpd logs must be owned by root user and group. By default, the path for httpd logs is /var/log/httpd/ To properly set the owner of /var/log/httpd, run the command: $ sudo chown root /var/log/httpd To properly set the owner of /var/log/httpd/*, run the command: $ sudo chown root /var/log/httpd/* |
A major tool in exploring the web site use, attempted use, unusual conditions, and problems are the access and error logs. In the event of a security incident, these logs can provide the SA and the web administrator with valuable information. Because of the information that is captured in the logs, it is critical that only authorized individuals have access to the logs. |
medium |
NaN |
NaN |
NaN |
NaN |
Restrict File and Directory Access |
| CCE-80381-7 |
Set Permissions on All Configuration Files Inside /etc/httpd/conf.d/ |
640 |
via chmod |
To properly set the permissions of /etc/http/conf.d/*, run the command: $ sudo chmod 0640 /etc/http/conf.d/* |
Access to the web server's configuration files may allow an unauthorized user or attacker to access information about the web server or to alter the server's configuration files. |
unknown |
AC-6(1),CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict File and Directory Access |
| CCE-80322-1 |
Set Permissions on the /var/log/httpd/ Directory |
700 |
via chmod |
Ensure that the permissions on the web server log directory is set to 700: $ sudo chmod 700 /var/log/httpd/ This is its default setting. |
A major tool in exploring the web site use, attempted use, unusual conditions, and problems are the access and error logs. In the event of a security incident, these logs can provide the SA and the web manager with valuable information. To ensure the integrity of the log files and protect the SA and the web manager from a conflict of interest related to the maintenance of these files, only the members of the Auditors group will be granted permissions to move, copy, and delete these files in the course of their duties related to the archiving of these files. |
medium |
AC-6(1),CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict File and Directory Access |
| CCE-80382-5 |
Set Permissions on All Configuration Files Inside /etc/httpd/conf.modules.d/ |
640 |
via chmod |
To properly set the permissions of /etc/http/conf.modules.d/*, run the command: $ sudo chmod 0640 /etc/http/conf.modules.d/* |
Access to the web server's configuration files may allow an unauthorized user or attacker to access information about the web server or to alter the server's configuration files. |
unknown |
AC-6(1),CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict File and Directory Access |
| CCE-80323-9 |
Set Permissions on the /etc/httpd/conf/ Directory |
750 |
via chmod |
To properly set the permissions of /etc/http/conf, run the command: $ sudo chmod 0750 /etc/http/conf |
Access to the web server's configuration files may allow an unauthorized user or attacker to access information about the web server or alter the server's configuration files. |
unknown |
NaN |
NaN |
NaN |
NaN |
Restrict File and Directory Access |
| CCE-80324-7 |
Set Permissions on All Configuration Files Inside /etc/httpd/conf/ |
640 |
via chmod |
To properly set the permissions of /etc/http/conf/*, run the command: $ sudo chmod 0640 /etc/http/conf/* |
Access to the web server's configuration files may allow an unauthorized user or attacker to access information about the web server or to alter the server's configuration files. |
unknown |
AC-6(1),CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict File and Directory Access |
| CCE-80560-6 |
Configure HTTP PERL Scripts To Use TAINT Option |
-T |
via /etc/httpd/conf/httpd.conf |
If the mod_perl module is installed, enable Perl Taint checking in /etc/httpd/conf/httpd.conf. To enable Perl Taint checking, add or uncomment the following to /etc/httpd/conf.d/perl.conf: PerlSwitches -T |
PERL (Practical Extraction and Report Language) is an interpreted language optimized for scanning arbitrary text files, extracting information from those text files, and printing reports based on that information. The language is often used in shell scripting and is intended to be practical, easy to use, and efficient means of generating interactive web pages for the user. Unfortunately, many widely available freeware PERL programs (scripts) are extremely insecure. This is most readily accomplished by a malicious user substituting input to a PERL script during a POST or a GET operation. Consequently, the founders of PERL have developed a mechanism named TAINT that protects the system from malicious input sent from outside the program. When the data is tainted, it cannot be used in programs or functions such as eval(), system(), exec(), pipes, or popen(). The script will exit with a warning message. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure PERL Securely |
| CCE-80553-1 |
Disable Anonymous FTP Access |
configure |
via chmod |
If any directories that contain dynamic scripts can be accessed via FTP by any group or user that does not require access, remove permissions to such directories that allow anonymous access. Also, ensure that any such access employs an encrypted connection. |
The directories containing the CGI scripts, such as PERL, must not be accessible to anonymous users via FTP. This applies to all directories that contain scripts that can dynamically produce web pages in an interactive manner (i.e., scripts based upon user-provided input). Such scripts contain information that could be used to compromise a web service, access system resources, or deface a web site. |
medium |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80318-9 |
Restrict Other Critical Directories |
Restrict |
via /etc/httpd/conf/httpd.conf |
All accessible web directories should be configured with similarly restrictive settings. The Options directive should be limited to necessary functionality and the AllowOverride directive should be used only if needed. The Order and Deny access control tags should be used to deny access by default, allowing access only where necessary. |
Directories accessible from a web client should be configured with the least amount of access possible in order to avoid unauthorized access to restricted content or server information. |
unknown |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80555-6 |
Web Content Directories Must Not Be Shared Anonymously |
configure |
via chmod |
Web content directories should not be shared anonymously over remote filesystems such as nfs and smb. Remove the shares from the applicable directories. |
Sharing web content is a security risk when a web server is involved. Users accessing the share anonymously could experience privileged access to the content of such directories. Network sharable directories expose those directories and their contents to unnecessary access. Any unnecessary exposure increases the risk that someone could exploit that access and either compromises the web content or cause web server performance problems. |
medium |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80319-7 |
Limit Available Methods |
configure |
via /etc/httpd/conf/httpd.conf |
Web server methods are defined in section 9 of RFC 2616 ( http://www.ietf.org/rfc/rfc2616.txt). If a web server does not require the implementation of all available methods, they should be disabled. Note: GET and POST are the most common methods. A majority of the others are limited to the WebDAV protocol. <Directory /var/www/html> # ... # Only allow specific methods (this command is case-sensitive!) <LimitExcept GET POST> Order allow,deny </LimitExcept> # ... </Directory> |
Minimizing the number of available methods to the web client reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80556-4 |
Remove Write Permissions From Filesystem Paths And Server Scripts |
go-w |
via chmod |
Configure permissions for each instance of Alias, ScriptAlias, and ScriptAliasMatch that exist. $ sudo find DIR -type d -exec chmod 755 {} \; $ sudo find DIR -type f -exec chmod 555 {} \; Where DIR matches the paths from Alias, ScriptAlias, and ScriptAliasMatch. |
Excessive permissions for the anonymous web user account are one of the most common faults contributing to the compromise of a web server. If this user is able to upload and execute files on the web server, the organization or owner of the server will no longer have control of the asset. |
high |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80317-1 |
Restrict Web Directory |
SymLinksIfOwnerMatch |
via /etc/httpd/conf/httpd.conf |
The default configuration for the web (/var/www/html) Directory allows directory indexing (Indexes) and the following of symbolic links (FollowSymLinks). Neither of these is recommended. The /var/www/html directory hierarchy should not be viewable via the web, and symlinks should only be followed if the owner of the symlink also owns the linked file. Ensure that this policy is adhered to by altering the related section of the configuration: <Directory "/var/www/html"> # ... Options SymLinksIfOwnerMatch # ... </Directory> |
Access to the web server's directory hierarchy could allow access to unauthorized files by web clients. Following symbolic links could also allow such access. |
unknown |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80554-9 |
Ignore HTTPD .htaccess Files |
none |
via /etc/httpd/conf/httpd.conf |
Set AllowOverride to none for each instant of <Directory>. |
CGI scripts represents one of the most common and exploitable means of compromising a web server. By definition, CGI are executable by the operating system of the host server. While access control is provided via the web service, the execution of CGI programs is not otherwise limited unless the SA or Web Manager takes specific measures. CGI programs can access and alter data files, launch other programs and use the network. CGI programs can be written in any available programming language. C, PERL, PHP, Javascript, VBScript and shell (sh, ksh, bash) are popular choices. |
medium |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80316-3 |
Restrict Root Directory |
Configure |
via /etc/httpd/conf/httpd.conf |
The httpd root directory should always have the most restrictive configuration enabled. <Directory / > Options None AllowOverride None Order allow,deny </Directory> |
The Web Server's root directory content should be protected from unauthorized access by web clients. |
unknown |
NaN |
NaN |
NaN |
NaN |
Directory Restrictions |
| CCE-80310-6 |
Disable Server Activity Status |
disable |
via /etc/http/conf/httpd.conf |
The status module provides real-time access to statistics on the internal operation of the web server. This may constitute an unnecessary information leak and should be disabled unless necessary. To do so, comment out the related module: #LoadModule status_module modules/mod_status.so If there is a critical need for this module, ensure that access to the status page is properly restricted to a limited set of hosts in the status handler configuration. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80305-6 |
Disable HTTP mod_rewrite |
disable |
via /etc/http/conf/httpd.conf |
The mod_rewrite module is very powerful and can protect against certain classes of web attacks. However, it is also very complex and has a significant history of vulnerabilities itself. If its functionality is unnecessary, comment out the related module: #LoadModule rewrite_module modules/mod_rewrite.so |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80304-9 |
Disable HTTP Digest Authentication |
disable |
via /etc/http/conf/httpd.conf |
The auth_digest module provides encrypted authentication sessions. If this functionality is unnecessary, comment out the related module: #LoadModule auth_digest_module modules/mod_auth_digest.so |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80307-2 |
Disable Server Side Includes |
disable |
via /etc/http/conf/httpd.conf |
Server Side Includes provide a method of dynamically generating web pages through the insertion of server-side code. However, the technology is also deprecated and introduces significant security concerns. If this functionality is unnecessary, comment out the related module: #LoadModule include_module modules/mod_include.so If there is a critical need for Server Side Includes, they should be enabled with the option IncludesNoExec to prevent arbitrary code execution. Additionally, user supplied data should be encoded to prevent cross-site scripting vulnerabilities. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80308-0 |
Disable MIME Magic |
disable |
via /etc/http/conf/httpd.conf |
The mime_magic module provides a second layer of MIME support that in most configurations is likely extraneous. If its functionality is unnecessary, comment out the related module: #LoadModule mime_magic_module modules/mod_mime_magic.so |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80311-4 |
Disable Web Server Configuration Display |
disable |
via /etc/http/conf/httpd.conf |
The info module creates a web page illustrating the configuration of the web server. This can create an unnecessary security leak and should be disabled. If its functionality is unnecessary, comment out the module: #LoadModule info_module modules/mod_info.so If there is a critical need for this module, use the Location directive to provide an access control list to restrict access to the information. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80552-3 |
Enable log_config_module For HTTPD Logging |
enable |
via /etc/http/conf/httpd.conf |
The log_config_module should exist and be configured in the /etc/httpd/conf/httpd.conf file by adding the following module to configure logging: log_config_module |
A major tool in exploring the web site use, attempted use, unusual conditions, and problems are reported in the access and error logs. In the event of a security incident, these logs can provide the SA and the web manager with valuable information. Without these log files, SAs and web managers are seriously hindered in their efforts to respond appropriately to suspicious or criminal actions targeted at the web site. |
medium |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80313-0 |
Disable Proxy Support |
disable |
via /etc/http/conf/httpd.conf |
The proxy module provides proxying support, allowing httpd to forward requests and serve as a gateway for other servers. If its functionality is unnecessary, comment out the module: #LoadModule proxy_module modules/mod_proxy.so If proxy support is needed, load mod_proxy and the appropriate proxy protocol handler module (one of mod_proxy_http, mod_proxy_ftp, or mod_proxy_connect). Additionally, make certain that a server is secure before enabling proxying, as open proxy servers are a security risk. mod_proxy_balancer enables load balancing, but requires that mod status be enabled. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80309-8 |
Disable WebDAV (Distributed Authoring and Versioning) |
disable |
via /etc/http/conf/httpd.conf |
WebDAV is an extension of the HTTP protocol that provides distributed and collaborative access to web content. If its functionality is unnecessary, comment out the related modules: #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.so If there is a critical need for WebDAV, extra care should be taken in its configuration. Since DAV access allows remote clients to manipulate server files, any location on the server that is DAV enabled should be protected by access controls. |
Minimizing the number of loadable modules available to the web server, reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80312-2 |
Disable URL Correction on Misspelled Entries |
disable |
via /etc/http/conf/httpd.conf |
The speling module attempts to find a document match by allowing one misspelling in an otherwise failed request. If this functionality is unnecessary, comment out the module: #LoadModule speling_module modules/mod_speling.so This functionality weakens server security by making site enumeration easier. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80315-5 |
Disable CGI Support |
disable |
via /etc/http/conf/httpd.conf |
The cgi module allows HTML to interact with the CGI web programming language. If this functionality is unnecessary, comment out the module: #LoadModule cgi_module modules/mod_cgi.so If the web server requires the use of CGI, enable mod_cgi. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80314-8 |
Disable Cache Support |
disable |
via /etc/http/conf/httpd.conf |
The cache module allows httpd to cache data, optimizing access to frequently accessed content. However, it introduces potential security flaws such as the possibility of circumventing Allow and Deny directives. If this functionality is unnecessary, comment out the module: #LoadModule cache_module modules/mod_cache.so If caching is required, it should not be enabled for any limited-access content. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80306-4 |
Disable LDAP Support |
disable |
via /etc/http/conf/httpd.conf |
The ldap module provides HTTP authentication via an LDAP directory. If its functionality is unnecessary, comment out the related modules: #LoadModule ldap_module modules/mod_ldap.so #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so If LDAP is to be used, SSL encryption should be used as well. |
Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
unknown |
NaN |
NaN |
NaN |
NaN |
httpd Core Modules |
| CCE-80321-3 |
Install mod_security |
install |
via yum |
Install the security module: The mod_security package can be installed with the following command: $ sudo yum install mod_security |
mod_security provides an additional level of protection for the web server by enabling the administrator to implement content access policies and filters at the application layer. |
unknown |
NaN |
NaN |
NaN |
NaN |
Deploy mod_security |
| CCE-80558-0 |
Require Client Certificates |
require |
via /etc/httpd/conf/httpd.conf |
SSLVerifyClient should be set and configured to require by setting the following in /etc/httpd/conf/httpd.conf: SSLVerifyClient require |
Web sites requiring authentication within the DoD must utilize PKI as an authentication mechanism for web users. Information systems residing behind web servers requiring authorization based on individual identity must use the identity provided by certificate-based authentication to support access control decisions. |
medium |
NaN |
NaN |
NaN |
NaN |
Deploy mod_ssl |
| CCE-80559-8 |
Configure A Valid Server Certificate |
Configure |
via /etc/httpd/conf.modules.d/ssl.conf |
Configure the web site to use a valid organizationally defined certificate. For DoD, this is a DoD server certificate issued by the DoD CA. |
This check verifies that DoD is a hosted web site's CA. The certificate is actually a DoD-issued server certificate used by the organization being reviewed. This is used to verify the authenticity of the web site to the user. If the certificate is not for the server (Certificate belongs to), if the certificate is not issued by DoD (Certificate was issued by), or if the current date is not included in the valid date (Certificate is valid from), then there is no assurance that the use of the certificate is valid. The entire purpose of using a certificate is, therefore, compromised. |
medium |
NaN |
NaN |
NaN |
NaN |
Deploy mod_ssl |
| CCE-80320-5 |
Install mod_ssl |
install |
via yum |
Install the mod_ssl module: The mod_ssl package can be installed with the following command: $ sudo yum install mod_ssl |
mod_ssl provides encryption capabilities for the httpd Web server. Unencrypted content is transmitted in plain text which could be passively monitored and accessed by unauthorized parties. |
unknown |
NaN |
NaN |
NaN |
NaN |
Deploy mod_ssl |
| CCE-80557-2 |
Enable Transport Layer Security (TLS) Encryption |
Configure |
via /etc/httpd/conf.modules.d/ssl.conf |
Disable old SSL and TLS version and enable the latest TLS encryption by setting the following in /etc/httpd/conf.modules.d/ssl.conf: SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1 Make sure to also set SSLEngine to on in /etc/httpd/conf.modules.d/ssl.conf like the following: SSLEngine on |
Transport Layer Security (TLS) encryption is a required security setting for a private web server. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. A web server must use a FIPS 140-2 approved TLS version, and all non-FIPS-approved SSL versions must be disabled. |
medium |
NaN |
NaN |
NaN |
NaN |
Deploy mod_ssl |
| CCE-27594-1 |
Uninstall quagga Package |
remove |
via yum |
The quagga package can be removed with the following command: $ sudo yum erase quagga |
Routing software is typically used on routers to exchange network topology information with other routers. If routing software is used when not required, system network information may be unnecessarily transmitted across the network. If there is no need to make the router software available, removing it provides a safeguard against its activation. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disable Quagga if Possible |
| CCE-27191-6 |
Disable Quagga Service |
disable |
via systemctl |
The zebra service can be disabled with the following command: $ sudo systemctl disable zebra.service The zebra service can be masked with the following command: $ sudo systemctl mask zebra.service |
Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If routing daemons are used when not required, system network information may be unnecessarily transmitted across the network. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disable Quagga if Possible |
| CCE-80275-1 |
Uninstall net-snmp Package |
remove |
via yum |
The net-snmp package provides the snmpd service. The net-snmp package can be removed with the following command: $ sudo yum erase net-snmp |
If there is no need to run SNMP server software, removing the package provides a safeguard against its activation. |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable SNMP Server if Possible |
| CCE-80274-4 |
Disable snmpd Service |
disable |
via systemctl |
The snmpd service can be disabled with the following command: $ sudo systemctl disable snmpd.service The snmpd service can be masked with the following command: $ sudo systemctl mask snmpd.service |
Running SNMP software provides a network-based avenue of attack, and should be disabled if not needed. |
low |
NaN |
NaN |
NaN |
NaN |
Disable SNMP Server if Possible |
| CCE-82732-9 |
Ensure SNMP Read Write is disabled |
remove |
via /etc/snmp/snmpd.conf |
Edit /etc/snmp/snmpd.conf, remove any rwuser entries. Once the read write users have been removed, restart the SNMP service: $ sudo service snmpd restart |
Certain SNMP settings can permit users to execute system behaviors from user writes to the community strings. This may permit a compromised account to execute commands on a remote system. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure SNMP Server if Necessary |
| CCE-80276-9 |
Configure SNMP Service to Use Only SNMPv3 or Newer |
configure |
via /etc/snmp/snmpd.conf |
Edit /etc/snmp/snmpd.conf, removing any references to rocommunity, rwcommunity, or com2sec. Upon doing that, restart the SNMP service: $ sudo service snmpd restart |
Earlier versions of SNMP are considered insecure, as they potentially allow unauthorized access to detailed system management information. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure SNMP Server if Necessary |
| CCE-27386-2 |
Ensure Default SNMP Password Is Not Used |
configure |
via /etc/snmp/snmpd.conf |
Edit /etc/snmp/snmpd.conf, remove or change the default community strings of public and private. Once the default community strings have been changed, restart the SNMP service: $ sudo service snmpd restart |
Whether active or not, default simple network management protocol (SNMP) community strings must be changed to maintain security. If the service is running with the default authenticators, then anyone can gather data about the system and the network and use the information to potentially compromise the integrity of the system and network(s). |
high |
IA-5(e) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure SNMP Server if Necessary |
| CCE-80332-0 |
Do Not Use Dynamic DNS |
none |
via /etc/dhcp/dhcpd.conf |
To prevent the DHCP server from receiving DNS information from clients, edit /etc/dhcp/dhcpd.conf, and add or correct the following global option: ddns-update-style none; |
The Dynamic DNS protocol is used to remotely update the data served by a DNS server. DHCP servers can use Dynamic DNS to publish information about their clients. This setup carries security risks, and its use is not recommended. If Dynamic DNS must be used despite the risks it poses, it is critical that Dynamic DNS transactions be protected using TSIG or some other cryptographic authentication mechanism. See dhcpd.conf(5) for more information about protecting the DHCP server from passing along malicious DNS data from its clients. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure DHCP Server |
| CCE-80334-6 |
Deny BOOTP Queries |
bootp |
via /etc/dhcp/dhcpd.conf |
Unless your network needs to support older BOOTP clients, disable support for the bootp protocol by adding or correcting the global option: deny bootp; |
The bootp option tells dhcpd to respond to BOOTP queries. If support for this simpler protocol is not needed, it should be disabled to remove attack vectors against the DHCP server. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure DHCP Server |
| CCE-80333-8 |
Deny Decline Messages |
NaN |
NaN |
Edit /etc/dhcp/dhcpd.conf and add or correct the following global option to prevent the DHCP server from responding the DHCPDECLINE messages, if possible: deny declines; |
The DHCPDECLINE message can be sent by a DHCP client to indicate that it does not consider the lease offered by the server to be valid. By issuing many DHCPDECLINE messages, a malicious client can exhaust the DHCP server's pool of IP addresses, causing the DHCP server to forget old address allocations. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure DHCP Server |
| CCE-80336-1 |
Configure Logging |
daemon.* |
via /etc/rsyslog.conf |
Ensure that the following line exists in /etc/rsyslog.conf: daemon.* /var/log/daemon.log Configure logwatch or other log monitoring tools to summarize error conditions reported by the dhcpd process. |
By default, dhcpd logs notices to the daemon facility. Sending all daemon messages to a dedicated log file is part of the syslog configuration outlined in the Logging and Auditing section |
unknown |
AU-12(a),AU-12(c),CM-6(a) |
NaN |
NaN |
NaN |
Configure DHCP Server |
| CCE-80337-9 |
Disable DHCP Client in ifcfg |
none |
via ifcfg |
For each interface on the system (e.g. eth0), edit /etc/sysconfig/network-scripts/ifcfg-interface and make the following changes: Correct the BOOTPROTO line to read: BOOTPROTO=none Add or correct the following lines, substituting the appropriate values based on your site's addressing scheme: NETMASK=255.255.255.0 IPADDR=192.168.1.2 GATEWAY=192.168.1.1 |
DHCP relies on trusting the local network. If the local network is not trusted, then it should not be used. However, the automatic configuration provided by DHCP is commonly used and the alternative, manual configuration, presents an unacceptable burden in many circumstances. |
unknown |
CM-6(a) |
NaN |
NaN |
NaN |
Disable DHCP Client |
| CCE-80331-2 |
Uninstall DHCP Server Package |
remove |
via yum |
If the system does not need to act as a DHCP server, the dhcp package can be uninstalled. The dhcp package can be removed with the following command: $ sudo yum erase dhcp |
Removing the DHCP server ensures that it cannot be easily or accidentally reactivated and disrupt network operation. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable DHCP Server |
| CCE-80330-4 |
Disable DHCP Service |
disable |
via systemctl |
The dhcpd service should be disabled on any system that does not need to act as a DHCP server. The dhcpd service can be disabled with the following command: $ sudo systemctl disable dhcpd.service The dhcpd service can be masked with the following command: $ sudo systemctl mask dhcpd.service |
Unmanaged or unintentionally activated DHCP servers may provide faulty information to clients, interfering with the operation of a legitimate site DHCP server if there is one. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable DHCP Server |
| CCE-80297-5 |
Configure Dovecot to Use the SSL Certificate file |
configure |
via /etc/dovecot/conf.d/10-ssl.conf |
This option tells Dovecot where to find the the mail server's SSL Certificate. Edit /etc/dovecot/conf.d/10-ssl.conf and add or correct the following line (note: the path below is the default path set by the Dovecot installation. If you are using a different path, ensure you reference the appropriate file): ssl_cert = </etc/pki/dovecot/certs/dovecot.pem" |
SSL certificates are used by the client to authenticate the identity of the server, as well as to encrypt credentials and message traffic. Not using SSL to encrypt mail server traffic could allow unauthorized access to credentials and mail messages since they are sent in plain text over the network. |
unknown |
NaN |
NaN |
NaN |
NaN |
Enable SSL Support |
| CCE-80299-1 |
Disable Plaintext Authentication |
yes |
via /etc/dovecot/conf.d/10-ssl.conf |
To prevent Dovecot from attempting plaintext authentication of clients, edit /etc/dovecot/conf.d/10-auth.conf and add\or correct the following line: disable_plaintext_auth = yes |
Using plain text authentication to the mail server could allow an attacker access to credentials by monitoring network traffic. |
unknown |
NaN |
NaN |
NaN |
NaN |
Enable SSL Support |
| CCE-80298-3 |
Configure Dovecot to Use the SSL Key file |
configure |
via /etc/dovecot/conf.d/10-ssl.conf |
This option tells Dovecot where to find the the mail server's SSL Key. Edit /etc/dovecot/conf.d/10-ssl.conf and add or correct the following line (note: the path below is the default path set by the Dovecot installation. If you are using a different path, ensure you reference the appropriate file): ssl_key = </etc/pki/dovecot/private/dovecot.pem |
SSL certificates are used by the client to authenticate the identity of the server, as well as to encrypt credentials and message traffic. Not using SSL to encrypt mail server traffic could allow unauthorized access to credentials and mail messages since they are sent in plain text over the network. |
unknown |
NaN |
NaN |
NaN |
NaN |
Enable SSL Support |
| CCE-80296-7 |
Enable the SSL flag in /etc/dovecot.conf |
yes |
via /etc/dovecot/conf.d/10-ssl.conf |
To allow clients to make encrypted connections the ssl flag in Dovecot's configuration file needs to be set to yes. Edit /etc/dovecot/conf.d/10-ssl.conf and add or correct the following line: ssl = yes |
SSL encrypt network traffic between the Dovecot server and its clients protecting user credentials, mail as it is downloaded, and clients may use SSL certificates to authenticate the server, preventing another system from impersonating the server. |
unknown |
NaN |
NaN |
NaN |
NaN |
Enable SSL Support |
| CCE-80295-9 |
Uninstall dovecot Package |
remove |
via yum |
The dovecot package can be removed with the following command: $ sudo yum erase dovecot |
If there is no need to make the Dovecot software available, removing it provides a safeguard against its activation. |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Dovecot |
| CCE-80294-2 |
Disable Dovecot Service |
disable |
via systemctl |
The dovecot service can be disabled with the following command: $ sudo systemctl disable dovecot.service The dovecot service can be masked with the following command: $ sudo systemctl mask dovecot.service |
Running an IMAP or POP3 server provides a network-based avenue of attack, and should be disabled if not needed. |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Dovecot |
| CCE-82461-5 |
Uninstall the telnet server |
remove |
via yum |
The telnet daemon should be uninstalled. |
telnet allows clear text communications, and does not protect any data transmission between client and server. Any confidential data can be listened and no integrity checking is made.' |
high |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Deprecated services |
| CCE-80282-7 |
Disable the CUPS Service |
disable |
via systemctl |
The cups service can be disabled with the following command: $ sudo systemctl disable cups.service The cups service can be masked with the following command: $ sudo systemctl mask cups.service |
Turn off unneeded services to reduce attack surface. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Print Support |
| CCE-80284-3 |
Disable Print Server Capabilities |
disable |
via /etc/cups/cupsd.conf |
To prevent remote users from potentially connecting to and using locally configured printers, disable the CUPS print server sharing capabilities. To do so, limit how the server will listen for print jobs by removing the more generic port directive from /etc/cups/cupsd.conf: Port 631 and replacing it with the Listen directive: Listen localhost:631 This will prevent remote users from printing to locally configured printers while still allowing local users on the system to print normally. |
By default, locally configured printers will not be shared over the network, but if this functionality has somehow been enabled, these recommendations will disable it again. Be sure to disable outgoing printer list broadcasts, or remote users will still be able to see the locally configured printers, even if they cannot actually print to them. To limit print serving to a particular set of users, use the Policy directive. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure the CUPS Service if Necessary |
| CCE-80283-5 |
Disable Printer Browsing Entirely if Possible |
disable |
via /etc/cups/cupsd.conf |
By default, CUPS listens on the network for printer list broadcasts on UDP port 631. This functionality is called printer browsing. To disable printer browsing entirely, edit the CUPS configuration file, located at /etc/cups/cupsd.conf, to include the following: Browsing Off BrowseAllow none |
The CUPS print service can be configured to broadcast a list of available printers to the network. Other systems on the network, also running the CUPS print service, can be configured to listen to these broadcasts and add and configure these printers for immediate use. By disabling this browsing capability, the system will no longer generate or receive such broadcasts. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure the CUPS Service if Necessary |
| CCE-82960-6 |
Install usbguard Package |
install |
via yum |
The usbguard package can be installed with the following command: $ sudo yum install usbguard |
usbguard is a software framework that helps to protect against rogue USB devices by implementing basic whitelisting/blacklisting capabilities based on USB device attributes. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000378-GPOS-00163 |
USBGuard daemon |
| CCE-27218-7 |
Remove the X Windows Package Group |
remove |
via yum |
By removing the xorg-x11-server-common package, the system no longer has X Windows installed. If X Windows is not installed then the system cannot boot into graphical user mode. This prevents the system from being accidentally or maliciously booted into a graphical.target mode. To do so, run the following command: $ sudo yum groupremove "X Window System" $ sudo yum remove xorg-x11-server-common |
Unnecessary service packages must not be installed to decrease the attack surface of the system. X windows has a long history of security vulnerabilities and should not be installed unless approved and documented. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disable X Windows |
| CCE-27285-6 |
Disable X Windows Startup By Setting Default Target |
mult-user.target |
via systemctl |
Systems that do not require a graphical user interface should only boot by default into multi-user.target mode. This prevents accidental booting of the system into a graphical.target mode. Setting the system's default target to multi-user.target will prevent automatic startup of the X server. To do so, run: $ systemctl set-default multi-user.target You should see the following output: Removed symlink /etc/systemd/system/default.target. Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target. |
Services that are not required for system and application processes must not be active to decrease the attack surface of the system. X windows has a long history of security vulnerabilities and should not be used unless approved and documented. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disable X Windows |
| CCE-82403-7 |
Install the psacct package |
install |
via yum |
The process accounting service, psacct, works with programs including acct and ac to allow system administrators to view user activity, such as commands issued by users of the system. The psacct package can be installed with the following command: $ sudo yum install psacct |
The psacct service can provide administrators a convenient view into some user activities. However, it should be noted that the auditing system and its audit records provide more authoritative and comprehensive records. |
low |
AU-12(a),CM-6(a) |
NaN |
NaN |
NaN |
Base Services |
| CCE-81040-8 |
Uninstall Automatic Bug Reporting Tool (abrt) |
remove |
via yum |
The Automatic Bug Reporting Tool (abrt) collects and reports crash data when an application crash is detected. Using a variety of plugins, abrt can email crash reports to system administrators, log crash reports to files, or forward crash reports to a centralized issue tracking system such as RHTSupport. The abrt package can be removed with the following command: $ sudo yum erase abrt |
Mishandling crash data could expose sensitive information about vulnerabilities in software executing on the system, as well as sensitive information from within a process's address space or registers. |
medium |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
Base Services |
| CCE-80257-9 |
Enable IRQ Balance (irqbalance) |
enable |
via systemctl |
The irqbalance service optimizes the balance between power savings and performance through distribution of hardware interrupts across multiple processors. The irqbalance service can be enabled with the following command: $ sudo systemctl enable irqbalance.service |
In an environment with multiple processors (now common), the irqbalance service provides potential speedups for handling interrupt requests. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80265-2 |
Enable Process Accounting (psacct) |
enable |
via systemctl |
The process accounting service, psacct, works with programs including acct and ac to allow system administrators to view user activity, such as commands issued by users of the system. The psacct service can be enabled with the following command: $ sudo systemctl enable psacct.service |
The psacct service can provide administrators a convenient view into some user activities. However, it should be noted that the auditing system and its audit records provide more authoritative and comprehensive records. |
low |
AU-12(a),CM-6(a) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80263-7 |
Disable Odd Job Daemon (oddjobd) |
disable |
via systemctl |
The oddjobd service exists to provide an interface and access control mechanism through which specified privileged tasks can run tasks for unprivileged client applications. Communication with oddjobd through the system message bus. The oddjobd service can be disabled with the following command: $ sudo systemctl disable oddjobd.service The oddjobd service can be masked with the following command: $ sudo systemctl mask oddjobd.service |
The oddjobd service may provide necessary functionality in some environments, and can be disabled if it is not needed. Execution of tasks by privileged programs, on behalf of unprivileged ones, has traditionally been a source of privilege escalation security issues. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80256-1 |
Disable CPU Speed (cpupower) |
disable |
via systemctl |
The cpupower service can adjust the clock speed of supported CPUs based upon the current processing load thereby conserving power and reducing heat. The cpupower service can be disabled with the following command: $ sudo systemctl disable cpupower.service The cpupower service can be masked with the following command: $ sudo systemctl mask cpupower.service |
The cpupower service is only necessary if adjusting the CPU clock speed provides benefit. Traditionally this has included laptops (to enhance battery life), but may also apply to server or desktop environments where conserving power is highly desirable or necessary. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80268-6 |
Disable Network Router Discovery Daemon (rdisc) |
disable |
via systemctl |
The rdisc service implements the client side of the ICMP Internet Router Discovery Protocol (IRDP), which allows discovery of routers on the local subnet. If a router is discovered then the local routing table is updated with a corresponding default route. By default this daemon is disabled. The rdisc service can be disabled with the following command: $ sudo systemctl disable rdisc.service The rdisc service can be masked with the following command: $ sudo systemctl mask rdisc.service |
General-purpose systems typically have their network and routing information configured statically by a system administrator. Workstations or some special-purpose systems often use DHCP (instead of IRDP) to retrieve dynamic network configuration information. |
medium |
AC-4,CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80272-8 |
Disable SMART Disk Monitoring Service (smartd) |
disable |
via systemctl |
SMART (Self-Monitoring, Analysis, and Reporting Technology) is a feature of hard drives that allows them to detect symptoms of disk failure and relay an appropriate warning. The smartd service can be disabled with the following command: $ sudo systemctl disable smartd.service The smartd service can be masked with the following command: $ sudo systemctl mask smartd.service |
SMART can help ensure availability of systems by notifying system operators of failing hardware. Nevertheless, if it is not needed or the system's drives are not SMART-capable (such as solid state drives), this service can be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80258-7 |
Disable KDump Kernel Crash Analyzer (kdump) |
disable |
via systemctl |
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 disable kdump.service The kdump service can be masked with the following command: $ sudo systemctl mask kdump.service |
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. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Base Services |
| CCE-80259-5 |
Disable Software RAID Monitor (mdmonitor) |
disable |
via systemctl |
The mdmonitor service is used for monitoring a software RAID array; hardware RAID setups do not use this service. The mdmonitor service can be disabled with the following command: $ sudo systemctl disable mdmonitor.service The mdmonitor service can be masked with the following command: $ sudo systemctl mask mdmonitor.service |
If software RAID monitoring is not required, there is no need to run this service. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80270-2 |
Disable Red Hat Subscription Manager Daemon (rhsmcertd) |
disable |
via systemctl |
The Red Hat Subscription Manager (rhsmcertd) periodically checks for changes in the entitlement certificates for a registered system and updates it accordingly. The rhsmcertd service can be disabled with the following command: $ sudo systemctl disable rhsmcertd.service The rhsmcertd service can be masked with the following command: $ sudo systemctl mask rhsmcertd.service |
The rhsmcertd service can provide administrators with some additional control over which of their systems are entitled to particular subscriptions. However, for systems that are managed locally or which are not expected to require remote changes to their subscription status, it is unnecessary and can be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80273-6 |
Disable System Statistics Reset Service (sysstat) |
disable |
via systemctl |
The sysstat service resets various I/O and CPU performance statistics to zero in order to begin counting from a fresh state at boot time. The sysstat service can be disabled with the following command: $ sudo systemctl disable sysstat.service The sysstat service can be masked with the following command: $ sudo systemctl mask sysstat.service |
By default the sysstat service runs a program at boot to reset performance statistics. This data can be retrieved using programs such as sar and sadc. While the sysstat service may provide useful insight into system operation, through the lens of providing only essential system services, this service should be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80271-0 |
Disable Cyrus SASL Authentication Daemon (saslauthd) |
disable |
via systemctl |
The saslauthd service handles plaintext authentication requests on behalf of the SASL library. The service isolates all code requiring superuser privileges for SASL authentication into a single process, and can also be used to provide proxy authentication services to clients that do not understand SASL based authentication. The saslauthd service can be disabled with the following command: $ sudo systemctl disable saslauthd.service The saslauthd service can be masked with the following command: $ sudo systemctl mask saslauthd.service |
The saslauthd service provides essential functionality for performing authentication in some directory environments, such as those which use Kerberos and LDAP. For others, however, in which only local files may be consulted, it is not necessary and should be disabled. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80264-5 |
Disable Portreserve (portreserve) |
disable |
via systemctl |
The portreserve service is a TCP port reservation utility that can be used to prevent portmap from binding to well known TCP ports that are required for other services. The portreserve service can be disabled with the following command: $ sudo systemctl disable portreserve.service The portreserve service can be masked with the following command: $ sudo systemctl mask portreserve.service |
The portreserve service provides helpful functionality by preventing conflicting usage of ports in the reserved port range, but it can be disabled if not needed. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80260-3 |
Disable D-Bus IPC Service (messagebus) |
disable |
via systemctl |
D-Bus provides an IPC mechanism used by a growing list of programs, such as those used for Gnome, Bluetooth, and Avahi. Due to these dependencies, disabling D-Bus may not be practical for many systems. The messagebus service can be disabled with the following command: $ sudo systemctl disable messagebus.service The messagebus service can be masked with the following command: $ sudo systemctl mask messagebus.service |
If no services which require D-Bus are needed, then it can be disabled. As a broker for IPC between processes of different privilege levels, it could be a target for attack. However, disabling D-Bus is likely to be impractical for any system which needs to provide a graphical login session. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80253-8 |
Disable Certmonger Service (certmonger) |
disable |
via systemctl |
Certmonger is a D-Bus based service that attempts to simplify interaction with certifying authorities on networks which use public-key infrastructure. It is often combined with Red Hat's IPA (Identity Policy Audit) security information management solution to aid in the management of certificates. The certmonger service can be disabled with the following command: $ sudo systemctl disable certmonger.service The certmonger service can be masked with the following command: $ sudo systemctl mask certmonger.service |
The services provided by certmonger may be essential for systems fulfilling some roles a PKI infrastructure, but its functionality is not necessary for many other use cases. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80262-9 |
Disable ntpdate Service (ntpdate) |
disable |
via systemctl |
The ntpdate service sets the local hardware clock by polling NTP servers when the system boots. It synchronizes to the NTP servers listed in /etc/ntp/step-tickers or /etc/ntp.conf and then sets the local hardware clock to the newly synchronized system time. The ntpdate service can be disabled with the following command: $ sudo systemctl disable ntpdate.service The ntpdate service can be masked with the following command: $ sudo systemctl mask ntpdate.service |
The ntpdate service may only be suitable for systems which are rebooted frequently enough that clock drift does not cause problems between reboots. In any event, the functionality of the ntpdate service is now available in the ntpd program and should be considered deprecated. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80254-6 |
Disable Control Group Config (cgconfig) |
disable |
via systemctl |
Control groups allow an administrator to allocate system resources (such as CPU, memory, network bandwidth, etc) among a defined group (or groups) of processes executing on a system. The cgconfig daemon starts at boot and establishes the predefined control groups. The cgconfig service can be disabled with the following command: $ sudo systemctl disable cgconfig.service The cgconfig service can be masked with the following command: $ sudo systemctl mask cgconfig.service |
Unless control groups are used to manage system resources, running the cgconfig service is not necessary. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80255-3 |
Disable Control Group Rules Engine (cgred) |
disable |
via systemctl |
The cgred service moves tasks into control groups according to parameters set in the /etc/cgrules.conf configuration file. The cgred service can be disabled with the following command: $ sudo systemctl disable cgred.service The cgred service can be masked with the following command: $ sudo systemctl mask cgred.service |
Unless control groups are used to manage system resources, running the cgred service service is not necessary. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80266-0 |
Disable Apache Qpid (qpidd) |
disable |
via systemctl |
The qpidd service provides high speed, secure, guaranteed delivery services. It is an implementation of the Advanced Message Queuing Protocol. By default the qpidd service will bind to port 5672 and listen for connection attempts. The qpidd service can be disabled with the following command: $ sudo systemctl disable qpidd.service The qpidd service can be masked with the following command: $ sudo systemctl mask qpidd.service |
The qpidd service is automatically installed when the base package selection is selected during installation. The qpidd service listens for network connections, which increases the attack surface of the system. If the system is not intended to receive AMQP traffic, then the qpidd service is not needed and should be disabled or removed. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-82027-4 |
Disable Automatic Bug Reporting Tool (abrtd) |
disable |
via systemctl |
The Automatic Bug Reporting Tool (abrtd) daemon collects and reports crash data when an application crash is detected. Using a variety of plugins, abrtd can email crash reports to system administrators, log crash reports to files, or forward crash reports to a centralized issue tracking system such as RHTSupport. The abrtd service can be disabled with the following command: $ sudo systemctl disable abrtd.service The abrtd service can be masked with the following command: $ sudo systemctl mask abrtd.service |
Mishandling crash data could expose sensitive information about vulnerabilities in software executing on the system, as well as sensitive information from within a process's address space or registers. |
medium |
CM-6(a),CM-7(a) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80261-1 |
Disable Network Console (netconsole) |
disable |
via systemctl |
The netconsole service is responsible for loading the netconsole kernel module, which logs kernel printk messages over UDP to a syslog server. This allows debugging of problems where disk logging fails and serial consoles are impractical. The netconsole service can be disabled with the following command: $ sudo systemctl disable netconsole.service The netconsole service can be masked with the following command: $ sudo systemctl mask netconsole.service |
The netconsole service is not necessary unless there is a need to debug kernel panics, which is not common. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80269-4 |
Disable Red Hat Network Service (rhnsd) |
disable |
via systemctl |
The Red Hat Network service automatically queries Red Hat Network servers to determine whether there are any actions that should be executed, such as package updates. This only occurs if the system was registered to an RHN server or satellite and managed as such. The rhnsd service can be disabled with the following command: $ sudo systemctl disable rhnsd.service The rhnsd service can be masked with the following command: $ sudo systemctl mask rhnsd.service |
Although systems management and patching is extremely important to system security, management by a system outside the enterprise enclave is not desirable for some environments. However, if the system is being managed by RHN or RHN Satellite Server the rhnsd daemon can remain on. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80267-8 |
Disable Quota Netlink (quota_nld) |
disable |
via systemctl |
The quota_nld service provides notifications to users of disk space quota violations. It listens to the kernel via a netlink socket for disk quota violations and notifies the appropriate user of the violation using D-Bus or by sending a message to the terminal that the user has last accessed. The quota_nld service can be disabled with the following command: $ sudo systemctl disable quota_nld.service The quota_nld service can be masked with the following command: $ sudo systemctl mask quota_nld.service |
If disk quotas are enforced on the local system, then the quota_nld service likely provides useful functionality and should remain enabled. However, if disk quotas are not used or user notification of disk quota violation is not desired then there is no need to run this service. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-80252-0 |
Disable Advanced Configuration and Power Interface (acpid) |
disable |
via systemctl |
The Advanced Configuration and Power Interface Daemon (acpid) dispatches ACPI events (such as power/reset button depressed) to userspace programs. The acpid service can be disabled with the following command: $ sudo systemctl disable acpid.service The acpid service can be masked with the following command: $ sudo systemctl mask acpid.service |
ACPI support is highly desirable for systems in some network roles, such as laptops or desktops. For other systems, such as servers, it may permit accidental or trivially achievable denial of service situations and disabling it is appropriate. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Base Services |
| CCE-82751-9 |
Remove the FreeRadius Server Package |
remove |
via yum |
The freeradius package should be removed if not in use. Is this system a RADIUS server? If not, remove the package. The freeradius package can be removed with the following command: $ sudo yum erase freeradius The freeradius RPM is not installed by default on a Red Hat Enterprise Linux 7 system. It is needed only by the RADIUS servers, not by the clients which use RADIUS for authentication. If the system is not intended for use as a RADIUS Server it should be removed. |
Unnecessary packages should not be installed to decrease the attack surface of the system. While this software is clearly essential on a RADIUS server, it is not necessary on typical desktop or workstation systems. |
low |
NaN |
NaN |
NaN |
NaN |
Remote Authentication Dial-In User Service (RADIUS) |
| CCE-80215-7 |
Install the OpenSSH Server Package |
install |
via yum |
The openssh-server package should be installed. The openssh-server package can be installed with the following command: $ sudo yum install openssh-server |
Without protection of the transmitted information, confidentiality, and integrity may be compromised because unprotected communications can be intercepted and either read or altered. |
medium |
CM-6(a) |
FIA_UAU.5,FTP_ITC_EXT.1 |
NaN |
SRG-OS-000423-GPOS-00187,SRG-OS-000424-GPOS-00188,SRG-OS-000425-GPOS-00189,SRG-OS-000426-GPOS-00190 |
SSH Server |
| CCE-80216-5 |
Enable the OpenSSH Service |
enable |
via systemctl |
The SSH server service, sshd, is commonly needed. The sshd service can be enabled with the following command: $ sudo systemctl enable sshd.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. |
medium |
CM-6(a),SC-8,SC-8(1),SC-8(2),SC-8(3),SC-8(4) |
NaN |
NaN |
SRG-OS-000423-GPOS-00187,SRG-OS-000423-GPOS-00188,SRG-OS-000423-GPOS-00189,SRG-OS-000423-GPOS-00190 |
SSH Server |
| CCE-80217-3 |
Disable SSH Server If Possible (Unusual) |
disable |
via systemctl |
The SSH server service, sshd, is commonly needed. However, if it can be disabled, do so. The sshd service can be disabled with the following command: $ sudo systemctl disable sshd.service The sshd service can be masked with the following command: $ sudo systemctl mask sshd.service This is unusual, as SSH is a common method for encrypted and authenticated remote access. |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
SSH Server |
| CCE-82895-4 |
Verify Permissions on SSH Server config file |
600 |
via chmod |
To properly set the permissions of /etc/ssh/sshd_config, run the command: $ sudo chmod 0600 /etc/ssh/sshd_config |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-17(a),AC-6(1),CM-6(a) |
NaN |
5.2.1 |
SRG-OS-000480-GPOS-00227 |
SSH Server |
| CCE-82899-6 |
Verify Owner on SSH Server config file |
root |
via chown |
To properly set the owner of /etc/ssh/sshd_config, run the command: $ sudo chown root /etc/ssh/sshd_config |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-17(a),AC-6(1),CM-6(a) |
NaN |
5.2.1 |
SRG-OS-000480-GPOS-00227 |
SSH Server |
| CCE-82902-8 |
Verify Group Who Owns SSH Server config file |
root |
via chgrp |
To properly set the group owner of /etc/ssh/sshd_config, run the command: $ sudo chgrp root /etc/ssh/sshd_config |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-17(a),AC-6(1),CM-6(a) |
NaN |
5.2.1 |
SRG-OS-000480-GPOS-00227 |
SSH Server |
| CCE-80218-1 |
Remove SSH Server firewalld Firewall exception (Unusual) |
ssh |
via firewall-cmd |
By default, inbound connections to SSH's port are allowed. If the SSH server is not being used, this exception should be removed from the firewall configuration. To configure firewalld to prevent access, run the following command(s): firewall-cmd --permanent --remove-service=ssh |
If inbound SSH connections are not expected, disallowing access to the SSH port will avoid possible exploitation of the port by an attacker. |
unknown |
NaN |
NaN |
NaN |
NaN |
SSH Server |
| CCE-27485-2 |
Verify Permissions on SSH Server Private *_key Key Files |
640 |
via chmod |
To properly set the permissions of /etc/ssh/*_key, run the command: $ sudo chmod 0640 /etc/ssh/*_key |
If an unauthorized user obtains the private SSH host key file, the host could be impersonated. |
medium |
AC-17(a),AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
SSH Server |
| CCE-27311-0 |
Verify Permissions on SSH Server Public *.pub Key Files |
644 |
via chmod |
To properly set the permissions of /etc/ssh/*.pub, run the command: $ sudo chmod 0644 /etc/ssh/*.pub |
If a public host key file is modified by an unauthorized user, the SSH service may be compromised. |
medium |
AC-17(a),AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
SSH Server |
| CCE-80223-1 |
Enable Use of Privilege Separation |
sandbox |
/etc/ssh/sshd_config |
When enabled, SSH will create an unprivileged child process that has the privilege of the authenticated user. To enable privilege separation in SSH, add or correct the following line in the /etc/ssh/sshd_config file: UsePrivilegeSeparation |
SSH daemon privilege separation causes the SSH process to drop root privileges when not needed which would decrease the impact of software vulnerabilities in the unprivileged section. |
medium |
AC-17(a),AC-6,CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-80645-5 |
Set LogLevel to INFO |
INFO |
/etc/ssh/sshd_config |
The INFO parameter specifices that record login and logout activity will be logged. To specify the log level in SSH, add or correct the following line in the /etc/ssh/sshd_config file: LogLevel INFO |
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 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. |
low |
AC-17(a),CM-6(a) |
NaN |
5.2.3 |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-27363-1 |
Do Not Allow SSH Environment Options |
no |
/etc/ssh/sshd_config |
To ensure users are not able to override environment variables of the SSH daemon, add or correct the following line in /etc/ssh/sshd_config: PermitUserEnvironment no |
SSH environment options potentially allow users to bypass access restriction in some configurations. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
NaN |
5.2.10 |
SRG-OS-000480-GPOS-00229 |
Configure OpenSSH Server if Necessary |
| CCE-80225-6 |
Enable SSH Print Last Log |
yes |
/etc/ssh/sshd_config |
When enabled, SSH will display the date and time of the last successful account logon. To enable LastLog in SSH, add or correct the following line in the /etc/ssh/sshd_config file: PrintLastLog yes |
Providing users feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use. |
medium |
AC-17(a),AC-9,CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-27455-5 |
Use Only FIPS 140-2 Validated MACs |
configure |
/etc/ssh/sshd_config |
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-256,hmac-sha1 The man page sshd_config(5) contains a list of supported MACs. Only the following message authentication codes are FIPS 140-2 certified on Red Hat Enterprise Linux 7: - hmac-sha1 - hmac-sha2-256 - hmac-sha2-512 - hmac-sha1-etm@openssh.com - hmac-sha2-256-etm@openssh.com - hmac-sha2-512-etm@openssh.com Any combination of the above MACs will pass this check. Official FIPS 140-2 paperwork for Red Hat Enterprise Linux 7 can be found at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp2630.pdf The rule is parametrized to use the following MACs: . |
DoD Information Systems are required to use FIPS-approved cryptographic hash functions. The only SSHv2 hash algorithms meeting this requirement is SHA2. |
medium |
AC-17(2),AC-17(a),CM-6(a),MA-4(6),SC-12(2),SC-12(3),SC-13 |
NaN |
5.2.12 |
SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093,SRG-OS-000394-GPOS-00174 |
Configure OpenSSH Server if Necessary |
| CCE-80221-5 |
Disable Kerberos Authentication |
no |
/etc/ssh/sshd_config |
Unless needed, SSH should not permit extraneous or unnecessary authentication mechanisms like Kerberos. To disable Kerberos authentication, add or correct the following line in the /etc/ssh/sshd_config file: KerberosAuthentication no |
Kerberos authentication for SSH is often implemented using GSSAPI. If Kerberos is enabled through SSH, the SSH daemon provides a means of access to the system's Kerberos implementation. Vulnerabilities in the system's Kerberos implementations may be subject to exploitation. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
FTP_ITC_EXT.1 |
NaN |
SRG-OS-000364-GPOS-00151 |
Configure OpenSSH Server if Necessary |
| CCE-80224-9 |
Disable Compression Or Set Compression to delayed |
no |
/etc/ssh/sshd_config |
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 |
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. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-80372-6 |
Disable SSH Support for User Known Hosts |
yes |
/etc/ssh/sshd_config |
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 |
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. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
FIA_UAU.1 |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-27377-1 |
Disable SSH Support for .rhosts Files |
yes |
/etc/ssh/sshd_config |
SSH can emulate the behavior of the obsolete rsh command in allowing users to enable insecure access to their accounts via .rhosts files. To ensure this behavior is disabled, add or correct the following line in /etc/ssh/sshd_config: IgnoreRhosts yes |
SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
FIA_UAU.1 |
5.2.6 |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-27433-2 |
Set SSH Idle Timeout Interval |
600 |
/etc/ssh/sshd_config |
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. |
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. |
medium |
AC-12,AC-17(a),AC-17(a),AC-2(5),CM-6(a),CM-6(a),SC-10 |
NaN |
5.2.12 |
SRG-OS-000126-GPOS-00066,SRG-OS-000163-GPOS-00072,SRG-OS-000279-GPOS-00109,SRG-OS-000395-GPOS-00175 |
Configure OpenSSH Server if Necessary |
| CCE-27082-7 |
Set SSH Client Alive Max Count |
0 |
/etc/ssh/sshd_config |
To ensure the SSH idle timeout occurs precisely when the ClientAliveInterval is set, edit /etc/ssh/sshd_config as follows: ClientAliveCountMax |
This ensures a user login will be terminated as soon as the ClientAliveInterval is reached. |
medium |
AC-12,AC-17(a),AC-2(5),CM-6(a),SC-10 |
NaN |
5.2.12 |
SRG-OS-000163-GPOS-00072,SRG-OS-000279-GPOS-00109 |
Configure OpenSSH Server if Necessary |
| CCE-83359-0 |
Disable X11 Forwarding |
no |
/etc/ssh/sshd_config |
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. To disable X11 Forwarding, add or correct the following line in /etc/ssh/sshd_config: X11Forwarding no |
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. |
low |
NaN |
NaN |
5.2.4 |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-27295-5 |
Use Only FIPS 140-2 Validated Ciphers |
configure |
/etc/ssh/sshd_config |
Limit the ciphers to those algorithms which are FIPS-approved. Counter (CTR) mode is also preferred over cipher-block chaining (CBC) mode. The following line in /etc/ssh/sshd_config demonstrates use of FIPS-approved ciphers: Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc The man page sshd_config(5) contains a list of supported ciphers. Only the following ciphers are FIPS 140-2 certified on Red Hat Enterprise Linux 7: - aes128-ctr - aes192-ctr - aes256-ctr - aes128-cbc - aes192-cbc - aes256-cbc - 3des-cbc - rijndael-cbc@lysator.liu.se Any combination of the above ciphers will pass this check. Official FIPS 140-2 paperwork for Red Hat Enterprise Linux 7 can be found at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp2630.pdf The rule is parametrized to use the following 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 Red Hat Enterprise Linux 7. |
medium |
AC-17(2),AC-17(a),CM-6(a),IA-5(1)(c),MA-4(6),SC-12(2),SC-12(3),SC-13 |
NaN |
5.2.10 |
SRG-OS-000033-GPOS-00014,SRG-OS-000120-GPOS-00061,SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093,SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174 |
Configure OpenSSH Server if Necessary |
| CCE-80226-4 |
Enable Encrypted X11 Forwarding |
yes |
/etc/ssh/sshd_config |
By default, remote X11 connections are not encrypted when initiated by users. SSH has the capability to encrypt remote X11 connections when SSH's X11Forwarding option is enabled. To enable X11 Forwarding, add or correct the following line in /etc/ssh/sshd_config: X11Forwarding yes |
Non-encrypted X displays allow an attacker to capture keystrokes and to execute commands remotely. |
high |
AC-17(2),AC-17(a),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-82363-3 |
Use Only Strong Ciphers |
configure |
/etc/ssh/sshd_config |
Limit the ciphers to strong algorithms. Counter (CTR) mode is also preferred over cipher-block chaining (CBC) mode. The following line in /etc/ssh/sshd_config demonstrates use of those ciphers: Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr The man page sshd_config(5) contains a list of supported ciphers. |
Based on research conducted at various institutions, it was determined that the symmetric portion of the SSH Transport Protocol (as described in RFC 4253) has security weaknesses that allowed recovery of up to 32 bits of plaintext from a block of ciphertext that was encrypted with the Cipher Block Chaining (CBD) method. From that research, new Counter mode algorithms (as described in RFC4344) were designed that are not vulnerable to these types of attacks and these algorithms are now recommended for standard use. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-27314-4 |
Enable SSH Warning Banner |
/etc/issue |
/etc/ssh/sshd_config |
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/issue Another section contains information on how to create an appropriate system-wide 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. |
medium |
AC-17(a),AC-8(a),AC-8(c),CM-6(a) |
FTA_TAB.1 |
5.2.15 |
SRG-OS-000023-GPOS-00006,SRG-OS-000024-GPOS-00007,SRG-OS-000228-GPOS-00088 |
Configure OpenSSH Server if Necessary |
| CCE-80361-9 |
Enable SSH Server firewalld Firewall Exception |
ssh |
via firewall-cmd |
By default, inbound connections to SSH's port are allowed. If the SSH server is being used but denied by the firewall, this exception should be added to the firewall configuration. To configure firewalld to allow access, run the following command(s): firewall-cmd --permanent --add-service=ssh |
If inbound SSH connections are expected, adding a firewall rule exception will allow remote access through the SSH port. |
medium |
AC-17(a),CM-6(b),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-82354-2 |
Set SSH authentication attempt limit |
3 |
/etc/ssh/sshd_config |
The MaxAuthTries parameter specifies the maximum number of authentication attempts permitted per connection. Once the number of failures reaches half this value, additional failures are logged. to set MaxAUthTries edit /etc/ssh/sshd_config as follows: MaxAuthTries |
Setting the MaxAuthTries parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. |
medium |
NaN |
NaN |
5.2.5 |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-80373-4 |
Disable SSH Support for Rhosts RSA Authentication |
no |
/etc/ssh/sshd_config |
SSH can allow authentication through the obsolete rsh command through the use of the authenticating user's SSH keys. This should be disabled. To ensure this behavior is disabled, add or correct the following line in /etc/ssh/sshd_config: RhostsRSAAuthentication no |
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. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
FIA_UAU.1 |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-80220-7 |
Disable GSSAPI Authentication |
no |
/etc/ssh/sshd_config |
Unless needed, SSH should not permit extraneous or unnecessary authentication mechanisms like GSSAPI. To disable GSSAPI authentication, add or correct the following line in the /etc/ssh/sshd_config file: GSSAPIAuthentication no |
GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, increasing the attack surface of the system. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
FTP_ITC_EXT.1 |
NaN |
SRG-OS-000364-GPOS-00151 |
Configure OpenSSH Server if Necessary |
| CCE-27445-6 |
Disable SSH Root Login |
no |
/etc/ssh/sshd_config |
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 |
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. |
medium |
AC-17(a),AC-6(2),CM-6(a),CM-7(a),CM-7(b),IA-2,IA-2(5) |
FIA_UAU.1 |
5.2.8 |
SRG-OS-000109-GPOS-00056,SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-27471-2 |
Disable SSH Access via Empty Passwords |
no |
/etc/ssh/sshd_config |
To explicitly disallow SSH login from accounts with empty passwords, add or correct the following line in /etc/ssh/sshd_config: PermitEmptyPasswords no Any accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves 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. |
high |
AC-17(a),CM-6(a),CM-7(a),CM-7(b) |
FIA_UAU.1 |
5.2.9 |
SRG-OS-000106-GPOS-00053,SRG-OS-000480-GPOS-00229 |
Configure OpenSSH Server if Necessary |
| CCE-80222-3 |
Enable Use of Strict Mode Checking |
yes |
/etc/ssh/sshd_config |
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. To enable StrictModes in SSH, add or correct the following line in the /etc/ssh/sshd_config file: StrictModes yes |
If other users have access to modify user-specific SSH configuration files, they may be able to log into the system as another user. |
medium |
AC-17(a),AC-6,CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-27413-4 |
Disable Host-Based Authentication |
no |
/etc/ssh/sshd_config |
SSH's cryptographic host-based authentication is more secure than .rhosts authentication. However, it is not recommended that hosts unilaterally trust one another, even within an organization. To disable host-based authentication, add or correct the following line in /etc/ssh/sshd_config: HostbasedAuthentication no |
SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
medium |
AC-17(a),AC-3,CM-6(a),CM-7(a),CM-7(b) |
FIA_UAU.1 |
5.2.7 |
SRG-OS-000480-GPOS-00229 |
Configure OpenSSH Server if Necessary |
| CCE-80219-9 |
Limit Users' SSH Access |
configure |
/etc/ssh/sshd_config |
By default, the SSH configuration allows any user with an account to access the system. In order to specify the users that are allowed to login via SSH and deny all other users, add or correct the following line in the /etc/ssh/sshd_config file: DenyUsers USER1 USER2 Where USER1 and USER2 are valid user names. |
Specifying which accounts are allowed SSH access into the system reduces the possibility of unauthorized access to the system. |
unknown |
AC-3,CM-6(a) |
NaN |
NaN |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-82364-1 |
Use Only Strong MACs |
configure |
/etc/ssh/sshd_config |
Limit the MACs to strong hash algorithms. The following line in /etc/ssh/sshd_config demonstrates use of those MACs: MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160 |
MD5 and 96-bit MAC algorithms are considered weak and have been shown to increase exploitability in SSH downgrade attacks. Weak algorithms continue to have a great deal of attention as a weak spot that can be exploited with expanded computing power. An attacker that breaks the algorithm could take advantage of a MiTM position to decrypt the SSH tunnel and capture credentials and information |
medium |
NaN |
NaN |
NaN |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-82344-3 |
Disable PubkeyAuthentication Authentication |
no |
/etc/ssh/sshd_config |
Unless needed, SSH should not permit extraneous or unnecessary authentication mechanisms. To disable PubkeyAuthentication authentication, add or correct the following line in the /etc/ssh/sshd_config file: PubkeyAuthentication no |
PubkeyAuthentication authentication is used to provide additional authentication mechanisms to applications. Allowing PubkeyAuthentication authentication through SSH allows users to generate their own authentication tokens, increasing the attack surface of the system. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure OpenSSH Server if Necessary |
| CCE-27320-1 |
Allow Only SSH Protocol 2 |
2 |
/etc/ssh/sshd_config |
Only SSH protocol version 2 connections should be permitted. The default setting in /etc/ssh/sshd_config is correct, and can be verified by ensuring that the following line appears: Protocol 2 |
SSH protocol version 1 is an insecure implementation of the SSH protocol and has many well-known vulnerability exploits. Exploits of the SSH daemon could provide immediate root access to the system. |
high |
AC-17(2),AC-17(a),CM-6(a),IA-5(1)(c),MA-4(6),SC-13 |
NaN |
5.2.2 |
SRG-OS-000074-GPOS-00042,SRG-OS-000480-GPOS-00227 |
Configure OpenSSH Server if Necessary |
| CCE-82419-3 |
Set SSH Daemon LogLevel to VERBOSE |
VERBOSE |
/etc/ssh/sshd_config |
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 the /etc/ssh/sshd_config file: LogLevel 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. |
medium |
AC-17(1),AC-17(a),CM-6(a) |
NaN |
NaN |
SRG-OS-000032-GPOS-00013 |
Configure OpenSSH Server if Necessary |
| CCE-82933-3 |
Uninstall nfs-utils Package |
remove |
via yum |
The nfs-utils package can be removed with the following command: $ sudo yum erase nfs-utils |
nfs-utils provides a daemon for the kernel NFS server and related tools. This package also contains the showmount program. showmount queries the mount daemon on a remote host for information about the Network File System (NFS) server on the remote host. For example, showmount can display the clients which are mounted on that host. |
low |
NaN |
NaN |
NaN |
SRG-OS-000095-GPOS-00049 |
NFS and RPC |
| CCE-80235-5 |
Configure mountd to use static port |
configure |
via /etc/sysconfig/nfs |
Configure the mountd daemon to use a static port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line: MOUNTD_PORT=statd-port Where mountd-port is a port which is not used by any other service on your network. |
Restricting services to always use a given port enables firewalling to be done more effectively. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure NFS Services to Use Fixed Ports (NFSv3 and NFSv2) |
| CCE-80232-2 |
Configure lockd to use static TCP port |
configure |
via /etc/sysconfig/nfs |
Configure the lockd daemon to use a static TCP port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line: LOCKD_TCPPORT=lockd-port Where lockd-port is a port which is not used by any other service on your network. |
Restrict service to always use a given port, so that firewalling can be done effectively. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure NFS Services to Use Fixed Ports (NFSv3 and NFSv2) |
| CCE-80234-8 |
Configure statd to use static port |
configure |
via /etc/sysconfig/nfs |
Configure the statd daemon to use a static port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line: STATD_PORT=statd-port Where statd-port is a port which is not used by any other service on your network. |
Restricting services to always use a given port enables firewalling to be done more effectively. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure NFS Services to Use Fixed Ports (NFSv3 and NFSv2) |
| CCE-80233-0 |
Configure lockd to use static UDP port |
configure |
via /etc/sysconfig/nfs |
Configure the lockd daemon to use a static UDP port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line: LOCKD_UDPPORT=lockd-port Where lockd-port is a port which is not used by any other service on your network. |
Restricting services to always use a given port enables firewalling to be done more effectively. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure NFS Services to Use Fixed Ports (NFSv3 and NFSv2) |
| CCE-80243-9 |
Ensure Insecure File Locking is Not Allowed |
remove insecure_locks |
via /etc/exports |
By default the NFS server requires secure file-lock requests, which require credentials from the client in order to lock a file. Most NFS clients send credentials with file lock requests, however, there are a few clients that do not send credentials when requesting a file-lock, allowing the client to only be able to lock world-readable files. To get around this, the insecure_locks option can be used so these clients can access the desired export. This poses a security risk by potentially allowing the client access to data for which it does not have authorization. Remove any instances of the insecure_locks option from the file /etc/exports. |
Allowing insecure file locking could allow for sensitive data to be viewed or edited by an unauthorized user. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure NFS Servers |
| CCE-80242-1 |
Restrict NFS Clients to Privileged Ports |
remove insecure |
via /etc/exports |
By default, the server NFS implementation requires that all client requests be made from ports less than 1024. If your organization has control over systems connected to its network, and if NFS requests are prohibited at the border firewall, this offers some protection against malicious requests from unprivileged users. Therefore, the default should not be changed. To ensure that the default has not been changed, ensure no line in /etc/exports contains the option insecure. |
Allowing client requests to be made from ports higher than 1024 could allow a unprivileged user to initiate an NFS connection. If the unprivileged user account has been compromised, an attacker could gain access to data on the NFS server. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure NFS Servers |
| CCE-80241-3 |
Use Root-Squashing on All Exports |
remove no_root_squash |
via /etc/exports |
If a filesystem is exported using root squashing, requests from root on the client are considered to be unprivileged (mapped to a user such as nobody). This provides some mild protection against remote abuse of an NFS server. Root squashing is enabled by default, and should not be disabled. Ensure that no line in /etc/exports contains the option no_root_squash. |
If the NFS server allows root access to local file systems from remote hosts, this access could be used to compromise the system. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure NFS Servers |
| CCE-27464-7 |
Use Kerberos Security on All Exports |
krb5:krb5i:krb5p |
via /etc/exports |
Using Kerberos on all exported mounts prevents a malicious client or user from impersonating a system user. To cryptography authenticate users to the NFS server, add sec=krb5:krb5i:krb5p to each export in /etc/exports. |
When an NFS server is configured to use AUTH_SYS a selected userid and groupid are used to handle requests from the remote user. The userid and groupid could mistakenly or maliciously be set incorrectly. The AUTH_GSS method of authentication uses certificates on the server and client systems to more securely authenticate the remote mount request. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b),IA-2,IA-2(8),IA-2(9) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Configure NFS Servers |
| CCE-27458-9 |
Mount Remote Filesystems with Kerberos Security |
krb5:krb5i:krb5p |
via /etc/exports |
Add the sec=krb5:krb5i:krb5p option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts. |
When an NFS server is configured to use AUTH_SYS a selected userid and groupid are used to handle requests from the remote user. The userid and groupid could mistakenly or maliciously be set incorrectly. The AUTH_GSS method of authentication uses certificates on the server and client systems to more securely authenticate the remote mount request. |
medium |
AC-17(a),CM-6(a),CM-7(a),CM-7(b),IA-2,IA-2(8),IA-2(9) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Mount Remote Filesystems with Restrictive Options |
| CCE-80436-9 |
Mount Remote Filesystems with noexec |
noexec |
via /etc/fstab |
Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts. |
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. |
medium |
AC-6,AC-6(10),AC-6(8),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Mount Remote Filesystems with Restrictive Options |
| CCE-80239-7 |
Mount Remote Filesystems with nodev |
nodev |
via /etc/fstab |
Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts. |
Legitimate device files should only exist in the /dev directory. NFS mounts should not present device files to users. |
medium |
CM-6(a),MP-2 |
NaN |
NaN |
NaN |
Mount Remote Filesystems with Restrictive Options |
| CCE-80240-5 |
Mount Remote Filesystems with nosuid |
nosuid |
via /etc/fstab |
Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts. |
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. |
medium |
AC-6,AC-6(1),CM6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Mount Remote Filesystems with Restrictive Options |
| CCE-80237-1 |
Disable Network File System (nfs) |
disable |
via systemctl |
The Network File System (NFS) service allows remote hosts to mount and interact with shared filesystems on the local system. If the local system is not designated as a NFS server then this service should be disabled. The nfs service can be disabled with the following command: $ sudo systemctl disable nfs.service The nfs service can be masked with the following command: $ sudo systemctl mask nfs.service |
Unnecessary services should be disabled to decrease the attack surface of the system. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable NFS Server Daemons |
| CCE-80238-9 |
Disable Secure RPC Server Service (rpcsvcgssd) |
disable |
via systemctl |
The rpcsvcgssd service manages RPCSEC GSS contexts required to secure protocols that use RPC (most often Kerberos and NFS). The rpcsvcgssd service is the server-side of RPCSEC GSS. If the system does not require secure RPC then this service should be disabled. The rpcsvcgssd service can be disabled with the following command: $ sudo systemctl disable rpcsvcgssd.service The rpcsvcgssd service can be masked with the following command: $ sudo systemctl mask rpcsvcgssd.service |
Unnecessary services should be disabled to decrease the attack surface of the system. |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable NFS Server Daemons |
| CCE-80236-3 |
Specify UID and GID for Anonymous NFS Connections |
configure |
via /etc/exports |
To specify the UID and GID for remote root users, edit the /etc/exports file and add the following for each export: anonuid=value greater than UID_MAX from /etc/login.defs anongid=value greater than GID_MAX from /etc/login.defs Note that a value of "-1" is technically acceptable as this will randomize the anonuid and anongid values on a Red Hat Enterprise Linux 6 based NFS server. While acceptable from a security perspective, a value of -1 may cause interoperability issues, particularly with Red Hat Enterprise Linux 7 client systems. Alternatively, functionally equivalent values of 60001, 65534, 65535 may be used. |
Specifying the anonymous UID and GID ensures that the remote root user is mapped to a local account which has no permissions on the system. |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable NFS Server Daemons |
| CCE-80229-8 |
Disable Secure RPC Client Service (rpcgssd) |
disable |
via systemctl |
The rpcgssd service manages RPCSEC GSS contexts required to secure protocols that use RPC (most often Kerberos and NFS). The rpcgssd service is the client-side of RPCSEC GSS. If the system does not require secure RPC then this service should be disabled. The rpcgssd service can be disabled with the following command: $ sudo systemctl disable rpcgssd.service The rpcgssd service can be masked with the following command: $ sudo systemctl mask rpcgssd.service |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Services Used Only by NFS |
| CCE-80231-4 |
Disable RPC ID Mapping Service (rpcidmapd) |
disable |
via systemctl |
The rpcidmapd service is used to map user names and groups to UID and GID numbers on NFSv4 mounts. If NFS is not in use on the local system then this service should be disabled. The rpcidmapd service can be disabled with the following command: $ sudo systemctl disable rpcidmapd.service The rpcidmapd service can be masked with the following command: $ sudo systemctl mask rpcidmapd.service |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Services Used Only by NFS |
| CCE-80230-6 |
Disable rpcbind Service |
disable |
via systemctl |
The rpcbind utility maps RPC services to the ports on which they listen. RPC processes notify rpcbind when they start, registering the ports they are listening on and the RPC program numbers they expect to serve. The rpcbind service redirects the client to the proper port number so it can communicate with the requested service. If the system does not require RPC (such as for NFS servers) then this service should be disabled. The rpcbind service can be disabled with the following command: $ sudo systemctl disable rpcbind.service The rpcbind service can be masked with the following command: $ sudo systemctl mask rpcbind.service |
If the system does not require rpc based services, it is recommended that rpcbind be disabled to reduce the attack surface. |
low |
NaN |
NaN |
NaN |
NaN |
Disable Services Used Only by NFS |
| CCE-80228-0 |
Disable Network File System Lock Service (nfslock) |
disable |
via systemctl |
The Network File System Lock (nfslock) service starts the required remote procedure call (RPC) processes which allow clients to lock files on the server. If the local system is not configured to mount NFS filesystems then this service should be disabled. The nfslock service can be disabled with the following command: $ sudo systemctl disable nfslock.service The nfslock service can be masked with the following command: $ sudo systemctl mask nfslock.service |
NaN |
unknown |
NaN |
NaN |
NaN |
NaN |
Disable Services Used Only by NFS |
| CCE-80246-2 |
Install vsftpd Package |
install |
via yum |
If this system must operate as an FTP server, install the vsftpd package via the standard channels. The vsftpd package can be installed with the following command: $ sudo yum install vsftpd |
After Red Hat Enterprise Linux 2.1, Red Hat switched from distributing wu-ftpd with Red Hat Enterprise Linux to distributing vsftpd. For security and for consistency with future Red Hat releases, the use of vsftpd is recommended. |
low |
CM-6(a) |
NaN |
NaN |
NaN |
Use vsftpd to Provide FTP Service if Necessary |
| CCE-80245-4 |
Uninstall vsftpd Package |
remove |
via yum |
The vsftpd package can be removed with the following command: $ sudo yum erase vsftpd |
Removing the vsftpd package decreases the risk of its accidental activation. |
high |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Disable vsftpd if Possible |
| CCE-80244-7 |
Disable vsftpd Service |
disable |
via systemctl |
The vsftpd service can be disabled with the following command: $ sudo systemctl disable vsftpd.service The vsftpd service can be masked with the following command: $ sudo systemctl mask vsftpd.service |
Running FTP server software provides a network-based avenue of attack, and should be disabled if not needed. Furthermore, the FTP protocol is unencrypted and creates a risk of compromising sensitive information. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable vsftpd if Possible |
| CCE-80248-8 |
Create Warning Banners for All FTP Users |
configure |
via /etc/vsftpd/vsftpd.conf |
Edit the vsftpd configuration file, which resides at /etc/vsftpd/vsftpd.conf by default. Add or correct the following configuration options: banner_file=/etc/issue |
This setting will cause the system greeting banner to be used for FTP connections as well. |
medium |
NaN |
NaN |
NaN |
NaN |
Configure vsftpd to Provide FTP Service if Necessary |
| CCE-80247-0 |
Enable Logging of All FTP Transactions |
YES |
via /etc/vsftpd/vsftpd.conf |
Add or correct the following configuration options within the vsftpd configuration file, located at /etc/vsftpd/vsftpd.conf: xferlog_enable=YES xferlog_std_format=NO log_ftp_protocol=YES |
To trace malicious activity facilitated by the FTP service, it must be configured to ensure that all commands sent to the FTP server are logged using the verbose vsftpd log format. The default vsftpd log file is /var/log/vsftpd.log. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure vsftpd to Provide FTP Service if Necessary |
| CCE-80250-4 |
Disable FTP Uploads if Possible |
NO |
via /etc/vsftpd/vsftpd.conf |
Is there a mission-critical reason for users to upload files via FTP? If not, edit the vsftpd configuration file to add or correct the following configuration options: write_enable=NO If FTP uploads are necessary, follow the guidance in the remainder of this section to secure these transactions as much as possible. |
Anonymous FTP can be a convenient way to make files available for universal download. However, it is less common to have a need to allow unauthenticated users to place files on the FTP server. If this must be done, it is necessary to ensure that files cannot be uploaded and downloaded from the same directory. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure vsftpd to Provide FTP Service if Necessary |
| CCE-80251-2 |
Place the FTP Home Directory on its Own Partition |
partition |
via /etc/fstab |
By default, the anonymous FTP root is the home directory of the FTP user account. The df command can be used to verify that this directory is on its own partition. |
If there is a mission-critical reason for anonymous users to upload files, precautions must be taken to prevent these users from filling a disk used by other services. |
unknown |
NaN |
NaN |
NaN |
NaN |
Configure vsftpd to Provide FTP Service if Necessary |
| CCE-80249-6 |
Restrict Access to Anonymous Users if Possible |
NO |
via /etc/vsftpd/vsftpd.conf |
Is there a mission-critical reason for users to transfer files to/from their own accounts using FTP, rather than using a secure protocol like SCP/SFTP? If not, edit the vsftpd configuration file. Add or correct the following configuration option: local_enable=NO If non-anonymous FTP logins are necessary, follow the guidance in the remainder of this section to secure these logins as much as possible. |
The use of non-anonymous FTP logins is strongly discouraged. Since SSH clients and servers are widely available, and since SSH provides support for a transfer mode which resembles FTP in user interface, there is no good reason to allow password-based FTP access.' |
medium |
AC-17(a),AC-3,CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Restrict the Set of Users Allowed to Access FTP |
| CCE-27323-5 |
Enable cron Service |
enable |
via systemctl |
The crond service is used to execute commands at preconfigured times. It is required by almost all systems to perform necessary maintenance tasks, such as notifying root of system activity. The crond service can be enabled with the following command: $ sudo systemctl enable crond.service |
Due to its usage for maintenance and security-supporting tasks, enabling the cron daemon is essential. |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
Cron and At Daemons |
| CCE-80345-2 |
Disable At Service (atd) |
disable |
via systemctl |
The at and batch commands can be used to schedule tasks that are meant to be executed only once. This allows delayed execution in a manner similar to cron, except that it is not recurring. The daemon atd keeps track of tasks scheduled via at and batch, and executes them at the specified time. The atd service can be disabled with the following command: $ sudo systemctl disable atd.service The atd service can be masked with the following command: $ sudo systemctl mask atd.service |
The atd service could be used by an unsophisticated insider to carry out activities outside of a normal login session, which could complicate accountability. Furthermore, the need to schedule tasks with at or batch is not common. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Cron and At Daemons |
| CCE-82250-2 |
Verify Permissions on cron.weekly |
700 |
via chmod |
To properly set the permissions of /etc/cron.weekly, run the command: $ sudo chmod 0700 /etc/cron.weekly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should have the correct access rights to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.5 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82208-0 |
Verify Owner on cron.hourly |
root |
via chown |
To properly set the owner of /etc/cron.hourly, run the command: $ sudo chown root /etc/cron.hourly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct user to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.3 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82242-9 |
Verify Group Who Owns cron.weekly |
root |
via chgrp |
To properly set the group owner of /etc/cron.weekly, run the command: $ sudo chgrp root /etc/cron.weekly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.5 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82222-1 |
Verify Group Who Owns Crontab |
root |
via chgrp |
To properly set the group owner of /etc/crontab, run the command: $ sudo chgrp root /etc/crontab |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.2 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82217-1 |
Verify Owner on crontab |
root |
via chown |
To properly set the owner of /etc/crontab, run the command: $ sudo chown root /etc/crontab |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct user to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.2 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82255-1 |
Verify Group Who Owns cron.monthly |
root |
via chgrp |
To properly set the group owner of /etc/cron.monthly, run the command: $ sudo chgrp root /etc/cron.monthly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.6 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82232-0 |
Verify Group Who Owns cron.daily |
root |
via chgrp |
To properly set the group owner of /etc/cron.daily, run the command: $ sudo chgrp root /etc/cron.daily |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.4 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82246-0 |
Verify Owner on cron.weekly |
root |
via chown |
To properly set the owner of /etc/cron.weekly, run the command: $ sudo chown root /etc/cron.weekly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct user to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.5 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82236-1 |
Verify Owner on cron.daily |
root |
via chown |
To properly set the owner of /etc/cron.daily, run the command: $ sudo chown root /etc/cron.daily |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct user to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.4 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82259-3 |
Verify Owner on cron.monthly |
root |
via chown |
To properly set the owner of /etc/cron.monthly, run the command: $ sudo chown root /etc/cron.monthly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct user to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.6 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82205-6 |
Verify Permissions on crontab |
600 |
via chmod |
To properly set the permissions of /etc/crontab, run the command: $ sudo chmod 0600 /etc/crontab |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should have the correct access rights to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.2 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82276-7 |
Verify Permissions on cron.d |
700 |
via chmod |
To properly set the permissions of /etc/cron.d, run the command: $ sudo chmod 0700 /etc/cron.d |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should have the correct access rights to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.7 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82229-6 |
Verify Permissions on cron.hourly |
700 |
via chmod |
To properly set the permissions of /etc/cron.hourly, run the command: $ sudo chmod 0700 /etc/cron.hourly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should have the correct access rights to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.3 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82270-0 |
Verify Owner on cron.d |
root |
via chown |
To properly set the owner of /etc/cron.d, run the command: $ sudo chown root /etc/cron.d |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct user to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.7 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82239-5 |
Verify Permissions on cron.daily |
700 |
via chmod |
To properly set the permissions of /etc/cron.daily, run the command: $ sudo chmod 0700 /etc/cron.daily |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should have the correct access rights to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.4 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-80344-5 |
Disable anacron Service |
remove |
via yum |
The cronie-anacron package, which provides anacron functionality, is installed by default. The cronie-anacron package can be removed with the following command: $ sudo yum erase cronie-anacron |
The anacron service provides cron functionality for systems such as laptops and workstations that may be shut down during the normal times that cron jobs are scheduled to run. On systems which do not require this additional functionality, anacron could needlessly increase the possible attack surface for an intruder. |
unknown |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Cron and At Daemons |
| CCE-82226-2 |
Verify Group Who Owns cron.hourly |
root |
via chgrp |
To properly set the group owner of /etc/cron.hourly, run the command: $ sudo chgrp root /etc/cron.hourly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.3 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82262-7 |
Verify Permissions on cron.monthly |
700 |
via chmod |
To properly set the permissions of /etc/cron.monthly, run the command: $ sudo chmod 0700 /etc/cron.monthly |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should have the correct access rights to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.6 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-82265-0 |
Verify Group Who Owns cron.d |
root |
via chgrp |
To properly set the group owner of /etc/cron.d, run the command: $ sudo chgrp root /etc/cron.d |
Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the correct group to prevent unauthorized changes. |
medium |
AC-6(1),CM-6(a) |
NaN |
5.1.7 |
SRG-OS-000480-GPOS-00227 |
Cron and At Daemons |
| CCE-80378-3 |
Verify User Who Owns /etc/cron.allow file |
root |
via chown |
If /etc/cron.allow exists, it must be owned by root. To properly set the owner of /etc/cron.allow, run the command: $ sudo chown root /etc/cron.allow |
If the owner of the cron.allow file is not set to root, the possibility exists for an unauthorized user to view or edit sensitive information. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Restrict at and cron to Authorized Users if Necessary |
| CCE-80379-1 |
Verify Group Who Owns /etc/cron.allow file |
root |
via chgrp |
If /etc/cron.allow exists, it must be group-owned by root. To properly set the group owner of /etc/cron.allow, run the command: $ sudo chgrp root /etc/cron.allow |
If the owner of the cron.allow file is not set to root, the possibility exists for an unauthorized user to view or edit sensitive information. |
medium |
AC-6(1),CM-6(a) |
NaN |
NaN |
SRG-OS-000480-GPOS-00227 |
Restrict at and cron to Authorized Users if Necessary |
| CCE-80440-1 |
Enable the Docker service |
enable |
via systemctl |
The docker service is commonly needed to create containers. The docker service can be enabled with the following command: $ sudo systemctl enable docker.service |
To be able to find any problems with misconfiguration of the docker daemon and running containers, the docker service has to be enabled. |
medium |
NaN |
NaN |
NaN |
NaN |
Docker Service |
| CCE-80442-7 |
Ensure SELinux support is enabled in Docker |
--selinux-enabled |
via /etc/sysconfig/docker |
To enable the SELinux for the Docker service, the Docker service must be configured to run the Docker daemon with --selinux-enabled option. In /etc/sysconfig/docker configuration file, add or correct the following line to enable SELinux support in the Docker daemon: OPTIONS='--selinux-enabled' |
If SELinux is not explicitely enabled in the Docker daemon configuration, Docker does not use SELinux which means Docker runs unconfined, and SELinux will not provide security separation for Docker container processes. However enabling SELinux for the Docker service prevents an attacker or rogue container from attacking other container processes and content as well as prevents taking over the host operating system. |
high |
NaN |
NaN |
NaN |
NaN |
Docker Service |
| CCE-80441-9 |
Use direct-lvm with the Device Mapper Storage Driver |
configure |
via /etc/docker/daemon.json |
To use Docker in production with the device mapper storage driver, the Docker daemon should be configured to use direct-lvm instead of loopback device as a storage. For setting up the LVM and configuring Docker, see the Docker Device Mapper Storage Documentation. |
For using Docker in production, the device mapper storage driver with loopback devices is discouraged. The suggested way of configuring device mapper storage driver is direct-lvm. Choosing the right storage driver and backing filesystem is crucial to stability and performance. |
low |
NaN |
NaN |
NaN |
NaN |
Docker Service |
| CCE-83419-2 |
The Chrony package is installed |
install |
via yum |
System time should be synchronized between all systems in an environment. This is typically done by establishing an authoritative time server or set of servers and having all systems synchronize their clocks to them. The chrony package can be installed with the following command: $ sudo yum install chrony |
Time synchronization is important to support time sensitive security mechanisms like Kerberos and also ensures log files have consistent time records across the enterprise, which aids in forensic investigations. |
medium |
NaN |
NaN |
2.2.1.1 |
NaN |
Network Time Protocol |
| CCE-27444-9 |
Enable the NTP Daemon |
enable |
via systemctl |
Run the following command to determine the current status of the chronyd service: $ systemctl is-active chronyd If the service is running, it should return the following: active Note: The chronyd daemon is enabled by default. Run the following command to determine the current status of the ntpd service: $ systemctl is-active ntpd If the service is running, it should return the following: active Note: The ntpd daemon is not enabled by default. Though as mentioned in the previous sections in certain environments the ntpd daemon might be preferred to be used rather than the chronyd one. Refer to: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html for guidance which NTP daemon to choose depending on the environment used. |
Enabling some of chronyd or ntpd services ensures that the NTP daemon will be running and that the system will synchronize its time to any servers specified. This is important whether the system is configured to be a client (and synchronize only its own clock) or it is also acting as an NTP server to other systems. Synchronizing time is essential for authentication services such as Kerberos, but it is also important for maintaining accurate logs and auditing possible security breaches. The chronyd and ntpd NTP daemons offer all of the functionality of ntpdate, which is now deprecated. Additional information on this is available at http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate |
medium |
AU-8(1)(a),CM-6(a) |
NaN |
NaN |
NaN |
Network Time Protocol |
| CCE-83420-0 |
The Chronyd service is enabled |
enable |
via systemctl |
chrony is a daemon which implements the Network Time Protocol (NTP) is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. More information on chrony can be found at http://chrony.tuxfamily.org/. Chrony can be configured to be a client and/or a server. To enable Chronyd service, you can run: # systemctl enable chronyd.service This recommendation only applies if chrony is in use on the system. |
If chrony is in use on the system proper configuration is vital to ensuring time synchronization is working properly. |
medium |
NaN |
NaN |
2.2.1.3 |
NaN |
Network Time Protocol |
| CCE-27278-1 |
Specify a Remote NTP Server |
configure |
via /etc/chrony.conf or /etc/ntp.conf |
Depending on specific functional requirements of a concrete production environment, the Red Hat Enterprise Linux 7 system can be configured to utilize the services of the chronyd NTP daemon (the default), or services of the ntpd NTP daemon. Refer to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html for more detailed comparison of the features of both of the choices, and for further guidance how to choose between the two NTP daemons. To specify a remote NTP server for time synchronization, perform the following: if the system is configured to use the chronyd as the NTP daemon (the default), edit the file /etc/chrony.conf as follows, if the system is configured to use the ntpd as the NTP daemon, edit the file /etc/ntp.conf as documented below. Add or correct the following lines, substituting the IP or hostname of a remote NTP server for ntpserver: server ntpserver This instructs the NTP software to contact that remote server to obtain time data. |
Synchronizing with an NTP server makes it possible to collate system logs from multiple sources or correlate computer events with real time events. |
medium |
AU-8(1)(a),AU-8(2),CM-6(a) |
NaN |
NaN |
NaN |
Network Time Protocol |
| CCE-82878-0 |
Ensure that chronyd is running under chrony user account |
-u chrony |
/etc/sysconfig/chronyd |
chrony is a daemon which implements the Network Time Protocol (NTP). It is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. More information on chrony can be found at http://chrony.tuxfamily.org/. Chrony can be configured to be a client and/or a server. To ensure that chronyd is running under chrony user account, Add or edit the OPTIONS variable in /etc/sysconfig/chronyd to include -u chrony: OPTIONS="-u chrony" This recommendation only applies if chrony is in use on the system. |
If chrony is in use on the system proper configuration is vital to ensuring time synchronization is working properly. |
medium |
NaN |
NaN |
2.2.1.3 |
NaN |
Network Time Protocol |
| CCE-27012-4 |
Specify Additional Remote NTP Servers |
configure |
via /etc/chrony.conf or /etc/ntp.conf |
Depending on specific functional requirements of a concrete production environment, the Red Hat Enterprise Linux 7 system can be configured to utilize the services of the chronyd NTP daemon (the default), or services of the ntpd NTP daemon. Refer to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html for more detailed comparison of the features of both of the choices, and for further guidance how to choose between the two NTP daemons. Additional NTP servers can be specified for time synchronization. To do so, perform the following: if the system is configured to use the chronyd as the NTP daemon (the default), edit the file /etc/chrony.conf as follows, if the system is configured to use the ntpd as the NTP daemon, edit the file /etc/ntp.conf as documented below. Add additional lines of the following form, substituting the IP address or hostname of a remote NTP server for ntpserver: server ntpserver |
Specifying additional NTP servers increases the availability of accurate time data, in the event that one of the specified servers becomes unavailable. This is typical for a system acting as an NTP server for other systems. |
medium |
AU-8(1)(a),AU-8(2),CM-6(a) |
NaN |
NaN |
NaN |
Network Time Protocol |
| CCE-84299-7 |
Configure server restrictions for ntpd |
configure |
via /etc/ntp.conf |
ntpd is a daemon which implements the Network Time Protocol (NTP). It is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. More information on NTP can be found at http://www.ntp.org. ntp can be configured to be a client and/or a server. To ensure that ntpd implements correct server restrictions, make sure that the following lines exist in the file /etc/ntpd.conf: restrict -4 default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery This recommendation only applies if ntp is in use on the system. |
If ntp is in use on the system proper configuration is vital to ensuring time synchronization is working properly. |
medium |
NaN |
NaN |
2.2.1.2 |
NaN |
Network Time Protocol |
| CCE-80439-3 |
Configure Time Service Maxpoll Interval |
10 |
via /etc/chrony.conf or /etc/ntp.conf |
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: maxpoll |
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. |
medium |
AU-8(1)(b),CM-6(a) |
NaN |
NaN |
SRG-OS-000355-GPOS-00143,SRG-OS-000356-GPOS-00144 |
Network Time Protocol |
| CCE-84295-5 |
Configure ntpd To Run As ntp User |
-u ntp:ntp |
via /etc/ntp.conf |
ntp is a daemon which implements the Network Time Protocol (NTP). It is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. More information on NTP can be found at http://www.ntp.org. ntp can be configured to be a client and/or a server. To ensure that ntpd is running as ntp user, Add or edit the OPTIONS variable in /etc/sysconfig/ntpd to include ' -u ntp:ntp ': OPTIONS="-u ntp:ntp" This recommendation only applies if ntp is in use on the system. |
If ntp is in use on the system proper configuration is vital to ensuring time synchronization is working properly. Running ntpd under dedicated user accounts limits the attack surface for potential attacker exploiting security flaws in the daemon or the protocol. |
medium |
NaN |
NaN |
2.2.1.2 |
NaN |
Network Time Protocol |
| CCE-83418-4 |
A remote time server for Chrony is configured |
configure |
via /etc/chrony.conf |
Chrony is a daemon which implements the Network Time Protocol (NTP). It is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. More information on chrony can be found at http://chrony.tuxfamily.org/. Chrony can be configured to be a client and/or a server. Add or edit server or pool lines to /etc/chrony.conf as appropriate: server <remote-server> Multiple servers may be configured. |
If chrony is in use on the system proper configuration is vital to ensuring time synchronization is working properly. |
medium |
NaN |
NaN |
2.2.1.3 |
NaN |
Network Time Protocol |
| CCE-80326-2 |
Uninstall bind Package |
remove |
via yum |
The named service is provided by the bind package. The bind package can be removed with the following command: $ sudo yum erase bind |
If there is no need to make DNS server software available, removing it provides a safeguard against its activation. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable DNS Server |
| CCE-80325-4 |
Disable named Service |
disable |
via systemctl |
The named service can be disabled with the following command: $ sudo systemctl disable named.service The named service can be masked with the following command: $ sudo systemctl mask named.service |
All network services involve some risk of compromise due to implementation flaws and should be disabled if possible. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Disable DNS Server |
| CCE-80328-8 |
Authenticate Zone Transfers |
configure |
via /etc/named.conf |
If it is necessary for a secondary nameserver to receive zone data via zone transfer from the primary server, follow the instructions here. Use dnssec-keygen to create a symmetric key file in the current directory: $ cd /tmp $ sudo dnssec-keygen -a HMAC-MD5 -b 128 -n HOST dns.example.com Kdns.example.com .+aaa +iiiii This output is the name of a file containing the new key. Read the file to find the base64-encoded key string: $ sudo cat Kdns.example.com .+NNN +MMMMM .key dns.example.com IN KEY 512 3 157 base64-key-string Add the directives to /etc/named.conf on the primary server: key zone-transfer-key { algorithm hmac-md5; secret "base64-key-string "; }; zone "example.com " IN { type master; allow-transfer { key zone-transfer-key; }; ... }; Add the directives below to /etc/named.conf on the secondary nameserver: key zone-transfer-key { algorithm hmac-md5; secret "base64-key-string "; }; server IP-OF-MASTER { keys { zone-transfer-key; }; }; zone "example.com " IN { type slave; masters { IP-OF-MASTER ; }; ... }; |
The BIND transaction signature (TSIG) functionality allows primary and secondary nameservers to use a shared secret to verify authorization to perform zone transfers. This method is more secure than using IP-based limiting to restrict nameserver access, since IP addresses can be easily spoofed. However, if you cannot configure TSIG between your servers because, for instance, the secondary nameserver is not under your control and its administrators are unwilling to configure TSIG, you can configure an allow-transfer directive with numerical IP addresses or ACLs as a last resort. |
medium |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Protect DNS Data from Tampering or Attack |
| CCE-80329-6 |
Disable Dynamic Updates |
disable |
via /etc/named.conf |
Is there a mission-critical reason to enable the risky dynamic update functionality? If not, edit /etc/named.conf. For each zone specification, correct the following directive if necessary: zone "example.com " IN { allow-update { none; }; ... }; |
Dynamic updates allow remote servers to add, delete, or modify any entries in your zone file. Therefore, they should be considered highly risky, and disabled unless there is a very good reason for their use. If dynamic updates must be allowed, IP-based ACLs are insufficient protection, since they are easily spoofed. Instead, use TSIG keys (see the previous section for an example), and consider using the update-policy directive to restrict changes to only the precise type of change needed. |
unknown |
NaN |
NaN |
NaN |
NaN |
Protect DNS Data from Tampering or Attack |
| CCE-80327-0 |
Disable Zone Transfers from the Nameserver |
disable |
via /etc/named.conf |
Is it necessary for a secondary nameserver to receive zone data via zone transfer from the primary server? If not, follow the instructions in this section. If so, see the next section for instructions on protecting zone transfers. Add or correct the following directive within /etc/named.conf: options { allow-transfer { none; }; ... } |
If both the primary and secondary nameserver are under your control, or if you have only one nameserver, it may be possible to use an external configuration management mechanism to distribute zone updates. In that case, it is not necessary to allow zone transfers within BIND itself, so they should be disabled to avoid the potential for abuse. |
unknown |
NaN |
NaN |
NaN |
NaN |
Protect DNS Data from Tampering or Attack |
| CCE-82884-8 |
Ensure LDAP client is not installed |
remove |
via yum |
The Lightweight Directory Access Protocol (LDAP) is a service that provides a method for looking up information from a central database. The openldap-clients package can be removed with the following command: $ sudo yum erase openldap-clients |
If the system does not need to act as an LDAP client, it is recommended that the software is removed to reduce the potential attack surface. |
low |
NaN |
NaN |
2.3.5 |
NaN |
Configure OpenLDAP Clients |
| CCE-80291-8 |
Configure LDAP Client to Use TLS For All Transactions |
configure |
via /etc/pam_ldap.conf |
This check verifies cryptography has been implemented to protect the integrity of remote LDAP authentication sessions. To determine if LDAP is being used for authentication, use the following command: $ sudo grep -i useldapauth /etc/sysconfig/authconfig If USELDAPAUTH=yes, then LDAP is being used. To check if LDAP is configured to use TLS, use the following command: $ sudo grep -i ssl /etc/pam_ldap.conf |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. The ssl directive specifies whether to use TLS or not. If not specified it will default to no. It should be set to start_tls rather than doing LDAP over SSL. |
medium |
AC-17(2),AC-17(a),CM-6(a),SC-12(a),SC-12(b) |
NaN |
NaN |
SRG-OS-000250-GPOS-00093 |
Configure OpenLDAP Clients |
| CCE-80448-4 |
Enable the LDAP Client For Use in Authconfig |
useldapauth |
/etc/sysconfig/authconfig |
To determine if LDAP is being used for authentication, use the following command: $ sudo grep -i useldapauth /etc/sysconfig/authconfig If USELDAPAUTH=yes, then LDAP is being used. If not, set USELDAPAUTH to yes. |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. The ssl directive specifies whether to use TLS or not. If not specified it will default to no. It should be set to start_tls rather than doing LDAP over SSL. |
medium |
AC-17(a),CM-6(a) |
NaN |
NaN |
SRG-OS-000250-GPOS-00093 |
Configure OpenLDAP Clients |
| CCE-80292-6 |
Configure Certificate Directives for LDAP Use of TLS |
configure |
via /etc/nslcd.conf |
Ensure a copy of a trusted CA certificate has been placed in the file /etc/pki/tls/CA/cacert.pem. Configure LDAP to enforce TLS use and to trust certificates signed by that CA. First, edit the file /etc/nslcd.conf, and add or correct either of the following lines: tls_cacertdir /etc/pki/tls/CA or tls_cacertfile /etc/pki/tls/CA/cacert.pem Then review the LDAP server and ensure TLS has been configured. |
The tls_cacertdir or tls_cacertfile directives are required when tls_checkpeer is configured (which is the default for openldap versions 2.1 and up). These directives define the path to the trust certificates signed by the site CA. |
medium |
CM-6(a) |
NaN |
NaN |
NaN |
Configure OpenLDAP Clients |
| CCE-80293-4 |
Uninstall openldap-servers Package |
remove |
via yum |
The openldap-servers RPM is not installed by default on a Red Hat Enterprise Linux 7 system. It is needed only by the OpenLDAP server, not by the clients which use LDAP for authentication. If the system is not intended for use as an LDAP Server it should be removed. |
Unnecessary packages should not be installed to decrease the attack surface of the system. While this software is clearly essential on an LDAP server, it is not necessary on typical desktop or workstation systems. |
low |
CM-6(a),CM-7(a),CM-7(b) |
NaN |
NaN |
NaN |
Configure OpenLDAP Server |