Rules In Red Hat Enterprise Linux 7 Security Technical Implementation Guide


V-ID CCI CAT Title Description Check Procedures Fixtext
RHEL-07-010010 CCI-001494 high The file permissions, ownership, and group membership of system files and commands must match the vendor values. Discretionary access control is weakened if a user or group has access permissions to system files and directories greater than the default. Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000278-GPOS-00108 Verify the file permissions, ownership, and group membership of system files and commands match the vendor values. Check the file permissions, ownership, and group membership of system files and commands with the following command: # rpm -Va | grep '^.M' If there is any output from the command, this is a finding. Run the following command to determine which package owns the file: # rpm -qf <filename> Reset the permissions of files within a package with the following command: #rpm --setperms <packagename> Reset the user and group ownership of files within a package with the following command: #rpm --setugids <packagename>
RHEL-07-010020 CCI-000663 high The cryptographic hash of system files and commands must match vendor values. Without cryptographic integrity protections, system command and files 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 secret key used to generate the hash. Verify the cryptographic hash of system files and commands match the vendor values. Check the cryptographic hash of system files and commands with the following command: Note: System configuration files (indicated by a "c" in the second column) are expected to change over time. Unusual modifications should be investigated through the system audit log. # rpm -Va | grep '^..5' If there is any output from the command for system binaries, this is a finding. 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>
RHEL-07-010030 CCI-000048 medium The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon. Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088 Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Check to see if the operating system displays a banner at the logon screen with the following command: # grep banner-message-enable /etc/dconf/db/local.d/* banner-message-enable=true If banner-message-enable is set to false or is missing, this is a finding. Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command: # touch /etc/dconf/db/local.d/01-banner-message Add the following line to the [org/gnome/login-screen] section of the /etc/dconf/db/local.d/01-banner-message: [org/gnome/login-screen] banner-message-enable=true
RHEL-07-010031 CCI-000048 medium The operating system must display the approved Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon. Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088 Verify the operating system displays the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Check that the operating system displays the exact approved Standard Mandatory DoD Notice and Consent Banner text with the command: # grep banner-message-text /etc/dconf/db/local.d/* banner-message-text= ‘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.’ If the banner does not match the approved Standard Mandatory DoD Notice and Consent Banner, this is a finding. Configure the operating system to display the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the system. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command: # touch /etc/dconf/db/local.d/01-banner-message Add the following lines to the [org/gnome/login-screen] section of the /etc/dconf/db/local.d/01-banner-message: [org/gnome/login-screen] banner-message-text=’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.’
RHEL-07-010040 CCI-000048 medium The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon. Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007 Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a command line user logon. Check to see if the operating system displays a banner at the command line logon screen with the following command: # more /etc/issue The command should return the following text: “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.” If the operating system does not display a graphical logon banner or the banner does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding. If the text in the /etc/issue file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding. Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the command line by editing the /etc/issue file. Replace the default text with the Standard Mandatory DoD Notice and Consent Banner. The DoD required text is: "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."
RHEL-07-010060 CCI-000056 medium The operating system must enable a user session lock until that user re-establishes access using established identification and authentication procedures. A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. The session lock is implemented at the point where session activity can be determined. Regardless of where the session lock is determined and implemented, once invoked, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system. Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011 Verify the operating system enables a user's session lock until that user re-establishes access using established identification and authentication procedures. The screen program must be installed to lock sessions on the console. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Check to see if the screen lock is enabled with the following command: # grep -i lock-enabled /etc/dconf/db/local.d/00-screensaver lock-enabled=true If the "lock-enabled" setting is missing or is not set to true, this is a finding. Configure the operating system to enable a user's session lock until that user re-establishes access using established identification and authentication procedures. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: # touch /etc/dconf/db/local.d/00-screensaver Add the setting to enable screensaver locking to the file: [org/gnome/desktop/screensaver] lock-enabled=true After the setting has been set, run dconf update.
RHEL-07-010070 CCI-000057 medium The operating system must initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. Verify the operating system initiates a screensaver after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Check to see if GNOME is configured to display a screensaver after a 15 minute delay with the following command: # grep -i idle-delay /etc/dconf/db/local.d/* idle-delay=uint32 900 If the "idle-delay" setting is missing or is not set to “900” or less, this is a finding. Configure the operating system to initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: # touch /etc/dconf/db/local.d/00-screensaver Add the setting to enable screensaver/session locking after 15 minutes of inactivity: [org/gnome/desktop/screensaver] idle-delay=uint32 900 After the setting has been set, run dconf update.
RHEL-07-010074 CCI-000057 medium The operating system must initiate a session lock for graphical user interfaces when the screensaver is activated. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. Verify the operating system initiates a session lock a for graphical user interfaces when the screensaver is activated. The screen program must be installed to lock sessions on the console. Note: If the system does not have GNOME installed, this requirement is Not Applicable. If GNOME is installed, check to see a session lock occurs when the screensaver is activated with the following command: # grep -i lock-delay /etc/dconf/db/local.d/* lock-delay=uint32 5 If the “lock-delay” setting is missing, or is not set, this is a finding. Configure the operating system to initiate a session lock for graphical user interfaces when a screensaver is activated. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: # touch /etc/dconf/db/local.d/00-screensaver Add the setting to enable session locking when a screensaver is activated: [org/gnome/desktop/screensaver] lock-delay=uint32 5 After the setting has been set, run dconf update.
RHEL-07-010071 CCI-000057 medium The operating system must initiate a session lock after a 15-minute period of inactivity for all connection types. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. Verify the operating system prevents the user from overriding session lock after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console. If it is installed, GNOME must be configured to prevent users from overriding the system-wide session lock settings. Check for the session lock settings with the following commands: # grep -i idle-delay /etc/dconf/db/local.d/locks/* /org/gnome/desktop/screensaver/idle-delay /org/gnome/desktop/session/idle-delay If the command does not return a result for the screensaver and session keywords, this is a finding. # grep -i lock-delay /etc/dconf/db/local.d/locks/* /org/gnome/desktop/screensaver/lock-delay If the command does not return a result, this is a finding. Configure the operating system to initiate a session lock after a 15-minute period of inactivity for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: # touch /etc/dconf/db/local.d/locks/session Add the settings to enable screensaver/session locking after 15 minutes of inactivity: /org/gnome/desktop/screensaver/idle-delay /org/gnome/desktop/screensaver/lock-delay /org/gnome/desktop/session/idle-delay
RHEL-07-010072 CCI-000057 medium The operating system must have the screen package installed. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. The screen package allows for a session lock to be implemented and configured. Verify the operating system has the screen package installed. Check to see if the screen package is installed with the following command: # yum list installed | grep screen screen-4.3.1-3-x86_64.rpm If is not installed, this is a finding. Install the screen package to allow the initiation a session lock after a 15-minute period of inactivity for graphical users interfaces. Install the screen program (if it is not on the system) with the following command: # yum install screen The console can now be locked with the following key combination: ctrl+a x
RHEL-07-010073 CCI-000057 medium The operating system must initiate a session lock for the screensaver after a period of inactivity for graphical user interfaces. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. Verify the operating system initiates a session lock after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console. If it is installed, GNOME must be configured to enforce a session lock after a 15-minute delay. Check for the session lock settings with the following commands: # grep -i idle_activation_enabled /etc/dconf/db/local.d/* [org/gnome/desktop/screensaver] idle-activation-enabled=true If the idle-activation-enabled not set to “true”, this is a finding. Configure the operating system to initiate a session lock after a 15-minute period of inactivity for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: # touch /etc/dconf/db/local.d/00-screensaver Add the setting to enable screensaver locking after 15 minutes of inactivity: [org/gnome/desktop/screensaver] idle-activation-enabled=true
RHEL-07-010090 CCI-000192 medium When passwords are changed or new passwords are established, the new password must contain at least one upper-case character. 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. Note: The value to require a number of upper-case characters to be set is expressed as a negative number in /etc/security/pwquality.conf. Check the value for "ucredit" in /etc/security/pwquality.conf with the following command: # grep ucredit /etc/security/pwquality.conf ucredit = -1 If the value of "ucredit" is not set to a negative value, this is a finding. Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used by setting the “ucredit” option. Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value): ucredit = -1
RHEL-07-010100 CCI-000193 medium When passwords are changed or new passwords are established, the new password must contain at least one lower-case character. 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. Note: The value to require a number of lower-case characters to be set is expressed as a negative number in /etc/security/pwquality.conf. Check the value for "lcredit" in /etc/security/pwquality.conf with the following command: # grep lcredit /etc/security/pwquality.conf lcredit = -1 If the value of "lcredit" is not set to a negative value, this is a finding. Configure the operating system to enforce password complexity by requiring that at least one lower-case character be used by setting the “lcredit” option. Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value): lcredit = -1
RHEL-07-010110 CCI-000194 medium When passwords are changed or new passwords are assigned, the new password must contain at least one numeric character. 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. Note: The value to require a number of numeric characters to be set is expressed as a negative number in /etc/security/pwquality.conf. Check the value for "dcredit" in /etc/security/pwquality.conf with the following command: # grep dcredit /etc/security/pwquality.conf dcredit = -1 If the value of “dcredit” is not set to a negative value, this is a finding. Configure the operating system to enforce password complexity by requiring that at least one numeric character be used by setting the “dcredit” option. Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value): dcredit = -1
RHEL-07-010120 CCI-001619 medium When passwords are changed or new passwords are assigned, the new password must contain at least one special character. 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. Verify the operating system enforces password complexity by requiring that at least one special character be used. Note: The value to require a number of special characters to be set is expressed as a negative number in /etc/security/pwquality.conf. Check the value for “ocredit” in /etc/security/pwquality.conf with the following command: # grep ocredit /etc/security/pwquality.conf ocredit=-1 If the value of “ocredit” is not set to a negative value, this is a finding. Configure the operating system to enforce password complexity by requiring that at least one special character be used by setting the “dcredit” option. Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value): ocredit = -1
RHEL-07-010130 CCI-000195 medium When passwords are changed a minimum of eight of the total number of characters must be changed. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. The "difok" option sets the number of characters in a password that must not be present in the old password. Check for the value of the difok option in /etc/security/pwquality.conf with the following command: # grep difok /etc/security/pwquality.conf difok = 8 If the value of “difok” is set to less than 8, this is a finding. Configure the operating system to require the change of at least eight of the total number of characters when passwords are changed by setting the “difok” option. Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value): difok = 8
RHEL-07-010140 CCI-000195 medium When passwords are changed a minimum of four character classes must be changed. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. The "minclass" option sets the minimum number of required classes of characters for the new password (digits, uppercase, lowercase, others). Check for the value of the “minclass” option in /etc/security/pwquality.conf with the following command: # grep minclass /etc/security/pwquality.conf minclass = 4 If the value of “minclass” is set to less than 4, this is a finding. Configure the operating system to require the change of at least four character classes when passwords are changed by setting the “minclass” option. Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value): minclass = 4
RHEL-07-010150 CCI-000195 medium When passwords are changed the number of repeating consecutive characters must not be more than four characters. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. The "maxrepeat" option sets the maximum number of allowed same consecutive characters in a new password. Check for the value of the “maxrepeat” option in /etc/security/pwquality.conf with the following command: # grep maxrepeat /etc/security/pwquality.conf maxrepeat = 2 If the value of “maxrepeat” is set to more than 2, this is a finding. Configure the operating system to require the change of the number of repeating consecutive characters when passwords are changed by setting the “maxrepeat” option. Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value): maxrepeat = 2
RHEL-07-010160 CCI-000195 medium When passwords are changed the number of repeating characters of the same character class must not be more than four characters. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. The "maxclassrepeat" option sets the maximum number of allowed same consecutive characters in the same class in the new password. Check for the value of the maxclassrepeat option in /etc/security/pwquality.conf with the following command: # grep maxclassrepeat /etc/security/pwquality.conf maxclassrepeat = 4 If the value of “maxclassrepeat” is set to more than 4, this is a finding. Configure the operating system to require the change of the number of repeating characters of the same character class when passwords are changed by setting the “maxclassrepeat” option. Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value): maxclassrepeat = 4
RHEL-07-010170 CCI-000196 medium The PAM system service must be configured to store only encrypted representations of passwords. Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text. Verify the PAM system service is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512. Check that the system is configured to create SHA512 hashed passwords with the following command: # grep password /etc/pam.d/system-auth password sufficient pam_unix.so sha512 If the /etc/pam.d/system-auth configuration files allow for password hashes other than SHA512 to be used, this is a finding. Configure the operating system to store only SHA512 encrypted representations of passwords. Add the following line in /etc/pam.d/system-auth: password sufficient pam_unix.so sha512
RHEL-07-010180 CCI-000196 medium The shadow file must be configured to store only encrypted representations of passwords. Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text. Verify the system's shadow file is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512. Check that the system is configured to create SHA512 hashed passwords with the following command: # grep -i encrypt /etc/login.defs ENCRYPT_METHOD SHA512 If the /etc/login.defs configuration file does not exist or allows for password hashes other than SHA512 to be used, this is a finding. Configure the operating system to store only SHA512 encrypted representations of passwords. Add or update the following line in /etc/login.defs: ENCRYPT_METHOD SHA512
RHEL-07-010190 CCI-000196 medium User and group account administration utilities must be configured to store only encrypted representations of passwords. Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text. Verify the user and group account administration utilities are configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512. Check that the system is configured to create SHA512 hashed passwords with the following command: # cat /etc/libuser.conf | grep -i sha512 [defaults] crypt_style = sha512 If the "crypt_style" variable is not set to "sha512", is not in the defaults section, or does not exist, this is a finding. Configure the operating system to store only SHA512 encrypted representations of passwords. Add or update the following line in /etc/libuser.conf in the [defaults] section: crypt_style = sha512
RHEL-07-010200 CCI-000198 medium Passwords for new users must be restricted to a 24 hours/1 day minimum lifetime. Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse. Verify the operating system enforces 24 hours/1 day as the minimum password lifetime for new user accounts. Check for the value of “PASS_MIN_DAYS” in /etc/login.defs with the following command: # grep -i pass_min_days /etc/login.defs PASS_MIN_DAYS 1 If the “PASS_MIN_DAYS” parameter value is not “1” or greater, or is commented out, this is a finding. Configure the operating system to enforce 24 hours/1 day as the minimum password lifetime. Add the following line in /etc/login.defs (or modify the line to have the required value): PASS_MIN_DAYS 1
RHEL-07-010210 CCI-000198 medium Passwords must be restricted to a 24 hours/1 day minimum lifetime. Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse. Check whether the minimum time period between password changes for each user account is one day or greater. # awk -F: '$4 < 1 {print $1}' /etc/shadow If any results are returned that are not associated with a system account, this is a finding. Configure non-compliant accounts to enforce a 24 hours/1 day minimum password lifetime: # chage -m 1 [user]
RHEL-07-010220 CCI-000199 medium Passwords for new users must be restricted to a 60-day maximum lifetime. 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. Verify the operating system enforces a 60-day maximum password lifetime restriction for new user accounts. Check for the value of “PASS_MAX_DAYS” in /etc/login.defs with the following command: # grep -i pass_max_days /etc/login.defs PASS_MAX_DAYS 60 If the “PASS_MAX_DAYS” parameter value is not 60 or less, or is commented out, this is a finding. Configure the operating system to enforce a 60-day maximum password lifetime restriction. Add the following line in /etc/login.defs (or modify the line to have the required value): PASS_MAX_DAYS 60
RHEL-07-010230 CCI-000199 medium Existing passwords must be restricted to a 60-day maximum lifetime. 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. Check whether the maximum time period for existing passwords is restricted to 60 days. # awk -F: '$5 > 60 {print $1}' /etc/shadow If any results are returned that are not associated with a system account, this is a finding. Configure non-compliant accounts to enforce a 60-day maximum password lifetime restriction. # chage -M 60 [user]
RHEL-07-010240 CCI-000200 medium Passwords must be prohibited from reuse for a minimum of five generations. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements. Verify the operating system prohibits password reuse for a minimum of five generations. Check for the value of the “remember” argument in /etc/pam.d/system-auth with the following command: # grep -i remember /etc/pam.d/system-auth password sufficient pam_unix.so use_authtok sha512 shadow remember=5 If the line containing the pam_unix.so line does not have the “remember” module argument set, or the value of the “remember” module argument is set to less than “5”, this is a finding. Configure the operating system to prohibit password reuse for a minimum of five generations. Add the following line in /etc/pam.d/system-auth (or modify the line to have the required value): password sufficient pam_unix.so use_authtok sha512 shadow remember=5
RHEL-07-010250 CCI-000205 medium Passwords must be a minimum of 15 characters in length. The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password. Verify the operating system enforces a minimum 15-character password length. The “minlen” option sets the minimum number of characters in a new password. Check for the value of the “minlen” option in /etc/security/pwquality.conf with the following command: # grep minlen /etc/security/pwquality.conf minlen = 15 If the command does not return a “minlen” value of 15 or greater, this is a finding. Configure operating system to enforce a minimum 15-character password length. Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value): minlen = 15
RHEL-07-010260 CCI-000366 high The system must not have accounts configured with blank or null passwords. If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments. To verify that null passwords cannot be used, run the following command: # grep nullok /etc/pam.d/system-auth If this produces any output, it may be possible to log on with accounts with empty passwords. If null passwords can be used, this is a finding. If an account is configured for password authentication but does not have an assigned password, it may be possible to log on to the account without authenticating. Remove any instances of the "nullok" option in "/etc/pam.d/system-auth" to prevent logons with empty passwords.
RHEL-07-010270 CCI-000766 high The SSH daemon must not allow authentication using an empty password. Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere. To determine how the SSH daemon's "PermitEmptyPasswords" option is set, run the following command: # grep -i PermitEmptyPasswords /etc/ssh/sshd_config If no line, a commented line, or a line indicating the value "no" is returned, the required value is set. If the required value is not set, this is a finding. To explicitly disallow remote logon 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.
RHEL-07-010280 CCI-000795 medium The operating system must disable account identifiers (individuals, groups, roles, and devices) if the password expires. Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Operating systems need to track periods of inactivity and disable application identifiers after zero days of inactivity. Verify the operating system disables account identifiers (individuals, groups, roles, and devices) after the password expires with the following command: # grep -i inactive /etc/default/useradd INACTIVE=0 If the value is not set to “0”, is commented out, or is not defined, this is a finding. Configure the operating system to disable account identifiers (individuals, groups, roles, and devices) after the password expires. Add the following line /etc/default/useradd (or modify the line to have the required value): INACTIVE=0
RHEL-07-010371 CCI-002238 medium If three unsuccessful logon attempts within 15 minutes occur the associated account must be locked. 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. Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005 Verify the operating system automatically locks an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. Check that the system locks the account after three unsuccessful logon attempts within a period of 15 minutes with the following command: # grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 If the “fail_interval” setting is greater than 900 on both lines with the pam_faillock.so module name or is missing from a line, this is a finding. Configure the operating system to lock an account for the maximum period when three unsuccessful logon attempts in 15 minutes are made. Modify the first three lines of the auth section of the /etc/pam.d/system-auth and /etc/pam.d/password-auth files to match the following lines: auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800 auth sufficient pam_unix.so try_first_pass auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
RHEL-07-010372 CCI-002238 medium Accounts subject to three unsuccessful login attempts within 15 minutes must be locked for the maximum configurable period. 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. Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005 Verify the operating system automatically locks an account for the maximum period for which the system can be configured. Check that the system locks an account for the maximum period after three unsuccessful logon attempts within a period of 15 minutes with the following command: # grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth silent audit deny=3 even_deny_root unlock_time=604800 auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root unlock_time=604800 If the “unlock_time” setting is greater than 604800 on both lines with the pam_faillock.so module name or is missing from a line, this is a finding. Configure the operating system to lock an account for the maximum period when three unsuccessful logon attempts in 15 minutes are made. Modify the first three lines of the auth section of the /etc/pam.d/system-auth and /etc/pam.d/password-auth files to match the following lines: auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800 auth sufficient pam_unix.so try_first_pass auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
RHEL-07-010373 CCI-002238 medium If three unsuccessful root logon attempts within 15 minutes occur the associated account must be locked. 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. Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005 Verify the operating system automatically locks the root account until it is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. # grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 If the “even_deny_root” setting is not defined on both lines with the pam_faillock.so module name, this is a finding. Configure the operating system to automatically lock the root account until the locked is released by an administrator when three unsuccessful logon attempts in 15 minutes are made. Modify the first three lines of the auth section of the /etc/pam.d/system-auth and /etc/pam.d/password-auth files to match the following lines: auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800 auth sufficient pam_unix.so try_first_pass auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
RHEL-07-010380 CCI-002038 medium Users must provide a password for privilege escalation. Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158 Verify the operating system requires users to supply a password for privilege escalation. Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command: # grep -i nopasswd /etc/sudoers /etc/sudoers.d/* If any line is found with a "NOPASSWD" tag, this is a finding. Configure the operating system to require users to supply a password for privilege escalation. Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command: # grep -i nopasswd /etc/sudoers /etc/sudoers.d/* Remove any occurrences of "NOPASSWD" tags in the file.
RHEL-07-010381 CCI-002038 medium Users must re-authenticate for privilege escalation. Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158 Verify the operating system requires users to reauthenticate for privilege escalation. Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command: # grep -i authenticate /etc/sudoers /etc/sudoers.d/* If any line is found with a "!authenticate" tag, this is a finding. Configure the operating system to require users to reauthenticate for privilege escalation. Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command: Remove any occurrences of "!authenticate" tags in the file.
RHEL-07-010400 CCI-002007 medium The operating system must prohibit the use of cached nss authenticators after one day. If cached authentication information is out of date, the validity of the authentication information may be questionable. Verify the operating system prohibits the use of cached nss authenticators after one day. Check to see if the “sssd” service is active with the following command: # systemctl status sssd.service If the service is active, the command will return: sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled) Active: active (running) since Thu 2014-09-25 10:46:43 CEST; 5s ago If the service is not active, this is a finding. Check the services option for the active services of each domain configured with the following command: # grep services /etc/sssd/sssd.conf The command will return one line for each domain. In the example: services = nss, pam services = nss, pam There are two services lines as the “nss” and “pam” services are being used by two domains (ldap and local). If nss is an active service, check the memcache_timeout option with the following command: # grep -i memcache_timeout /etc/sssd/sssd.conf memcache_timeout = 86400 If the “memcache_timeout” is set to a value greater than “86400”, is commented out, or is missing, this is a finding. Configure the operating system to prohibit the use of cached nss authenticators after one day. If “nss” is in use on the system, set the “memcache_timeout” value to “86400” or less in /etc/sssd/sssd.conf: memcache_timeout = 86400
RHEL-07-010401 CCI-002007 medium The operating system must prohibit the use of cached PAM authenticators after one day. If cached authentication information is out of date, the validity of the authentication information may be questionable. Verify the operating system prohibits the use of cached PAM authenticators after one day. Check to see if the “sssd” service is active with the following command: # systemctl status sssd.service If the service is active, the command will return: sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled) Active: active (running) since Thu 2014-09-25 10:46:43 CEST; 5s ago If the service is not active, this is a finding. Check the services option for the active services of each domain configured with the following command: # grep services /etc/sssd/sssd.conf The command will return one line for each domain. In the example: services = nss, pam services = nss, pam There are two services lines as the “nss” and “pam” services are being used by two domains (ldap and local). If “pam” is an active service, check the “offline_credentials_expiration” option with the following command: # grep -i offline_credentials_expiration /etc/sssd/sssd.conf offline_credentials_expiration = 1 If “pam” is not an active service, this requirement is Not Applicable. Configure the operating system to prohibit the use of cached PAM authenticators after one day. If “pam” is in use on the system, set the “offline_credentials_expiration” value to “1” in /etc/sssd/sssd.conf: offline_credentials_expiration = 1
RHEL-07-010402 CCI-002007 medium The operating system must prohibit the use of cached SSH authenticators after one day. If cached authentication information is out of date, the validity of the authentication information may be questionable. Verify the operating system prohibits the use of cached SSH authenticators after one day. Check to see if the “sssd” service is active with the following command: # systemctl status sssd.service If the service is active, the command will return: sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled) Active: active (running) since Thu 2014-09-25 10:46:43 CEST; 5s ago If the service is not active, this is a finding. Check the services option for the active services of each domain configured with the following command: # grep services /etc/sssd/sssd.conf The command will return one line for each domain. In the example: services = nss, pam services = nss, pam There are two services lines as the “nss” and “pam” services are being used by two domains (ldap and local). If “pam” is an active service, check the “offline_credentials_expiration” option with the following command: # grep -i offline_credentials_expiration /etc/sssd/sssd.conf offline_credentials_expiration = 1 If “offline_credentials_expiration” is set to a value greater than “1”, is commented out, or is missing, this is a finding. Configure the operating system to prohibit the use of cached SSH authenticators after one day. If “ssh” is in use on the system, set the “ssh_known_hosts_timeout” value to “86400” or less in /etc/sssd/sssd.conf: ssh_known_hosts_timeout = 86400
RHEL-07-010420 CCI-000366 medium The delay between logon prompts following a failed console logon attempt must be at least four seconds. Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example, registry settings; account, file, and directory permission settings; and settings for functions, ports, protocols, services, and remote connections. Verify the operating system enforces a delay of at least four seconds between console logon prompts following a failed logon attempt. Check the value of the fail_delay parameter in “/etc/login.defs” file with the following command: # grep -i fail_delay /etc/login.defs FAIL_DELAY 4 If the value of “FAIL_DELAY” is not set to “4” or greater, this is a finding. Configure the operating system to enforce a delay of at least four seconds between logon prompts following a failed console logon attempt. Modify the “/etc/login.defs” file to set the “FAIL_DELAY” parameter to “4” or greater: FAIL_DELAY 4
RHEL-07-010430 CCI-000366 high The operating system must not allow an unattended or automatic logon to the system via a graphical user interface. Failure to restrict system access to authenticated users negatively impacts operating system security. Verify the operating system does not allow an unattended or automatic logon to the system via a graphical user interface. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Check for the value of the “AutomaticLoginEnable” in “/etc/gdm/custom.conf” file with the following command: # grep -i automaticloginenable /etc/gdm/custom.conf AutomaticLoginEnable=false If the value of “AutomaticLoginEnable” is not set to “false”, this is a finding. Configure the operating system to not allow an unattended or automatic logon to the system via a graphical user interface. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Add or edit the line for the “AutomaticLoginEnable” parameter in the [daemon] section of the “/etc/gdm/custom.conf” file to “false”: [daemon] AutomaticLoginEnable=false
RHEL-07-010431 CCI-000366 high The operating system must not allow guest logon to the system. Failure to restrict system access to authenticated users negatively impacts operating system security. Verify the operating system does not allow guest logon to the system via a graphical user interface. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Check for the value of the “AutomaticLoginEnable” in “/etc/gdm/custom.conf” file with the following command: # grep -i timedloginenable /etc/gdm/custom.conf TimedLoginEnable=false If the value of “TimedLoginEnable” is not set to “false”, this is a finding. Configure the operating system to not allow a guest account to log on to the system via a graphical user interface. Note: If the system does not have GNOME installed, this requirement is Not Applicable. Add or edit the line for the “TimedLoginEnable” parameter in the [daemon] section of the “/etc/gdm/custom.conf” file to “false”: [daemon] TimedLoginEnable=false
RHEL-07-010440 CCI-000366 high The operating system must not allow empty passwords for SSH logon to the system. Failure to restrict system access to authenticated users negatively impacts operating system security. Verify the operating system does not allow empty passwords to be used for SSH logon to the system. Check for the value of the PermitEmptyPasswords keyword with the following command: # grep -i permitemptypassword /etc/ssh/sshd_config PermitEmptyPasswords no If the “PermitEmptyPasswords” keyword is not set to “no”, is missing, or is commented out, this is a finding. Configure the operating system to not allow empty passwords for SSH logon to the system. Edit the /etc/ssh/sshd_config file to uncomment or add the line for “PermitEmptyPasswords” keyword and set the value to “no”: PermitEmptyPasswords no
RHEL-07-010441 CCI-000366 medium The operating system must not allow users to override SSH environment variables. Failure to restrict system access to authenticated users negatively impacts operating system security. Verify the operating system does not allow users to override environment variables to the SSH daemon. Check for the value of the PermitUserEnvironment keyword with the following command: # grep -i permituserenvironment /etc/ssh/sshd_config PermitUserEnvironment no If the “PermitUserEnvironment” keyword is not set to “no”, is missing, or is commented out, this is a finding. Configure the operating system to not allow users to override environment variables to the SSH daemon. Edit the /etc/ssh/sshd_config file to uncomment or add the line for “PermitUserEnvironment” keyword and set the value to “no”: PermitUserEnvironment no
RHEL-07-010442 CCI-000366 medium The operating system must not allow a non-certificate trusted host SSH logon to the system. Failure to restrict system access to authenticated users negatively impacts operating system security. Verify the operating system does not allow a non-certificate trusted host SSH logon to the system. Check for the value of the HostbasedAuthentication keyword with the following command: # grep -i hostbasedauthentication /etc/ssh/sshd_config HostbasedAuthentication no If the “HostbasedAuthentication” keyword is not set to “no”, is missing, or is commented out, this is a finding. Configure the operating system to not allow a non-certificate trusted host SSH logon to the system. Edit the /etc/ssh/sshd_config file to uncomment or add the line for “HostbasedAuthentication” keyword and set the value to “no”: HostbasedAuthentication no
RHEL-07-010460 CCI-000213 high Systems with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes. If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu. Check to see if an encrypted root password is set. On systems that use a BIOS, use the following command: # grep -i password /boot/grub2/grub.cfg password_pbkdf2 superusers-account password-hash If the root password entry does not begin with “password_pbkdf2”, this is a finding. Configure the system to encrypt the boot password for root. Generate an encrypted grub2 password for root with the following command: Note: The hash generated is an example. # grub-mkpasswd-pbkdf2 Enter Password: Reenter Password: PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45 Using this hash, modify the “/etc/grub.d/10_linux” file with the following commands to add the password to the root entry: # cat << EOF > set superusers="root" password_pbkdf2 smithj grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45 > EOF Generate a new grub.conf file with the new password with the following commands: # grub2-mkconfig --output=/tmp/grub2.cfg # mv /tmp/grub2.cfg /boot/grub2/grub.cfgirement
RHEL-07-010470 CCI-000213 high Systems using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes. If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu. Check to see if an encrypted root password is set. On systems that use UEFI, use the following command: # grep -i password /boot/efi/EFI/redhat/grub.cfg password_pbkdf2 superusers-account password-hash If the root password entry does not begin with “password_pbkdf2”, this is a finding. Configure the system to encrypt the boot password for root. Generate an encrypted grub2 password for root with the following command: Note: The hash generated is an example. # grub-mkpasswd-pbkdf2 Enter Password: Reenter Password: PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45 Using this hash, modify the “/etc/grub.d/10_linux” file with the following commands to add the password to the root entry: # cat << EOF > set superusers="root" password_pbkdf2 smithj grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45 > EOF Generate a new grub.conf file with the new password with the following commands: # grub2-mkconfig --output=/tmp/grub2.cfg # mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg
RHEL-07-010490 CCI-000366 low Unnecessary default system accounts must be removed. Default system accounts created at install time but never used by the system may inadvertently be configured for interactive logon. Vendor accounts and software may contain accounts that provide unauthorized access to the system. All accounts that are not used to support the system and application operation must be removed from the system. Verify unnecessary default system accounts have been removed. Check the accounts that are on the system with the following command: # more /etc/passwd root:x:0:0:root:/root:/bin/bash bin:x:1:1:bin:/bin:/sbin/nologin daemon:x:2:2:daemon:/sbin:/sbin/nologin adm:x:3:4:adm:/var/adm:/sbin/nologin lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync If unnecessary default accounts such as games or ftp exist in the “/etc/passwd” file, this is a finding. Remove unnecessary default accounts from the system by using the account management tool or manually editing the “/etc/password” and “/etc/shadow” files.
RHEL-07-010500 CCI-000766 medium The operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users) using multi-factor authentication. To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: 1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and 2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. Satisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000109-GPOS-00056, SRG-OS-000108-GPOS-00055, SRG-OS-000108-GPOS-00057, SRG-OS-000108-GPOS-00058 Verify the operating system requires multifactor authentication to uniquely identify organizational users using multi-factor authentication. Check to see if smartcard authentication is enforced on the system: # authconfig --test | grep -i smartcard The entry for use only smartcard for login may be enabled, and the smartcard module and smartcard removal actions must not be blank. If smartcard authentication is disabled or the smartcard and smartcard removal actions are blank, this is a finding. Configure the operating system to require individuals to be authenticated with a multi-factor authenticator. Enable smartcard logins with the following commands: # authconfig --enablesmartcard --smartcardaction=1 --update # authconfig --enablerequiresmartcard -update Modify the /etc/pam_pkcs11/pkcs11_eventmgr.conf file to uncomment the following line: #/usr/X11R6/bin/xscreensaver-command -lock Modify the /etc/pam_pkcs11/pam_pkcs11.conf file to use the cackey module if required.
RHEL-07-020000 CCI-000381 high The rsh-server package must not be installed. It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). The rsh-server service provides an unencrypted remote access service that 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 log on using this service, the privileged user password could be compromised. Check to see if the rsh-server package is installed with the following command: # yum list installed | grep rsh-server If the rsh-server package is installed, this is a finding. Configure the operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command: # yum remove rsh-server
RHEL-07-020010 CCI-000381 high The ypserv package must not be installed. Removing the "ypserv" package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services. The NIS service provides an unencrypted authentication service that does not provide for the confidentiality and integrity of user passwords or the remote session. Check to see if the “ypserve” package is installed with the following command: # yum list installed | grep ypserv If the “ypserv” package is installed, this is a finding. Configure the operating system to disable non-essential capabilities by removing the “ypserv” package from the system with the following command: # yum remove ypserv
RHEL-07-020090 CCI-002165 medium The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileged functions include, for example, establishing accounts, 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. Verify the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. Get a list of authorized users (other than system administrator and guest accounts) for the system. Check the list against the system by using the following command: # semanage login -l | more Login Name SELinux User MLS/MCS Range Service __default__ user_u s0-s0:c0.c1023 * root unconfined_u s0-s0:c0.c1023 * system_u system_u s0-s0:c0.c1023 * joe staff_u s0-s0:c0.c1023 * All administrators must be mapped to the sysadm_u or staff_u users with the appropriate domains (sysadm_t and staff_t). All authorized non-administrative users must be mapped to the user_u role or the appropriate domain (user_t). If they are not mapped in this way, this is a finding. Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. Use the following command to map a new user to the sysdam_u role: #semanage login -a -s sysadm_u <username> Use the following command to map an existing user to the sysdam_u role: #semanage login -m -s sysadm_u <username> Use the following command to map a new user to the staff_u role: #semanage login -a -s staff_u <username> Use the following command to map an existing user to the staff_u role: #semanage login -m -s staff_u <username> Use the following command to map a new user to the user_u role: # semanage login -a -s user_u <username> Use the following command to map an existing user to the user_u role: # semanage login -m -s user_u <username>
RHEL-07-020130 CCI-001744 medium A file integrity tool must verify the baseline operating system configuration at least weekly. 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. Verify the operating system routinely checks that baseline configuration changes are not performed in an authorized manner. Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed at least once per week. Check for the presence of a cron job running daily or weekly on the system that executes AIDE daily to scan for changes to the system baseline. The command used in the example will use a daily occurrence. Check the /etc/cron.daily subdirectory for a crontab file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following command: # ls -al /etc/cron.* | grep aide -rwxr-xr-x 1 root root 29 Nov 22 2015 aide If the file integrity application is not executed on the system with the required frequency, this is a finding. Configure the file integrity tool to automatically run on the system at least weekly. The following example output is generic. It will set cron to run AIDE daily, but other file integrity tools may be used: # cat /etc/cron.daily/aide 0 0 * * * /usr/sbin/aide --check | /bin/mail -s "aide integrity check run for <system name>" root@sysname.mil
RHEL-07-020140 CCI-001744 medium Designated personnel must be notified if baseline configurations are changed in an unauthorized manner. Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be 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. Verify the operating system notifies designated personnel if baseline configurations are changed in an unauthorized manner. Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed and notify specified individuals via email or an alert. Check for the presence of a cron job running routinely on the system that executes AIDE to scan for changes to the system baseline. The commands used in the example will use a daily occurrence. Check the /etc/cron.daily subdirectory for a crontab file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following commands: # ls -al /etc/cron.daily | grep aide -rwxr-xr-x 1 root root 32 Jul 1 2011 aide AIDE does not have a configuration that will send a notification, so the cron job uses the mail application on the system to email the results of the file integrity run as in the following example: # more /etc/cron.daily/aide 0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil If the file integrity application does not notify designated personnel of changes, this is a finding. Configure the operating system to notify designated personnel if baseline configurations are changed in an unauthorized manner. The AIDE tool can be configured to email designated personnel through the use of the cron system. The following example output is generic. It will set cron to run AIDE daily and to send email at the completion of the analysis. # more /etc/cron.daily/aide 0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil
RHEL-07-020150 CCI-001749 high The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor. Accordingly, patches, 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 verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA. Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components from a repository without verification that they have been digitally signed using a certificate that is recognized and approved by the organization. Check that yum verifies the signature of packages from a repository prior to install with the following command: # grep gpgcheck /etc/yum.conf gpgcheck=1 If "gpgcheck" is not set to ”1”, or if options are missing or commented out, this is a finding. Configure the operating system to verify the signature of packages from a repository prior to install by setting the following option in the /etc/yum.conf file: gpgcheck=1
RHEL-07-020151 CCI-001749 high The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor. Accordingly, patches, 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 verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA. Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components of local packages without verification that they have been digitally signed using a certificate that is recognized and approved by the organization. Check that yum verifies the signature of local packages prior to install with the following command: # grep localpkg_gpgcheck /etc/yum.conf localpkg_gpgcheck=1 If "localpkg_gpgcheck" is not set to ”1”, or if options are missing or commented out, this is a finding. Configure the operating system to verify the signature of local packages prior to install by setting the following option in the /etc/yum.conf file: localpkg_gpgcheck=1
RHEL-07-020152 CCI-001749 high The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of packages without verification of the repository metadata. Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor. Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved Certificate Authority. 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 package metadata prior to install with the following command: # grep repo_gpgcheck /etc/yum.conf repo_gpgcheck=1 If "repo_gpgcheck" is not set to ”1”, or if options are missing or commented out, this is a finding. Configure the operating system to verify the repository metadata by setting the following options in the /etc/yum.conf file: repo_gpgcheck=1
RHEL-07-020160 CCI-000366 medium USB mass storage must be disabled. USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity. Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227 If there is an HBSS with a Device Control Module and a Data Loss Prevention mechanism, this requirement is not applicable. Verify the operating system disables the ability to use USB mass storage devices. Check to see if USB mass storage is disabled with the following command: #grep -i usb-storage /etc/modprobe.d/* install usb-storage /bin/true If the command does not return any output, and use of USB storage devices is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Configure the operating system to disable the ability to use USB mass storage devices. Create a file under /etc/modprobe.d with the following command: #touch /etc/modprobe.d/nousbstorage Add the following line to the created file: install usb-storage /bin/true
RHEL-07-020161 CCI-000366 medium File system automounter must be disabled unless required. Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity. Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227 Verify the operating system disables the ability to automount devices. Check to see if automounter service is active with the following command: # systemctl status autofs autofs.service - Automounts filesystems on demand Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled) Active: inactive (dead) If the “autofs” status is set to “active” and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Configure the operating system to disable the ability to automount devices. Turn off the automount service with the following command: # systemctl disable autofs If “autofs” is required for Network File System (NFS), it must be documented with the ISSO.
RHEL-07-020170 CCI-002476 high Operating systems handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a cryptographic mechanism is based on the need to protect the integrity and confidentiality of sensitive information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). This requirement is applicable if the organization determines that its sensitive information is to be protected at the storage device level. Satisfies: SRG-OS-000405-GPOS-00184, SRG-OS-000185-GPOS-00079 Verify the operating system, if handling data that requires protection to prevent the unauthorized discloser or modification of information at rest, is using disk encryption. Note: If the organization determines that no data resident on the system requires protection, or that sensitive data is being protected through an application encryption mechanism, this requirement is Not Applicable. Check the system partitions to determine if they are all encrypted with the following command: # blkid /dev/sda1: UUID=" ab12c3de-4f56-789a-8f33-3850cc8ce3a2 " TYPE="crypto_LUKS" /dev/sda2: UUID=" bc98d7ef-6g54-321h-1d24-9870de2ge1a2 " TYPE="crypto_LUKS" Pseudo-file systems, such as /proc, /sys, and tmpfs, are not required to use disk encryption and are not a finding. If any other partitions do not have a type of “crypto_LUKS”, this is a finding. Configure the operating system to implement cryptographic mechanisms to prevent unauthorized disclosure of all sensitive information at rest on operating system storage devices. This must be performed during the creation of the operating system as attempting to encrypt the system partitions afterward is not a trivial operation.
RHEL-07-020200 CCI-002617 low The operating system must remove all software components after updated versions have been installed. Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system. Verify the operating system removes all software components after updated versions have been installed. Check if yum is configured to remove unneeded packages with the following command: # grep -i clean_requirements_on_remove /etc/yum.conf clean_requirements_on_remove=1 If “clean_requirements_on_remove” is not set to “1”, “True”, or “yes”, or is not set in /etc/yum.conf, this is a finding. Configure the operating system to remove all software components after updated versions have been installed. Set the “clean_requirements_on_remove” option to “1” in the /etc/yum.conf file: clean_requirements_on_remove=1
RHEL-07-020210 CCI-002165 high The operating system must enable SELinux. Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality. Verify the operating system verifies correct operation of all security functions. Check if SELinux is active and in enforcing mode with the following command: # getenforce Enforcing If the “SELinux” mode is not set to “Enforcing”, this is a finding. Configure the operating system to verify correct operation of all security functions. Set the “Selinux” status and the “enforcing” mode by modifying the /etc/selinux/config file to have the following line: SELINUX=enforcing A reboot is required for the changes to take effect.
RHEL-07-020211 CCI-002165 high The operating system must enable the SELinux targeted policy. Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality. Verify the operating system verifies correct operation of all security functions. Check if SELinux is active and is enforcing the targeted policy with the following command: # sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: enforcing Mode from config file: enforcing Policy version: 24 Policy from config file: targeted If the “Policy from config file” not set to “targeted”, this is a finding. Configure the operating system to verify correct operation of all security functions. Set the “Selinuxtype” to the “targeted” policy by modifying the /etc/selinux/config file to have the following line: SELINUXTYPE=targeted A reboot is required for the changes to take effect.
RHEL-07-020220 CCI-000366 high The x86 Ctrl-Alt-Delete key sequence must be disabled. A locally logged-on user who presses Ctrl-Alt-Delete, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In the GNOME graphical environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken. Verify the operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed. Check that the ctrl-alt-del.service is not active with the following command: # systemctl status ctrl-alt-del.service reboot.target - Reboot Loaded: loaded (/usr/lib/systemd/system/reboot.target; disabled) Active: inactive (dead) Docs: man:systemd.special(7) If the ctrl-alt-del.service is active , this is a finding. Configure the system to disable the Ctrl-Alt_Delete sequence for the command line with the following command: # systemctl mask ctrl-alt-del.target If Gnome is active on the system, create a database to contain the system-wide setting (if it does not already exist) with the following command: # cat /etc/dconf/db/local.d/00-disable-CAD Add the setting to disable the Ctrl-Alt_Delete sequence for Gnome: [org/gnome/settings-daemon/plugins/media-keys] logout=’’
RHEL-07-020230 CCI-000366 medium The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access. Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files. Check for the value of the “UMASK” parameter in “/etc/login.defs” file with the following command: Note: If the value of the “UMASK” parameter is set to “000” in “/etc/login.defs” file, the Severity is raised to a CAT I. # grep -i umask /etc/login.defs UMASK 077 If the value for the “UMASK” parameter is not “077”, or the “UMASK” parameter is missing or is commented out, this is a finding. Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. Add or edit the line for the “UMASK” parameter in “/etc/login.defs” file to “077”: UMASK 077
RHEL-07-020240 CCI-000366 high The operating system must be a supported release. An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software. Severity Override Guidance: Check the version of the operating system with the following command: # cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.2 (Maipo) Current End of Life for RHEL 7 is June 30, 2024. If the release is not supported by the vendor, this is a finding. Upgrade to a supported version of the operating system.
RHEL-07-020250 CCI-000366 medium System security patches and updates must be installed and up to date. Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. However, failure to keep operating system and application software patched is a common mistake made by IT professionals. New patches are released daily, and it is often difficult for even experienced system administrators to keep abreast of all the new patches. When new weaknesses in an operating system exist, patches are usually made available by the vendor to resolve the problems. 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. Verify the operating system security patches and updates are installed and up to date. Updates are required to be applied with a frequency determined by the site or Program Management Office (PMO). Obtain the list of available package security updates from Red Hat. The URL for updates is https://rhn.redhat.com/errata/. It is important to note that updates provided by Red Hat may not be present on the system if the underlying packages are not installed. Check that the available package security updates have been installed on the system with the following command: # yum history list | more Loaded plugins: langpacks, product-id, subscription-manager ID | Command line | Date and time | Action(s) | Altered ------------------------------------------------------------------------------- 70 | install aide | 2016-05-05 10:58 | Install | 1 69 | update -y | 2016-05-04 14:34 | Update | 18 EE 68 | install vlc | 2016-04-21 17:12 | Install | 21 67 | update -y | 2016-04-21 17:04 | Update | 7 EE 66 | update -y | 2016-04-15 16:47 | E, I, U | 84 EE If package updates have not been performed on the system within the timeframe that the site/program documentation requires, this is a finding. Typical update frequency may be overridden by information assurance vulnerability alert (IAVA) notifications from CYBERCOM. If the operating system is in non-compliance with the IAVM process, this is a finding. Install the operating system patches or updated packages available from Red Hat within 30 days or sooner as local policy dictates.
RHEL-07-020290 CCI-000366 medium The system must not have unnecessary accounts. Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system. Verify all accounts on the system are assigned to an active system, application, or user account. Obtain the list of authorized system accounts from the Information System Security Officer (ISSO). Check the system accounts on the system with the following command: # more /etc/passwd root:x:0:0:root:/root:/bin/bash bin:x:1:1:bin:/bin:/sbin/nologin daemon:x:2:2:daemon:/sbin:/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt games:x:12:100:games:/usr/games:/sbin/nologin gopher:x:13:30:gopher:/var/gopher:/sbin/nologin Accounts such as “games” and “gopher” are not authorized accounts as they do not support authorized system functions. If the accounts on the system do not match the provided documentation, or accounts that do not support an authorized system function are present, this is a finding. Configure the system so all accounts on the system are assigned to an active system, application, or user account. Remove accounts that do not support approved system activities or that allow for a normal user to perform administrative-level actions. Document all authorized accounts on the system.
RHEL-07-020300 CCI-000764 low All Group Identifiers (GIDs) referenced in the /etc/passwd file must be defined in the /etc/group file. If a user is assigned the GID of a group not existing on the system, and a group with the GID is subsequently created, the user may have unintended rights to any files associated with the group. Verify all GIDs referenced in the “/etc/passwd” file are defined in the “/etc/group” file. Check that all referenced GIDs exist with the following command: # pwck -r If GIDs referenced in “/etc/passwd” file are returned as not defined in “/etc/group” file, this is a finding. Configure the system to define all GIDs found in the “/etc/passwd” file by modifying the “/etc/group” file to add any non-existent group referenced in the “/etc/passwd” file, or change the GIDs referenced in the “/etc/passwd” file to a group that exists in “/etc/group”.
RHEL-07-020310 CCI-000366 high The root account must be the only account having unrestricted access to the system. If an account other than root also has a User Identifier (UID) of “0”, it has root authority, giving that account unrestricted access to the entire operating system. Multiple accounts with a UID of “0” afford an opportunity for potential intruders to guess a password for a privileged account. Check the system for duplicate UID “0” assignments with the following command: # awk -F: '$3 == 0 {print $1}' /etc/passwd If any accounts other than root have a UID of “0”, this is a finding. Change the UID of any account on the system, other than root, that has a UID of “0”. 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 of greater than “1000” that has not already been assigned.
RHEL-07-020360 CCI-002165 medium All files and directories must have a valid owner. Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier “UID” as the UID of the un-owned files. Verify all files and directories on the system have a valid owner. Check the owner of all files and directories with the following command: # find / -fstype local -xdev -nouser If any files on the system do not have an assigned owner, this is a finding. Either remove all files and directories from the system that do not have a valid user, or assign a valid user to all unowned files and directories on the system with the chown command: # chown <user> <file>
RHEL-07-020370 CCI-002165 medium All files and directories must have a valid group owner. Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files without a valid group owner. Verify all files and directories on the system have a valid group. Check the owner of all files and directories with the following command: # find / -fstype local -xdev -nogroup If any files on the system do not have an assigned group, this is a finding. Either remove all files and directories from the system that do not have a valid group, or assign a valid group to all files and directories on the system with the chgrp command: # chgrp <group> <file>
RHEL-07-020620 CCI-000366 medium All local interactive users must have a home directory assigned in the /etc/passwd file. 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. Verify local interactive users on the system have a home directory assigned. Check for missing local interactive user home directories with the following command: # pwck -r user 'lp': directory '/var/spool/lpd' does not exist user 'news': directory '/var/spool/news' does not exist user 'uucp': directory '/var/spool/uucp' does not exist user 'smithj': directory '/home/smithj' does not exist Ask the System Administrator (SA) if any users found without home directories are local interactive users. If the SA is unable to provide a response, check for users with a User Identifier (UID) of 1000 or greater with the following command: # cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" If any interactive users do not have a home directory assigned, this is a finding. Assign home directories to all local interactive users that currently do not have a home directory assigned.
RHEL-07-020630 CCI-000366 medium All local interactive user accounts, upon creation, must be assigned a home directory. 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. Verify all local interactive users on the system are assigned a home directory upon creation. Check to see if the system is configured to create home directories for local interactive users with the following command: # grep -i create_home /etc/login.defs CREATE_HOME yes If the value for “CREATE_HOME” parameter is not set to "yes", the line is missing, or the line is commented out, this is a finding. 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
RHEL-07-020640 CCI-000366 medium All local interactive user home directories defined in the /etc/passwd file must exist. If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a Denial of Service because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to access. Verify the assigned home directory of all local interactive users on the system exists. Check the home directory assignment for all local interactive non-privileged users on the system with the following command: # cut -d: -f 1,3 /etc/passwd | egrep ":[1-9][0-9]{2}$|:[0-9]{1,2}$" smithj /home/smithj Note: This may miss interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information. Check that all referenced home directories exist with the following command: # pwck -r user 'smithj': directory '/home/smithj' does not exist If any home directories referenced in “/etc/passwd” are returned as not defined, this is a finding. Create home directories to all local 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”: Note: The example will be for the user smithj, who has a home directory of “/home/smithj”, a UID of “smithj”, and a Group Identifier (GID) of “users assigned” in “/etc/passwd”. # mkdir /home/smithj # chown smithj /home/smithj # chgrp users /home/smithj # chmod 0750 /home/smithj
RHEL-07-020650 CCI-000366 medium All local interactive user home directories must have mode 0750 or less permissive. Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users. Verify the assigned home directory of all local interactive users has a mode of “0750” or less permissive. Check the home directory assignment for all non-privileged users on the system with the following command: # cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" smithj /home/smithj Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. Check the mode on all local interactive users’ home directories with the following command: # ls -al <users home directory> drwxr-x--- 1 smithj users 860 Nov 28 06:43 smithj If home directories referenced in “/etc/passwd” do not have a mode of “0750” or less permissive, this is a finding. Change the mode of interactive user’s home directories to “0750”. To change the mode of a local interactive user’s home directory, use the following command: Note: The example will be for the user “smithj”. # chmod 0750 /home/smithj
RHEL-07-020660 CCI-000366 medium All local interactive user home directories must be owned by their respective users. 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. Verify the assigned home directory of all local interactive users is owned by that user. Check the home directory assignment for all non-privileged users on the system with the following command: # cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" smithj /home/smithj Note: This may miss local interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. Check the owner of all local interactive users home directories with the following command: # ls -al <users home directory> drwxr-x--- 1 smithj users 860 Nov 28 06:43 smithj If user home directory referenced in “/etc/passwd” is not owned by that user, this is a finding. Change the owner of a local interactive user’s home directories to that owner. To change the owner of a local interactive user’s home directory use the following command: Note: The example will be for the user smithj, who has a home directory of “/home/smithj”. # chown smithj /home/smithj
RHEL-07-020670 CCI-000366 medium All local interactive user home directories must be group-owned by the home directory owners primary group. If the Group Identifier (GID) of a local interactive user’s home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user’s files, and users that share the same group may not be able to access files that they legitimately should. Verify the assigned home directory of all local interactive users is group-owned by that user’s primary GID. Check the home directory assignment for all non-privileged users on the system with the following command: # cut -d: -f 1,3,4 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" smithj /home/smithj 250 # grep 250 /etc/group users:x:250:smithj,jonesj,jacksons Note: This may miss local interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information. Check the group owner of all local interactive users’ home directories with the following command: # ls -al <users home directory> drwxr-x--- 1 smithj users 860 Nov 28 06:43 smithj If the user home directory referenced in “/etc/passwd” is not group-owned by that user’s primary GID, this is a finding. Change the group owner of a local interactive user’s home directory to the group found in “/etc/passwd”. To change the group owner of a local interactive user’s home directory, use the following command: Note: The example will be for the user “smithj”, who has a home directory of “/home/smithj”, and has a primary group of users. # chgrp users /home/smithj
RHEL-07-020680 CCI-000366 medium All files and directories contained in local interactive user home directories must be owned by the owner of the home directory. 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. Verify all files and directories in a local interactive user’s home directory are owned by the user. Check the owner of all files and directories in a local interactive user’s home directory with the following command: # ls -lLR /<home directory path>/<users home directory>/ /home/smithj -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1 -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2 -rw-r--r-- 1 smithj smithj 231 Mar 5 17:06 file3 If any files are found with an owner different than the home directory user, this is a finding. Change the owner of a local interactive user’s files and rectories to that owner. To change the owner of a local interactive user’s files and directories, use the following command: Note: The example will be for the user smithj, who has a home directory of “/home/smithj”. # chown smithj /home/smithj/<file or directory>
RHEL-07-020690 CCI-000366 medium All files and directories contained in local interactive user home directories must be group-owned by a group of which the home directory owner is a member. If a local interactive user’s files are group-owned by a group of which the user is not a member, unintended users may be able to access them. Verify all files and directories in a local interactive user home directory are group-owned by a group the user is a member of. Check the group owner of all files and directories in a local interactive user’s home directory with the following command: Note: The example will be for the user “smithj”, who has a home directory of “/home/smithj/home/smithj”. # ls -lLR /<home directory>/<users home directory>/ -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1 -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2 -rw-r--r-- 1 smithj sa 231 Mar 5 17:06 file3 If any files are found with an owner different than the group home directory user, check to see if the user is a member of that group with the following command: # grep smithj /etc/group sa:x:100:juan,shelley,bob,smithj smithj:x:521:smithj If the user is not a member of a group that group owns file(s) in a local interactive user’s home directory, this is a finding. Change the group of a local interactive user’s files and directories to a group that the interactive user is a member of. To change the group owner of a local interactive user’s files and directories, use the following command: Note: The example will be for the user smithj, who has a home directory of “/home/smithj” and is a member of the users group. # chgrp users /home/smithj/<file>
RHEL-07-020700 CCI-000366 medium All files and directories contained in local interactive user home directories must have mode 0750 or less permissive. If a local interactive user files have excessive permissions, unintended users may be able to access or modify them. Verify all files and directories contained in a local interactive user home directory, excluding local initialization files, have a mode of “0750”. Check the mode of all non-initialization files in a local interactive user home directory with the following command: Files that begin with a “.” are excluded from this requirement. Note: The example will be for the user “smithj”, who has a home directory of “/home/smithj/home/smithj” # ls -lLR /<home directory>/<users home directory>/ -rwxr-x--- 1 smithj smithj 18 Mar 5 17:06 file1 -rwxr----- 1 smithj smithj 193 Mar 5 17:06 file2 -rw-r-x--- 1 smithj sa 231 Mar 5 17:06 file3 If any files are found with a mode more permissive than “0750”, this is a finding. Set the mode on files and directories in the local interactive user home directory with the following command: # chmod 0750 /<home directory>/<users home directory>/<file>
RHEL-07-020840 CCI-000366 medium All local initialization files for interactive users must be owned by the home directory user or root. Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon. Verify all local initialization files for interactive users are owned by the home directory user or root. Check the owner on all local initialization files with the following command: Note: The example will be for the “smithj” user, who has a home directory of “/home/smithj”. # ls -al /home/smithj/.* | more -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .bash_profile -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .profile If any file that sets a local interactive user’s environment variables to override the system is not owned by the home directory owner or root, this is a finding. Set the owner of the local initialization files for interactive users to either the directory owner or root with the following command: Note: The example will be for the smithj user, who has a home directory of “/home/smithj”. # chown smithj /home/smithj/.*
RHEL-07-020850 CCI-000366 medium Local initialization files for local interactive users must be group-owned by the users primary group or root. 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. Verify the local initialization files of all local interactive users are group-owned by that user’s primary Group Identifier (GID). Check the home directory assignment for all non-privileged users on the system with the following command: Note: The example will be for the smithj user, who has a home directory of “/home/smithj” and a primary group of users. # cut -d: -f 1,3,4 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" smithj /home/smithj 250 # grep 250 /etc/group users:x:250:smithj,jonesj,jacksons Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. Check the group owner of all local interactive users’ initialization files with the following command: # ls -al /home/smithj/.* -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something If all local interactive users’ initialization files are not group-owned by that user’s primary GID, this is a finding. Change the group owner of a local interactive user’s 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: Note: The example will be for the user smithj, who has a home directory of “/home/smithj”, and has a primary group of users. # chgrp users /home/smithj/<file>
RHEL-07-020860 CCI-000366 medium All local initialization files must have mode 0740 or less permissive. Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon. Verify that all local initialization files have a mode of “0740” or less permissive. Check the mode on all local initialization files with the following command: Note: The example will be for the smithj user, who has a home directory of “/home/smithj”. # ls -al /home/smithj/.* | more -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something If any local initialization files have a mode more permissive than “0740”, this is a finding. Set the mode of the local initialization files to “0740” with the following command: Note: The example will be for the smithj user, who has a home directory of “/home/smithj”. # chmod 0740 /home/smithj/.*
RHEL-07-020870 CCI-000366 medium All local interactive user initialization files executable search paths must contain only absolute paths. 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 user’s 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). Verify that all local interactive user initialization files path statements do not contain statements that will reference a working directory other than the users’ home directory. Check the path statement for all local interactive user initialization files in the users' home directory with the following commands: Note: The example will be for the smithj user, which has a home directory of “/home/smithj”. # grep -i path /home/smithj/.* /home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin /home/smithj/.bash_profile:export PATH If any local interactive user initialization files have path statements that include directories outside of their home directory, this is a finding. Edit the local interactive user initialization files to change any PATH variable statements that reference directories other than their home directory. If a local interactive user requires path variables to reference a directory owned by the application, it must be documented with the ISSO.
RHEL-07-020880 CCI-000366 medium Local initialization files must not execute world-writable programs. If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level. Verify that local initialization files do not execute world-writable programs. Check the system for world-writable files with the following command: # find / -perm -002 -type f -exec ls -ld {} \; | more For all files listed, check for their presence in the local initialization files with the following commands: Note: The example will be for a system that is configured to create users’ home directories in the /home directory. # grep <file> /home/*/.* If any local initialization files are found to reference world-writable files, this is a finding. Set the mode on files being executed by the local initialization files with the following command: # chmod 0755 <file>
RHEL-07-020940 CCI-000318 medium All system device files must be correctly labeled to prevent unauthorized modification. If an unauthorized or modified device is allowed to exist on the system, there is the possibility the system may perform unintended or unauthorized operations. Verify that all system device files are correctly labeled to prevent unauthorized modification. List all device files on the system that are incorrectly labeled with the following commands: Note: Device files are normally found under “/dev”, but applications may place device files in other directories, necessitating a search of the entire system. #find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n" #find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n" If there is output from either of these commands, this is a finding. Run the following command to determine which package owns the device 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>
RHEL-07-021010 CCI-000366 medium Files systems that contain user home directories must be mounted to prevent files with the setuid and setgid bit set from being executed. The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. Verify file systems that contain user home directories are mounted with the “nosetuid” option. Find the file system(s) that contain the user home directories with the following command: Note: If a separate file system has not been created for the user home directories (user home directories are mounted under “/”) this is not a finding as the “nosetuid” option cannot be used on the “/” system. # cut -d: -f 1,7 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" smithj /home/smithj thomasr /home/thomasr Check the file systems that are mounted at boot time with the following command: # more /etc/fstab UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4 rw,relatime,discard,data=ordered,nosuid 0 2 If a file system found in “/etc/fstab” refers to the user home directory file system and it does not have the “nosetuid” option set, this is a finding. Configure the “/etc/fstab” to use the “nosuid” option on file systems that contain user home directories.
RHEL-07-021011 CCI-000366 medium Files systems that are used with removable media must be mounted to prevent files with the setuid and setgid bit set from being executed. The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. Verify file systems that are used for removable media are mounted with the “nosetuid” option. Check the file systems that are mounted at boot time with the following command: # more /etc/fstab UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid 0 0 If a file system found in “/etc/fstab” refers to removable media and it does not have the “nosetuid” option set, this is a finding. Configure the “/etc/fstab” to use the “nosuid” option on file systems that are associated with removable media.
RHEL-07-021012 CCI-000366 medium Files systems that are being imported via Network File System (NFS) must be mounted to prevent files with the setuid and setgid bit set from being executed. The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. Verify file systems that are being NFS exported are mounted with the “nosetuid” option. Find the file system(s) that contain the directories being exported with the following command: # more /etc/fstab | grep nfs UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 0 0 If a file system found in “/etc/fstab” refers to NFS and it does not have the “nosuid” option set, this is a finding. Configure the “/etc/fstab” to use the “nosuid” option on file systems that are being exported via NFS.
RHEL-07-021050 CCI-000366 medium All world-writable directories must be group-owned by root, sys, bin, or an application group. If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others. 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 and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write access. Verify all world-writable directories are group-owned by root, sys, bin, or an application group. Check the system for world-writable directories with the following command: # find / -perm -002 -type d -exec ls -lLd {} \; drwxrwxrwt. 2 root root 40 Aug 26 13:07 /dev/mqueue drwxrwxrwt. 2 root root 220 Aug 26 13:23 /dev/shm drwxrwxrwt. 14 root root 4096 Aug 26 13:29 /tmp If any world-writable directories are not owned by root, sys, bin, or an application group associated with the directory, this is a finding. Change the group of the world-writable directories to root with the following command: # chgrp root <directory>
RHEL-07-021060 CCI-000368 medium The umask must be set to 077 for all local interactive user accounts. 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. Verify that the default umask for all local interactive users is “077”. Identify the locations of all local interactive user home directories by looking at the “/etc/passwd” file. Check all local interactive user initialization files for interactive users with the following command: Note: The example is for a system that is configured to create users home directories in the /home directory. # grep -i umask /home/*/.* If any local interactive user initialization files are found to have a umask statement that has a value less restrictive than “077”, this is a finding. Remove the umask statement from all local interactive users’ initialization files. If the account is for an application, the requirement for a umask less restrictive than "077" can be documented with the Information System Security Manager (ISSM), but the user agreement for access to the account must specify that the local interactive user must log on to their account first and then switch the user to the application account with the correct option to gain the account’s environment variables.
RHEL-07-021160 CCI-000366 medium Cron logging must be implemented. 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. Verify that rsyslog is configured to log cron events. Check the configuration of /etc/rsyslog.conf for the cron facility with the following command: Note: If another logging package is used, substitute the utility configuration file for /etc/rsyslog.conf. # grep cron /etc/rsyslog.conf cron.* /var/log/cron.log If the command does not return a response, check for cron logging all facilities by inspecting the /etc/rsyslog.conf file: # more /etc/rsyslog.conf Look for the following entry: *.* /var/log/messages If rsyslog is not logging messages for the cron facility or all facilities, this is a finding. If the entry is in the “/etc/rsyslog.conf” file but is after the entry: *.*', this is a finding. Configure rsyslog to log all cron messages by adding or updating the following line to /etc/rsyslog.conf: cron.* /var/log/cron.log Note: The line must be added before the following entry if it exists in /etc/rsyslog.conf: *.* ~ # discards everything
RHEL-07-021190 CCI-000366 medium If the cron.allow file exists it must be owned by root. If the owner of the "cron.allow" file is not set to root, the possibility exists for an unauthorized user to view or to edit sensitive information. Verify that the "cron.allow" file is owned by root. Check the owner of the "cron.allow" file with the following command: # l s -al /etc/cron.allow -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow If the “cron.allow” file exists and has an owner other than root, this is a finding. Set the owner on the “/etc/cron.allow” file to root with the following command: # chown root /etc/cron.allow
RHEL-07-021200 CCI-000366 medium If the cron.allow file exists it must be group-owned by root. If the group owner of the “cron.allow” file is not set to root, sensitive information could be viewed or edited by unauthorized users. Verify that the “cron.allow” file is group-owned by root. Check the group owner of the “cron.allow” file with the following command: # ls -al /etc/cron.allow -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow If the “cron.allow” file exists and has a group owner other than root, this is a finding. Set the group owner on the “/etc/cron.allow” file to root with the following command: # chgrp root /etc/cron.allow
RHEL-07-021230 CCI-000366 medium Kernel core dumps must be disabled unless needed. Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may 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. Verify that kernel core dumps are disabled unless needed. Check the status of the “kdump” service with the following command: # systemctl status kdump.service kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago Main PID: 1130 (code=exited, status=0/SUCCESS) kernel arming. If the “kdump” service is active, ask the System Administrator (SA) if the use of the service is required and documented with the Information System Security Manager (ISSM). If the service is active and is not documented, this is a finding. If kernel core dumps are not required, disable the “kdump” service with the following command: # systemctl disable kdump.service If kernel core dumps are required, document the need with the ISSM.
RHEL-07-021240 CCI-000366 low A separate file system must be used for user home directories (such as /home or an equivalent). The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. Verify that a separate file system/partition has been created for non-privileged local interactive user home directories. Check the home directory assignment for all non-privileged users (those with a UID greater than 1000) on the system with the following command: #cut -d: -f 1,3,6,7 /etc/passwd | egrep ":[1-4][0-9]{3}" | tr ":" "\t" adamsj /home/adamsj /bin/bash jacksonm /home/jacksonm /bin/bash smithj /home/smithj /bin/bash The output of the command will give the directory/partition that contains the home directories for the non-privileged users on the system (in this example, /home) and users’ shell. All accounts with a valid shell (such as /bin/bash) are considered interactive users. Check that a file system/partition has been created for the non-privileged interactive users with the following command: Note: The partition of /home is used in the example. # grep /home /etc/fstab UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1 2 If a separate entry for the file system/partition that contains the non-privileged interactive users' home directories does not exist, or the file system/partition for the non-privileged interactive users is not /home, this is a finding. Migrate the /home directory onto a separate file system/partition.
RHEL-07-021250 CCI-000366 low The system must use a separate file system for /var. The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. Verify that a separate file system/partition has been created for /var. Check that a file system/partition has been created for /var with the following command: # grep /var /etc/fstab UUID=c274f65f /var ext4 noatime,nobarrier 1 2 If a separate entry for /var is not in use, this is a finding. Migrate the /var path onto a separate file system.
RHEL-07-021260 CCI-000366 low The system must use /var/log/audit for the system audit data path. The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. Verify that a separate file system/partition has been created for the system audit data path. Check that a file system/partition has been created for the system audit data path with the following command: #grep /var/log/audit /etc/fstab UUID=3645951a /var/log/audit ext4 defaults 1 2 If a separate entry for /var/log/audit does not exist, ask the System Administrator (SA) if the system audit logs are being written to a different file system/partition on the system, then grep for that file system/partition. If a separate file system/partition does not exist for the system audit data path, this is a finding. Migrate the system audit data path onto a separate file system.
RHEL-07-021270 CCI-000366 low The system must use a separate file system for /tmp (or equivalent). The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. Verify that a separate file system/partition has been created for /tmp. Check that a file system/partition has been created for “/tmp” with the following command: # grep /tmp /etc/fstab UUID=7835718b /tmp ext4 nodev,nosetuid,noexec 1 2 If a separate entry for /tmp is not in use, this is a finding. Migrate the /tmp path onto a separate file system.
RHEL-07-021280 CCI-000068 high The operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Use of weak or untested encryption algorithms undermines the purposes of using 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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000396-GPOS-00176, SRG-OS-000478-GPOS-00223 Verify the operating system implements DoD-approved encryption to protect the confidentiality of remote access sessions. Check to see if the dracut-fips package is installed with the following command: # yum list installed | grep dracut-fips dracut-fips-033-360.el7_2.x86_64.rpm If the dracut-fips package is installed, check to see if the kernel command line is configured to use FIPS mode with the following command: Note: GRUB 2 reads its configuration from the “/boot/grub2/grub.cfg” file on traditional BIOS-based machines and from the “/boot/efi/EFI/redhat/grub.cfg” file on UEFI machines. #grep fips /boot/grub2/grub.cfg /vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0 rd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us rd.lvm.lv=rhel/root rhgb fips=1 quiet If the kernel command line is configured to use FIPS mode, check to see if the system is in FIPS mode with the following command: # cat /proc/sys/crypto/fips_enabled 1 If the dracut-fips package is not installed, the kernel command line does not have a fips entry, or the system has a value of “0” for fips_enabled in /proc/sys/crypto, this is a finding. Configure the operating system to implement DoD-approved encryption by installing the dracut-fips package. To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel command line during system installation so key generation is done with FIPS-approved algorithms and continuous monitoring tests in place. Placing a system into FIPS mode after system creation involves a number of modifications to the GRUB2 configuration that are not trivial to implement.
RHEL-07-021600 CCI-000366 low The file integrity tool must be configured to verify Access Control Lists (ACLs). ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools. Verify the file integrity tool is configured to verify ACLs. Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command: # yum list installed | grep aide If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. If there is no application installed to perform integrity checks, this is a finding. Note: AIDE is highly configurable at install time. These commands assume the “aide.conf” file is under the “/etc directory”. Use the following command to determine if the file is in another location: # find / -name aide.conf Check the “aide.conf” file to determine if the “acl” rule has been added to the rule list being applied to the files and directories selection lists. An example rule that includes the “acl” rule is below: All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux /bin All # apply the custom rule to the files in bin /sbin All # apply the same custom rule to the files in sbin If the “acl” rule is not being used on all selection lines in the “/etc/aide.conf” file, or acls are not being checked by another file integrity tool, this is a finding. Configure the file integrity tool to check file and directory acls. If “aide” is installed, ensure the “acl” rule is present on all file and directory selection lists.
RHEL-07-021610 CCI-000366 low The file integrity tool must be configured to verify extended attributes. Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications. Verify the file integrity tool is configured to verify extended attributes. Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command: # yum list installed | grep aide If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. If there is no application installed to perform integrity checks, this is a finding. Note: AIDE is highly configurable at install time. These commands assume the “aide.conf” file is under the “/etc directory”. Use the following command to determine if the file is in another location: # find / -name aide.conf Check the “aide.conf” file to determine if the “xattrs” rule has been added to the rule list being applied to the files and directories selection lists. An example rule that includes the “xattrs” rule follows: All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux /bin All # apply the custom rule to the files in bin /sbin All # apply the same custom rule to the files in sbin If the "xattrs" rule is not being used on all selection lines in the “/etc/aide.conf” file, or extended attributes are not being checked by another file integrity tool, this is a finding. Configure the file integrity tool to check file and directory extended attributes. If AIDE is installed, ensure the “xattrs” rule is present on all file and directory selection lists.
RHEL-07-021620 CCI-000366 medium The file integrity tool must use FIPS 140-2 approved cryptographic hashes for validating file contents and directories. 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. Verify the file integrity tool is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories. Note: If RHEL-07-021280 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes. Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command: # yum list installed | grep aide If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. If there is no application installed to perform integrity checks, this is a finding. Note: AIDE is highly configurable at install time. These commands assume the “aide.conf” file is under the “/etc directory”. Use the following command to determine if the file is in another location: # find / -name aide.conf Check the “aide.conf” file to determine if the “sha512” rule has been added to the rule list being applied to the files and directories selection lists. An example rule that includes the sha512 rule follows: All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux /bin All # apply the custom rule to the files in bin /sbin All # apply the same custom rule to the files in sbin If the “sha512” rule is not being used on all selection lines in the “/etc/aide.conf” file, or another file integrity tool is not using FIPS 140-2 approved cryptographic hashes for validating file contents and directories, this is a finding. Configure the file integrity tool to use FIPS 140-2 cryptographic hashes for validating file and directory contents. If AIDE is installed, ensure the “sha512” rule is present on all file and directory selection lists.
RHEL-07-021760 CCI-000368 medium The system must not allow removable media to be used as the boot loader unless approved. Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. If removable media is designed to be used as the boot loader, the requirement must be documented with the Information System Security Officer (ISSO). Verify the system is not configured to use a boot loader on removable media. Note: GRUB 2 reads its configuration from the “/boot/grub2/grub.cfg” file on traditional BIOS-based machines and from the “/boot/efi/EFI/redhat/grub.cfg” file on UEFI machines. Check for the existence of alternate boot loader configuration files with the following command: # find / -name grub.conf /boot/grub2/grub.cfg If a “grub.cfg” is found in any subdirectories other than “/boot/grub2” and “/boot/efi/EFI/redhat”, ask the System Administrator (SA) if there is documentation signed by the ISSO to approve the use of removable media as a boot loader. Check that the grub configuration file has the set root command in each menu entry with the following commands: # grep -c menuentry /boot/grub2/grub.cfg 1 # grep ‘set root’ /boot/grub2/grub.cfg set root=(hd0,1) If the system is using an alternate boot loader on removable media, and documentation does not exist approving the alternate configuration, this is a finding. Remove alternate methods of booting the system from removable media or document the configuration to boot from removable media with the ISSO.
RHEL-07-021910 CCI-000381 high The telnet-server package must not be installed. It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled. Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed. The telnet service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. Check to see if the telnet-server package is installed with the following command: # yum list installed | grep telnet-server If the telnet-server package is installed, this is a finding. Configure the operating system to disable non-essential capabilities by removing the telnet-server package from the system with the following command: # yum remove telnet-server
RHEL-07-030010 CCI-000131 high Auditing must be configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events. These audit records must also identify individual identities of group account users. Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. Satisfies: SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000042-GPOS-00021, SRG-OS-000254-GPOS-00095, SRG-OS-000255-GPOS-00096 Verify the operating system produces audit records containing information to establish when (date and time) the events occurred. Check to see if auditing is active by issuing the following command: # systemctl is-active auditd.service Active: active (running) since Tue 2015-01-27 19:41:23 EST; 22h ago If the auditd status is not active, this is a finding. Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred. Enable the auditd service with the following command: # chkconfig auditd on
RHEL-07-030090 CCI-000139 medium The operating system must shut down upon audit processing failure, unless availability is an overriding concern. If availability is a concern, the system must alert the designated staff (System Administrator [SA] and Information System Security Officer [ISSO] at a minimum) in the event of an audit processing failure. It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both. Satisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000047-GPOS-00023 Confirm the audit configuration regarding how auditing processing failures are handled. Check to see what level auditctl is set to in /etc/audit/auditd.conf with the following command: # grep \-f /etc/audit/auditd.conf auditctl -f 2 If the value of "-f" is set to “2”, the system is configured to panic (shut down) in the event of an auditing failure. If the value of "-f" is set to “1”, the system is configured to only send information to the kernel log regarding the failure. If the "-f" flag is not set, this is a CAT I finding. If the "-f" flag is set to any value other than “1” or “2”, this is a CAT II finding. If the "-f" flag is set to “1” but the availability concern is not documented or there is no monitoring of the kernel log, this is a CAT III finding. Configure the operating system to shut down in the event of an audit processing failure. Add or correct the following line in the /etc/audit/auditd.confs file: auditctl -f 2 If availability has been determined to be more important, and this decision is documented with the ISSO, configure the operating system to notify system administration staff and ISSO staff in the event of audit processing failure. Add or correct the following line in the /etc/audit/auditd.conf file: auditctl -f 1 Kernel log monitoring must also be configured to properly alert designed staff. The audit daemon must be restarted for the changes to take effect.
RHEL-07-030310 CCI-002234 medium All privileged function executions must be audited. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat. Verify the operating system audits the execution of privileged functions. To find relevant setuid and setgid programs, use the following command once for each local partition [PART]: # find [PART] -xdev -local -type f \( -perm -4000 -o -perm -2000 \) 2>/dev/null Run the following command to verify entries in the audit rules for all programs found with the previous command: #grep <suid_prog_with_full_path> a always,exit -F <suid_prog_with_full_path> -F perm=x -F auid>=1000 -F auid!=4294967295 -k setuid/setgid All setuid and setgid files on the system must have a corresponding audit rule, or must have an audit rule for the (sub) directory that contains the setuid/setgid file. If all setuid/setgid files on the system do not have audit rule coverage, this is a finding. Configure the operating system to audit the execution of privileged functions. To find the relevant setuid/setgid programs, run the following command for each local partition [PART]: # find [PART] -xdev -type f \( -perm -4000 -o -perm -2000 \) 2>/dev/null For each setuid/setgid program on the system, which is not covered by an audit rule for a (sub) directory (such as /usr/sbin), add a line of the following form to "/etc/audit/rules.d/audit.rules", where <suid_prog_with_full_path> is the full path to each setuid/setgid program in the list: a always,exit -F <suid_prog_with_full_path> -F perm=x -F auid>=1000 -F auid!=4294967295 -k setuid/setgid
RHEL-07-030330 CCI-001851 medium The operating system must off-load audit records onto a different system or media from the system being audited. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224 Verify the operating system off-loads audit records onto a different system or media from the system being audited. To determine the remote server that the records are being sent to, use the following command: # grep -i remote_server /etc/audisp/audisp-remote.conf remote_server = 10.0.21.1 If a remote server is not configured, or the line is commented out, this is a finding. Configure the operating system 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 the IP address of the log aggregation server.
RHEL-07-030331 CCI-001851 medium The operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224 Verify the operating system encrypts audit records off-loaded onto a different system or media from the system being audited. To determine if the transfer is encrypted, use the following command: # grep -i enable_krb5 /etc/audisp/audisp-remote.conf enable_krb5 = yes If the value of the “enable_krb5” option is not set to "yes" or the line is commented out, this is a finding. 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
RHEL-07-030340 CCI-001851 medium The audit system must take appropriate action when the audit storage volume is full. Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records. Verify the action the operating system takes if the disk the audit records are written to becomes full. To determine the action that takes place if the disk is full on the remote server, use the following command: # grep -i disk_full_action /etc/audisp/audisp-remote.conf disk_full_action = single To determine the action that takes place if the network connection fails, use the following command: # grep -i network_failure_action /etc/audisp/audisp-remote.conf network_failure_action = stop If the value of the “network_failure_action” option is not “syslog”, “single”, or “halt”, or the line is commented out, this is a finding. If the value of the “disk_full_action” option is not "syslog", "single", or "halt", or the line is commented out, this is a finding. Configure the operating system to off-load audit records onto a different system or media from the system being audited. Uncomment or edit the "disk_full_action" option in /etc/audisp/audisp-remote.conf and set it to syslog, single, or halt, such as the following line: disk_full_action = single Uncomment the network_failure_action option in /etc/audisp/audisp-remote.conf and set it to syslog, single, or halt.
RHEL-07-030350 CCI-001855 medium The operating system must immediately notify the System Administrator (SA) and Information System Security Officer ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity. If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion. Verify the operating system immediately notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. Check the system configuration to determine the partition the audit records are being written to with the following command: # grep log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log Check the size of the partition that audit records are written to (with the example being /var/log/audit/): # df -h /var/log/audit/ 0.9G /var/log/audit If the audit records are not being written to a partition specifically created for audit records (in this example /var/log/audit is a separate partition), determine the amount of space other files in the partition are currently occupying with the following command: # du -sh <partition> 1.8G /var Determine what the threshold is for the system to take action when 75 percent of the repository maximum audit record storage capacity is reached: # grep -i space_left /etc/audit/auditd.conf space_left = 225 If the value of the “space_left” keyword is not set to 75 percent of the total partition size, this is a finding. Configure the operating system to immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. Check the system configuration to determine the partition the audit records are being written to: # grep log_file /etc/audit/auditd.conf Determine the size of the partition that audit records are written to (with the example being /var/log/audit/): # df -h /var/log/audit/ Set the value of the “space_left” keyword in /etc/audit/auditd.conf to 75 percent of the partition size.
RHEL-07-030351 CCI-001855 medium The operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached. If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost. Verify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. Check what action the operating system takes when the threshold for the repository maximum audit record storage capacity is reached with the following command: # grep -I space_left_action /etc/audit/auditd.conf space_left_action = email If the value of the “space_left_action” keyword is not set to email, this is a finding. Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached. Uncomment or edit the “space_left_action” keyword in /etc/audit/auditd.conf and set it to email. space_left_action = email
RHEL-07-030352 CCI-001855 medium The operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached. If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost. Verify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached. Check what account the operating system emails when the threshold for the repository maximum audit record storage capacity is reached with the following command: # grep -i action_mail_acct /etc/audit/auditd.conf action_mail_acct = root If the value of the “action_mail_acct” keyword is not set to “root” and other accounts for security personnel, this is a finding. Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached. Uncomment or edit the action_mail_acct keyword in /etc/audit/auditd.conf and set it to root and any other accounts associated with security personnel. action_mail_acct = root
RHEL-07-030380 CCI-000172 medium All uses of the chown command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chown” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i chown /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chown” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030381 CCI-000172 medium All uses of the fchown command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchown” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i fchown /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Verify the operating system generates audit records when successful/unsuccessful attempts to use the fchown command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030382 CCI-000172 medium All uses of the lchown command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lchown” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i lchown /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lchown” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030383 CCI-000172 medium All uses of the fchownat command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchownat” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i fchownat /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchownat” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030390 CCI-000172 medium All uses of the chmod command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chmod” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following command: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i chmod /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chmod” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030391 CCI-000172 medium All uses of the fchmod command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchmod” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following command: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i fchmod /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fchmod” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030392 CCI-000172 medium All uses of the fchmodat command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchmodat” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following command: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i fchmodat /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fchmodat” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030400 CCI-000172 medium All uses of the setxattr command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “setxattr” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i setxattr /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “setxattr” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030401 CCI-000172 medium All uses of the fsetxattr command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fsetxattr” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i fsetxattr /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fsetxattr” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030402 CCI-000172 medium All uses of the lsetxattr command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lsetxattr” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i lsetxattr /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “lsetxattr” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030403 CCI-000172 medium All uses of the removexattr command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “removexattr” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i removexattr /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “removexattr” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030404 CCI-000172 medium All uses of the fremovexattr command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fremovexattr” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i fremovexattr /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fremovexattr” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030405 CCI-000172 medium All uses of the lremovexattr command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lremovexattr” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i lremovexattr /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “lremovexattr” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod The audit daemon must be restarted for the changes to take effect.
RHEL-07-030420 CCI-000172 medium All uses of the creat command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “creat” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i creat /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S creat -Fexit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “creat” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access The audit daemon must be restarted for the changes to take effect.
RHEL-07-030421 CCI-000172 medium All uses of the open command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “open” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i open /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S open -Fexit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “open” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access The audit daemon must be restarted for the changes to take effect.
RHEL-07-030422 CCI-000172 medium All uses of the openat command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “openat” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i openat /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S openat -Fexit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “openat” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access The audit daemon must be restarted for the changes to take effect.
RHEL-07-030423 CCI-000172 medium All uses of the open_by_handle_at command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “open_by_handle_at” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i open_by_handle_at /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S open_by_handle_at -Fexit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “open_by_handle_at” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access The audit daemon must be restarted for the changes to take effect.
RHEL-07-030424 CCI-000172 medium All uses of the truncate command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “truncate” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i truncate /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S truncate -Fexit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the truncate command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access The audit daemon must be restarted for the changes to take effect.
RHEL-07-030425 CCI-000172 medium All uses of the ftruncate command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “ftruncate” command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i ftruncate /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S ftruncate -Fexit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “ftruncate” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access The audit daemon must be restarted for the changes to take effect.
RHEL-07-030441 CCI-000172 medium All uses of the semanage command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “semanage” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/sbin/semanage /etc/audit/rules.d/audit.rules If the command does not return the following output, this is a finding. -a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change Configure the operating system to generate audit records when successful/unsuccessful attempts to use the semanage command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030442 CCI-000172 medium All uses of the setsebool command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “setsebool” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/sbin/setsebool /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “setsebool” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030443 CCI-000172 medium All uses of the chcon command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chcon” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/bin/chcon /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chcon” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030444 CCI-000172 medium All uses of the restorecon command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “restorecon” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/sbin/restorecon /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/sbin/restorecon -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “restorecon” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/sbin/restorecon -F perm=x -F auid>=1000 -F auid!=4294967295 -k -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 privileged-priv_change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030490 CCI-000172 medium The operating system must generate audit records for all successful/unsuccessful account access count events. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218 Verify the operating system generates audit records when successful/unsuccessful account access count events occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following commands: # grep -i /var/log/tallylog etc/audit/audit.rules -w /var/log/tallylog -p wa -k logins If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful account access count events occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -w /var/log/tallylog -p wa -k logins The audit daemon must be restarted for the changes to take effect.
RHEL-07-030491 CCI-000172 medium The operating system must generate audit records for all unsuccessful account access events. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218 Verify the operating system generates audit records when unsuccessful account access events occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following commands: # grep -i /var/run/faillock etc/audit/audit.rules -w /var/run/faillock -p wa -k logins If the command does not return any output, this is a finding. Configure the operating system to generate audit records when unsuccessful account access events occur. Add or update the following rules in /etc/audit/rules.d/audit.rule: -w /var/run/faillock/ -p wa -k logins The audit daemon must be restarted for the changes to take effect.
RHEL-07-030492 CCI-000172 medium The operating system must generate audit records for all successful account access events. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218 Verify the operating system generates audit records when successful account access events occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: # grep -i /var/log/lastlog etc/audit/audit.rules -w /var/log/lastlog -p wa -k logins If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful account access events occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -w /var/log/lastlog -p wa -k logins The audit daemon must be restarted for the changes to take effect.
RHEL-07-030510 CCI-000135 medium All uses of the passwd command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “passwd” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/bin/passwd /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “passwd” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd The audit daemon must be restarted for the changes to take effect.
RHEL-07-030511 CCI-000135 medium All uses of the unix_chkpwd command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “unix_chkpwd” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /sbin/unix_chkpwd /etc/audit/rules.d/audit.rules -a always,exit -F path=/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “unix_chkpwd” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd The audit daemon must be restarted for the changes to take effect.
RHEL-07-030512 CCI-000135 medium All uses of the gpasswd command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “gpasswd” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/bin/gpasswd /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “gpasswd” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd The audit daemon must be restarted for the changes to take effect.
RHEL-07-030513 CCI-000135 medium All uses of the chage command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chage” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/bin/chage /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chage” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd The audit daemon must be restarted for the changes to take effect.
RHEL-07-030514 CCI-000135 medium All uses of the userhelper command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “userhelper” command occur. Check the file system rule in /etc/audit/rules.d/audit.rules with the following command: # grep -i /usr/sbin/userhelper /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “userhelper” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd The audit daemon must be restarted for the changes to take effect.
RHEL-07-030521 CCI-000130 medium All uses of the su command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: 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 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “su” command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /bin/su /etc/audit/rules.d/audit.rules -a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “su” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030522 CCI-000130 medium All uses of the sudo command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: 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 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “sudo” command occur. Check for the following system calls being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/bin/sudo /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “sudo” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030526 CCI-000130 medium All uses of the sudoedit command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: 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 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “sudoedit” command occur. Check for the following system calls being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/bin/sudoedit /etc/audit/rules.d/audit.rules -a always,exit -F path=/bin/sudoedit-F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “sudoedit” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/bin/sudoedit-F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
RHEL-07-030523 CCI-000130 medium The operating system must generate audit records containing the full-text recording of modifications to sudo configuration files. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: 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 Verify the operating system generates audit records containing the full-text recording of modifications to sudo configuration files. Check for modification of the following files being audited by performing the following commands to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /etc/sudoers /etc/audit/rules.d/audit.rules -w /etc/sudoers -p wa -k privileged-actions # grep -i /etc/sudoers.d/etc/audit/rules.d/audit.rules -w /etc/sudoers.d/ -p wa -k privileged-actions If the command does not return output that does not match the examples, this is a finding. Configure the operating system to generate audit records containing the full-text recording of modifications to sudo configuration files. Add or update the following rule in /etc/audit/rules.d/audit.rules: -w /etc/sudoers -p wa -k privileged-actions -w /etc/sudoers.d/ -p wa -k privileged-actions
RHEL-07-030524 CCI-000130 medium All uses of the newgrp command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: 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 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “newgrp” command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/bin/newgrp /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “newgrp” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
RHEL-07-030525 CCI-000130 medium All uses of the chsh command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: 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 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chsh” command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/bin/chsh /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chsh” command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
RHEL-07-030530 CCI-000135 medium All uses of the mount command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “mount” command occur. Check for the following system calls being audited by performing the following series of commands to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /bin/mount /etc/audit/rules.d/audit.rules -a always,exit -F path=/bin/mount -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-mount If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “mount” command occur. Add or update the following rules in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/bin/mount -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-mount The audit daemon must be restarted for the changes to take effect.
RHEL-07-030531 CCI-000135 medium All uses of the umount command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the “umount” command occur. Check for the following system calls being audited by performing the following series of commands to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /bin/umount /etc/audit/rules.d/audit.rules -a always,exit -F path=/bin/umount -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-mount If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the umount command occur. Add or update the following rules in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/bin/umount -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-mount The audit daemon must be restarted for the changes to take effect.
RHEL-07-030540 CCI-000135 medium All uses of the postdrop command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the postdrop command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/sbin/postdrop /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the postdrop command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix The audit daemon must be restarted for the changes to take effect.
RHEL-07-030541 CCI-000135 medium All uses of the postqueue command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the postdrop command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/sbin/postqueue /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the postqueue command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix The audit daemon must be restarted for the changes to take effect.
RHEL-07-030550 CCI-000135 medium All uses of the ssh-keysign command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged ssh commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the ssh-keysign command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/libexec/openssh/ssh-keysign /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-ssh If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the ssh-keysign command occur. Add or update the following rule to /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-ssh The audit daemon must be restarted for the changes to take effect.
RHEL-07-030560 CCI-000135 medium All uses of the pt_chown command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the pt_chown command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/libexec/pt_chown /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/libexec/pt_chown -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged_terminal If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the pt_chown command occur. Add or update the following rule to /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/libexec/pt_chown -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged_terminal The audit daemon must be restarted for the changes to take effect.
RHEL-07-030561 CCI-000135 medium All uses of the crontab command must be audited. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215 Verify the operating system generates audit records when successful/unsuccessful attempts to use the crontab command occur. Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: # grep -i /usr/bin/crontab /etc/audit/rules.d/audit.rules -a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-cron If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the crontab command occur. Add or update the following rule to /etc/audit/rules.d/audit.rules: -a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-cron The audit daemon must be restarted for the changes to take effect.
RHEL-07-030630 CCI-000172 medium All uses of the pam_timestamp_check command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Verify the operating system generates audit records when successful/unsuccessful attempts to use the pam_timestamp_check command occur. Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command: # grep -i /sbin/pam_timestamp_check /etc/audit/rules.d/audit.rules -a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-pam If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the pam_timestamp_check command occur. Add or update the following rule in /etc/audit/rules.d/audit.rules: -a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-pam The audit daemon must be restarted for the changes to take effect.
RHEL-07-030670 CCI-000172 medium All uses of the init_module command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222 Verify the operating system generates audit records when successful/unsuccessful attempts to use the init_module command occur. Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present. # grep -i init_module /etc/audit/etc/audit/rules.d/audit.rules If the command does not return the following output (appropriate to the architecture), this is a finding. -a always,exit -F arch=b32 -S init_module -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change -a always,exit -F arch=b64 -S init_module -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change If the command does not return any output, this is a finding. Configure the operating system generates audit records when successful/unsuccessful attempts to use the init_module command occur. Add or update the following rules to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S init_module -F key=module-change -a always,exit -F arch=b64 -S init_module -F key=module-change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030671 CCI-000172 medium All uses of the delete_module command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222 Verify the operating system generates audit records when successful/unsuccessful attempts to use the delete_module command occur. Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present. # grep -i delete_module /etc/audit/etc/audit/rules.d/audit.rules If the command does not return the following output (appropriate to the architecture), this is a finding. -a always,exit -F arch=b32 -S delete_module -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change -a always,exit -F arch=b64 -S delete_module -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the delete_module command occur. Add or update the following rules to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S delete_module -F key=module-change -a always,exit -F arch=b64 -S delete_module -F key=module-change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030672 CCI-000172 medium All uses of the insmod command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222 Verify the operating system generates audit records when successful/unsuccessful attempts to use the insmod command occur. Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command: # grep -i insmod /etc/audit/etc/audit/rules.d/audit.rules If the command does not return the following output (appropriate to the architecture), this is a finding. -w /sbin/insmod -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the insmod command occur. Add or update the following rule to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -w /sbin/insmod -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030673 CCI-000172 medium All uses of the rmmod command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222 Verify the operating system generates audit records when successful/unsuccessful attempts to use the rmmod command occur. Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command: # grep -i rmmod /etc/audit/etc/audit/rules.d/audit.rules If the command does not return the following output (appropriate to the architecture), this is a finding. -w /sbin/rmmod -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the rmmod command occur. Add or update the following rule to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -w /sbin/rmmod-p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030674 CCI-000172 medium All uses of the modprobe command must be audited. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222 Verify the operating system generates audit records when successful/unsuccessful attempts to use the modprobe command occur. Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present. # grep -i modprobe /etc/audit/etc/audit/rules.d/audit.rules If the command does not return the following output (appropriate to the architecture), this is a finding. -w /sbin/modprobe -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the modprobe command occur. Add or update the following rule to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): -w /sbin/modprobe -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change The audit daemon must be restarted for the changes to take effect.
RHEL-07-030710 CCI-000018 medium The operating system must generate audit records for all account creations, modifications, disabling, and termination events. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000241-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221 Verify the operating system automatically audits account creation by performing the following series of commands to check the file system rules in /etc/audit/rules.d/audit.rules: # grep /etc/group /etc/audit/rules.d/audit.rules If the command does not return the following output, this is a finding. -w /etc/group -p wa -k audit_rules_usergroup_modification # grep /etc/passwd /etc/audit/rules.d/audit.rules If the command does not return the following output, this is a finding. -w /etc/passwd -p wa -k audit_rules_usergroup_modification # grep /etc/gshadow /etc/audit/rules.d/audit.rules If the command does not return the following output, this is a finding. -w /etc/gshadow -p wa -k audit_rules_usergroup_modification # grep /etc/shadow /etc/audit/rules.d/audit.rules If the command does not return the following output, this is a finding. -w /etc/shadow -p wa -k audit_rules_usergroup_modification # grep /etc/security/opasswd /etc/audit/rules.d/audit.rules If the command does not return the following output, this is a finding. -w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events. Add or update the following file system rules to /etc/audit/rules.d/audit.rules: -w /etc/group -p wa -k identity -w /etc/passwd -p wa -k identity -w /etc/gshadow -p wa -k identity -w /etc/shadow -p wa -k identity -w /etc/security/opasswd -p wa -k identity The audit daemon must be restarted for the changes to take effect.
RHEL-07-030750 CCI-000172 medium All uses of the rename command must be audited. If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise. Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the rename command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i rename /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S rename -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S rename -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the rename command occur. Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S rename -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S rename -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete The audit daemon must be restarted for the changes to take effect.
RHEL-07-030751 CCI-000172 medium All uses of the renameat command must be audited. If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise. Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the renameat command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i renameat /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S renameat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S renameat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the renameat command occur. Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S renameat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S renameat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete The audit daemon must be restarted for the changes to take effect.
RHEL-07-030752 CCI-000172 medium All uses of the rmdir command must be audited. If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise. Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the rmdir command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i rmdir /etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S rmdir -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S rmdir -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the rmdir command occur. Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S rmdir -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S rmdir -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete The audit daemon must be restarted for the changes to take effect.
RHEL-07-030753 CCI-000172 medium All uses of the unlink command must be audited. If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise. Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the unlink command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i unlink/etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S unlink -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S unlink -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the unlink command occur. Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S unlink -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S unlink -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete The audit daemon must be restarted for the changes to take effect.
RHEL-07-030754 CCI-000172 medium All uses of the unlinkat command must be audited. If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise. Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172 Verify the operating system generates audit records when successful/unsuccessful attempts to use the unlinkat command occur. Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present. # grep -i unlinkat/etc/audit/rules.d/audit.rules -a always,exit -F arch=b32 -S unlinkat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S unlinkat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete If the command does not return any output, this is a finding. Configure the operating system to generate audit records when successful/unsuccessful attempts to use the unlinkat command occur. Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture): -a always,exit -F arch=b32 -S unlinkat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete -a always,exit -F arch=b64 -S unlinkat -F perm=x -F auid>=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete The audit daemon must be restarted for the changes to take effect.
RHEL-07-030770 CCI-000366 medium The system must send rsyslog output to a log aggregation server. Sending rsyslog output to another system ensures that the logs cannot be removed or modified in the event that the system is compromised or has a hardware failure. Verify “rsyslog” is configured to send all messages to a log aggregation server. Check the configuration of “rsyslog” with the following command: # grep @ /etc/rsyslog.conf *.* @@logagg.site.mil If there are no lines in the “/etc/rsyslog.conf” file that contain the “@” or “@@” symbol(s), and the lines with the correct symbol(s) to send output to another system do not cover all “rsyslog” output, this is a finding. Modify the “/etc/rsyslog.conf” file to contain a configuration line to send all “rsyslog” output to a log aggregation system: *.* @@<log aggregation system name>
RHEL-07-030780 CCI-000368 medium The rsyslog daemon must not accept log messages from other servers unless the server is being used for log aggregation. Unintentionally running a rsyslog server accepting remote messages puts the system at increased risk. Malicious rsyslog messages sent to the server could exploit vulnerabilities in the server software itself, could introduce misleading information in to the system's logs, or could fill the system's storage leading to a Denial of Service. If the system is intended to be a log aggregation server its use must be documented with the ISSO. Verify that the system is not accepting "rsyslog" messages from other systems unless it is documented as a log aggregation server. Check the configuration of rsyslog with the following command: # grep imtcp /etc/rsyslog.conf ModLoad imtcp If the "imtcp" module is being loaded in the "/etc/rsyslog.conf" file ask to see the documentation for the system being used for log aggregation. If the documentation does not exist, or does not specify the server as a log aggregation system, this is a finding. Modify the “/etc/rsyslog.conf” file to remove the “ModLoad imtcp” configuration line, or document the system as being used for log aggregation.
RHEL-07-030810 CCI-001668 high The system must use a DoD-approved virus scan program. 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. Verify the system is using a DoD-approved virus scan program. Check for the presence of “McAfee VirusScan Enterprise for Linux” with the following command: # systemctl status nails nails - service for McAfee VirusScan Enterprise for Linux > Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.<build_number>; enabled) > Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago If the “nails” service is not active, check for the presence of “clamav” on the system with the following command: # systemctl status clamav-daemon.socket systemctl status clamav-daemon.socket clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled) Active: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago If neither of these applications are loaded and active, ask the System Administrator (SA) if there is an antivirus package installed and active on the system. If no antivirus scan program is active on the system, this is a finding. Install an approved DoD antivirus solution on the system.
RHEL-07-030820 CCI-001668 medium The system must update the DoD-approved virus scan program every seven days or more frequently. 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 check for software and virus definition updates with a frequency no longer than seven days. If a manual process is required to update the virus scan software or definitions, it must be documented with the Information System Security Manager (ISSM). Verify the system is using a DoD-approved virus scan program and the virus definition file is less than seven days old. Check for the presence of “McAfee VirusScan Enterprise for Linux” with the following command: # systemctl status nails nails - service for McAfee VirusScan Enterprise for Linux > Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.<build_number>; enabled) > Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago If the “nails” service is not active, check for the presence of “clamav” on the system with the following command: # systemctl status clamav-daemon.socket systemctl status clamav-daemon.socket clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled) Active: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago If “McAfee VirusScan Enterprise for Linux” is active on the system, check the dates of the virus definition files with the following command: # ls -al /opt/NAI/LinuxShield/engine/dat/*.dat <need output> If the virus definition files have dates older than seven days from the current date, this is a finding. If “clamav” is active on the system, check the dates of the virus database with the following commands: # grep -I databasedirectory /etc/clamav.conf DatabaseDirectory /var/lib/clamav # ls -al /var/lib/clamav/*.cvd -rwxr-xr-x 1 root root 149156 Mar 5 2011 daily.cvd If the database file has a date older than seven days from the current date, this is a finding. Update the approved DoD virus scan software and virus definition files.
RHEL-07-040010 CCI-000054 low The operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types. Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to DoS attacks. This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system. Verify the operating system limits the number of concurrent sessions to ten for all accounts and/or account types by issuing the following command: # grep "maxlogins" /etc/security/limits.conf * hard maxlogins 10 This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains. If the maxlogins item is missing or the value is not set to 10 or less for all domains that have the maxlogins item assigned, this is a finding. Configure the operating system to limit the number of concurrent sessions to 10 for all accounts and/or account types. Add the following line to the top of the /etc/security/limits.conf: * hard maxlogins 10
RHEL-07-040020 CCI-000067 medium The system must log informational authentication data. Access services, such as those providing remote access to network devices and information systems, that lack automated monitoring capabilities increase risk and make remote user access management difficult at best. Automated monitoring of access sessions allows organizations to detect cyber attacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets). Verify the operating system logs informational authentication data. Check to see if rsyslog is logging authentication information with the following commands: # grep auth* /etc/rsyslog.conf auth,authpriv.debug /var/log/auth.log # grep daemon.* /etc/rsyslog.conf daemon.notice /var/log/messages If the auth, authpriv, and daemon facilities are not being logged, or they are being logged at a priority of notice or higher, this is a finding. Configure the operating system to log informational authentication data. Add the following rules to the /etc/rsyslog.conf file: auth.*,authpriv.* /var/log/auth.log daemon.notice /var/log/messages
RHEL-07-040030 CCI-000185 medium The operating system, for PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. A certificate’s certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. Certification path validation includes checks such as certificate issuer trust, time validity, and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses. Operating systems that do not validate certificates by performing RFC 5280-compliant certification path validation to a trust anchor are in danger of accepting certificates that are invalid and or counterfeit. This could allow unauthorized access to a system. Verify the operating system, for PKI–based authentication, validates certificates by performing RFC 5280–compliant certification path validation. Check to see if Online Certificate Status Protocol (OCSP) is enabled on the system with the following command: # grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf cert_policy =ca, ocsp_on, signature; cert_policy =ca, ocsp_on, signature; cert_policy =ca, ocsp_on, signature; There must be at least three lines returned. If oscp_on is present in all cert_policy lines this is not a finding. If oscp_on is not present in all lines check for the presence of certificate revocation lists: # grep crl_dir = /etc/pam_pkcs11/crls crl_dir = /etc/pam_pkcs11/crls; Check the returned directory for the presence of a crl file. If the file exists this in the configured directory is not a finding. If the system is not configured to use OCSP or crls, or the crls file is missing, this is a finding. Configure the operating system, for PKI-based authentication, to validate certificates by performing RFC 5280-compliant certification path validation. Set all cert_policy lines to use Online Certificate Status Protocol (OCSP) in /etc/pam_pkcs11/pam_pkcs11.conf: cert_policy = ca, ocsp_on, signature; If the system cannot use OCSP, configure the system to use certificate revocation lists in /etc/pam_pkcs11/ pam_pkcs11.conf: crl_dir = /etc/pam_pkcs11/crls; and place a certificate revocation file in the configured directory.
RHEL-07-040040 CCI-000186 medium The operating system, for PKI-based authentication, must enforce authorized access to all PKI private keys stored or used by the operating system. If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If private keys are stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key(s) to digitally sign data and thus impersonate the associated subjects (systems or users). Both the holders of a digital certificate and the issuing authority must take careful measures to protect the corresponding private keys. Private keys should always be generated and protected in appropriate FIPS 140-2 validated cryptographic modules. Verify the operating system, for PKI–based authentication, enforces authorized access to all PKI private keys stored/utilized by the operating system. Check the module being used by the system smartcard architecture with the following command: # grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf use_pkcs11_module = cackey; If the module returned is not cackey or coolkey, or the line is commented out, this is a finding. Configure the operating system, for PKI-based authentication, to enforce authorized access to all PKI private keys stored or used by the operating system. To use cackey edit /etc/pam_pkcs11/pam_pkcs11.conf: Change the use_pkcs11_module option to cackey. use_pkcs11_module = cackey; Then directly after the aforementioned line, copy the following lines: # Cackey Support pkcs11_module cackey { module = /usr/lib64/libcackey.so; description = "Cackey"; slot_num = 0; support_threads = false; ca_dir = /etc/pam_pkcs11/cacerts; crl_dir = /etc/pam_pkcs11/crls; cert_policy = signature; } To use coolkey edit /etc/pam_pkcs11/pam_pkcs11.conf: Change the use_pkcs11_module option to coolkey. use_pkcs11_module = coolkey; Then directly after the aforementioned line, copy the following lines: # Cackey Support pkcs11_module coolkey { module = libcoolkeypk11.so; description = "Coolkey"; slot_num = 0; support_threads = false; ca_dir = “/etc/pam_pkcs11/cacerts”; crl_dir = “/etc/pam_pkcs11/crls”; cert_policy = signature; } Find and change the line: use_mappers = digest, cn, pwent, uid, mail, subject, null; to use_mappers = subject;
RHEL-07-040050 CCI-000187 medium The operating system must map the authenticated identity to the user or group account for PKI-based authentication. Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. Verify the operating system maps the authenticated identity to the user or group account for PKI–based authentication by verifying the common name map file exists with the following command: # ls –al /etc/pam_pkcs11/cn_map –rw–r––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/subject_mapping If the file does not exist, this is a finding. Configure the operating system to map the authenticated identity to the user or group account for PKI-based authentication by creating the common name map file with the following command: # touch /etc/pam_pkcs11/subject_mapping
RHEL-07-040060 CCI-000187 medium The cn_map file must have mode 0644 or less permissive. Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. Verify the operating system protects the file that maps the authenticated identity to the user or group account for PKI–based authentication. Check the mode on the cn_map file with the following command: # ls –al /etc/pam_pkcs11/cn_map –rw––––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/cn_map If the cn_map file has a mode more permissive than “0644”, this is a finding. Configure the operating system to protect the file that maps the authenticated identity to the user or group account for PKI-based authentication by setting the mode on the cn_map file to “0644” with the following command: # chmod 0644 /etc/pam_pkcs11/cn_map
RHEL-07-040070 CCI-000187 medium The cn_map file must be owned by root. Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. Verify the operating system protects the file that maps the authenticated identity to the user or group account for PKI–based authentication. Check the owner on the cn_map file with the following command: # ls –al /etc/pam_pkcs11/cn_map –rw––––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/cn_map If the cn_map file has an owner other than root, this is a finding. Configure the operating system to protect the file that maps the authenticated identity to the user or group account for PKI-based authentication by setting the owner on the cn_map file to root with the following command: # chown root /etc/pam_pkcs11/cn_map
RHEL-07-040080 CCI-000187 medium The cn_map file must be group owned by root. Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. Verify the operating system protects the file that maps the authenticated identity to the user or group account for PKI–based authentication. Check the group owner on the cn_map file with the following command: # ls –al /etc/pam_pkcs11/cn_map –rw––––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/cn_map If the cn_map file has a group owner other than root, this is a finding. Configure the operating system to protect the file that maps the authenticated identity to the user or group account for PKI-based authentication by setting the group owner on the cn_map file to root with the following command: # chgrp root /etc/pam_pkcs11/cn_map
RHEL-07-040100 CCI-000382 medium The host must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA) and vulnerability assessments. In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical 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. Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115 Inspect the firewall configuration and running services to verify that it is configured to prohibit or restrict the use of functions, ports, protocols, and/or services that are unnecessary or prohibited. Check which services are currently active with the following command: # firewall-cmd --list-all public (default, active) interfaces: enp0s3 sources: services: dhcpv6-client dns http https ldaps rpc-bind ssh ports: masquerade: no forward-ports: icmp-blocks: rich rules: Ask the system administrator for the site or program PPSM CLSA. Verify the services allowed by the firewall match the PPSM CLSA. If there are additional ports, protocols, or services that are not in the PPSM CLSA, or there are ports, protocols, or services that are prohibited by the PPSM Category Assurance List (CAL), this is a finding. Update the host's firewall settings and/or running services to comply with the PPSM CLSA for the site or program and the PPSM CAL.
RHEL-07-040110 CCI-000068 medium A FIPS 140-2 approved cryptographic algorithm must be used for SSH communications. Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised. Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system. Satisfies: 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 Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. Note: If RHEL-07-021280 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes. The location of the sshd_config file may vary on the system and can be found using the following command: # find / -name ‘sshd*_config’ If there is more than one ssh server daemon configuration file on the system, determine which daemons are active on the system with the following command: # ps -ef | grep sshd The command will return the full path of the ssh daemon. This will indicate which sshd_config file will be checked with the following command: # grep -i ciphers /etc/ssh/sshd_config Ciphers aes128-ctr aes192-ctr, aes256-ctr If any ciphers other than “aes128-ctr”, “aes192-ctr”, or “aes256-ctr” are listed, the “Ciphers” keyword is missing, or the retuned line is commented out, this is a finding. Configure SSH to use FIPS 140-2 approved cryptographic algorithms. Add the following line (or modify the line to have the required value) to the /etc/ssh/sshd_config file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). Ciphers aes128-ctr aes192-ctr, aes256-ctr
RHEL-07-040160 CCI-001133 medium All network connections associated with a communication session must be terminated at the end of the session or after 10 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements. Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. Verify the operating system terminates all network connections associated with a communications session at the end of the session or based on inactivity. Check the value of the system inactivity timeout with the following command: # grep -i tmout /etc/profile TMOUT=600 If “TMOUT” is not set to 600 or less in /etc/profile, this is a finding. Configure the operating system to terminate all network connections associated with a communications session at the end of the session or after a period of inactivity. Add the following line to /etc/profile (or modify the line to have the required value): TMOUT=600
RHEL-07-040170 CCI-000048 medium The Standard Mandatory DoD Notice and Consent Banner must be displayed immediately prior to, or as part of, remote access logon prompts. Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007 , SRG-OS-000228-GPOS-00088 Verify any publicly accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. Check for the location of the banner file being used with the following command: # grep -i banner /etc/ssh/sshd_config banner=/etc/issue This command will return the banner keyword and the name of the file that contains the ssh banner (in this case /etc/issue). If the line is commented out, this is a finding. View the file specified by the banner keyword to check that it matches the text of the Standard Mandatory DoD Notice and Consent Banner: "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.” If the system does not display a graphical logon banner or the banner does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding. If the text in the file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding. Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the ssh. Edit the /etc/ssh/sshd_config file to uncomment the banner keyword and configure it to point to a file that will contain the logon banner (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). An example configuration line is: banner=/etc/issue Either create the file containing the banner or replace the text in the file with the Standard Mandatory DoD Notice and Consent Banner. The DoD required text is: "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."
RHEL-07-040180 CCI-001453 medium The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications. 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 secret key used to generate the hash. Verify the operating system implements cryptography to protect the integrity of remote LDAP authentication sessions. To determine if LDAP is being used for authentication, use the following command: # grep -i useldapauth /etc/sysconfig/authconfig USELDAPAUTH=yes If USELDAPAUTH=yes, then LDAP is being used. To see if LDAP is configured to use TLS, use the following command: # grep -i ssl /etc/pam_ldap.conf ssl start_tls If the “ssl” option is not “start_tls”, this is a finding. Configure the operating system to implement cryptography to protect the integrity of LDAP authentication sessions. Set the USELDAPAUTH=yes in /etc/sysconfig/authconfig. Set ssl start_tls in /etc/pam_ldap.conf.
RHEL-07-040181 CCI-001453 medium The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. 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 secret key used to generate the hash. Verify the operating system implements cryptography to protect the integrity of remote LDAP access sessions. To determine if LDAP is being used for authentication, use the following command: # grep -i useldapauth /etc/sysconfig/authconfig USELDAPAUTH=yes If USELDAPAUTH=yes, then LDAP is being used. Check for the directory containing X.509 certificates for peer authentication with the following command: # grep -i cacertdir /etc/pam_ldap.conf tls_cacertdir /etc/openldap/certs Verify the directory set with the “tls_cacertdir” option exists. If the directory does not exist or the option is commented out, this is a finding. Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions. Set the tls_cacertdir option in /etc/pam_ldap.conf to point to the directory that will contain the X.509 certificates for peer authentication. Set the tls_cacertfile option in /etc/pam_ldap.conf to point to the path for the X.509 certificates used for peer authentication.
RHEL-07-040182 CCI-001453 medium The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. 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 secret key used to generate the hash. Verify the operating system implements cryptography to protect the integrity of remote ldap access sessions. To determine if LDAP is being used for authentication, use the following command: # grep -i useldapauth /etc/sysconfig/authconfig USELDAPAUTH=yes If USELDAPAUTH=yes, then LDAP is being used. Check that the path to the X.509 certificate for peer authentication with the following command: # grep -i cacertfile /etc/pam_ldap.conf tls_cacertfile /etc/openldap/ldap-cacert.pem Verify the “tls_cacertfile” option points to a file that contains the trusted CA certificate. If this file does not exist, or the option is commented out or missing, this is a finding. Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions. Set the tls_cacertfile option in /etc/pam_ldap.conf to point to the path for the X.509 certificates used for peer authentication.
RHEL-07-040190 CCI-001133 medium All network connections associated with SSH traffic must terminate at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements. 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 left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109 Verify the operating system automatically terminates a user session after inactivity time-outs have expired. Check for the value of the ClientAlive keyword with the following command: # grep -i clientalive /etc/ssh/sshd_config ClientAliveInterval 600 If “ClientAliveInterval” is not set to “600” in /etc/ ssh/sshd_config, and a lower value is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown. Add the following line (or modify the line to have the required value) to the /etc/ssh/sshd_config file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): ClientAliveInterval 600
RHEL-07-040191 CCI-001133 medium All network connections associated with SSH traffic must terminate after a period of inactivity. 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 left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109 Verify the operating system automatically terminates a user session after inactivity time-outs have expired. Check for the value of the ClientAliveCountMax keyword with the following command: # grep -i clientalivecount /etc/ssh/sshd_config ClientAliveCountMax 0 If “ClientAliveCountMax” is not set to “0” in /etc/ ssh/sshd_config, this is a finding. Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown. Add the following line (or modify the line to have the required value) to the /etc/ssh/sshd_config file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): ClientAliveCountMax 0
RHEL-07-040210 CCI-001891 medium The operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000355-GPOS-00144 Check to see if ntp is running in continuous mode. # ps -ef | grep ntp If NTP is not running, this is a finding. If the process is found, then check the ntp.conf file for the “maxpoll” option setting: # grep maxpoll /etc/ntp.conf maxpoll 10 If the file does not exist, this is a finding. If the option is set to “17” or is not set, this is a finding. Edit the "/etc/ntp.conf" file and add or update an entry to define "maxpoll" to "10" as follows: maxpoll 10 If NTP was running and "maxpoll" was updated, the ntp service must be restarted: # systemctl restart ntpd If NTP was not running, it must be started: # systemctl start ntpd
RHEL-07-040230 CCI-001991 medium The operating system, if using PKI-based authentication, must implement a local cache of revocation data to certificate validation in case of the inability to access revocation information via the network. Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). Verify the operating system, for PKI-based authentication, implements a local cache of revocation data to support certificate validation in case of the inability to access revocation information via the network. Check to see if the certificate authority certificate revocation data cache is enabled on the system with the following command: # grep -i revocationchecking /var/lib/pki-ca/conf/CS.cfg auths.revocationChecking.bufferSize=50 auths.revocationChecking.ca=ca auths.revocationChecking.enabled=true auths.revocationChecking.unknownStateInterval=0 auths.revocationChecking.validityInterval=120 If auths.revocationChecking.enabled is not set to "true", this is a finding. If auths.revocationChecking.bufferSize is not set to a value of “50” or less, this is a finding. Check to see if the Online Certificate Status Protocol (OCSP) certificate revocation data cache is enabled on the system with the following command: # grep -i ocsp /var/lib/pki-kra/conf/server.xml enableOCSP="true" ocspResponderURL="http://server.pki.mil:9180/ca/ocsp" ocspResponderCertNickname="ocspSigningCert cert-pki-ca 102409a" ocspCacheSize="50" ocspMinCacheEntryDuration="60" ocspMaxCacheEntryDuration="120" ocspTimeout="10" If “enableOCSP” is not set to "true", this is a finding. If “ocspCacheSize” is not set to a value of “50” or less, this is a finding. Configure the operating system, for PKI-based authentication, to implement a local cache of revocation data to support certificate validation in case of the inability to access revocation information via the network. Add the following lines to /var/lib/pki-kra/conf/server.xml (or modify the line to have the required value): auths.revocationChecking.bufferSize=50 auths.revocationChecking.enabled=true Add the following lines to /var/lib/pki-kra/conf/server.xml (or modify the line to have the required value): enableOCSP="true" ocspCacheSize="50"
RHEL-07-040250 CCI-002385 medium The operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of the operating system 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. Verify the operating system protects against or limits the effects of DoS attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces. Check the firewall configuration with the following command: # firewall-cmd --direct --get-rule ipv4 filter IN_public_allow rule ipv4 filter IN_public_allow 0 -m tcp -p tcp -m limit --limit 25/minute --limit-burst 100 -j ACCEPT If a rule with both the limit and limit-burst arguments parameters does not exist, this is a finding. Create a direct firewall rule to protect against DoS attacks with the following command: # firewall-cmd --direct --add-rule ipv4 filter IN_public_allow 0 -m tcp -p tcp -m limit --limit 25/minute --limit-burst 100 -j ACCEPT
RHEL-07-040260 CCI-002418 medium All networked systems must have SSH installed. Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, logical means (cryptography) do not have to be employed, and vice versa. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000423-GPOS-00188, SRG-OS-000423-GPOS-00189, SRG-OS-000423-GPOS-00190 Check to see if sshd is installed with the following command: # yum list installed | grep ssh libssh2.x86_64 1.4.3-8.el7 @anaconda/7.1 openssh.x86_64 6.6.1p1-11.el7 @anaconda/7.1 openssh-clients.x86_64 6.6.1p1-11.el7 @anaconda/7.1 openssh-server.x86_64 6.6.1p1-11.el7 @anaconda/7.1 If the “SSH server” package is not installed, this is a finding. If the “SSH client” package is not installed, this is a finding. Install SSH packages onto the host with the following commands: # yum install openssh-clients.x86_64 # yum install openssh-server.x86_64 Note: 32-bit versions will require different packages.
RHEL-07-040261 CCI-002418 medium All networked systems must use SSH for confidentiality and integrity of transmitted and received information as well as information during preparation for transmission. Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000423-GPOS-00188, SRG-OS-000423-GPOS-00189, SRG-OS-000423-GPOS-00190 Verify SSH is loaded and active with the following command: # systemctl status sshd sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled) Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days ago Main PID: 1348 (sshd) CGroup: /system.slice/sshd.service ??1348 /usr/sbin/sshd -D If “sshd” does not show a status of “active” and “running”, this is a finding. Configure the SSH service to automatically start after reboot with the following command: # systemctl enable sshd ln -s '/usr/lib/systemd/system/sshd.service' '/etc/systemd/system/multi-user.target.wants/sshd.service'
RHEL-07-040290 CCI-000366 medium The operating system must enable an application firewall, if available. Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network. Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00231, SRG-OS-000480-GPOS-00232 Verify the operating system enabled an application firewall. Check to see if "firewalld" is installed with the following command: # yum list installed | grep firewalld firewalld-0.3.9-11.el7.noarch.rpm If the “firewalld” package is not installed, ask the system administrator if another firewall application (such as iptables) is installed. If an application firewall is not installed, this is a finding. Check to see if the firewall is loaded and active with the following command: # systemctl status firewalld - must show that the firewall if loaded and active firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago If “firewalld” does not show a status of “loaded and active”, this is a finding. Check the state of the firewall: # firewall-cmd --state running If “firewalld” does not show a state of “running”, this is a finding. Ensure the operating system's application firewall is enabled. Install the “firewalld” package if it is not on the system with the following command: # yum install firewalld Start the firewall via systemctl with the following command: # systemctl start firewalld
RHEL-07-040300 CCI-000366 low The system must display the date and time of the last successful account logon upon logon. Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use. Verify that users are provided with feedback on when account accesses last occurred. Check that “pam_lastlog” is used and not silent with the following command: # grep pam_lastlog /etc/pam.d/postlogin session required pam_lastlog.so showfailed silent If “pam_lastlog” is missing from “/etc/pam.d/postlogin” file, or the silent option is present on the line check for the “PrintLastLog” keyword in the sshd daemon configuration file, this is a finding. Configure the operating system to provide users with feedback on when account accesses last occurred by setting the required configuration options in “/etc/pam.d/postlogin”. Add the following line to the top of “/etc/pam.d/postlogin”: session required pam_lastlog.so showfailed
RHEL-07-040301 CCI-000366 medium The system must display the date and time of the last successful account logon upon an SSH logon. Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use. Verify SSH provides users with feedback on when account accesses last occurred. Check that “PrintLastLog” keyword in the sshd daemon configuration file is used and set to “yes” with the following command: # grep -i printlastlog /etc/ssh/sshd_config PrintLastLog yes If the “PrintLastLog” keyword is set to “no”, is missing, or is commented out, this is a finding. Configure SSH to provide users with feedback on when account accesses last occurred by setting the required configuration options in “/etc/pam.d/sshd” or in the “sshd_config” file used by the system (/etc/ssh/sshd_config will be used in the example) (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). Add the following line to the top of “/etc/pam.d/sshd”: session required pam_lastlog.so showfailed Or modify the PrintLastLog line in “/etc/ssh/sshd_config” to match the following: PrintLastLog yes
RHEL-07-040310 CCI-000366 medium The system must not permit direct logons to the root account using remote access via SSH. Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system. Verify remote access using SSH prevents users from logging on directly as root. Check that SSH prevents users from logging on directly as root with the following command: # grep -i permitrootlogin /etc/ssh/sshd_config PermitRootLogin no If the “PermitRootLogin” keyword is set to “yes”, is missing, or is commented out, this is a finding. Configure SSH to stop users from logging on remotely as the root user. Edit the appropriate /etc/ssh/sshd_config file to uncomment or add the line for the PermitRootLogin keyword and set its value to “no” (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): PermitRootLogin no
RHEL-07-040320 CCI-000366 low For systems using DNS resolution, at least two name servers must be configured. To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging. Determine whether the system is using local or DNS name resolution with the following command: # grep hosts /etc/nsswitch.conf hosts: files dns If the dns entry is missing from the host’s line in the “/etc/nsswitch.conf” file, the “/etc/resolv.conf” file must be empty. Verify the “/etc/resolv.conf” file is empty with the following command: # l s -al /etc/resolv.conf -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf If local host authentication is being used and the “/etc/resolv.conf” file is not empty, this is a finding. If the dns entry is found on the host’s line of the “/etc/nsswitch.conf” file, verify the operating system is configured to use two or more name servers for DNS resolution. Determine the name servers used by the system with the following command: # grep nameserver /etc/resolv.conf nameserver 192.168.1.2 nameserver 192.168.1.3 If less than two lines are returned that are not commented out, this is a finding. Configure the operating system to use two or more name servers for DNS resolution. Edit the “/etc/resolv.conf” file to uncomment or add the two or more nameserver option lines with the IP address of local authoritative name servers. If local host resolution is being performed, the “/etc/resolv.conf” file must be empty. An empty “/etc/resolv.conf” file can be created as follows: # echo -n > /etc/resolv.conf And then make the file immutable with the following command: # chattr +i /etc/resolv.conf
RHEL-07-040330 CCI-000366 high There must be no .shosts files on the system. 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. Verify there are no .shosts files on the system. Check the system for the existence of these files with the following command: # find / -name '*.shosts’ If any .shosts files are found on the system, this is a finding. Remove any found .shosts files from the system. # rm /[path]/[to]/[file]/.shosts
RHEL-07-040331 CCI-000366 high There must be no shosts.equiv files on the system. 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. Verify there are no shosts.equiv files on the system. Check the system for the existence of these files with the following command: # find / -name shosts.equiv If any shosts.equiv files are found on the system, this is a finding. Remove any found shosts.equiv files from the system. # rm /[path]/[to]/[file]/shosts.equiv
RHEL-07-040334 CCI-000366 medium The SSH daemon must not allow authentication using rhosts authentication. Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere. Verify the SSH daemon does not allow authentication using known hosts authentication. To determine how the SSH daemon's "IgnoreRhosts" option is set, run the following command: # grep -i IgnoreRhosts /etc/ssh/sshd_config IgnoreRhosts yes If the value is returned as “no”, the returned line is commented out, or no output is returned, this is a finding. Configure the SSH daemon to not allow authentication using known hosts authentication. Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to “yes”: IgnoreRhosts yes
RHEL-07-040332 CCI-000366 medium The SSH daemon must not allow authentication using known hosts authentication. Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere. Verify the SSH daemon does not allow authentication using known hosts authentication. To determine how the SSH daemon's "IgnoreUserKnownHosts" option is set, run the following command: # grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config IgnoreUserKnownHosts yes If the value is returned as “no”, the returned line is commented out, or no output is returned, this is a finding. Configure the SSH daemon to not allow authentication using known hosts authentication. Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to yes: IgnoreUserKnownHosts yes
RHEL-07-040333 CCI-000366 medium The SSH daemon must not allow authentication using RSA rhosts authentication. Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere. Verify the SSH daemon does not allow authentication using RSA rhosts authentication. To determine how the SSH daemon's "RhostsRSAAuthentication" option is set, run the following command: # grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config RhostsRSAAuthentication yes If the value is returned as “no”, the returned line is commented out, or no output is returned, this is a finding. Configure the SSH daemon to not allow authentication using RSA rhosts authentication. Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to yes: RhostsRSAAuthentication yes
RHEL-07-040350 CCI-000366 medium The system must not forward Internet Protocol version 4 (IPv4) source-routed packets. Source-routed packets allow the source of the packet to suggest that 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-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router. Verify the system does not accept IPv4 source-routed packets. Check the value of the accept source route variable with the following command: # /sbin/sysctl -a | grep net.ipv4.conf.all.accept_source_route net.ipv4.conf.all.accept_source_route=0 If the returned line does not have a value of “0”, a line is not returned, or the returned line is commented out, this is a finding. Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value): net.ipv4.conf.all.accept_source_route = 0
RHEL-07-040351 CCI-000366 medium The system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default. Source-routed packets allow the source of the packet to suggest that 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-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router. Verify the system does not accept IPv4 source-routed packets by default. Check the value of the accept source route variable with the following command: # /sbin/sysctl -a | grep net.ipv4.conf.default.accept_source_route net.ipv4.conf.default.accept_source_route=0 If the returned line does not have a value of “0”, a line is not returned, or the returned line is commented out, this is a finding. Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value): net.ipv4.conf.default.accept_source_route = 0
RHEL-07-040380 CCI-000366 medium The system must not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address. Responding to broadcast (ICMP) echoes facilitates network mapping and provides a vector for amplification attacks. Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast address. Check the value of the icmp_echo_ignore_broadcasts variable with the following command: # /sbin/sysctl -a | grep net.ipv4.icmp_echo_ignore_broadcasts net.ipv4.icmp_echo_ignore_broadcasts=1 If the returned line does not have a value of “1”, a line is not returned, or the retuned line is commented out, this is a finding. Set the system to the required kernel parameter with the following command: # /sbin/sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1
RHEL-07-040410 CCI-000366 medium The system must ignore to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages. 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. Verify the system ignores IPv4 ICMP redirect messages. Check the value of the “accept_redirects” variables with the following command: # /sbin/sysctl -a | grep 'net.ipv4.conf.*.accept_redirects' net.ipv4.conf.default.accept_redirects=0 net.ipv4.conf.all.accept_redirects=0 If both of the returned line do not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding. Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value): net.ipv4.conf.all.accept_redirects = 0 net.ipv4.conf.default.accept_redirects = 0
RHEL-07-040420 CCI-000366 medium The system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default. ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology. Verify the system does not allow interfaces to perform IPv4 ICMP redirects by default. Check the value of the "default send_redirects" variables with the following command: # /sbin/sysctl -a | grep 'net.ipv4.conf.default.send_redirects' net.ipv4.conf.default.send_redirects=0 If the returned line does not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding. Configure the system to not allow interfaces to perform IPv4 ICMP redirects by default. Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value): net.ipv4.conf.default.send_redirects=0
RHEL-07-040421 CCI-000366 medium The system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects. 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. Verify the system does not send IPv4 ICMP redirect messages. Check the value of the "all send_redirects" variables with the following command: # /sbin/sysctl -a | grep net.ipv4.conf.all.send_redirects net.ipv4.conf.all.send_redirects=0 If the returned line does not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding. Configure the system to not allow interfaces to perform IPv4 ICMP redirects. Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value): net.ipv4.conf.all.send_redirects=0
RHEL-07-040470 CCI-000366 medium Network interfaces must not be in promiscuous mode. 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 then 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 System Security Manager (ISSM) and restricted to only authorized personnel. Verify network interfaces are not in promiscuous mode unless approved by the Information System Security Manager (ISSM) and documented. Check for the status with the following command: # ip link | grep -i promisc If network interfaces are found on the system in promiscuous mode and their use has not been approved by the ISSM and documented, this is a finding. Configure network interfaces to turn off promiscuous mode unless approved by the ISSM and documented. Set the promiscuous mode of an interface to off with the following command: #ip link set dev <devicename> multicast off promisc off
RHEL-07-040480 CCI-000366 medium The system must be configured to prevent unrestricted mail relaying. If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity. Verify the system is configured to prevent unrestricted mail relaying. Determine if "postfix" or "sendmail" are installed with the following commands: # yum list installed | grep postfix postfix-2.6.6-6.el7.x86_64.rpm # yum list installed | grep sendmail If neither are installed, this is Not Applicable. If postfix is installed, determine if it is configured to reject connections from unknown or untrusted networks with the following command: # grep smtpd_client_restrictions /etc/postfix/main.cf smtpd_client_restrictions = permit_mynetworks, reject If the “smtpd_client_restrictions” parameter contains any entries other than "permit_mynetworks" and "reject", this is a finding. If “postfix” is installed, modify the “/etc/postfix/main.cf” file to restrict client connections to the local network with the following configuration line: smtpd_client_restrictions = permit_mynetworks, reject
RHEL-07-040490 CCI-000366 high A File Transfer Protocol (FTP) server package must not be installed unless needed. The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service. Verify a lightweight FTP server has not been installed on the system. Check to see if a lightweight FTP server has been installed with the following commands: # yum list installed | grep lftpd lftp-4.4.8-7.el7.x86_64.rpm An alternate method of determining if a lightweight FTP server is active on the server is to use the following command: # netstat -a | grep 21 If “lftpd” is installed, or if an application is listening on port 21, and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Document the "lftpd" package with the ISSO as an operational requirement or remove it from the system with the following command: # yum remove lftpd
RHEL-07-040500 CCI-000368 high The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for operational support. If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Manager (ISSM), restricted to only authorized personnel, and have access control rules established. Verify a TFTP server has not been installed on the system. Check to see if a TFTP server has been installed with the following command: # yum list installed | grep tftp-server tftp-server-0.49-9.el7.x86_64.rpm An alternate method of determining if a TFTP server is active on the server is to use the following commands: # netstat -a | grep 69 # netstat -a | grep 8099 If TFTP is installed and the requirement for TFTP is not documented with the ISSM, this is a finding. Remove the TFTP package from the system with the following command: # yum remove tftp
RHEL-07-040520 CCI-000366 medium If the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon must be configured to operate in secure mode. Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files. Verify the TFTP daemon is configured to operate in secure mode. Check to see if a TFTP server has been installed with the following commands: # yum list installed | grep tftp tftp-0.49-9.el7.x86_64.rpm If a TFTP server is not installed, this is Not Applicable. If a TFTP server is installed, check for the server arguments with the following command: # grep server_arge /etc/xinetd.d/tftp server_args = -s /var/lib/tftpboot If the “server_args” line does not have a -s option and the directory /var/lib/tftpboot, this is a finding. Configure the TFTP daemon to operate in secure mode by adding the following line to /etc/xinetd.d/tftp (or modify the line to have the required value): server_args = -s /var/lib/tftpboot
RHEL-07-040540 CCI-000366 high Remote X connections for interactive users must be encrypted. Open X displays allow an attacker to capture keystrokes and execute commands remotely. Verify remote X connections for interactive users are encrypted. Check that remote X connections are encrypted with the following command: # grep -i x11forwarding /etc/ssh/sshd_config X11Fowarding yes If the X11Forwarding keyword is set to "no", is missing, or is commented out, this is a finding. Configure SSH to encrypt connections for interactive users. Edit the /etc/ssh/sshd_config file to uncomment or add the line for the X11Forwarding keyword and set its value to “yes” (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): X11Fowarding yes
RHEL-07-040560 CCI-000366 medium An X Windows display manager must not be installed unless approved. Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. X Windows has a long history of security vulnerabilities and will not be used unless approved and documented. Verify that if the system has X Windows installed, it is authorized. Check for the X11 package with the following command: #yum groupinstall "X Window System" Ask the System Administrator (SA) if use of the X Windows system is an operational requirement. If the use of X Windows on the system is not documented with the Information System Security Manager (ISSM), this is a finding. Document the requirement for an X Windows server with the ISSM or remove the related packages with the following commands: #yum groupremove "X Window System" #yum remove xorg-x11-server-common
RHEL-07-040580 CCI-000366 high SNMP community strings must be changed from the default. 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, anyone can gather data about the system and the network and use the information to potentially compromise the integrity of the system or network(s). It is highly recommended that SNMP version 3 user authentication and message encryption be used in place of the version 2 community strings. Verify that a system using SNMP is not using default community strings. Check to see if the “/etc/snmp/snmpd.conf” file exists with the following command: # ls -al /etc/snmp/snmpd.conf -rw------- 1 root root 52640 Mar 12 11:08 snmpd.conf If the file does not exist, this is Not Applicable. If the file does exist, check for the default community strings with the following commands: # grep public /etc/snmp/snmpd.conf # grep private /etc/snmp/snmpd.conf If either of these command returns any output, this is a finding. If the “/etc/snmp/snmpd.conf” file exists, modify any lines that contain a community string of public or private to another string.
RHEL-07-040590 CCI-000197 high The SSH daemon must be configured to only use the SSHv2 protocol. SSHv1 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. Satisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000480-GPOS-00227 Verify the SSH daemon is configured to only use the SSHv2 protocol. Check that the SSH daemon is configured to only use the SSHv2 protocol with the following command: # grep -i protocol /etc/ssh/sshd_config Protocol 2 #Protocol 1,2 If any protocol line other than "Protocol 2" is uncommented, this is a finding. Remove all Protocol lines that reference version 1 in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). The "Protocol" line must be as follows: Protocol 2
RHEL-07-040620 CCI-001453 medium The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. The only SSHv2 hash algorithm meeting this requirement is SHA. Verify the SSH daemon is configured to only use MACs employing FIPS 140-2 approved ciphers. Note: If RHEL-07-021280 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes. Check that the SSH daemon is configured to only use MACs employing FIPS 140-2 approved ciphers with the following command: # grep -i macs /etc/ssh/sshd_config MACs hmac-sha2-256,hmac-sha2-512 If any ciphers other than “hmac-sha2-256” or “hmac-sha2-512” are listed or the retuned line is commented out, this is a finding. Edit the /etc/ssh/sshd_config file to uncomment or add the line for the MACs keyword and set its value to “hmac-sha2-256” and/or “hmac-sha2-512 “(this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): MACs hmac-sha2-256,hmac-sha2-512
RHEL-07-040640 CCI-000366 medium The SSH public host key files must have mode 0644 or less permissive. If a public host key file is modified by an unauthorized user, the SSH service may be compromised. Verify the SSH public host key files have mode “0644” or less permissive. Note: SSH public key files may be found in other directories on the system depending on the installation. The following command will find all SSH public key files on the system: # find / -name '*.pub' Check the mode of the public host key files under /etc/ssh file with the following command: # ls -lL /etc/ssh/*.pub -rw-r--r-- 1 root wheel 618 Nov 28 06:43 ssh_host_dsa_key.pub -rw-r--r-- 1 root wheel 347 Nov 28 06:43 ssh_host_key.pub -rw-r--r-- 1 root wheel 238 Nov 28 06:43 ssh_host_rsa_key.pub If any file has a mode more permissive than “0644”, this is a finding. Note: SSH public key files may be found in other directories on the system depending on the installation. The following command will find all SSH public key files on the system: # find / -name ‘*key.pub’ Change the mode of public host key files under “/etc/ssh” to “0644” with the following command: # chmod 0644 /etc/ssh/*.key.pub
RHEL-07-040650 CCI-000366 medium The SSH private host key files must have mode 0600 or less permissive. If an unauthorized user obtains the private SSH host key file, the host could be impersonated. Verify the SSH private host key files have mode “0600” or less permissive. The following command will find all SSH private key files on the system: # find / -name '*ssh_host*key' Check the mode of the private host key files under /etc/ssh file with the following command: # ls -lL /etc/ssh/*key -rw------- 1 root wheel 668 Nov 28 06:43 ssh_host_dsa_key -rw------- 1 root wheel 582 Nov 28 06:43 ssh_host_key -rw------- 1 root wheel 887 Nov 28 06:43 ssh_host_rsa_key If any file has a mode more permissive than “0600”, this is a finding. Configure the mode of SSH private host key files under “/etc/ssh” to “0600” with the following command: # chmod 0600 /etc/ssh/ssh_host*key
RHEL-07-040660 CCI-000368 medium The SSH daemon must not permit Generic Security Service Application Program Interface (GSSAPI) authentication unless needed. 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. GSSAPI authentication must be disabled unless needed. Verify the SSH daemon does not permit GSSAPI authentication unless approved. Check that the SSH daemon does not permit GSSAPI authentication with the following command: # grep -i gssapiauth /etc/ssh/sshd_config GSSAPIAuthentication no If the “GSSAPIAuthentication” keyword is missing, is set to “yes” and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding. Uncomment the “GSSAPIAuthentication” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "no": GSSAPIAuthentication no If GSSAPI authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.
RHEL-07-040670 CCI-000368 medium The SSH daemon must not permit Kerberos authentication unless needed. Kerberos authentication for SSH is often implemented using Generic Security Service Application Program Interface (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 implementation may then be subject to exploitation. To reduce the attack surface of the system, the Kerberos authentication mechanism within SSH must be disabled for systems not using this capability. Verify the SSH daemon does not permit Kerberos to authenticate passwords unless approved. Check that the SSH daemon does not permit Kerberos to authenticate passwords with the following command: # grep -i kerberosauth /etc/ssh/sshd_config KerberosAuthentication no If the “KerberosAuthentication” keyword is missing, or is set to "yes" and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding. Uncomment the “KerberosAuthentication” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "no": KerberosAuthentication no If Kerberos authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.
RHEL-07-040680 CCI-000366 medium The SSH daemon must perform strict mode checking of home directory configuration files. If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user. Verify the SSH daemon performs strict mode checking of home directory configuration files. The location of the sshd_config file may vary on the system and can be found using the following command: # find / -name 'sshd*_config' If there is more than one ssh server daemon configuration file on the system, determine which daemons are active on the system with the following command: # ps -ef | grep sshd The command will return the full path of the ssh daemon. This will indicate which sshd_config file will be checked with the following command: # grep -i strictmodes /etc/ssh/sshd_config StrictModes yes If “StrictModes” is set to "no", is missing, or the retuned line is commented out, this is a finding. Uncomment the “StrictModes” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "yes": StrictModes yes
RHEL-07-040690 CCI-000366 medium The SSH daemon must use privilege separation. 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. Verify the SSH daemon performs privilege separation. Check that the SSH daemon performs privilege separation with the following command: # grep -i usepriv /etc/ssh/sshd_config UsePrivilegeSeparation yes If the “UsePrivilegeSeparation” keyword is set to "no", is missing, or the retuned line is commented out, this is a finding. Uncomment the “UsePrivilegeSeparation” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "yes": UsePrivilegeSeparation yes
RHEL-07-040700 CCI-000366 medium The SSH daemon must not allow compression or must only allow compression after successful authentication. 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. Verify the SSH daemon performs compression after a user successfully authenticates. Check that the SSH daemon performs compression after a user successfully authenticates with the following command: # grep -i compression /etc/ssh/sshd_config Compression delayed If the “Compression” keyword is set to “yes”, is missing, or the retuned line is commented out, this is a finding. Uncomment the “Compression” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) on the system and set the value to "delayed" or "no": Compression no
RHEL-07-040730 CCI-000366 medium The system must not be performing packet forwarding unless the system is a router. Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network. Verify the system is not performing packet forwarding, unless the system is a router. Check to see if IP forwarding is enabled using the following command: # /sbin/sysctl -a | grep net.ipv4.ip_forward net.ipv4.ip_forward=0 If IP forwarding value is “1” and the system is hosting any application, database, or web servers, this is a finding. Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value): net.ipv4.ip_forward = 0
RHEL-07-040740 CCI-000366 medium The Network File System (NFS) must be configured to use AUTH_GSS. 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. Verify “AUTH_GSS’ is being used to authenticate NFS mounts. To check if the system is importing an NFS file system, look for any entries in the “/etc/fstab” file that have a file system type of “nfs” with the following command: # cat /etc/fstab | grep nfs 192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=sys, krb5:krb5i:krb5p If the system is mounting file systems via NFS and has the sec option without the “krb5:krb5i:krb5p” settings, the sec option has the “sys” setting, or the “sec” option is missing, this is a finding. Update the “/etc/fstab” file so the option “sec” is defined for each file system and the “sec” option does not have the “sys” setting. Ensure the “sec” option is defined as “krb5:krb5i:krb5p”.
RHEL-07-040810 CCI-000366 medium The system must use a local firewall. A firewall provides the ability to enhance system security posture by restricting services to known good IP addresses and address ranges. This prevents connections from unknown hosts and protocols. Verify that a firewall is in use on the system. Check to see if “firewalld” is installed with the following command: # yum list installed | grep firewalld If “firewalld” is not installed, ask the System Administrator if they are performing another method of access control (such as iptables) for all network services on the system. If there is no access control being performed on all network services, this is a finding. If “firewalld” is installed, determine whether it is active with the following command: # systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago If “firewalld” is not active, this is a finding. Install “firewalld” on the system if it is not already installed with the following command: # yum install firewalld firewall-config Enable firewalld with the following command: #systemctl enable firewalld
RHEL-07-040820 CCI-000366 medium The system's access control program must be configured to grant or deny system access to specific hosts and services. If the systems access control program is not configured with appropriate rules for allowing and denying access to system network resources, services may be accessible to unauthorized hosts. If the “firewalld” package is not installed, ask the System Administrator if another firewall application (such as iptables) is installed. If an application firewall is not installed, this is a finding. Verify the system's access control program is configured to grant or deny system access to specific hosts. Check to see if “firewalld” is active with the following command: # systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago If “firewalld” is active, check to see if it is configured to grant or deny access to specific hosts or services with the following commands: # firewall-cmd --get-default-zone public # firewall-cmd --list-all --zone=public public (default, active) interfaces: eth0 sources: services: mdns ssh ports: masquerade: no forward-ports: icmp-blocks: rich rules: rule family="ipv4" source address="92.188.21.1/24" accept rule family="ipv4" source address="211.17.142.46/32" accept If “firewalld” is not active, determine whether “tcpwrappers” is being used by checking whether the “hosts.allow” and “hosts.deny” files are empty with the following commands: # ls -al /etc/hosts.allow rw-r----- 1 root root 9 Aug 2 23:13 /etc/hosts.allow # ls -al /etc/hosts.deny -rw-r----- 1 root root 9 Apr 9 2007 /etc/hosts.deny If “firewalld” and “tcpwrappers” are not installed, configured, and active, ask the System Administrator (SA) if another access control program (such as iptables) is installed and active. Ask the SA to show that the running configuration grants or denies access to specific hosts or services. If “firewalld” is active and is not configured to grant access to specific hosts and “tcpwrappers” is not configured to grant or deny access to specific hosts, this is a finding. If “firewalld” is installed and active on the system, configure rules for allowing specific services and hosts. If “tcpwrappers” is installed. configure the “/etc/hosts.allow” and “/etc/hosts.deny” to allow or deny access to specific hosts.
RHEL-07-040830 CCI-000366 medium The system must not have unauthorized IP tunnels configured. IP tunneling mechanisms can be used to bypass network filtering. If tunneling is required, it must be documented with the Information System Security Officer (ISSO). Verify the system does not have unauthorized IP tunnels configured. Check to see if “libreswan” is installed with the following command: # yum list installed libreswan openswan-2.6.32-27.el6.x86_64 If “libreswan” is installed, check to see if the “IPsec” service is active with the following command: # systemctl status ipsec ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled) Active: inactive (dead) If the “IPsec” service is active, check to see if any tunnels are configured in “/etc/ipsec.conf” and “/etc/ipsec.d/” with the following commands: # grep -i conn /etc/ipsec.conf conn mytunnel # grep -i conn /etc/ipsec.d/*.conf conn mytunnel If there are indications that a “conn” parameter is configured for a tunnel, ask the System Administrator (SA) if the tunnel is documented with the ISSO. If “libreswan” is installed, “IPsec” is active, and an undocumented tunnel is active, this is a finding. Remove all unapproved tunnels from the system, or document them with the ISSO.
RHEL-07-040860 CCI-000366 medium The system must not forward IPv6 source-routed packets. Source-routed packets allow the source of the packet to suggest that 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-routed traffic, such as when IPv6 forwarding is enabled and the system is functioning as a router. Verify the system does not accept IPv6 source-routed packets. Note: If IPv6 is not enabled, the key will not exist, and this is not a finding. Check the value of the accept source route variable with the following command: # /sbin/sysctl -a | grep net.ipv6.conf.all.accept_source_route net.ipv6.conf.all.accept_source_route=0 If the returned lines do not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding. Set the system to the required kernel parameter, if IPv6 is enabled, by adding the following line to /etc/sysctl.conf (or modify the line to have the required value): net.ipv6.conf.all.accept_source_route = 0