{"platform":{"name":"centos","release":"7.9.2009"},"profiles":[{"attributes":[],"controls":[{"code":"control \"V-71849\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the file permissions, ownership, and group membership of system files and\ncommands match the vendor values.\"\n desc \"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file permissions, ownership, and group membership of system\nfiles and commands match the vendor values.\n\n Check the default file permissions, ownership, and group membership of\nsystem files and commands with the following command:\n\n # for i in `rpm -Va | egrep -i '^\\\\.[M|U|G|.]{8}' | cut -d \\\" \\\" -f4,5`;do\nfor j in `rpm -qf $i`;do rpm -ql $j --dump | cut -d \\\" \\\" -f1,5,6,7 | grep\n$i;done;done\n\n /var/log/gdm 040755 root root\n /etc/audisp/audisp-remote.conf 0100640 root root\n /usr/bin/passwd 0104755 root root\n\n For each file returned, verify the current permissions, ownership, and\ngroup membership:\n # ls -la \n\n -rw-------. 1 root root 133 Jan 11 13:25 /etc/audisp/audisp-remote.conf\n\n If the file is more permissive than the default permissions, this is a\nfinding.\n\n If the file is not owned by the default owner and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.\n\n If the file is not a member of the default group and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.\n \"\n desc \"fix\", \"\n Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n Reset the user and group ownership of files within a package with the\nfollowing command:\n\n #rpm --setugids \n\n\n Reset the permissions of files within a package with the following command:\n\n #rpm --setperms \n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000257-GPOS-00098\"\n tag satisfies: [\"SRG-OS-000257-GPOS-00098\", \"SRG-OS-000278-GPOS-00108\"]\n tag gid: \"V-71849\"\n tag rid: \"SV-86473r4_rule\"\n tag stig_id: \"RHEL-07-010010\"\n tag fix_id: \"F-78201r4_fix\"\n tag cci: [\"CCI-001494\", \"CCI-001496\", \"CCI-002165\", \"CCI-002235\"]\n tag nist: [\"AU-9\", \"AU-9 (3)\", \"AC-3 (4)\", \"AC-6 (10)\"]\n\n rpm_verify_perms_except = input('rpm_verify_perms_except')\n\n if input('disable_slow_controls')\n describe \"This control consistently takes a long time to run and has been disabled\n using the disable_slow_controls attribute.\" do\n skip \"This control consistently takes a long time to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.\"\n end\n else\n describe command(\"rpm -Va | grep '^.M' | awk 'NF>1{print $NF}'\").stdout.strip.split(\"\\n\") do\n it { should all(be_in rpm_verify_perms_except) }\n end\n end\nend\n","desc":"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.","descriptions":[{"data":"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file permissions, ownership, and group membership of system\nfiles and commands match the vendor values.\n\n Check the default file permissions, ownership, and group membership of\nsystem files and commands with the following command:\n\n # for i in `rpm -Va | egrep -i '^\\.[M|U|G|.]{8}' | cut -d \" \" -f4,5`;do\nfor j in `rpm -qf $i`;do rpm -ql $j --dump | cut -d \" \" -f1,5,6,7 | grep\n$i;done;done\n\n /var/log/gdm 040755 root root\n /etc/audisp/audisp-remote.conf 0100640 root root\n /usr/bin/passwd 0104755 root root\n\n For each file returned, verify the current permissions, ownership, and\ngroup membership:\n # ls -la \n\n -rw-------. 1 root root 133 Jan 11 13:25 /etc/audisp/audisp-remote.conf\n\n If the file is more permissive than the default permissions, this is a\nfinding.\n\n If the file is not owned by the default owner and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.\n\n If the file is not a member of the default group and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.","label":"check"},{"data":"Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n Reset the user and group ownership of files within a package with the\nfollowing command:\n\n #rpm --setugids \n\n\n Reset the permissions of files within a package with the following command:\n\n #rpm --setperms ","label":"fix"}],"id":"V-71849","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71849.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000257-GPOS-00098","satisfies":["SRG-OS-000257-GPOS-00098","SRG-OS-000278-GPOS-00108"],"gid":"V-71849","rid":"SV-86473r4_rule","stig_id":"RHEL-07-010010","fix_id":"F-78201r4_fix","cci":["CCI-001494","CCI-001496","CCI-002165","CCI-002235"],"nist":["AU-9","AU-9 (3)","AC-3 (4)","AC-6 (10)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file permissions, ownership, and group membership of system files and\ncommands match the vendor values.","waiver_data":{}},{"code":"control \"V-71855\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the cryptographic hash of system files and commands matches vendor values.\"\n desc \"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the cryptographic hash of system files and commands match the vendor\nvalues.\n\n Check the cryptographic hash of system files and commands with the\nfollowing command:\n\n Note: System configuration files (indicated by a \\\"c\\\" in the second\ncolumn) are expected to change over time. Unusual modifications should be\ninvestigated through the system audit log.\n\n # rpm -Va --noconfig | grep '^..5'\n\n If there is any output from the command for system files or binaries, this\nis a finding.\n \"\n desc \"fix\", \"\n Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh \n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71855\"\n tag rid: \"SV-86479r4_rule\"\n tag stig_id: \"RHEL-07-010020\"\n tag fix_id: \"F-78207r1_fix\"\n tag cci: [\"CCI-001749\"]\n tag nist: [\"CM-5 (3)\"]\n\nrpm_verify_integrity_except = input('rpm_verify_integrity_except')\n\nif input('disable_slow_controls')\n describe \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.\" do\n skip \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.\"\n end\n else\n # grep excludes files that are marked with 'c' attribute (config files)\n describe command(\"rpm -Va | grep '^..5' | grep -E -v '[a-z]*c[a-z]*\\\\s+\\\\S+$' | awk 'NF>1{print $NF}'\").\n stdout.strip.split(\"\\n\") do\n it { should all(be_in rpm_verify_integrity_except) }\n end\n end\nend\n","desc":"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the cryptographic hash of system files and commands match the vendor\nvalues.\n\n Check the cryptographic hash of system files and commands with the\nfollowing command:\n\n Note: System configuration files (indicated by a \"c\" in the second\ncolumn) are expected to change over time. Unusual modifications should be\ninvestigated through the system audit log.\n\n # rpm -Va --noconfig | grep '^..5'\n\n If there is any output from the command for system files or binaries, this\nis a finding.","label":"check"},{"data":"Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh ","label":"fix"}],"id":"V-71855","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71855.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71855","rid":"SV-86479r4_rule","stig_id":"RHEL-07-010020","fix_id":"F-78207r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cryptographic hash of system files and commands matches vendor values.","waiver_data":{}},{"code":"control \"V-71859\" do\n title \"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a graphical user logon.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a graphical\nuser logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the operating system displays a banner at the logon screen\nwith the following command:\n\n # grep banner-message-enable /etc/dconf/db/local.d/*\n banner-message-enable=true\n\n If \\\"banner-message-enable\\\" is set to \\\"false\\\" or is missing, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/01-banner-message\n\n Add the following line to the [org/gnome/login-screen] section of the\n\\\"/etc/dconf/db/local.d/01-banner-message\\\":\n\n [org/gnome/login-screen]\n banner-message-enable=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\",\n\"SRG-OS-000228-GPOS-00088\"]\n tag gid: \"V-71859\"\n tag rid: \"SV-86483r4_rule\"\n tag stig_id: \"RHEL-07-010030\"\n tag fix_id: \"F-78211r4_fix\"\n tag cci: [\"CCI-000048\"]\n tag nist: [\"AC-8 a\"]\n\n if package('gnome-desktop3').installed?\n if !input('dconf_user').nil? and command('whoami').stdout.strip == 'root'\n describe command(\"sudo -u input('dconf_user') dconf read /org/gnome/login-screen/banner-message-enable\") do\n its('stdout.strip') { should cmp input('banner_message_enabled').to_s }\n end\n else\n describe command(\"dconf read /org/gnome/login-screen/banner-message-enable\") do\n its('stdout.strip') { should cmp input('banner_message_enabled').to_s }\n end\n end\n else\n impact 0.0\n describe \"The GNOME desktop is not installed\" do \n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n end\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a graphical\nuser logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the operating system displays a banner at the logon screen\nwith the following command:\n\n # grep banner-message-enable /etc/dconf/db/local.d/*\n banner-message-enable=true\n\n If \"banner-message-enable\" is set to \"false\" or is missing, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/01-banner-message\n\n Add the following line to the [org/gnome/login-screen] section of the\n\"/etc/dconf/db/local.d/01-banner-message\":\n\n [org/gnome/login-screen]\n banner-message-enable=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71859","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71859.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-71859","rid":"SV-86483r4_rule","stig_id":"RHEL-07-010030","fix_id":"F-78211r4_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a graphical user logon.","waiver_data":{}},{"code":"control \"V-71861\" do\n title \"The Red Hat Enterprise Linux operating system must display the\napproved Standard Mandatory DoD Notice and Consent Banner before granting local\nor remote access to the system via a graphical user logon.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system displays the approved Standard Mandatory DoD\nNotice and Consent Banner before granting access to the operating system via a\ngraphical user logon.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Check that the operating system displays the exact approved Standard\nMandatory DoD Notice and Consent Banner text with the command:\n # grep banner-message-text /etc/dconf/db/local.d/*\n banner-message-text=\n 'You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\\\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\\\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\\\n -At any time, the USG may inspect and seize data stored on this IS.\\\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\\\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\\\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \\\"\\\n \\\" characters are for formatting only. They will not be displayed on the\nGUI.\n If the banner does not match the approved Standard Mandatory DoD Notice and\nConsent Banner, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the approved Standard Mandatory\nDoD Notice and Consent Banner before granting access to the system.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n # touch /etc/dconf/db/local.d/01-banner-message\n Add the following line to the [org/gnome/login-screen] section of the\n\\\"/etc/dconf/db/local.d/01-banner-message\\\":\n [org/gnome/login-screen]\n banner-message-enable=true\n banner-message-text='You are accessing a U.S. Government (USG) Information\nSystem (IS) that is provided for USG-authorized use only.\\\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\\\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\\\n -At any time, the USG may inspect and seize data stored on this IS.\\\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\\\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\\\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \\\"\\\n \\\" characters are for formatting only. They will not be displayed on the\nGUI.\n Run the following command to update the database:\n # dconf update\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\",\n\"SRG-OS-000228-GPOS-00088\"]\n tag gid: \"V-71861\"\n tag rid: \"SV-86485r4_rule\"\n tag stig_id: \"RHEL-07-010040\"\n tag fix_id: \"F-78213r5_fix\"\n tag cci: [\"CCI-000048\"]\n tag nist: [\"AC-8 a\"]\n if package('gnome-desktop3').installed?\n #Get all files that have the banner-message-text specified.\n banner_files =\n command(\"grep -l banner-message-text /etc/dconf/db/local.d/*\").stdout.split(\"\\n\")\n #If there are no banner files then this is a finding.\n banner_missing = banner_files.empty?\n describe \"If no files specify the banner text then this is a finding\" do\n subject { banner_missing }\n it{should be false}\n end if banner_missing\n #If there are banner files then check them to make sure they have the correct text.\n banner_files.each do |banner_file|\n banner_message =\n parse_config_file(banner_file).params(\"org/gnome/login-screen\",\"banner-message-text\").gsub(%r{[\\r\\n\\s]}, '')\n #dconf expects the banner-message-text to be quoted so remove leading and trailing quote.\n #See https://developer.gnome.org/dconf/unstable/dconf-tool.html which states:\n # VALUE arguments must be in GVariant format, so e.g. a string must include\n # explicit quotes: \"'foo'\". This format is also used when printing out values.\n if banner_message.start_with?('\"') || banner_message.start_with?('\\'')\n banner_message = banner_message[1,banner_message.length]\n end\n if banner_message.end_with?('\"') || banner_message.end_with?('\\'')\n banner_message = banner_message.chop\n end\n banner_message.gsub!('\\\\n', '')\n foo = input('banner_message_text_gui');\n foo2 = input('banner_message_text_gui_limited');\n describe.one do\n describe banner_message do\n it{should cmp foo.gsub(%r{[\\r\\n\\s]}, '')}\n end\n describe banner_message do\n it{should cmp foo2.gsub(%r{[\\r\\n\\s]}, '')}\n end\n end\n end\n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the approved Standard Mandatory DoD\nNotice and Consent Banner before granting access to the operating system via a\ngraphical user logon.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Check that the operating system displays the exact approved Standard\nMandatory DoD Notice and Consent Banner text with the command:\n # grep banner-message-text /etc/dconf/db/local.d/*\n banner-message-text=\n 'You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(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\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \" \" characters are for formatting only. They will not be displayed on the\nGUI.\n If the banner does not match the approved Standard Mandatory DoD Notice and\nConsent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the approved Standard Mandatory\nDoD Notice and Consent Banner before granting access to the system.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n # touch /etc/dconf/db/local.d/01-banner-message\n Add the following line to the [org/gnome/login-screen] section of the\n\"/etc/dconf/db/local.d/01-banner-message\":\n [org/gnome/login-screen]\n banner-message-enable=true\n banner-message-text='You are accessing a U.S. Government (USG) Information\nSystem (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(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\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \" \" characters are for formatting only. They will not be displayed on the\nGUI.\n Run the following command to update the database:\n # dconf update","label":"fix"}],"id":"V-71861","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71861.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-71861","rid":"SV-86485r4_rule","stig_id":"RHEL-07-010040","fix_id":"F-78213r5_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\napproved Standard Mandatory DoD Notice and Consent Banner before granting local\nor remote access to the system via a graphical user logon.","waiver_data":{}},{"code":"control \"V-71863\" do\n title \"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a command line user logon.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a command\nline user logon.\n\n Check to see if the operating system displays a banner at the command line\nlogon screen with the following command:\n\n # more /etc/issue\n\n The command should return the following text:\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n If the operating system does not display a graphical logon banner or the\nbanner does not match the Standard Mandatory DoD Notice and Consent Banner,\nthis is a finding.\n\n If the text in the \\\"/etc/issue\\\" file does not match the Standard\nMandatory DoD Notice and Consent Banner, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the command line by\nediting the \\\"/etc/issue\\\" file.\n\n Replace the default text with the Standard Mandatory DoD Notice and Consent\nBanner. The DoD required text is:\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\"]\n tag gid: \"V-71863\"\n tag rid: \"SV-86487r3_rule\"\n tag stig_id: \"RHEL-07-010050\"\n tag fix_id: \"F-78217r2_fix\"\n tag cci: [\"CCI-000048\"]\n tag nist: [\"AC-8 a\"]\n\n banner_message_text_cli = input('banner_message_text_cli')\n banner_message_text_cli_limited = input('banner_message_text_cli_limited')\n\n clean_banner = banner_message_text_cli.gsub(%r{[\\r\\n\\s]}, '')\n clean_banner_limited = banner_message_text_cli_limited.gsub(%r{[\\r\\n\\s]}, '')\n banner_file = file(\"/etc/issue\")\n banner_missing = !banner_file.exist?\n\n describe \"The banner text is not set because /etc/issue does not exist\" do\n subject { banner_missing }\n it { should be false }\n end if banner_missing\n\n banner_message = banner_file.content.gsub(%r{[\\r\\n\\s]}, '')\n describe.one do\n describe \"The banner text should match the standard banner\" do\n subject { banner_message }\n it { should cmp clean_banner }\n end\n describe \"The banner text should match the limited banner\" do\n subject { banner_message }\n it{should cmp clean_banner_limited }\n end\n end if !banner_missing\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a command\nline user logon.\n\n Check to see if the operating system displays a banner at the command line\nlogon screen with the following command:\n\n # more /etc/issue\n\n The command should return the following text:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n If the operating system does not display a graphical logon banner or the\nbanner does not match the Standard Mandatory DoD Notice and Consent Banner,\nthis is a finding.\n\n If the text in the \"/etc/issue\" file does not match the Standard\nMandatory DoD Notice and Consent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the command line by\nediting the \"/etc/issue\" file.\n\n Replace the default text with the Standard Mandatory DoD Notice and Consent\nBanner. The DoD required text is:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"fix"}],"id":"V-71863","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71863.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007"],"gid":"V-71863","rid":"SV-86487r3_rule","stig_id":"RHEL-07-010050","fix_id":"F-78217r2_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a command line user logon.","waiver_data":{}},{"code":"control \"V-71891\" do\n title \"The Red Hat Enterprise Linux operating system must enable a user\nsession lock until that user re-establishes access using established\nidentification and authentication procedures.\"\n desc \"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enables a user's session lock until that user\nre-establishes access using established identification and authentication\nprocedures. The screen program must be installed to lock sessions on the\nconsole.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the screen lock is enabled with the following command:\n\n # grep -i lock-enabled /etc/dconf/db/local.d/*\n lock-enabled=true\n\n If the \\\"lock-enabled\\\" setting is missing or is not set to \\\"true\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enable a user's session lock until that\nuser re-establishes access using established identification and authentication\nprocedures.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following example:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit the \\\"[org/gnome/desktop/screensaver]\\\" section of the database file\nand add or update the following lines:\n\n # Set this to true to lock the screen when the screensaver activates\n lock-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000028-GPOS-00009\"\n tag satisfies: [\"SRG-OS-000028-GPOS-00009\", \"SRG-OS-000030-GPOS-00011\"]\n tag gid: \"V-71891\"\n tag rid: \"SV-86515r6_rule\"\n tag stig_id: \"RHEL-07-010060\"\n tag fix_id: \"F-78243r9_fix\"\n tag cci: [\"CCI-000056\"]\n tag nist: [\"AC-11 b\"]\n\n if package('gnome-desktop3').installed?\n describe command('gsettings get org.gnome.desktop.screensaver lock-enabled') do\n its('stdout.strip') { should cmp 'true' }\n end\n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enables a user's session lock until that user\nre-establishes access using established identification and authentication\nprocedures. The screen program must be installed to lock sessions on the\nconsole.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the screen lock is enabled with the following command:\n\n # grep -i lock-enabled /etc/dconf/db/local.d/*\n lock-enabled=true\n\n If the \"lock-enabled\" setting is missing or is not set to \"true\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to enable a user's session lock until that\nuser re-establishes access using established identification and authentication\nprocedures.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following example:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit the \"[org/gnome/desktop/screensaver]\" section of the database file\nand add or update the following lines:\n\n # Set this to true to lock the screen when the screensaver activates\n lock-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71891","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71891.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000028-GPOS-00009","satisfies":["SRG-OS-000028-GPOS-00009","SRG-OS-000030-GPOS-00011"],"gid":"V-71891","rid":"SV-86515r6_rule","stig_id":"RHEL-07-010060","fix_id":"F-78243r9_fix","cci":["CCI-000056"],"nist":["AC-11 b"]},"title":"The Red Hat Enterprise Linux operating system must enable a user\nsession lock until that user re-establishes access using established\nidentification and authentication procedures.","waiver_data":{}},{"code":"control \"V-71893\" do\n title \"The Red Hat Enterprise Linux operating system must initiate a\nscreensaver after a 15-minute period of inactivity for graphical user\ninterfaces.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if GNOME is configured to display a screensaver after a 15\nminute delay with the following command:\n\n # grep -i idle-delay /etc/dconf/db/local.d/*\n idle-delay=uint32 900\n\n If the \\\"idle-delay\\\" setting is missing or is not set to \\\"900\\\" or less,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit /etc/dconf/db/local.d/00-screensaver and add or update the following\nlines:\n\n [org/gnome/desktop/session]\n # Set the lock time out to 900 seconds before the session is considered idle\n idle-delay=uint32 900\n\n You must include the \\\"uint32\\\" along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71893\"\n tag rid: \"SV-86517r5_rule\"\n tag stig_id: \"RHEL-07-010070\"\n tag fix_id: \"F-78245r5_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n unless package('gnome-desktop3').installed?\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n else \n describe command(\"gsettings get org.gnome.desktop.session idle-delay | cut -d ' ' -f2\") do\n its('stdout.strip') { should cmp <= 900 }\n end \n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if GNOME is configured to display a screensaver after a 15\nminute delay with the following command:\n\n # grep -i idle-delay /etc/dconf/db/local.d/*\n idle-delay=uint32 900\n\n If the \"idle-delay\" setting is missing or is not set to \"900\" or less,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to initiate a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit /etc/dconf/db/local.d/00-screensaver and add or update the following\nlines:\n\n [org/gnome/desktop/session]\n # Set the lock time out to 900 seconds before the session is considered idle\n idle-delay=uint32 900\n\n You must include the \"uint32\" along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71893","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71893.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71893","rid":"SV-86517r5_rule","stig_id":"RHEL-07-010070","fix_id":"F-78245r5_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a\nscreensaver after a 15-minute period of inactivity for graphical user\ninterfaces.","waiver_data":{}},{"code":"control \"V-71897\" do\n title \"The Red Hat Enterprise Linux operating system must have the screen\npackage installed.\"\n desc \": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system has the screen package installed.\n\n Check to see if the screen package is installed with the following command:\n\n # yum list installed screen\n screen-4.3.1-3-x86_64.rpm\n\n If the screen package is not installed, check to see if the tmux package is\ninstalled with the following command:\n\n #yum list installed tmux\n tmux-1.8-4.el7.x86_64.rpm\n\n If either the screen package or the tmux package is not installed, this is\na finding.\n \"\n desc \"fix\", \"\n Install the screen package to allow the initiation of a session lock after\na 15-minute period of inactivity.\n\n Install the screen program (if it is not on the system) with the following\ncommand:\n\n # yum install screen\n\n OR\n\n Install the tmux program (if it is not on the system) with the following\ncommand:\n\n #yum install tmux\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71897\"\n tag rid: \"SV-86521r3_rule\"\n tag stig_id: \"RHEL-07-010090\"\n tag fix_id: \"F-78249r3_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n multiplexer_packages = input('terminal_mux_pkgs')\n\n describe.one do\n multiplexer_packages.each do |pkg| \n describe package(pkg) do\n it { should be_installed }\n end\n end\n end\nend\n","desc":": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.","descriptions":[{"data":": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system has the screen package installed.\n\n Check to see if the screen package is installed with the following command:\n\n # yum list installed screen\n screen-4.3.1-3-x86_64.rpm\n\n If the screen package is not installed, check to see if the tmux package is\ninstalled with the following command:\n\n #yum list installed tmux\n tmux-1.8-4.el7.x86_64.rpm\n\n If either the screen package or the tmux package is not installed, this is\na finding.","label":"check"},{"data":"Install the screen package to allow the initiation of a session lock after\na 15-minute period of inactivity.\n\n Install the screen program (if it is not on the system) with the following\ncommand:\n\n # yum install screen\n\n OR\n\n Install the tmux program (if it is not on the system) with the following\ncommand:\n\n #yum install tmux","label":"fix"}],"id":"V-71897","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71897.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71897","rid":"SV-86521r3_rule","stig_id":"RHEL-07-010090","fix_id":"F-78249r3_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must have the screen\npackage installed.","waiver_data":{}},{"code":"control \"V-71899\" do\n title \"The Red Hat Enterprise Linux operating system must initiate a session\nlock for the screensaver after a period of inactivity for graphical user\ninterfaces.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have a Graphical User Interface installed,\nthis requirement is Not Applicable.\n\n Check for the session lock settings with the following commands:\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/*\n\n idle-activation-enabled=true\n\n If \\\"idle-activation-enabled\\\" is not set to \\\"true\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable screensaver locking after 15 minutes of\ninactivity:\n\n [org/gnome/desktop/screensaver]\n\n idle-activation-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71899\"\n tag rid: \"SV-86523r5_rule\"\n tag stig_id: \"RHEL-07-010100\"\n tag fix_id: \"F-78251r2_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n describe command('gsettings get org.gnome.desktop.screensaver idle-activation-enabled') do\n its('stdout.strip') { should cmp 'true' }\n end \n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have a Graphical User Interface installed,\nthis requirement is Not Applicable.\n\n Check for the session lock settings with the following commands:\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/*\n\n idle-activation-enabled=true\n\n If \"idle-activation-enabled\" is not set to \"true\", this is a finding.","label":"check"},{"data":"Configure the operating system to initiate a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable screensaver locking after 15 minutes of\ninactivity:\n\n [org/gnome/desktop/screensaver]\n\n idle-activation-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71899","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71899.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71899","rid":"SV-86523r5_rule","stig_id":"RHEL-07-010100","fix_id":"F-78251r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a session\nlock for the screensaver after a period of inactivity for graphical user\ninterfaces.","waiver_data":{}},{"code":"control \"V-71901\" do\n title \"The Red Hat Enterprise Linux operating system must initiate a session\nlock for graphical user interfaces when the screensaver is activated.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates a session lock a for graphical user\ninterfaces when the screensaver is activated.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n If GNOME is installed, check to see a session lock occurs when the\nscreensaver is activated with the following command:\n\n # grep -i lock-delay /etc/dconf/db/local.d/*\n lock-delay=uint32 5\n\n If the \\\"lock-delay\\\" setting is missing, or is not set to \\\"5\\\" or less,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate a session lock for graphical\nuser interfaces when a screensaver is activated.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable session locking when a screensaver is activated:\n\n [org/gnome/desktop/screensaver]\n lock-delay=uint32 5\n\n The \\\"uint32\\\" must be included along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71901\"\n tag rid: \"SV-86525r3_rule\"\n tag stig_id: \"RHEL-07-010110\"\n tag fix_id: \"F-78253r2_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n describe command(\"gsettings get org.gnome.desktop.screensaver lock-delay | cut -d ' ' -f2\") do\n its('stdout.strip') { should cmp <= input('lock_delay') }\n end\n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a session lock a for graphical user\ninterfaces when the screensaver is activated.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n If GNOME is installed, check to see a session lock occurs when the\nscreensaver is activated with the following command:\n\n # grep -i lock-delay /etc/dconf/db/local.d/*\n lock-delay=uint32 5\n\n If the \"lock-delay\" setting is missing, or is not set to \"5\" or less,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to initiate a session lock for graphical\nuser interfaces when a screensaver is activated.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable session locking when a screensaver is activated:\n\n [org/gnome/desktop/screensaver]\n lock-delay=uint32 5\n\n The \"uint32\" must be included along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71901","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71901.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71901","rid":"SV-86525r3_rule","stig_id":"RHEL-07-010110","fix_id":"F-78253r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a session\nlock for graphical user interfaces when the screensaver is activated.","waiver_data":{}},{"code":"control \"V-71903\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one upper-case character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Note: The value to require a number of upper-case characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"ucredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep ucredit /etc/security/pwquality.conf\n ucredit = -1\n\n If the value of \\\"ucredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce password complexity by requiring\nthat at least one upper-case character be used by setting the \\\"ucredit\\\"\noption.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\nline to have the required value):\n\n ucredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000069-GPOS-00037\"\n tag gid: \"V-71903\"\n tag rid: \"SV-86527r3_rule\"\n tag stig_id: \"RHEL-07-010120\"\n tag fix_id: \"F-78255r1_fix\"\n tag cci: [\"CCI-000192\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('ucredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of upper-case characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"ucredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep ucredit /etc/security/pwquality.conf\n ucredit = -1\n\n If the value of \"ucredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one upper-case character be used by setting the \"ucredit\"\noption.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n ucredit = -1","label":"fix"}],"id":"V-71903","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71903.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-71903","rid":"SV-86527r3_rule","stig_id":"RHEL-07-010120","fix_id":"F-78255r1_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one upper-case character.","waiver_data":{}},{"code":"control \"V-71905\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one lower-case character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Note: The value to require a number of lower-case characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"lcredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep lcredit /etc/security/pwquality.conf\n lcredit = -1\n\n If the value of \\\"lcredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the system to require at least one lower-case character when\ncreating or changing a password.\n\n Add or modify the following line\n in \\\"/etc/security/pwquality.conf\\\":\n\n lcredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000070-GPOS-00038\"\n tag gid: \"V-71905\"\n tag rid: \"SV-86529r5_rule\"\n tag stig_id: \"RHEL-07-010130\"\n tag fix_id: \"F-78257r6_fix\"\n tag cci: [\"CCI-000193\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('lcredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of lower-case characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"lcredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep lcredit /etc/security/pwquality.conf\n lcredit = -1\n\n If the value of \"lcredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the system to require at least one lower-case character when\ncreating or changing a password.\n\n Add or modify the following line\n in \"/etc/security/pwquality.conf\":\n\n lcredit = -1","label":"fix"}],"id":"V-71905","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71905.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000070-GPOS-00038","gid":"V-71905","rid":"SV-86529r5_rule","stig_id":"RHEL-07-010130","fix_id":"F-78257r6_fix","cci":["CCI-000193"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one lower-case character.","waiver_data":{}},{"code":"control \"V-71907\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are assigned, the new password\nmust contain at least one numeric character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Note: The value to require a number of numeric characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"dcredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep dcredit /etc/security/pwquality.conf\n dcredit = -1\n\n If the value of \\\"dcredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce password complexity by requiring\nthat at least one numeric character be used by setting the \\\"dcredit\\\" option.\n\n Add the following line to /etc/security/pwquality.conf (or modify the line\nto have the required value):\n\n dcredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000071-GPOS-00039\"\n tag gid: \"V-71907\"\n tag rid: \"SV-86531r3_rule\"\n tag stig_id: \"RHEL-07-010140\"\n tag fix_id: \"F-78259r1_fix\"\n tag cci: [\"CCI-000194\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('dcredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of numeric characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"dcredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep dcredit /etc/security/pwquality.conf\n dcredit = -1\n\n If the value of \"dcredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one numeric character be used by setting the \"dcredit\" option.\n\n Add the following line to /etc/security/pwquality.conf (or modify the line\nto have the required value):\n\n dcredit = -1","label":"fix"}],"id":"V-71907","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71907.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000071-GPOS-00039","gid":"V-71907","rid":"SV-86531r3_rule","stig_id":"RHEL-07-010140","fix_id":"F-78259r1_fix","cci":["CCI-000194"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are assigned, the new password\nmust contain at least one numeric character.","waiver_data":{}},{"code":"control \"V-71909\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one special character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enforces password complexity by requiring that\nat least one special character be used.\n\n Note: The value to require a number of special characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"ocredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep ocredit /etc/security/pwquality.conf\n ocredit=-1\n\n If the value of \\\"ocredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce password complexity by requiring\nthat at least one special character be used by setting the \\\"ocredit\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\nline to have the required value):\n\n ocredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000266-GPOS-00101\"\n tag gid: \"V-71909\"\n tag rid: \"SV-86533r2_rule\"\n tag stig_id: \"RHEL-07-010150\"\n tag fix_id: \"F-78261r2_fix\"\n tag cci: [\"CCI-001619\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('ocredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces password complexity by requiring that\nat least one special character be used.\n\n Note: The value to require a number of special characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"ocredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep ocredit /etc/security/pwquality.conf\n ocredit=-1\n\n If the value of \"ocredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one special character be used by setting the \"ocredit\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n ocredit = -1","label":"fix"}],"id":"V-71909","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71909.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000266-GPOS-00101","gid":"V-71909","rid":"SV-86533r2_rule","stig_id":"RHEL-07-010150","fix_id":"F-78261r2_fix","cci":["CCI-001619"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one special character.","waiver_data":{}},{"code":"control \"V-71911\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of eight of the total number of\ncharacters must be changed.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"difok\\\" option sets the number of characters in a password that must\nnot be present in the old password.\n\n Check for the value of the \\\"difok\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep difok /etc/security/pwquality.conf\n difok = 8\n\n If the value of \\\"difok\\\" is set to less than \\\"8\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of at least eight of\nthe total number of characters when passwords are changed by setting the\n\\\"difok\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\nline to have the required value):\n\n difok = 8\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71911\"\n tag rid: \"SV-86535r2_rule\"\n tag stig_id: \"RHEL-07-010160\"\n tag fix_id: \"F-78263r1_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n difok = input('difok')\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('difok.to_i') { should cmp >= difok }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"difok\" option sets the number of characters in a password that must\nnot be present in the old password.\n\n Check for the value of the \"difok\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep difok /etc/security/pwquality.conf\n difok = 8\n\n If the value of \"difok\" is set to less than \"8\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of at least eight of\nthe total number of characters when passwords are changed by setting the\n\"difok\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n difok = 8","label":"fix"}],"id":"V-71911","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71911.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71911","rid":"SV-86535r2_rule","stig_id":"RHEL-07-010160","fix_id":"F-78263r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of eight of the total number of\ncharacters must be changed.","waiver_data":{}},{"code":"control \"V-71913\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of four character classes must be\nchanged.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"minclass\\\" option sets the minimum number of required classes of\ncharacters for the new password (digits, upper-case, lower-case, others).\n\n Check for the value of the \\\"minclass\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep minclass /etc/security/pwquality.conf\n minclass = 4\n\n If the value of \\\"minclass\\\" is set to less than \\\"4\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of at least four\ncharacter classes when passwords are changed by setting the \\\"minclass\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf conf\\\" (or modify\nthe line to have the required value):\n\n minclass = 4\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71913\"\n tag rid: \"SV-86537r2_rule\"\n tag stig_id: \"RHEL-07-010170\"\n tag fix_id: \"F-78265r1_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('minclass.to_i') { should cmp >= 4 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"minclass\" option sets the minimum number of required classes of\ncharacters for the new password (digits, upper-case, lower-case, others).\n\n Check for the value of the \"minclass\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep minclass /etc/security/pwquality.conf\n minclass = 4\n\n If the value of \"minclass\" is set to less than \"4\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of at least four\ncharacter classes when passwords are changed by setting the \"minclass\" option.\n\n Add the following line to \"/etc/security/pwquality.conf conf\" (or modify\nthe line to have the required value):\n\n minclass = 4","label":"fix"}],"id":"V-71913","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71913.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71913","rid":"SV-86537r2_rule","stig_id":"RHEL-07-010170","fix_id":"F-78265r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of four character classes must be\nchanged.","waiver_data":{}},{"code":"control \"V-71915\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating consecutive characters\nmust not be more than three characters.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"maxrepeat\\\" option sets the maximum number of allowed same\nconsecutive characters in a new password.\n\n Check for the value of the \\\"maxrepeat\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep maxrepeat /etc/security/pwquality.conf\n maxrepeat = 3\n\n If the value of \\\"maxrepeat\\\" is set to more than \\\"3\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of the number of\nrepeating consecutive characters when passwords are changed by setting the\n\\\"maxrepeat\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf conf\\\" (or modify\nthe line to have the required value):\n\n maxrepeat = 3\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71915\"\n tag rid: \"SV-86539r3_rule\"\n tag stig_id: \"RHEL-07-010180\"\n tag fix_id: \"F-78267r2_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('maxrepeat.to_i') { should cmp <= 3 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"maxrepeat\" option sets the maximum number of allowed same\nconsecutive characters in a new password.\n\n Check for the value of the \"maxrepeat\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep maxrepeat /etc/security/pwquality.conf\n maxrepeat = 3\n\n If the value of \"maxrepeat\" is set to more than \"3\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of the number of\nrepeating consecutive characters when passwords are changed by setting the\n\"maxrepeat\" option.\n\n Add the following line to \"/etc/security/pwquality.conf conf\" (or modify\nthe line to have the required value):\n\n maxrepeat = 3","label":"fix"}],"id":"V-71915","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71915.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71915","rid":"SV-86539r3_rule","stig_id":"RHEL-07-010180","fix_id":"F-78267r2_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating consecutive characters\nmust not be more than three characters.","waiver_data":{}},{"code":"control \"V-71917\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating characters of the same\ncharacter class must not be more than four characters.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"maxclassrepeat\\\" option sets the maximum number of allowed same\nconsecutive characters in the same class in the new password.\n\n Check for the value of the \\\"maxclassrepeat\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep maxclassrepeat /etc/security/pwquality.conf\n maxclassrepeat = 4\n\n If the value of \\\"maxclassrepeat\\\" is set to more than \\\"4\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of the number of\nrepeating characters of the same character class when passwords are changed by\nsetting the \\\"maxclassrepeat\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" conf (or modify\nthe line to have the required value):\n\n maxclassrepeat = 4\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71917\"\n tag rid: \"SV-86541r2_rule\"\n tag stig_id: \"RHEL-07-010190\"\n tag fix_id: \"F-78269r1_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('maxclassrepeat.to_i') { should cmp <= 4 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"maxclassrepeat\" option sets the maximum number of allowed same\nconsecutive characters in the same class in the new password.\n\n Check for the value of the \"maxclassrepeat\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep maxclassrepeat /etc/security/pwquality.conf\n maxclassrepeat = 4\n\n If the value of \"maxclassrepeat\" is set to more than \"4\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to require the change of the number of\nrepeating characters of the same character class when passwords are changed by\nsetting the \"maxclassrepeat\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" conf (or modify\nthe line to have the required value):\n\n maxclassrepeat = 4","label":"fix"}],"id":"V-71917","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71917.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71917","rid":"SV-86541r2_rule","stig_id":"RHEL-07-010190","fix_id":"F-78269r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating characters of the same\ncharacter class must not be more than four characters.","waiver_data":{}},{"code":"control \"V-71919\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the PAM system service is configured to store only encrypted\nrepresentations of passwords.\"\n desc \"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the PAM system service is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep password /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n Outcome should look like following:\n /etc/pam.d/system-auth-ac:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n /etc/pam.d/password-auth:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n\n If the \\\"/etc/pam.d/system-auth\\\" and \\\"/etc/pam.d/password-auth\\\"\nconfiguration files allow for password hashes other than SHA512 to be used,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add the following line in \\\"/etc/pam.d/system-auth\\\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Add the following line in \\\"/etc/pam.d/password-auth\\\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000073-GPOS-00041\"\n tag gid: \"V-71919\"\n tag rid: \"SV-86543r3_rule\"\n tag stig_id: \"RHEL-07-010200\"\n tag fix_id: \"F-78271r4_fix\"\n tag cci: [\"CCI-000196\"]\n tag nist: [\"IA-5 (1) (c)\"]\n\n describe pam(\"/etc/pam.d/system-auth\") do\n its('lines') { should match_pam_rule('password sufficient pam_unix.so sha512') }\n its('lines') { should match_pam_rule('password .* pam_unix.so').all_without_args('^(md5|bigcrypt|sha256|blowfish)$') }\n end\nend\n","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the PAM system service is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep password /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n Outcome should look like following:\n /etc/pam.d/system-auth-ac:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n /etc/pam.d/password-auth:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n\n If the \"/etc/pam.d/system-auth\" and \"/etc/pam.d/password-auth\"\nconfiguration files allow for password hashes other than SHA512 to be used,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add the following line in \"/etc/pam.d/system-auth\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Add the following line in \"/etc/pam.d/password-auth\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71919","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71919.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71919","rid":"SV-86543r3_rule","stig_id":"RHEL-07-010200","fix_id":"F-78271r4_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the PAM system service is configured to store only encrypted\nrepresentations of passwords.","waiver_data":{}},{"code":"control \"V-71921\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nuse the shadow file to store only encrypted representations of passwords.\"\n desc \"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system's shadow file is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep -i encrypt /etc/login.defs\n ENCRYPT_METHOD SHA512\n\n If the \\\"/etc/login.defs\\\" configuration file does not exist or allows for\npassword hashes other than SHA512 to be used, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \\\"/etc/login.defs\\\":\n\n ENCRYPT_METHOD SHA512\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000073-GPOS-00041\"\n tag gid: \"V-71921\"\n tag rid: \"SV-86545r2_rule\"\n tag stig_id: \"RHEL-07-010210\"\n tag fix_id: \"F-78273r1_fix\"\n tag cci: [\"CCI-000196\"]\n tag nist: [\"IA-5 (1) (c)\"]\n\n describe login_defs do\n its('ENCRYPT_METHOD') { should cmp \"SHA512\" }\n end\nend\n","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system's shadow file is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep -i encrypt /etc/login.defs\n ENCRYPT_METHOD SHA512\n\n If the \"/etc/login.defs\" configuration file does not exist or allows for\npassword hashes other than SHA512 to be used, this is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \"/etc/login.defs\":\n\n ENCRYPT_METHOD SHA512","label":"fix"}],"id":"V-71921","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71921.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71921","rid":"SV-86545r2_rule","stig_id":"RHEL-07-010210","fix_id":"F-78273r1_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nuse the shadow file to store only encrypted representations of passwords.","waiver_data":{}},{"code":"control \"V-71923\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat user and group account administration utilities are configured to store\nonly encrypted representations of passwords.\"\n desc \"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the user and group account administration utilities are configured\nto store only encrypted representations of passwords. The strength of\nencryption that must be used to hash passwords for all accounts is \\\"SHA512\\\".\n\n Check that the system is configured to create \\\"SHA512\\\" hashed passwords\nwith the following command:\n\n # grep -i sha512 /etc/libuser.conf\n\n crypt_style = sha512\n\n If the \\\"crypt_style\\\" variable is not set to \\\"sha512\\\", is not in the\ndefaults section, is commented out, or does not exist, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \\\"/etc/libuser.conf\\\" in the [defaults]\nsection:\n\n crypt_style = sha512\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000073-GPOS-00041\"\n tag gid: \"V-71923\"\n tag rid: \"SV-86547r3_rule\"\n tag stig_id: \"RHEL-07-010220\"\n tag fix_id: \"F-78275r1_fix\"\n tag cci: [\"CCI-000196\"]\n tag nist: [\"IA-5 (1) (c)\"]\n\n describe command(\"cat /etc/libuser.conf | grep -i sha512\") do\n its('stdout.strip') { should match %r(^crypt_style = sha512$) }\n end\nend\n","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the user and group account administration utilities are configured\nto store only encrypted representations of passwords. The strength of\nencryption that must be used to hash passwords for all accounts is \"SHA512\".\n\n Check that the system is configured to create \"SHA512\" hashed passwords\nwith the following command:\n\n # grep -i sha512 /etc/libuser.conf\n\n crypt_style = sha512\n\n If the \"crypt_style\" variable is not set to \"sha512\", is not in the\ndefaults section, is commented out, or does not exist, this is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \"/etc/libuser.conf\" in the [defaults]\nsection:\n\n crypt_style = sha512","label":"fix"}],"id":"V-71923","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71923.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71923","rid":"SV-86547r3_rule","stig_id":"RHEL-07-010220","fix_id":"F-78275r1_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat user and group account administration utilities are configured to store\nonly encrypted representations of passwords.","waiver_data":{}},{"code":"control \"V-71925\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 24 hours/1 day minimum\nlifetime.\"\n desc \"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enforces 24 hours/1 day as the minimum password\nlifetime for new user accounts.\n\n Check for the value of \\\"PASS_MIN_DAYS\\\" in \\\"/etc/login.defs\\\" with the\nfollowing command:\n\n # grep -i pass_min_days /etc/login.defs\n PASS_MIN_DAYS 1\n\n If the \\\"PASS_MIN_DAYS\\\" parameter value is not \\\"1\\\" or greater, or is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce 24 hours/1 day as the minimum\npassword lifetime.\n\n Add the following line in \\\"/etc/login.defs\\\" (or modify the line to have\nthe required value):\n\n PASS_MIN_DAYS 1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000075-GPOS-00043\"\n tag gid: \"V-71925\"\n tag rid: \"SV-86549r2_rule\"\n tag stig_id: \"RHEL-07-010230\"\n tag fix_id: \"F-78277r1_fix\"\n tag cci: [\"CCI-000198\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n describe login_defs do\n its('PASS_MIN_DAYS.to_i') { should cmp >= 1 }\n end\nend\n","desc":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","descriptions":[{"data":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces 24 hours/1 day as the minimum password\nlifetime for new user accounts.\n\n Check for the value of \"PASS_MIN_DAYS\" in \"/etc/login.defs\" with the\nfollowing command:\n\n # grep -i pass_min_days /etc/login.defs\n PASS_MIN_DAYS 1\n\n If the \"PASS_MIN_DAYS\" parameter value is not \"1\" or greater, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce 24 hours/1 day as the minimum\npassword lifetime.\n\n Add the following line in \"/etc/login.defs\" (or modify the line to have\nthe required value):\n\n PASS_MIN_DAYS 1","label":"fix"}],"id":"V-71925","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71925.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000075-GPOS-00043","gid":"V-71925","rid":"SV-86549r2_rule","stig_id":"RHEL-07-010230","fix_id":"F-78277r1_fix","cci":["CCI-000198"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 24 hours/1 day minimum\nlifetime.","waiver_data":{}},{"code":"control \"V-71927\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are restricted to a 24 hours/1 day minimum lifetime.\"\n desc \"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check whether the minimum time period between password changes for each\nuser account is one day or greater.\n\n # awk -F: '$4 < 1 {print $1 \\\" \\\" $4}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure non-compliant accounts to enforce a 24 hours/1 day minimum\npassword lifetime:\n\n # chage -m 1 [user]\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000075-GPOS-00043\"\n tag gid: \"V-71927\"\n tag rid: \"SV-86551r2_rule\"\n tag stig_id: \"RHEL-07-010240\"\n tag fix_id: \"F-78279r1_fix\"\n tag cci: [\"CCI-000198\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n shadow.users.each do |user|\n # filtering on non-system accounts (uid >= 1000)\n next unless user(user).uid >= 1000\n describe shadow.users(user) do\n its('min_days.first.to_i') { should cmp >= 1 }\n end\n end\nend\n","desc":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","descriptions":[{"data":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Check whether the minimum time period between password changes for each\nuser account is one day or greater.\n\n # awk -F: '$4 < 1 {print $1 \" \" $4}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.","label":"check"},{"data":"Configure non-compliant accounts to enforce a 24 hours/1 day minimum\npassword lifetime:\n\n # chage -m 1 [user]","label":"fix"}],"id":"V-71927","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71927.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000075-GPOS-00043","gid":"V-71927","rid":"SV-86551r2_rule","stig_id":"RHEL-07-010240","fix_id":"F-78279r1_fix","cci":["CCI-000198"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are restricted to a 24 hours/1 day minimum lifetime.","waiver_data":{}},{"code":"control \"V-71929\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 60-day maximum lifetime.\"\n desc \"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system enforces a 60-day maximum password lifetime\nrestriction for new user accounts.\n\n Check for the value of \\\"PASS_MAX_DAYS\\\" in \\\"/etc/login.defs\\\" with the\nfollowing command:\n\n # grep -i pass_max_days /etc/login.defs\n PASS_MAX_DAYS 60\n\n If the \\\"PASS_MAX_DAYS\\\" parameter value is not 60 or less, or is commented\nout, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce a 60-day maximum password\nlifetime restriction.\n\n Add the following line in \\\"/etc/login.defs\\\" (or modify the line to have\nthe required value):\n\n PASS_MAX_DAYS 60\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000076-GPOS-00044\"\n tag gid: \"V-71929\"\n tag rid: \"SV-86553r2_rule\"\n tag stig_id: \"RHEL-07-010250\"\n tag fix_id: \"F-78281r1_fix\"\n tag cci: [\"CCI-000199\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n unless command(\"grep 'pam_unix.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'optional'\").stdout.empty? && command(\"grep 'pam_permit.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'required'\").stdout.empty?\n impact 0.0\n describe \"The system is not using password for authentication\" do\n skip \"The system is not using password for authentication, this control is Not Applicable.\"\n end\n else\n describe login_defs do\n its('PASS_MAX_DAYS.to_i') { should cmp <= 60 }\n end\n end\nend\n","desc":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","descriptions":[{"data":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system enforces a 60-day maximum password lifetime\nrestriction for new user accounts.\n\n Check for the value of \"PASS_MAX_DAYS\" in \"/etc/login.defs\" with the\nfollowing command:\n\n # grep -i pass_max_days /etc/login.defs\n PASS_MAX_DAYS 60\n\n If the \"PASS_MAX_DAYS\" parameter value is not 60 or less, or is commented\nout, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce a 60-day maximum password\nlifetime restriction.\n\n Add the following line in \"/etc/login.defs\" (or modify the line to have\nthe required value):\n\n PASS_MAX_DAYS 60","label":"fix"}],"id":"V-71929","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71929.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000076-GPOS-00044","gid":"V-71929","rid":"SV-86553r2_rule","stig_id":"RHEL-07-010250","fix_id":"F-78281r1_fix","cci":["CCI-000199"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 60-day maximum lifetime.","waiver_data":{}},{"code":"control \"V-71931\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat existing passwords are restricted to a 60-day maximum lifetime.\"\n desc \"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check whether the maximum time period for existing passwords is restricted\nto 60 days.\n\n # awk -F: '$5 > 60 {print $1 \\\" \\\" $5}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.\n\n \"\n desc \"fix\", \"\n Configure non-compliant accounts to enforce a 60-day maximum password\nlifetime restriction.\n\n # chage -M 60 [user]\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000076-GPOS-00044\"\n tag gid: \"V-71931\"\n tag rid: \"SV-86555r3_rule\"\n tag stig_id: \"RHEL-07-010260\"\n tag fix_id: \"F-78283r1_fix\"\n tag cci: [\"CCI-000199\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n shadow.users.each do |user|\n # filtering on non-system accounts (uid >= 1000)\n next unless user(user).uid >= 1000\n describe shadow.users(user) do\n its('max_days.first.to_i') { should cmp <= 60 }\n end\n end\nend\n","desc":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","descriptions":[{"data":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Check whether the maximum time period for existing passwords is restricted\nto 60 days.\n\n # awk -F: '$5 > 60 {print $1 \" \" $5}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.","label":"check"},{"data":"Configure non-compliant accounts to enforce a 60-day maximum password\nlifetime restriction.\n\n # chage -M 60 [user]","label":"fix"}],"id":"V-71931","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71931.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000076-GPOS-00044","gid":"V-71931","rid":"SV-86555r3_rule","stig_id":"RHEL-07-010260","fix_id":"F-78283r1_fix","cci":["CCI-000199"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat existing passwords are restricted to a 60-day maximum lifetime.","waiver_data":{}},{"code":"control \"V-71933\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are prohibited from reuse for a minimum of five generations.\"\n desc \"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prohibits password reuse for a minimum of five\ngenerations.\n\n Check for the value of the \\\"remember\\\" argument in\n\\\"/etc/pam.d/system-auth\\\" and \\\"/etc/pam.d/password-auth\\\" with the following\ncommand:\n\n # grep -i remember /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n If the line containing the \\\"pam_pwhistory.so\\\" line does not have the\n\\\"remember\\\" module argument set, is commented out, or the value of the\n\\\"remember\\\" module argument is set to less than \\\"5\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prohibit password reuse for a minimum of\nfive generations.\n\n Add the following line in \\\"/etc/pam.d/system-auth\\\" and\n\\\"/etc/pam.d/password-auth\\\" (or modify the line to have the required value):\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000077-GPOS-00045\"\n tag gid: \"V-71933\"\n tag rid: \"SV-86557r3_rule\"\n tag stig_id: \"RHEL-07-010270\"\n tag fix_id: \"F-78285r3_fix\"\n tag cci: [\"CCI-000200\"]\n tag nist: [\"IA-5 (1) (e)\"]\n\n min_reuse_generations = input('min_reuse_generations')\n\n describe pam(\"/etc/pam.d/system-auth\") do\n its('lines') { should match_pam_rule('password (required|requisite|sufficient) pam_(unix|pwhistory).so').any_with_integer_arg('remember', '>=', min_reuse_generations) }\n end\nend\n","desc":"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.","descriptions":[{"data":"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prohibits password reuse for a minimum of five\ngenerations.\n\n Check for the value of the \"remember\" argument in\n\"/etc/pam.d/system-auth\" and \"/etc/pam.d/password-auth\" with the following\ncommand:\n\n # grep -i remember /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n If the line containing the \"pam_pwhistory.so\" line does not have the\n\"remember\" module argument set, is commented out, or the value of the\n\"remember\" module argument is set to less than \"5\", this is a finding.","label":"check"},{"data":"Configure the operating system to prohibit password reuse for a minimum of\nfive generations.\n\n Add the following line in \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" (or modify the line to have the required value):\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"},{"data":"This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords","label":"caveat"}],"id":"V-71933","impact":0,"refs":[{"ref":[]}],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71933.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000077-GPOS-00045","gid":"V-71933","rid":"SV-86557r3_rule","stig_id":"RHEL-07-010270","fix_id":"F-78285r3_fix","cci":["CCI-000200"],"nist":["IA-5 (1) (e)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are prohibited from reuse for a minimum of five generations.","waiver_data":{}},{"code":"\t control \"V-71935\" do\n\t\ttitle \"The Red Hat Enterprise Linux operating system must be configured so\n\tthat passwords are a minimum of 24 characters in length.\"\n\t\tdesc 'caveat', 'The project2 requires more secure password length of 24 characters as approved on 1/12/2022'\n\t\tdesc \"check\", \"\n\t\t\tVerify the operating system enforces a minimum 24-character password\n\tlength. The \\\"minlen\\\" option sets the minimum number of characters in a new\n\tpassword.\n\t\t\tCheck for the value of the \\\"minlen\\\" option in\n\t\\\"/etc/security/pwquality.conf\\\" with the following command:\n\t\t\t# grep minlen /etc/security/pwquality.conf\n\t\t\tminlen = 24\n\t\t\tIf the command does not return a \\\"minlen\\\" value of 24 or greater, this is\n\ta finding.\n\t\t\"\n\t\tdesc \"fix\", \"\n\t\t\tConfigure operating system to enforce a minimum 24-character password\n\tlength.\n\t\t\tAdd the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\n\tline to have the required value):\n\t\t\tminlen = 24\n\t\t\"\n\tend\n","desc":"The shorter the password, the lower the number of possible\ncombinations that need to be tested before the password is compromised.\n\n Password complexity, or strength, is a measure of the effectiveness of a\npassword in resisting attempts at guessing and brute-force attacks. Password\nlength is one factor of several that helps to determine strength and how long\nit takes to crack a password. Use of more characters in a password helps to\nexponentially increase the time and/or resources required to compromise the\npassword.","descriptions":[{"data":"The shorter the password, the lower the number of possible\ncombinations that need to be tested before the password is compromised.\n\n Password complexity, or strength, is a measure of the effectiveness of a\npassword in resisting attempts at guessing and brute-force attacks. Password\nlength is one factor of several that helps to determine strength and how long\nit takes to crack a password. Use of more characters in a password helps to\nexponentially increase the time and/or resources required to compromise the\npassword.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces a minimum 24-character password\nlength. The \"minlen\" option sets the minimum number of characters in a new\npassword.\n\t\tCheck for the value of the \"minlen\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\t\t# grep minlen /etc/security/pwquality.conf\n\t\tminlen = 24\n\t\tIf the command does not return a \"minlen\" value of 24 or greater, this is\na finding.","label":"check"},{"data":"Configure operating system to enforce a minimum 24-character password\nlength.\n\t\tAdd the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\t\tminlen = 24","label":"fix"},{"data":"The project2 requires more secure password length of 24 characters as approved on 1/12/2022","label":"caveat"}],"id":"V-71935","impact":0.5,"refs":[{"ref":[]}],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71935.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000078-GPOS-00046","gid":"V-71935","rid":"SV-86559r2_rule","stig_id":"RHEL-07-010280","fix_id":"F-78287r1_fix","cci":["CCI-000205"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\n\tthat passwords are a minimum of 24 characters in length.","waiver_data":{}},{"code":"control \"V-71937\" do\n title \"The Red Hat Enterprise Linux operating system must not have accounts\nconfigured with blank or null passwords.\"\n desc \"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n To verify that null passwords cannot be used, run the following command:\n\n # grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n If this produces any output, it may be possible to log on with accounts\nwith empty passwords.\n\n If null passwords can be used, this is a finding.\n \"\n desc \"fix\", \"\n If an account is configured for password authentication but does not have\nan assigned password, it may be possible to log on to the account without\nauthenticating.\n\n Remove any instances of the \\\"nullok\\\" option in \\\"/etc/pam.d/system-auth\\\"\nand \\\"/etc/pam.d/password-auth\\\" to prevent logons with empty passwords.\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71937\"\n tag rid: \"SV-86561r3_rule\"\n tag stig_id: \"RHEL-07-010290\"\n tag fix_id: \"F-78289r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n # Fetch all files under /etc/pam.d excluding '*-ac' files\n # but including symlinks\n pam_file_list = command('find /etc/pam.d ! -name \\'*-ac\\' -a \\( -type f -o -type l \\)').stdout.strip.split\n\n pam_file_list.each do |pam_file|\n describe pam(pam_file) do\n its('lines') { should match_pam_rule('.* .* pam_unix.so').all_without_args('nullok') }\n end\n end\nend\n","desc":"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.","descriptions":[{"data":"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.","label":"default"},{"data":"","label":"rationale"},{"data":"To verify that null passwords cannot be used, run the following command:\n\n # grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n If this produces any output, it may be possible to log on with accounts\nwith empty passwords.\n\n If null passwords can be used, this is a finding.","label":"check"},{"data":"If an account is configured for password authentication but does not have\nan assigned password, it may be possible to log on to the account without\nauthenticating.\n\n Remove any instances of the \"nullok\" option in \"/etc/pam.d/system-auth\"\nand \"/etc/pam.d/password-auth\" to prevent logons with empty passwords.\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71937","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71937.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71937","rid":"SV-86561r3_rule","stig_id":"RHEL-07-010290","fix_id":"F-78289r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have accounts\nconfigured with blank or null passwords.","waiver_data":{}},{"code":"control \"V-71939\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using an empty password.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n To determine how the SSH daemon's \\\"PermitEmptyPasswords\\\" option is set,\nrun the following command:\n\n # grep -i PermitEmptyPasswords /etc/ssh/sshd_config\n PermitEmptyPasswords no\n\n If no line, a commented line, or a line indicating the value \\\"no\\\" is\nreturned, the required value is set.\n\n If the required value is not set, this is a finding.\n \"\n desc \"fix\", \"\n To explicitly disallow remote logon from accounts with empty passwords, add\nor correct the following line in \\\"/etc/ssh/sshd_config\\\":\n\n PermitEmptyPasswords no\n\n The SSH service must be restarted for changes to take effect. Any accounts\nwith empty passwords should be disabled immediately, and PAM configuration\nshould prevent users from being able to assign themselves empty passwords.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000106-GPOS-00053\"\n tag gid: \"V-71939\"\n tag rid: \"SV-86563r3_rule\"\n tag stig_id: \"RHEL-07-010300\"\n tag fix_id: \"F-78291r2_fix\"\n tag cci: [\"CCI-000766\"]\n tag nist: [\"IA-2 (2)\"]\n\n describe sshd_config do\n its('PermitEmptyPasswords') { should eq 'no' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"To determine how the SSH daemon's \"PermitEmptyPasswords\" option is set,\nrun the following command:\n\n # grep -i PermitEmptyPasswords /etc/ssh/sshd_config\n PermitEmptyPasswords no\n\n If no line, a commented line, or a line indicating the value \"no\" is\nreturned, the required value is set.\n\n If the required value is not set, this is a finding.","label":"check"},{"data":"To explicitly disallow remote logon from accounts with empty passwords, add\nor correct the following line in \"/etc/ssh/sshd_config\":\n\n PermitEmptyPasswords no\n\n The SSH service must be restarted for changes to take effect. Any accounts\nwith empty passwords should be disabled immediately, and PAM configuration\nshould prevent users from being able to assign themselves empty passwords.","label":"fix"}],"id":"V-71939","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71939.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000106-GPOS-00053","gid":"V-71939","rid":"SV-86563r3_rule","stig_id":"RHEL-07-010300","fix_id":"F-78291r2_fix","cci":["CCI-000766"],"nist":["IA-2 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using an empty password.","waiver_data":{}},{"code":"control \"V-71941\" do\n title \"The Red Hat Enterprise Linux operating system must disable account\nidentifiers (individuals, groups, roles, and devices) if the password expires.\"\n desc \"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system disables account identifiers (individuals,\ngroups, roles, and devices) after the password expires with the following\ncommand:\n\n # grep -i inactive /etc/default/useradd\n INACTIVE=0\n\n If the value is not set to \\\"0\\\", is commented out, or is not defined, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable account identifiers (individuals,\ngroups, roles, and devices) after the password expires.\n\n Add the following line to \\\"/etc/default/useradd\\\" (or modify the line to\nhave the required value):\n\n INACTIVE=0\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000118-GPOS-00060\"\n tag gid: \"V-71941\"\n tag rid: \"SV-86565r2_rule\"\n tag stig_id: \"RHEL-07-010310\"\n tag fix_id: \"F-78293r1_fix\"\n tag cci: [\"CCI-000795\"]\n tag nist: [\"IA-4 e\"]\n\n days_of_inactivity = input('days_of_inactivity')\n\n unless command(\"grep 'pam_unix.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'optional'\").stdout.empty? && command(\"grep 'pam_permit.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'required'\").stdout.empty?\n impact 0.0\n describe \"The system is not using password for authentication\" do\n skip \"The system is not using password for authentication, this control is Not Applicable.\"\n end\n else\n describe parse_config_file(\"/etc/default/useradd\") do\n its('INACTIVE') { should cmp >= 0 }\n its('INACTIVE') { should cmp <= days_of_inactivity }\n end\n end\n\nend\n","desc":"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.","descriptions":[{"data":"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system disables account identifiers (individuals,\ngroups, roles, and devices) after the password expires with the following\ncommand:\n\n # grep -i inactive /etc/default/useradd\n INACTIVE=0\n\n If the value is not set to \"0\", is commented out, or is not defined, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable account identifiers (individuals,\ngroups, roles, and devices) after the password expires.\n\n Add the following line to \"/etc/default/useradd\" (or modify the line to\nhave the required value):\n\n INACTIVE=0","label":"fix"}],"id":"V-71941","impact":0.5,"refs":[],"results":[],"source_location":{"line":1,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71941.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000118-GPOS-00060","gid":"V-71941","rid":"SV-86565r2_rule","stig_id":"RHEL-07-010310","fix_id":"F-78293r1_fix","cci":["CCI-000795"],"nist":["IA-4 e"]},"title":"The Red Hat Enterprise Linux operating system must disable account\nidentifiers (individuals, groups, roles, and devices) if the password expires.","waiver_data":{}},{"code":" control 'V-71943' do\n\t\t\ttitle \"The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 60 minutes after 20 unsuccessful logon attempts within a 120-minute timeframe.\"\n\t\t\tdesc 'caveat', 'The project2 needs to set this to 20 since we have an approved risk-based decision on 2/1/2022 allowing it'\n\t\t\tdesc 'check', \"\n\t\t\t\tCheck that the system locks an account for a minimum of 60 minutes after\n\t\t20 unsuccessful logon attempts within a period of 120 minutes with the\n\t\tfollowing command:\n\t\t\t\t# grep pam_faillock.so /etc/pam.d/password-auth\n\t\t\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\n\t\tfail_interval=7200 unlock_time=3600\n\t\t\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\n\t\tfail_interval=7200 unlock_time=3600\n\t\t\t\taccount required pam_faillock.so\n\t\t\t\tIf the \\\"deny\\\" parameter is set to \\\"0\\\" or a value less than \\\"20\\\" on\n\t\tboth \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module, or is missing from\n\t\tthese lines, this is a finding.\n\t\t\t\tIf the \\\"even_deny_root\\\" parameter is not set on both \\\"auth\\\" lines with\n\t\tthe \\\"pam_faillock.so\\\" module, or is missing from these lines, this is a\n\t\tfinding.\n\t\t\t\tIf the \\\"fail_interval\\\" parameter is set to \\\"0\\\" or is set to a value\n\t\tless than \\\"7200\\\" on both \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module,\n\t\tor is missing from these lines, this is a finding.\n\t\t\t\tIf the \\\"unlock_time\\\" parameter is not set to \\\"0\\\", \\\"never\\\", or is set\n\t\tto a value less than \\\"3600\\\" on both \\\"auth\\\" lines with the\n\t\t\\\"pam_faillock.so\\\" module, or is missing from these lines, this is a finding.\n\t\t\t\tNote: The maximum configurable value for \\\"unlock_time\\\" is \\\"604800\\\".\n\t\t\t\tIf any line referencing the \\\"pam_faillock.so\\\" module is commented out,\n\t\tthis is a finding.\n\t\t\t\t# grep pam_faillock.so /etc/pam.d/system-auth\n\t\t\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\n\t\tfail_interval=7200 unlock_time=3600\n\t\t\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\n\t\tfail_interval=7200 unlock_time=3600\n\t\t\t\taccount required pam_faillock.so\n\t\t\t\tIf the \\\"deny\\\" parameter is set to \\\"0\\\" or a value less than \\\"20\\\" on\n\t\tboth \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module, or is missing from\n\t\tthese lines, this is a finding.\n\t\t\t\tIf the \\\"even_deny_root\\\" parameter is not set on both \\\"auth\\\" lines with\n\t\tthe \\\"pam_faillock.so\\\" module, or is missing from these lines, this is a\n\t\tfinding.\n\t\t\t\tIf the \\\"fail_interval\\\" parameter is set to \\\"0\\\" or is set to a value\n\t\tless than \\\"7200\\\" on both \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module,\n\t\tor is missing from these lines, this is a finding.\n\t\t\t\tIf the \\\"unlock_time\\\" parameter is not set to \\\"0\\\", \\\"never\\\", or is set\n\t\tto a value less than \\\"3600\\\" on both \\\"auth\\\" lines with the\n\t\t\\\"pam_faillock.so\\\" module or is missing from these lines, this is a finding.\n\t\t\t\tNote: The maximum configurable value for \\\"unlock_time\\\" is \\\"604800\\\".\n\t\t\t\tIf any line referencing the \\\"pam_faillock.so\\\" module is commented out,\n\t\tthis is a finding.\n\t\t\t\"\n\t\t\tdesc 'fix', \"\n\t\t\t\tConfigure the ACME operating system to lock an account for 60 minutes\n\t\twhen 20 unsuccessful logon attempts in 120 minutes are made.\n\t\t\t\tModify the first three lines of the auth section and the first line of the\n\t\taccount section of the \\\"/etc/pam.d/system-auth\\\" and\n\t\t\\\"/etc/pam.d/password-auth\\\" files to match the following lines:\n\t\t\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\n\t\tfail_interval=7200 unlock_time=3600\n\t\t\t\tauth sufficient pam_unix.so try_first_pass\n\t\t\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\n\t\tfail_interval=7200 unlock_time=3600\n\t\t\t\taccount required pam_faillock.so\n\t\t\t\tNote: Manual changes to the listed files may be overwritten by the\n\t\t\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\n\t\tthe configurations listed in this requirement.\n\t\t\t\"\n\tend\n","desc":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as\nbrute-forcing, is reduced. Limits are imposed by locking the account.","descriptions":[{"data":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as\nbrute-forcing, is reduced. Limits are imposed by locking the account.","label":"default"},{"data":"","label":"rationale"},{"data":"Check that the system locks an account for a minimum of 60 minutes after\n20 unsuccessful logon attempts within a period of 120 minutes with the\nfollowing command:\n\t\t# grep pam_faillock.so /etc/pam.d/password-auth\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tIf the \"deny\" parameter is set to \"0\" or a value less than \"20\" on\nboth \"auth\" lines with the \"pam_faillock.so\" module, or is missing from\nthese lines, this is a finding.\n\t\tIf the \"even_deny_root\" parameter is not set on both \"auth\" lines with\nthe \"pam_faillock.so\" module, or is missing from these lines, this is a\nfinding.\n\t\tIf the \"fail_interval\" parameter is set to \"0\" or is set to a value\nless than \"7200\" on both \"auth\" lines with the \"pam_faillock.so\" module,\nor is missing from these lines, this is a finding.\n\t\tIf the \"unlock_time\" parameter is not set to \"0\", \"never\", or is set\nto a value less than \"3600\" on both \"auth\" lines with the\n\"pam_faillock.so\" module, or is missing from these lines, this is a finding.\n\t\tNote: The maximum configurable value for \"unlock_time\" is \"604800\".\n\t\tIf any line referencing the \"pam_faillock.so\" module is commented out,\nthis is a finding.\n\t\t# grep pam_faillock.so /etc/pam.d/system-auth\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tIf the \"deny\" parameter is set to \"0\" or a value less than \"20\" on\nboth \"auth\" lines with the \"pam_faillock.so\" module, or is missing from\nthese lines, this is a finding.\n\t\tIf the \"even_deny_root\" parameter is not set on both \"auth\" lines with\nthe \"pam_faillock.so\" module, or is missing from these lines, this is a\nfinding.\n\t\tIf the \"fail_interval\" parameter is set to \"0\" or is set to a value\nless than \"7200\" on both \"auth\" lines with the \"pam_faillock.so\" module,\nor is missing from these lines, this is a finding.\n\t\tIf the \"unlock_time\" parameter is not set to \"0\", \"never\", or is set\nto a value less than \"3600\" on both \"auth\" lines with the\n\"pam_faillock.so\" module or is missing from these lines, this is a finding.\n\t\tNote: The maximum configurable value for \"unlock_time\" is \"604800\".\n\t\tIf any line referencing the \"pam_faillock.so\" module is commented out,\nthis is a finding.","label":"check"},{"data":"Configure the ACME operating system to lock an account for 60 minutes\nwhen 20 unsuccessful logon attempts in 120 minutes are made.\n\t\tModify the first three lines of the auth section and the first line of the\naccount section of the \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" files to match the following lines:\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth sufficient pam_unix.so try_first_pass\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tNote: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"},{"data":"The project2 needs to set this to 20 since we have an approved risk-based decision on 2/1/2022 allowing it","label":"caveat"}],"id":"V-71943","impact":0.5,"refs":[{"ref":[]},{"ref":[]}],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71943.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000329-GPOS-00128","satisfies":["SRG-OS-000329-GPOS-00128","SRG-OS-000021-GPOS-00005"],"gid":"V-71943","rid":"SV-86567r5_rule","stig_id":"RHEL-07-010320","fix_id":"F-78295r5_fix","cci":["CCI-000044","CCI-002236","CCI-002237","CCI-002238"],"nist":["AC-7 a","AC-7 b","AC-7 b","AC-7 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 60 minutes after 20 unsuccessful logon attempts within a 120-minute timeframe.","waiver_data":{}},{"code":"control \"V-71945\" do\n title \"The Red Hat Enterprise Linux operating system must lock the associated\naccount after three unsuccessful root logon attempts are made within a\n15-minute period.\"\n desc \"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system automatically locks the root account until it\nis released by an administrator when three unsuccessful logon attempts in 15\nminutes are made.\n\n # grep pam_faillock.so /etc/pam.d/password-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \\\"even_deny_root\\\" setting is not defined on both lines with the\n\\\"pam_faillock.so\\\" module, is commented out, or is missing from a line, this\nis a finding.\n\n # grep pam_faillock.so /etc/pam.d/system-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \\\"even_deny_root\\\" setting is not defined on both lines with the\n\\\"pam_faillock.so\\\" module, is commented out, or is missing from a line, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to lock automatically the root account until\nthe locked account is released by an administrator when three unsuccessful\nlogon attempts in 15 minutes are made.\n\n Modify the first three lines of the auth section and the first line of the\naccount section of the \\\"/etc/pam.d/system-auth\\\" and\n\\\"/etc/pam.d/password-auth\\\" files to match the following lines:\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth sufficient pam_unix.so try_first_pass\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000329-GPOS-00128\"\n tag satisfies: [\"SRG-OS-000329-GPOS-00128\", \"SRG-OS-000021-GPOS-00005\"]\n tag gid: \"V-71945\"\n tag rid: \"SV-86569r4_rule\"\n tag stig_id: \"RHEL-07-010330\"\n tag fix_id: \"F-78297r3_fix\"\n tag cci: [\"CCI-002238\"]\n tag nist: [\"AC-7 b\"]\n\n required_lines = [\n 'auth required pam_faillock.so even_deny_root',\n 'auth sufficient pam_unix.so try_first_pass',\n 'auth [default=die] pam_faillock.so even_deny_root'\n ]\n\n describe pam('/etc/pam.d/password-auth') do\n its('lines') { should match_pam_rules(required_lines) }\n its('lines') { should match_pam_rule('auth .* pam_faillock.so (preauth|authfail)').all_with_args('even_deny_root') }\n end\n\n describe pam('/etc/pam.d/system-auth') do\n its('lines') { should match_pam_rules(required_lines) }\n its('lines') { should match_pam_rule('auth .* pam_faillock.so (preauth|authfail)').all_with_args('even_deny_root') }\n end\nend\n","desc":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.","descriptions":[{"data":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically locks the root account until it\nis released by an administrator when three unsuccessful logon attempts in 15\nminutes are made.\n\n # grep pam_faillock.so /etc/pam.d/password-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \"even_deny_root\" setting is not defined on both lines with the\n\"pam_faillock.so\" module, is commented out, or is missing from a line, this\nis a finding.\n\n # grep pam_faillock.so /etc/pam.d/system-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \"even_deny_root\" setting is not defined on both lines with the\n\"pam_faillock.so\" module, is commented out, or is missing from a line, this\nis a finding.","label":"check"},{"data":"Configure the operating system to lock automatically the root account until\nthe locked account is released by an administrator when three unsuccessful\nlogon attempts in 15 minutes are made.\n\n Modify the first three lines of the auth section and the first line of the\naccount section of the \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" files to match the following lines:\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth sufficient pam_unix.so try_first_pass\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71945","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71945.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000329-GPOS-00128","satisfies":["SRG-OS-000329-GPOS-00128","SRG-OS-000021-GPOS-00005"],"gid":"V-71945","rid":"SV-86569r4_rule","stig_id":"RHEL-07-010330","fix_id":"F-78297r3_fix","cci":["CCI-002238"],"nist":["AC-7 b"]},"title":"The Red Hat Enterprise Linux operating system must lock the associated\naccount after three unsuccessful root logon attempts are made within a\n15-minute period.","waiver_data":{}},{"code":"control \"V-71947\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat users must provide a password for privilege escalation.\"\n desc \"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system requires users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" and \\\"/etc/sudoers.d/*\\\"\nfiles with the following command:\n\n # grep -i nopasswd /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \\\"NOPASSWD\\\" tag, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" file with the following\ncommand:\n # visudo\n\n Remove any occurrences of \\\"NOPASSWD\\\" tags in the file.\n\n Check the configuration of the /etc/sudoers.d/* files with the following\ncommand:\n # grep -i nopasswd /etc/sudoers.d/*\n\n Remove any occurrences of \\\"NOPASSWD\\\" tags in the file.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000373-GPOS-00156\"\n tag satisfies: [\"SRG-OS-000373-GPOS-00156\", \"SRG-OS-000373-GPOS-00157\",\n\"SRG-OS-000373-GPOS-00158\"]\n tag gid: \"V-71947\"\n tag rid: \"SV-86571r3_rule\"\n tag stig_id: \"RHEL-07-010340\"\n tag fix_id: \"F-78299r2_fix\"\n tag cci: [\"CCI-002038\"]\n tag nist: [\"IA-11\"]\n\n processed = []\n to_process = ['/etc/sudoers', '/etc/sudoers.d']\n\n while !to_process.empty?\n in_process = to_process.pop\n next if processed.include? in_process\n processed.push in_process\n\n if file(in_process).directory?\n to_process.concat(\n command(\"find #{in_process} -maxdepth 1 -mindepth 1\").\n stdout.strip.split(\"\\n\").\n select { |f| file(f).file? }\n )\n elsif file(in_process).file?\n to_process.concat(\n command(\"grep -E '#include\\\\s+' #{in_process} | sed 's/.*#include[[:space:]]*//g'\").\n stdout.strip.split(\"\\n\").\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n select { |f| file(f).exist? }\n )\n to_process.concat(\n command(\"grep -E '#includedir\\\\s+' #{in_process} | sed 's/.*#includedir[[:space:]]*//g'\").\n stdout.strip.split(\"\\n\").\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n select { |f| file(f).exist? }\n )\n end\n end\n\n sudoers = processed.select { |f| file(f).file? }\n\n sudoers.each do |sudoer|\n sudo_content = file(sudoer).content.strip.split(\"\\n\")\n nopasswd_lines = sudo_content.select { |l| l.match?(/^[^#].*NOPASSWD/) }\n describe \"#{sudoer} rules containing NOPASSWD\" do\n subject { nopasswd_lines }\n it { should be_empty }\n end\n end\nend\n","desc":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.","descriptions":[{"data":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system requires users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" and \"/etc/sudoers.d/*\"\nfiles with the following command:\n\n # grep -i nopasswd /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \"NOPASSWD\" tag, this is a finding.","label":"check"},{"data":"Configure the operating system to require users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" file with the following\ncommand:\n # visudo\n\n Remove any occurrences of \"NOPASSWD\" tags in the file.\n\n Check the configuration of the /etc/sudoers.d/* files with the following\ncommand:\n # grep -i nopasswd /etc/sudoers.d/*\n\n Remove any occurrences of \"NOPASSWD\" tags in the file.","label":"fix"}],"id":"V-71947","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71947.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000373-GPOS-00156","satisfies":["SRG-OS-000373-GPOS-00156","SRG-OS-000373-GPOS-00157","SRG-OS-000373-GPOS-00158"],"gid":"V-71947","rid":"SV-86571r3_rule","stig_id":"RHEL-07-010340","fix_id":"F-78299r2_fix","cci":["CCI-002038"],"nist":["IA-11"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat users must provide a password for privilege escalation.","waiver_data":{}},{"code":"control \"V-71949\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat users must re-authenticate for privilege escalation.\"\n desc \"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system requires users to reauthenticate for privilege\nescalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" and \\\"/etc/sudoers.d/*\\\"\nfiles with the following command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \\\"!authenticate\\\" tag, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to require users to reauthenticate for\nprivilege escalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" file with the following\ncommand:\n\n # visudo\n Remove any occurrences of \\\"!authenticate\\\" tags in the file.\n\n Check the configuration of the \\\"/etc/sudoers.d/*\\\" files with the\nfollowing command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n Remove any occurrences of \\\"!authenticate\\\" tags in the file(s).\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000373-GPOS-00156\"\n tag satisfies: [\"SRG-OS-000373-GPOS-00156\", \"SRG-OS-000373-GPOS-00157\",\n\"SRG-OS-000373-GPOS-00158\"]\n tag gid: \"V-71949\"\n tag rid: \"SV-86573r3_rule\"\n tag stig_id: \"RHEL-07-010350\"\n tag fix_id: \"F-78301r3_fix\"\n tag cci: [\"CCI-002038\"]\n tag nist: [\"IA-11\"]\n\n describe command(\"grep -ir authenticate /etc/sudoers /etc/sudoers.d/*\") do\n its('stdout') { should_not match %r{!authenticate} }\n end\nend\n","desc":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.","descriptions":[{"data":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system requires users to reauthenticate for privilege\nescalation.\n\n Check the configuration of the \"/etc/sudoers\" and \"/etc/sudoers.d/*\"\nfiles with the following command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \"!authenticate\" tag, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to require users to reauthenticate for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" file with the following\ncommand:\n\n # visudo\n Remove any occurrences of \"!authenticate\" tags in the file.\n\n Check the configuration of the \"/etc/sudoers.d/*\" files with the\nfollowing command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n Remove any occurrences of \"!authenticate\" tags in the file(s).","label":"fix"}],"id":"V-71949","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71949.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000373-GPOS-00156","satisfies":["SRG-OS-000373-GPOS-00156","SRG-OS-000373-GPOS-00157","SRG-OS-000373-GPOS-00158"],"gid":"V-71949","rid":"SV-86573r3_rule","stig_id":"RHEL-07-010350","fix_id":"F-78301r3_fix","cci":["CCI-002038"],"nist":["IA-11"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat users must re-authenticate for privilege escalation.","waiver_data":{}},{"code":"control \"V-71951\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the delay between logon prompts following a failed console logon attempt\nis at least four seconds.\"\n desc \"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enforces a delay of at least four seconds\nbetween console logon prompts following a failed logon attempt.\n\n Check the value of the \\\"fail_delay\\\" parameter in the \\\"/etc/login.defs\\\"\nfile with the following command:\n\n # grep -i fail_delay /etc/login.defs\n FAIL_DELAY 4\n\n If the value of \\\"FAIL_DELAY\\\" is not set to \\\"4\\\" or greater, or the line\nis commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce a delay of at least four seconds\nbetween logon prompts following a failed console logon attempt.\n\n Modify the \\\"/etc/login.defs\\\" file to set the \\\"FAIL_DELAY\\\" parameter to\n\\\"4\\\" or greater:\n\n FAIL_DELAY 4\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00226\"\n tag gid: \"V-71951\"\n tag rid: \"SV-86575r2_rule\"\n tag stig_id: \"RHEL-07-010430\"\n tag fix_id: \"F-78303r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe login_defs do\n its('FAIL_DELAY.to_i') { should cmp >= 4 }\n end\nend\n","desc":"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.","descriptions":[{"data":"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces a delay of at least four seconds\nbetween console logon prompts following a failed logon attempt.\n\n Check the value of the \"fail_delay\" parameter in the \"/etc/login.defs\"\nfile with the following command:\n\n # grep -i fail_delay /etc/login.defs\n FAIL_DELAY 4\n\n If the value of \"FAIL_DELAY\" is not set to \"4\" or greater, or the line\nis commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce a delay of at least four seconds\nbetween logon prompts following a failed console logon attempt.\n\n Modify the \"/etc/login.defs\" file to set the \"FAIL_DELAY\" parameter to\n\"4\" or greater:\n\n FAIL_DELAY 4","label":"fix"}],"id":"V-71951","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71951.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00226","gid":"V-71951","rid":"SV-86575r2_rule","stig_id":"RHEL-07-010430","fix_id":"F-78303r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the delay between logon prompts following a failed console logon attempt\nis at least four seconds.","waiver_data":{}},{"code":"control \"V-71953\" do\n title \"The Red Hat Enterprise Linux operating system must not allow an\nunattended or automatic logon to the system via a graphical user interface.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow an unattended or automatic logon\nto the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \\\"AutomaticLoginEnable\\\" in the\n\\\"/etc/gdm/custom.conf\\\" file with the following command:\n\n # grep -i automaticloginenable /etc/gdm/custom.conf\n AutomaticLoginEnable=false\n\n If the value of \\\"AutomaticLoginEnable\\\" is not set to \\\"false\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow an unattended or automatic\nlogon to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \\\"AutomaticLoginEnable\\\" parameter in the\n[daemon] section of the \\\"/etc/gdm/custom.conf\\\" file to \\\"false\\\":\n\n [daemon]\n AutomaticLoginEnable=false\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71953\"\n tag rid: \"SV-86577r2_rule\"\n tag stig_id: \"RHEL-07-010440\"\n tag fix_id: \"F-78305r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n custom_conf = '/etc/gdm/custom.conf'\n\n if package('gdm').installed?\n if ((f = file(custom_conf)).exist?)\n describe ini(custom_conf) do\n its('daemon.AutomaticLoginEnable') { cmp false }\n end\n else\n describe f do\n it { should exist }\n end\n end\n else\n impact 0.0\n describe \"The system does not have GDM installed\" do\n skip \"The system does not have GDM installed, this requirement is Not Applicable.\"\n end\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow an unattended or automatic logon\nto the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \"AutomaticLoginEnable\" in the\n\"/etc/gdm/custom.conf\" file with the following command:\n\n # grep -i automaticloginenable /etc/gdm/custom.conf\n AutomaticLoginEnable=false\n\n If the value of \"AutomaticLoginEnable\" is not set to \"false\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to not allow an unattended or automatic\nlogon to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \"AutomaticLoginEnable\" parameter in the\n[daemon] section of the \"/etc/gdm/custom.conf\" file to \"false\":\n\n [daemon]\n AutomaticLoginEnable=false","label":"fix"}],"id":"V-71953","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71953.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71953","rid":"SV-86577r2_rule","stig_id":"RHEL-07-010440","fix_id":"F-78305r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow an\nunattended or automatic logon to the system via a graphical user interface.","waiver_data":{}},{"code":"control \"V-71955\" do\n title \"The Red Hat Enterprise Linux operating system must not allow an\nunrestricted logon to the system.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow an unrestricted logon to the\nsystem via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \\\"TimedLoginEnable\\\" parameter in\n\\\"/etc/gdm/custom.conf\\\" file with the following command:\n\n # grep -i timedloginenable /etc/gdm/custom.conf\n TimedLoginEnable=false\n\n If the value of \\\"TimedLoginEnable\\\" is not set to \\\"false\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow an unrestricted account to log\non to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \\\"TimedLoginEnable\\\" parameter in the [daemon]\nsection of the \\\"/etc/gdm/custom.conf\\\" file to \\\"false\\\":\n\n [daemon]\n TimedLoginEnable=false\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71955\"\n tag rid: \"SV-86579r3_rule\"\n tag stig_id: \"RHEL-07-010450\"\n tag fix_id: \"F-78307r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n custom_conf = '/etc/gdm/custom.conf'\n\n if package('gdm').installed?\n impact 0.7\n if ((f = file(custom_conf)).exist?)\n describe ini(custom_conf) do\n its('daemon.TimedLoginEnable') { cmp false }\n end\n else\n describe f do\n it { should exist }\n end\n end\n else\n impact 0.0\n describe \"The system does not have GDM installed\" do\n skip \"The system does not have GDM installed, this requirement is Not Applicable.\"\n end\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow an unrestricted logon to the\nsystem via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \"TimedLoginEnable\" parameter in\n\"/etc/gdm/custom.conf\" file with the following command:\n\n # grep -i timedloginenable /etc/gdm/custom.conf\n TimedLoginEnable=false\n\n If the value of \"TimedLoginEnable\" is not set to \"false\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to not allow an unrestricted account to log\non to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \"TimedLoginEnable\" parameter in the [daemon]\nsection of the \"/etc/gdm/custom.conf\" file to \"false\":\n\n [daemon]\n TimedLoginEnable=false","label":"fix"}],"id":"V-71955","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71955.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71955","rid":"SV-86579r3_rule","stig_id":"RHEL-07-010450","fix_id":"F-78307r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow an\nunrestricted logon to the system.","waiver_data":{}},{"code":"control \"V-71957\" do\n title \"The Red Hat Enterprise Linux operating system must not allow users to\noverride SSH environment variables.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow users to override environment\nvariables to the SSH daemon.\n\n Check for the value of the \\\"PermitUserEnvironment\\\" keyword with the\nfollowing command:\n\n # grep -i permituserenvironment /etc/ssh/sshd_config\n PermitUserEnvironment no\n\n If the \\\"PermitUserEnvironment\\\" keyword is not set to \\\"no\\\", is missing,\nor is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow users to override environment\nvariables to the SSH daemon.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for\n\\\"PermitUserEnvironment\\\" keyword and set the value to \\\"no\\\":\n\n PermitUserEnvironment no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71957\"\n tag rid: \"SV-86581r3_rule\"\n tag stig_id: \"RHEL-07-010460\"\n tag fix_id: \"F-78309r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('PermitUserEnvironment') { should eq 'no' }\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow users to override environment\nvariables to the SSH daemon.\n\n Check for the value of the \"PermitUserEnvironment\" keyword with the\nfollowing command:\n\n # grep -i permituserenvironment /etc/ssh/sshd_config\n PermitUserEnvironment no\n\n If the \"PermitUserEnvironment\" keyword is not set to \"no\", is missing,\nor is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to not allow users to override environment\nvariables to the SSH daemon.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for\n\"PermitUserEnvironment\" keyword and set the value to \"no\":\n\n PermitUserEnvironment no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-71957","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71957.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71957","rid":"SV-86581r3_rule","stig_id":"RHEL-07-010460","fix_id":"F-78309r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow users to\noverride SSH environment variables.","waiver_data":{}},{"code":"control \"V-71959\" do\n title \"The Red Hat Enterprise Linux operating system must not allow a\nnon-certificate trusted host SSH logon to the system.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow a non-certificate trusted host\nSSH logon to the system.\n\n Check for the value of the \\\"HostbasedAuthentication\\\" keyword with the\nfollowing command:\n\n # grep -i hostbasedauthentication /etc/ssh/sshd_config\n HostbasedAuthentication no\n\n If the \\\"HostbasedAuthentication\\\" keyword is not set to \\\"no\\\", is\nmissing, or is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow a non-certificate trusted host\nSSH logon to the system.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for\n\\\"HostbasedAuthentication\\\" keyword and set the value to \\\"no\\\":\n\n HostbasedAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71959\"\n tag rid: \"SV-86583r3_rule\"\n tag stig_id: \"RHEL-07-010470\"\n tag fix_id: \"F-78311r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('HostbasedAuthentication') { should eq 'no' }\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow a non-certificate trusted host\nSSH logon to the system.\n\n Check for the value of the \"HostbasedAuthentication\" keyword with the\nfollowing command:\n\n # grep -i hostbasedauthentication /etc/ssh/sshd_config\n HostbasedAuthentication no\n\n If the \"HostbasedAuthentication\" keyword is not set to \"no\", is\nmissing, or is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to not allow a non-certificate trusted host\nSSH logon to the system.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for\n\"HostbasedAuthentication\" keyword and set the value to \"no\":\n\n HostbasedAuthentication no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-71959","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71959.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71959","rid":"SV-86583r3_rule","stig_id":"RHEL-07-010470","fix_id":"F-78311r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow a\nnon-certificate trusted host SSH logon to the system.","waiver_data":{}},{"code":"control \"V-71961\" do\n title \"Red Hat Enterprise Linux operating systems prior to version 7.2 with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use UEFI, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -i password_pbkdf2 /boot/grub2/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \\\"password_pbkdf2\\\", this is\na finding.\n\n If the \\\"superusers-account\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \\\"/etc/grub.d/40_custom\\\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\\\"root\\\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \\\"grub.conf\\\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/grub2/grub.cfg\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-71961\"\n tag rid: \"SV-86585r6_rule\"\n tag stig_id: \"RHEL-07-010480\"\n tag fix_id: \"F-78313r3_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n grub_superuser = input('grub_superuser')\n grub_user_boot_files = input('grub_user_boot_files')\n grub_main_cfg = input('grub_main_cfg')\n\n grub_main_content = file(grub_main_cfg).content\n\n if file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running UEFI\" do\n skip \"The System is running UEFI, this control is Not Applicable.\"\n end\n else\n if os[:release] >= \"7.2\"\n impact 0.0\n describe \"System running version of RHEL that is equal to or newer than 7.2\" do\n skip \"The System is running version #{os[:release]} of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n # Check if any additional superusers are set\n pattern = %r{\\s*set superusers=\\\"(\\w+)\\\"}i\n matches = grub_main_content.match(pattern)\n superusers = matches.nil? ? [] : matches.captures\n describe \"There must be only one grub2 superuser, and it must have the value #{grub_superuser}\" do\n subject { superusers }\n its('length') { should cmp 1 }\n its('first') { should cmp grub_superuser }\n end\n\n # Need each password entry that has the superuser\n pattern = %r{(.*)\\s#{grub_superuser}\\s}i\n matches = grub_main_content.match(pattern)\n password_entries = matches.nil? ? [] : matches.captures\n # Each of the entries should start with password_pbkdf2\n describe 'The grub2 superuser password entry must begin with \\'password_pbkdf2\\'' do\n subject { password_entries }\n its('length') { is_expected.to be >= 1}\n password_entries.each do |entry|\n subject { entry }\n it { should include 'password_pbkdf2'}\n end\n end\n\n # Get lines such as 'password_pbkdf2 root ${ENV}'\n pattern = %r{password_pbkdf2\\s#{grub_superuser}\\s(\\${\\w+})}i\n matches = grub_main_content.match(pattern)\n env_vars = matches.nil? ? [] : matches.captures\n if env_vars.length > 0\n # If there is an environment variable in the configuration file check that it is set with correct values by looking\n # in user.cfg files.\n env_vars = env_vars.map { |env_var| env_var.gsub(/[${}]/, '') }\n present_user_boot_files = grub_user_boot_files.select { |user_boot_file| file(user_boot_file).exist? }\n describe 'grub2 user configuration files for the superuser should be present if they set an environment variable' do\n subject { present_user_boot_files }\n its('length') { is_expected.to be >= 1 }\n present_user_boot_files.each do |user_boot_file|\n env_vars.each do |env_var|\n describe \"#{user_boot_file} should set #{env_var} to a pbkdf2 value\" do\n subject { file(user_boot_file) }\n its('content') { should match %r{^#{env_var}=grub.pbkdf2}i }\n end\n end\n end\n end\n else\n # If there are no environment variable set, look for pbkdf2 after the superuser name\n pattern = %r{password_pbkdf2\\s#{grub_superuser}\\sgrub\\.pbkdf2}i\n describe 'The grub2 superuser account password should be encrypted with pbkdf2.' do\n subject { grub_main_content }\n it { should match pattern }\n end\n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use UEFI, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -i password_pbkdf2 /boot/grub2/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \"password_pbkdf2\", this is\na finding.\n\n If the \"superusers-account\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \"/etc/grub.d/40_custom\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\"root\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \"grub.conf\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/grub2/grub.cfg","label":"fix"}],"id":"V-71961","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71961.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-71961","rid":"SV-86585r6_rule","stig_id":"RHEL-07-010480","fix_id":"F-78313r3_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems prior to version 7.2 with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-71963\" do\n title \"Red Hat Enterprise Linux operating systems prior to version 7.2 using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use BIOS, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -i password /boot/efi/EFI/redhat/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \\\"password_pbkdf2\\\", this is\na finding.\n\n If the \\\"superusers-account\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \\\"/etc/grub.d/40_custom\\\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\\\"root\\\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \\\"grub.conf\\\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-71963\"\n tag rid: \"SV-86587r4_rule\"\n tag stig_id: \"RHEL-07-010490\"\n tag fix_id: \"F-78315r3_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n os_minor_version = os().release.split('.')[1].to_i\n\n efi_superusers = os_minor_version < 2 ? input('efi_superusers') : ['root']\n efi_superusers.push('root') if !efi_superusers.include?('root')\n efi_main_cfg = \"/boot/efi/EFI/#{os().name}/grub.cfg\"\n\n unless file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running BIOS\" do\n skip \"The System is running BIOS, this control is Not Applicable.\"\n end\n else\n if os[:release] < \"7.2\"\n impact 0.0\n describe \"System running version of RHEL prior to 7.2\" do\n skip \"The System is running an outdated version of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n efi_superusers.each do |user|\n describe file(efi_main_cfg) do\n its('content') { should match %r{^\\s*password_pbkdf2\\s+#{user} } }\n end\n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use BIOS, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -i password /boot/efi/EFI/redhat/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \"password_pbkdf2\", this is\na finding.\n\n If the \"superusers-account\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \"/etc/grub.d/40_custom\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\"root\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \"grub.conf\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg","label":"fix"}],"id":"V-71963","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71963.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-71963","rid":"SV-86587r4_rule","stig_id":"RHEL-07-010490","fix_id":"F-78315r3_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems prior to version 7.2 using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-71965\" do\n title \"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate organizational users (or processes acting on behalf of\norganizational users) using multifactor authentication.\"\n desc \"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system requires multifactor authentication to uniquely\nidentify organizational users using multifactor authentication.\n\n Check to see if smartcard authentication is enforced on the system:\n\n # authconfig --test | grep \\\"pam_pkcs11 is enabled\\\"\n\n If no results are returned, this is a finding.\n\n # authconfig --test | grep \\\"smartcard removal action\\\"\n\n If \\\"smartcard removal action\\\" is blank, this is a finding.\n\n # authconfig --test | grep \\\"smartcard module\\\"\n\n If \\\"smartcard module\\\" is blank, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require individuals to be authenticated\nwith a multifactor authenticator.\n\n Enable smartcard logons with the following commands:\n\n # authconfig --enablesmartcard --smartcardaction=0 --update\n # authconfig --enablerequiresmartcard -update\n\n Modify the \\\"/etc/pam_pkcs11/pkcs11_eventmgr.conf\\\" file to uncomment the\nfollowing line:\n\n #/usr/X11R6/bin/xscreensaver-command -lock\n\n Modify the \\\"/etc/pam_pkcs11/pam_pkcs11.conf\\\" file to use the cackey\nmodule if required.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000104-GPOS-00051\"\n tag satisfies: [\"SRG-OS-000104-GPOS-00051\", \"SRG-OS-000106-GPOS-00053\",\n\"SRG-OS-000107-GPOS-00054\", \"SRG-OS-000109-GPOS-00056\",\n\"SRG-OS-000108-GPOS-00055\", \"SRG-OS-000108-GPOS-00057\",\n\"SRG-OS-000108-GPOS-00058\"]\n tag gid: \"V-71965\"\n tag rid: \"SV-86589r2_rule\"\n tag stig_id: \"RHEL-07-010500\"\n tag fix_id: \"F-78317r3_fix\"\n tag cci: [\"CCI-000766\"]\n tag nist: [\"IA-2 (2)\"]\n\n smart_card_status = input('smart_card_status')\n if smart_card_status.eql?('enabled')\n impact 0.5\n describe command(\"authconfig --test | grep -i smartcard\") do\n its('stdout') { should match %r{use\\sonly\\ssmartcard\\sfor\\slogin\\sis\\s#{smart_card_status}} }\n its('stdout') { should match %r{smartcard\\smodule\\s=\\s\".+\"} }\n its('stdout') { should match %r{smartcard\\sremoval\\saction\\s=\\s\".+\"} }\n end\n else\n impact 0.0\n describe \"The system is not smartcard enabled\" do\n skip \"The system is not using Smartcards / PIVs to fulfil the MFA requirement, this control is Not Applicable.\"\n end\n end\nend\n","desc":"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.","descriptions":[{"data":"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system requires multifactor authentication to uniquely\nidentify organizational users using multifactor authentication.\n\n Check to see if smartcard authentication is enforced on the system:\n\n # authconfig --test | grep \"pam_pkcs11 is enabled\"\n\n If no results are returned, this is a finding.\n\n # authconfig --test | grep \"smartcard removal action\"\n\n If \"smartcard removal action\" is blank, this is a finding.\n\n # authconfig --test | grep \"smartcard module\"\n\n If \"smartcard module\" is blank, this is a finding.","label":"check"},{"data":"Configure the operating system to require individuals to be authenticated\nwith a multifactor authenticator.\n\n Enable smartcard logons with the following commands:\n\n # authconfig --enablesmartcard --smartcardaction=0 --update\n # authconfig --enablerequiresmartcard -update\n\n Modify the \"/etc/pam_pkcs11/pkcs11_eventmgr.conf\" file to uncomment the\nfollowing line:\n\n #/usr/X11R6/bin/xscreensaver-command -lock\n\n Modify the \"/etc/pam_pkcs11/pam_pkcs11.conf\" file to use the cackey\nmodule if required.","label":"fix"}],"id":"V-71965","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71965.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000104-GPOS-00051","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"],"gid":"V-71965","rid":"SV-86589r2_rule","stig_id":"RHEL-07-010500","fix_id":"F-78317r3_fix","cci":["CCI-000766"],"nist":["IA-2 (2)"]},"title":"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate organizational users (or processes acting on behalf of\norganizational users) using multifactor authentication.","waiver_data":{}},{"code":"control \"V-71967\" do\n title \"The Red Hat Enterprise Linux operating system must not have the\nrsh-server package installed.\"\n desc \"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check to see if the rsh-server package is installed with the following\ncommand:\n\n # yum list installed rsh-server\n\n If the rsh-server package is installed, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable non-essential capabilities by\nremoving the rsh-server package from the system with the following command:\n\n # yum remove rsh-server\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000095-GPOS-00049\"\n tag gid: \"V-71967\"\n tag rid: \"SV-86591r2_rule\"\n tag stig_id: \"RHEL-07-020000\"\n tag fix_id: \"F-78319r1_fix\"\n tag cci: [\"CCI-000381\"]\n tag nist: [\"CM-7 a\"]\n\n describe package(\"rsh-server\") do\n it { should_not be_installed }\n end\nend\n","desc":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.","descriptions":[{"data":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if the rsh-server package is installed with the following\ncommand:\n\n # yum list installed rsh-server\n\n If the rsh-server package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the rsh-server package from the system with the following command:\n\n # yum remove rsh-server","label":"fix"}],"id":"V-71967","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71967.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-71967","rid":"SV-86591r2_rule","stig_id":"RHEL-07-020000","fix_id":"F-78319r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the\nrsh-server package installed.","waiver_data":{}},{"code":"control \"V-71969\" do\n title \"The Red Hat Enterprise Linux operating system must not have the ypserv\npackage installed.\"\n desc \"Removing the \\\"ypserv\\\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The NIS service provides an unencrypted authentication service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n Check to see if the \\\"ypserve\\\" package is installed with the following\ncommand:\n\n # yum list installed ypserv\n\n If the \\\"ypserv\\\" package is installed, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable non-essential capabilities by\nremoving the \\\"ypserv\\\" package from the system with the following command:\n\n # yum remove ypserv\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000095-GPOS-00049\"\n tag gid: \"V-71969\"\n tag rid: \"SV-86593r2_rule\"\n tag stig_id: \"RHEL-07-020010\"\n tag fix_id: \"F-78321r1_fix\"\n tag cci: [\"CCI-000381\"]\n tag nist: [\"CM-7 a\"]\n\n describe package(\"ypserv\") do\n it { should_not be_installed }\n end\nend\n","desc":"Removing the \"ypserv\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.","descriptions":[{"data":"Removing the \"ypserv\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.","label":"default"},{"data":"","label":"rationale"},{"data":"The NIS service provides an unencrypted authentication service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n Check to see if the \"ypserve\" package is installed with the following\ncommand:\n\n # yum list installed ypserv\n\n If the \"ypserv\" package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the \"ypserv\" package from the system with the following command:\n\n # yum remove ypserv","label":"fix"}],"id":"V-71969","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71969.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-71969","rid":"SV-86593r2_rule","stig_id":"RHEL-07-020010","fix_id":"F-78321r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the ypserv\npackage installed.","waiver_data":{}},{"code":"control \"V-71971\" do\n title \"The Red Hat Enterprise Linux operating system must prevent\nnon-privileged users from executing privileged functions to include disabling,\ncircumventing, or altering implemented security safeguards/countermeasures.\"\n desc \"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system prevents non-privileged users from executing\nprivileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Get a list of authorized users (other than System Administrator and guest\naccounts) for the system.\n\n Check the list against the system by using the following command:\n\n # semanage login -l | more\n Login Name SELinux User MLS/MCS Range Service\n __default__ user_u s0-s0:c0.c1023 *\n root unconfined_u s0-s0:c0.c1023 *\n system_u system_u s0-s0:c0.c1023 *\n joe staff_u s0-s0:c0.c1023 *\n\n All administrators must be mapped to the \\\"sysadm_u\\\" or \\\"staff_u\\\" users\nrole.\n\n All authorized non-administrative users must be mapped to the \\\"user_u\\\"\nrole.\n\n If they are not mapped in this way, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent non-privileged users from\nexecuting privileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Use the following command to map a new user to the \\\"sysdam_u\\\" role:\n\n #semanage login -a -s sysadm_u \n\n Use the following command to map an existing user to the \\\"sysdam_u\\\" role:\n\n #semanage login -m -s sysadm_u \n\n Use the following command to map a new user to the \\\"staff_u\\\" role:\n\n #semanage login -a -s staff_u \n\n Use the following command to map an existing user to the \\\"staff_u\\\" role:\n\n #semanage login -m -s staff_u \n\n Use the following command to map a new user to the \\\"user_u\\\" role:\n\n # semanage login -a -s user_u \n\n Use the following command to map an existing user to the \\\"user_u\\\" role:\n\n # semanage login -m -s user_u \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000324-GPOS-00125\"\n tag gid: \"V-71971\"\n tag rid: \"SV-86595r2_rule\"\n tag stig_id: \"RHEL-07-020020\"\n tag fix_id: \"F-78323r1_fix\"\n tag cci: [\"CCI-002165\", \"CCI-002235\"]\n tag nist: [\"AC-3 (4)\", \"AC-6 (10)\"]\n\n admin_logins = input('admin_logins')\n\n if package('MFEhiplsm').installed? && processes(/hipclient/).exist?\n impact 0.0\n describe \"HIPS is active on the system\" do\n skip \"A HIPS process is active on the system, this control is Not Applicable.\"\n end\n elsif service('cma').installed? && service('cma').enabled?\n impact 0.0\n describe \"HBSS is active on the system\" do\n skip \"A HBSS service is active on the system, this control is Not Applicable.\"\n end\n else\n impact 0.5\n describe command('selinuxenabled') do\n its('exist?') { should be true }\n its('exit_status') { should eq 0 }\n end\n\n selinux_mode = file('/etc/selinux/config').content.lines.\n grep(/\\A\\s*SELINUXTYPE=/).last.split('=').last.strip\n\n seusers = file(\"/etc/selinux/#{selinux_mode}/seusers\").content.lines.\n grep_v(/(#|\\A\\s+\\Z)/).map(&:strip)\n\n seusers = seusers.map{|x| x.split(':')[0..1]}\n\n describe 'seusers' do\n it { expect(seusers).to_not be_empty }\n end\n\n users_to_ignore = [\n 'root',\n 'system_u'\n ]\n\n seusers.each do |user, context|\n next if users_to_ignore.include?(user)\n\n describe \"SELinux login #{user}\" do\n if user == '__default__'\n let(:valid_users){[ 'user_u' ]}\n elsif admin_logins.include?(user)\n let(:valid_users){[\n 'sysadm_u',\n 'staff_u'\n ]}\n else\n let(:valid_users){[\n 'user_u',\n 'guest_u',\n 'xguest_u'\n ]}\n end\n\n it { expect(context).to be_in(valid_users) }\n end\n end\n end\nend\n","desc":"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.","descriptions":[{"data":"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system prevents non-privileged users from executing\nprivileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Get a list of authorized users (other than System Administrator and guest\naccounts) for the system.\n\n Check the list against the system by using the following command:\n\n # semanage login -l | more\n Login Name SELinux User MLS/MCS Range Service\n __default__ user_u s0-s0:c0.c1023 *\n root unconfined_u s0-s0:c0.c1023 *\n system_u system_u s0-s0:c0.c1023 *\n joe staff_u s0-s0:c0.c1023 *\n\n All administrators must be mapped to the \"sysadm_u\" or \"staff_u\" users\nrole.\n\n All authorized non-administrative users must be mapped to the \"user_u\"\nrole.\n\n If they are not mapped in this way, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent non-privileged users from\nexecuting privileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Use the following command to map a new user to the \"sysdam_u\" role:\n\n #semanage login -a -s sysadm_u \n\n Use the following command to map an existing user to the \"sysdam_u\" role:\n\n #semanage login -m -s sysadm_u \n\n Use the following command to map a new user to the \"staff_u\" role:\n\n #semanage login -a -s staff_u \n\n Use the following command to map an existing user to the \"staff_u\" role:\n\n #semanage login -m -s staff_u \n\n Use the following command to map a new user to the \"user_u\" role:\n\n # semanage login -a -s user_u \n\n Use the following command to map an existing user to the \"user_u\" role:\n\n # semanage login -m -s user_u ","label":"fix"}],"id":"V-71971","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71971.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000324-GPOS-00125","gid":"V-71971","rid":"SV-86595r2_rule","stig_id":"RHEL-07-020020","fix_id":"F-78323r1_fix","cci":["CCI-002165","CCI-002235"],"nist":["AC-3 (4)","AC-6 (10)"]},"title":"The Red Hat Enterprise Linux operating system must prevent\nnon-privileged users from executing privileged functions to include disabling,\ncircumventing, or altering implemented security safeguards/countermeasures.","waiver_data":{}},{"code":"control \"V-71973\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat a file integrity tool verifies the baseline operating system configuration\nat least weekly.\"\n desc \"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system routinely checks the baseline configuration for\nunauthorized changes.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed at least once per\nweek.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running daily or weekly on the system\nthat executes AIDE daily to scan for changes to the system baseline. The\ncommand used in the example will use a daily occurrence.\n\n Check the cron directories for a script file controlling the execution of\nthe file integrity application. For example, if AIDE is installed on the\nsystem, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 29 Nov 22 2015 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n If the file integrity application does not exist, or a script file\ncontrolling the execution of the file integrity application does not exist,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to run automatically on the system at\nleast weekly. The following example output is generic. It will set cron to run\nAIDE daily, but other file integrity tools may be used:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \\\"$HOSTNAME - Daily aide integrity\ncheck run\\\" root@sysname.mil\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000363-GPOS-00150\"\n tag gid: \"V-71973\"\n tag rid: \"SV-86597r2_rule\"\n tag stig_id: \"RHEL-07-020030\"\n tag fix_id: \"F-78325r2_fix\"\n tag cci: [\"CCI-001744\"]\n tag nist: [\"CM-3 (5)\"]\n\n file_integrity_tool = input('file_integrity_tool')\n file_integrity_interval = input('file_integrity_interval')\n\n describe package(file_integrity_tool) do\n it { should be_installed }\n end\n\n if file_integrity_interval == 'monthly'\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n it { should exist }\n end\n describe file(\"/etc/cron.weekly/#{file_integrity_tool}\") do\n it { should exist }\n end\n describe file(\"/etc/cron.monthly/#{file_integrity_tool}\") do\n it { should exist }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n elsif file_integrity_interval == 'weekly'\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n it { should exist }\n end\n describe file(\"/etc/cron.weekly/#{file_integrity_tool}\") do\n it { should exist }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n elsif file_integrity_interval == 'daily'\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n it { should exist }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n end\n end\nend\n","desc":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","descriptions":[{"data":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system routinely checks the baseline configuration for\nunauthorized changes.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed at least once per\nweek.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running daily or weekly on the system\nthat executes AIDE daily to scan for changes to the system baseline. The\ncommand used in the example will use a daily occurrence.\n\n Check the cron directories for a script file controlling the execution of\nthe file integrity application. For example, if AIDE is installed on the\nsystem, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 29 Nov 22 2015 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n If the file integrity application does not exist, or a script file\ncontrolling the execution of the file integrity application does not exist,\nthis is a finding.","label":"check"},{"data":"Configure the file integrity tool to run automatically on the system at\nleast weekly. The following example output is generic. It will set cron to run\nAIDE daily, but other file integrity tools may be used:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil","label":"fix"}],"id":"V-71973","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71973.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000363-GPOS-00150","gid":"V-71973","rid":"SV-86597r2_rule","stig_id":"RHEL-07-020030","fix_id":"F-78325r2_fix","cci":["CCI-001744"],"nist":["CM-3 (5)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat a file integrity tool verifies the baseline operating system configuration\nat least weekly.","waiver_data":{}},{"code":"control \"V-71975\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat designated personnel are notified if baseline configurations are changed\nin an unauthorized manner.\"\n desc \"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system notifies designated personnel if baseline\nconfigurations are changed in an unauthorized manner.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed and notify\nspecified individuals via email or an alert.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running routinely on the system that\nexecutes AIDE to scan for changes to the system baseline. The commands used in\nthe example will use a daily occurrence.\n\n Check the cron directories for a \\\"crontab\\\" script file controlling the\nexecution of the file integrity application. For example, if AIDE is installed\non the system, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 32 Jul 1 2011 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n AIDE does not have a configuration that will send a notification, so the\ncron job uses the mail application on the system to email the results of the\nfile integrity run as in the following example:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \\\"$HOSTNAME - Daily aide integrity\ncheck run\\\" root@sysname.mil\n\n If the file integrity application does not notify designated personnel of\nchanges, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to notify designated personnel if baseline\nconfigurations are changed in an unauthorized manner. The AIDE tool can be\nconfigured to email designated personnel with the use of the cron system.\n\n The following example output is generic. It will set cron to run AIDE daily\nand to send email at the completion of the analysis.\n\n # more /etc/cron.daily/aide\n\n /usr/sbin/aide --check | /bin/mail -s \\\"$HOSTNAME - Daily aide integrity\ncheck run\\\" root@sysname.mil\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000363-GPOS-00150\"\n tag gid: \"V-71975\"\n tag rid: \"SV-86599r2_rule\"\n tag stig_id: \"RHEL-07-020040\"\n tag fix_id: \"F-78327r3_fix\"\n tag cci: [\"CCI-001744\"]\n tag nist: [\"CM-3 (5)\"]\n\n file_integrity_tool = input('file_integrity_tool')\n\n describe package(file_integrity_tool) do\n it { should be_installed }\n end\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n its('content') { should match %r{/bin/mail} }\n end\n describe file(\"/etc/cron.weekly/#{file_integrity_tool}\") do\n its('content') { should match %r{/bin/mail} }\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('commands.flatten') { should include(match %r{/bin/mail}) }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('commands') { should include(match %r{/bin/mail}) }\n end\n end\n end\nend\n","desc":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","descriptions":[{"data":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system notifies designated personnel if baseline\nconfigurations are changed in an unauthorized manner.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed and notify\nspecified individuals via email or an alert.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running routinely on the system that\nexecutes AIDE to scan for changes to the system baseline. The commands used in\nthe example will use a daily occurrence.\n\n Check the cron directories for a \"crontab\" script file controlling the\nexecution of the file integrity application. For example, if AIDE is installed\non the system, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 32 Jul 1 2011 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n AIDE does not have a configuration that will send a notification, so the\ncron job uses the mail application on the system to email the results of the\nfile integrity run as in the following example:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil\n\n If the file integrity application does not notify designated personnel of\nchanges, this is a finding.","label":"check"},{"data":"Configure the operating system to notify designated personnel if baseline\nconfigurations are changed in an unauthorized manner. The AIDE tool can be\nconfigured to email designated personnel with the use of the cron system.\n\n The following example output is generic. It will set cron to run AIDE daily\nand to send email at the completion of the analysis.\n\n # more /etc/cron.daily/aide\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil","label":"fix"}],"id":"V-71975","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71975.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000363-GPOS-00150","gid":"V-71975","rid":"SV-86599r2_rule","stig_id":"RHEL-07-020040","fix_id":"F-78327r3_fix","cci":["CCI-001744"],"nist":["CM-3 (5)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat designated personnel are notified if baseline configurations are changed\nin an unauthorized manner.","waiver_data":{}},{"code":"control \"V-71977\" do\n title \"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components from a repository without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.\"\n desc \"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components from a repository without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of packages from a repository prior\nto install with the following command:\n\n # grep gpgcheck /etc/yum.conf\n gpgcheck=1\n\n If \\\"gpgcheck\\\" is not set to \\\"1\\\", or if options are missing or commented\nout, ask the System Administrator how the certificates for patches and other\noperating system components are verified.\n\n If there is no process to validate certificates that is approved by the\norganization, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify the signature of packages from a\nrepository prior to install by setting the following option in the\n\\\"/etc/yum.conf\\\" file:\n\n gpgcheck=1\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000366-GPOS-00153\"\n tag gid: \"V-71977\"\n tag rid: \"SV-86601r2_rule\"\n tag stig_id: \"RHEL-07-020050\"\n tag fix_id: \"F-78329r1_fix\"\n tag cci: [\"CCI-001749\"]\n tag nist: [\"CM-5 (3)\"]\n\n yum_conf = '/etc/yum.conf'\n\n if ((f = file(yum_conf)).exist?)\n describe ini(yum_conf) do\n its('main.gpgcheck') { should cmp 1 }\n end\n else\n describe f do\n it { should exist }\n end\n end\nend\n","desc":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","descriptions":[{"data":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components from a repository without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of packages from a repository prior\nto install with the following command:\n\n # grep gpgcheck /etc/yum.conf\n gpgcheck=1\n\n If \"gpgcheck\" is not set to \"1\", or if options are missing or commented\nout, ask the System Administrator how the certificates for patches and other\noperating system components are verified.\n\n If there is no process to validate certificates that is approved by the\norganization, this is a finding.","label":"check"},{"data":"Configure the operating system to verify the signature of packages from a\nrepository prior to install by setting the following option in the\n\"/etc/yum.conf\" file:\n\n gpgcheck=1","label":"fix"}],"id":"V-71977","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71977.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000366-GPOS-00153","gid":"V-71977","rid":"SV-86601r2_rule","stig_id":"RHEL-07-020050","fix_id":"F-78329r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components from a repository without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.","waiver_data":{}},{"code":"control \"V-71979\" do\n title \"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components of local packages without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.\"\n desc \"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components of local packages without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of local packages prior to install\nwith the following command:\n\n # grep localpkg_gpgcheck /etc/yum.conf\n localpkg_gpgcheck=1\n\n If \\\"localpkg_gpgcheck\\\" is not set to \\\"1\\\", or if options are missing or\ncommented out, ask the System Administrator how the signatures of local\npackages and other operating system components are verified.\n\n If there is no process to validate the signatures of local packages that is\napproved by the organization, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify the signature of local packages\nprior to install by setting the following option in the \\\"/etc/yum.conf\\\" file:\n\n localpkg_gpgcheck=1\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000366-GPOS-00153\"\n tag gid: \"V-71979\"\n tag rid: \"SV-86603r2_rule\"\n tag stig_id: \"RHEL-07-020060\"\n tag fix_id: \"F-78331r1_fix\"\n tag cci: [\"CCI-001749\"]\n tag nist: [\"CM-5 (3)\"]\n\n yum_conf = '/etc/yum.conf'\n\n if ((f = file(yum_conf)).exist?)\n describe ini(yum_conf) do\n its('main.localpkg_gpgcheck') { cmp 1 }\n end\n else\n describe f do\n it { should exist }\n end\n end\nend\n","desc":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","descriptions":[{"data":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components of local packages without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of local packages prior to install\nwith the following command:\n\n # grep localpkg_gpgcheck /etc/yum.conf\n localpkg_gpgcheck=1\n\n If \"localpkg_gpgcheck\" is not set to \"1\", or if options are missing or\ncommented out, ask the System Administrator how the signatures of local\npackages and other operating system components are verified.\n\n If there is no process to validate the signatures of local packages that is\napproved by the organization, this is a finding.","label":"check"},{"data":"Configure the operating system to verify the signature of local packages\nprior to install by setting the following option in the \"/etc/yum.conf\" file:\n\n localpkg_gpgcheck=1","label":"fix"}],"id":"V-71979","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71979.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000366-GPOS-00153","gid":"V-71979","rid":"SV-86603r2_rule","stig_id":"RHEL-07-020060","fix_id":"F-78331r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components of local packages without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.","waiver_data":{}},{"code":"control \"V-71983\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\ndisable USB mass storage.\"\n desc \"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If there is an HBSS with a Device Control Module and a Data Loss Prevention\nmechanism, this requirement is not applicable.\n\n Verify the operating system disables the ability to load the USB Storage\nkernel module.\n\n # grep -r usb-storage /etc/modprobe.d/* | grep -i \\\"/bin/true\\\" | grep -v\n\\\"^#\\\"\n\n install usb-storage /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of USB Storage is not documented with the Information System Security\nOfficer (ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use USB mass storage\ndevices.\n\n Check to see if USB mass storage is disabled with the following command:\n\n # grep usb-storage /etc/modprobe.d/* | grep -i \\\"blacklist\\\" | grep -v\n\\\"^#\\\"\n blacklist usb-storage\n\n If the command does not return any output or the output is not \\\"blacklist\nusb-storage\\\", and use of USB storage devices is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable the ability to use the USB\nStorage kernel module.\n\n Create a file under \\\"/etc/modprobe.d\\\" with the following command:\n\n # touch /etc/modprobe.d/usb-storage.conf\n\n Add the following line to the created file:\n\n install usb-storage /bin/true\n\n Configure the operating system to disable the ability to use USB mass\nstorage devices.\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist usb-storage\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000114-GPOS-00059\"\n tag satisfies: [\"SRG-OS-000114-GPOS-00059\", \"SRG-OS-000378-GPOS-00163\",\n\"SRG-OS-000480-GPOS-00227\"]\n tag gid: \"V-71983\"\n tag rid: \"SV-86607r4_rule\"\n tag stig_id: \"RHEL-07-020100\"\n tag fix_id: \"F-78335r4_fix\"\n tag cci: [\"CCI-000366\", \"CCI-000778\", \"CCI-001958\"]\n tag nist: [\"CM-6 b\", \"IA-3\", \"IA-3\"]\n\n unless input('data_loss_prevention_installed')\n impact 0.0\n describe \"The system is not using an HBSS with a Device Control Module and a Data Loss Prevention mechanism\" do\n skip \"The system is not using an HBSS with a Device Control Module and a Data Loss Prevention mechanism, this control is Not Applicable.\"\n end\n else\n describe kernel_module('usb_storage') do\n it { should_not be_loaded }\n it { should be_blacklisted }\n end\n end\nend\n","desc":"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.","descriptions":[{"data":"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.","label":"default"},{"data":"","label":"rationale"},{"data":"If there is an HBSS with a Device Control Module and a Data Loss Prevention\nmechanism, this requirement is not applicable.\n\n Verify the operating system disables the ability to load the USB Storage\nkernel module.\n\n # grep -r usb-storage /etc/modprobe.d/* | grep -i \"/bin/true\" | grep -v\n\"^#\"\n\n install usb-storage /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of USB Storage is not documented with the Information System Security\nOfficer (ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use USB mass storage\ndevices.\n\n Check to see if USB mass storage is disabled with the following command:\n\n # grep usb-storage /etc/modprobe.d/* | grep -i \"blacklist\" | grep -v\n\"^#\"\n blacklist usb-storage\n\n If the command does not return any output or the output is not \"blacklist\nusb-storage\", and use of USB storage devices is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to use the USB\nStorage kernel module.\n\n Create a file under \"/etc/modprobe.d\" with the following command:\n\n # touch /etc/modprobe.d/usb-storage.conf\n\n Add the following line to the created file:\n\n install usb-storage /bin/true\n\n Configure the operating system to disable the ability to use USB mass\nstorage devices.\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist usb-storage","label":"fix"}],"id":"V-71983","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71983.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000114-GPOS-00059","satisfies":["SRG-OS-000114-GPOS-00059","SRG-OS-000378-GPOS-00163","SRG-OS-000480-GPOS-00227"],"gid":"V-71983","rid":"SV-86607r4_rule","stig_id":"RHEL-07-020100","fix_id":"F-78335r4_fix","cci":["CCI-000366","CCI-000778","CCI-001958"],"nist":["CM-6 b","IA-3","IA-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\ndisable USB mass storage.","waiver_data":{}},{"code":"control \"V-71985\" do\n title \"The Red Hat Enterprise Linux operating system must disable the file\nsystem automounter unless required.\"\n desc \"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system disables the ability to automount devices.\n\n Check to see if automounter service is active with the following command:\n\n # systemctl status autofs\n autofs.service - Automounts filesystems on demand\n Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)\n Active: inactive (dead)\n\n If the \\\"autofs\\\" status is set to \\\"active\\\" and is not documented with\nthe Information System Security Officer (ISSO) as an operational requirement,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable the ability to automount devices.\n\n Turn off the automount service with the following commands:\n\n # systemctl stop autofs\n # systemctl disable autofs\n\n If \\\"autofs\\\" is required for Network File System (NFS), it must be\ndocumented with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000114-GPOS-00059\"\n tag satisfies: [\"SRG-OS-000114-GPOS-00059\", \"SRG-OS-000378-GPOS-00163\",\n\"SRG-OS-000480-GPOS-00227\"]\n tag gid: \"V-71985\"\n tag rid: \"SV-86609r2_rule\"\n tag stig_id: \"RHEL-07-020110\"\n tag fix_id: \"F-78337r2_fix\"\n tag cci: [\"CCI-000366\", \"CCI-000778\", \"CCI-001958\"]\n tag nist: [\"CM-6 b\", \"IA-3\", \"IA-3\"]\n\n describe systemd_service('autofs.service') do\n it { should_not be_running }\n it { should_not be_enabled }\n it { should_not be_installed }\n end\nend\n","desc":"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.","descriptions":[{"data":"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system disables the ability to automount devices.\n\n Check to see if automounter service is active with the following command:\n\n # systemctl status autofs\n autofs.service - Automounts filesystems on demand\n Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)\n Active: inactive (dead)\n\n If the \"autofs\" status is set to \"active\" and is not documented with\nthe Information System Security Officer (ISSO) as an operational requirement,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to automount devices.\n\n Turn off the automount service with the following commands:\n\n # systemctl stop autofs\n # systemctl disable autofs\n\n If \"autofs\" is required for Network File System (NFS), it must be\ndocumented with the ISSO.","label":"fix"}],"id":"V-71985","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71985.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000114-GPOS-00059","satisfies":["SRG-OS-000114-GPOS-00059","SRG-OS-000378-GPOS-00163","SRG-OS-000480-GPOS-00227"],"gid":"V-71985","rid":"SV-86609r2_rule","stig_id":"RHEL-07-020110","fix_id":"F-78337r2_fix","cci":["CCI-000366","CCI-000778","CCI-001958"],"nist":["CM-6 b","IA-3","IA-3"]},"title":"The Red Hat Enterprise Linux operating system must disable the file\nsystem automounter unless required.","waiver_data":{}},{"code":"control \"V-71987\" do\n title \"The Red Hat Enterprise Linux operating system must remove all software\ncomponents after updated versions have been installed.\"\n desc \"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system removes all software components after updated\nversions have been installed.\n\n Check if yum is configured to remove unneeded packages with the following\ncommand:\n\n # grep -i clean_requirements_on_remove /etc/yum.conf\n clean_requirements_on_remove=1\n\n If \\\"clean_requirements_on_remove\\\" is not set to \\\"1\\\", \\\"True\\\", or\n\\\"yes\\\", or is not set in \\\"/etc/yum.conf\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to remove all software components after\nupdated versions have been installed.\n\n Set the \\\"clean_requirements_on_remove\\\" option to \\\"1\\\" in the\n\\\"/etc/yum.conf\\\" file:\n\n clean_requirements_on_remove=1\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000437-GPOS-00194\"\n tag gid: \"V-71987\"\n tag rid: \"SV-86611r2_rule\"\n tag stig_id: \"RHEL-07-020200\"\n tag fix_id: \"F-78339r1_fix\"\n tag cci: [\"CCI-002617\"]\n tag nist: [\"SI-2 (6)\"]\n\n describe parse_config_file(\"/etc/yum.conf\") do\n its('main.clean_requirements_on_remove') { should match %r{1|True|yes}i }\n end\nend\n","desc":"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.","descriptions":[{"data":"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system removes all software components after updated\nversions have been installed.\n\n Check if yum is configured to remove unneeded packages with the following\ncommand:\n\n # grep -i clean_requirements_on_remove /etc/yum.conf\n clean_requirements_on_remove=1\n\n If \"clean_requirements_on_remove\" is not set to \"1\", \"True\", or\n\"yes\", or is not set in \"/etc/yum.conf\", this is a finding.","label":"check"},{"data":"Configure the operating system to remove all software components after\nupdated versions have been installed.\n\n Set the \"clean_requirements_on_remove\" option to \"1\" in the\n\"/etc/yum.conf\" file:\n\n clean_requirements_on_remove=1","label":"fix"}],"id":"V-71987","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71987.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000437-GPOS-00194","gid":"V-71987","rid":"SV-86611r2_rule","stig_id":"RHEL-07-020200","fix_id":"F-78339r1_fix","cci":["CCI-002617"],"nist":["SI-2 (6)"]},"title":"The Red Hat Enterprise Linux operating system must remove all software\ncomponents after updated versions have been installed.","waiver_data":{}},{"code":"control \"V-71989\" do\n title \"The Red Hat Enterprise Linux operating system must enable SELinux.\"\n desc \"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \\\"SELinux\\\" is active and in \\\"Enforcing\\\" mode with the following\ncommand:\n\n # getenforce\n Enforcing\n\n If \\\"SELinux\\\" is not active and not in \\\"Enforcing\\\" mode, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \\\"SELinux\\\" status and the \\\"Enforcing\\\" mode by modifying the\n\\\"/etc/selinux/config\\\" file to have the following line:\n\n SELINUX=enforcing\n\n A reboot is required for the changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000445-GPOS-00199\"\n tag gid: \"V-71989\"\n tag rid: \"SV-86613r3_rule\"\n tag stig_id: \"RHEL-07-020210\"\n tag fix_id: \"F-78341r2_fix\"\n tag cci: [\"CCI-002165\", \"CCI-002696\"]\n tag nist: [\"AC-3 (4)\", \"SI-6 a\"]\n\n\n if package('MFEhiplsm').installed? && processes(/hipclient/).exist?\n impact 0.0\n describe \"HIPS is active on the system\" do\n skip \"A HIPS process is active on the system, this control is Not Applicable.\"\n end\n elsif service('cma').installed? && service('cma').enabled?\n impact 0.0\n describe \"HBSS is active on the system\" do\n skip \"A HBSS service is active on the system, this control is Not Applicable.\"\n end\n else\n impact 0.7\n describe command('getenforce') do\n its('stdout.strip') { should eq 'Enforcing' }\n end\n end\nend\n","desc":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","descriptions":[{"data":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \"SELinux\" is active and in \"Enforcing\" mode with the following\ncommand:\n\n # getenforce\n Enforcing\n\n If \"SELinux\" is not active and not in \"Enforcing\" mode, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \"SELinux\" status and the \"Enforcing\" mode by modifying the\n\"/etc/selinux/config\" file to have the following line:\n\n SELINUX=enforcing\n\n A reboot is required for the changes to take effect.","label":"fix"}],"id":"V-71989","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71989.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000445-GPOS-00199","gid":"V-71989","rid":"SV-86613r3_rule","stig_id":"RHEL-07-020210","fix_id":"F-78341r2_fix","cci":["CCI-002165","CCI-002696"],"nist":["AC-3 (4)","SI-6 a"]},"title":"The Red Hat Enterprise Linux operating system must enable SELinux.","waiver_data":{}},{"code":"control \"V-71991\" do\n title \"The Red Hat Enterprise Linux operating system must enable the SELinux\ntargeted policy.\"\n desc \"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \\\"SELinux\\\" is active and is enforcing the targeted policy with\nthe following command:\n\n # sestatus\n\n SELinux status: enabled\n\n SELinuxfs mount: /selinux\n\n SELinux root directory: /etc/selinux\n\n Loaded policy name: targeted\n\n Current mode: enforcing\n\n Mode from config file: enforcing\n\n Policy MLS status: enabled\n\n Policy deny_unknown status: allowed\n\n Max kernel policy version: 28\n\n If the \\\"Loaded policy name\\\" is not set to \\\"targeted\\\", this is a finding.\n\n Verify that the /etc/selinux/config file is configured to the\n\\\"SELINUXTYPE\\\" to \\\"targeted\\\":\n\n # grep -i \\\"selinuxtype\\\" /etc/selinux/config | grep -v '^#'\n\n SELINUXTYPE = targeted\n\n If no results are returned or \\\"SELINUXTYPE\\\" is not set to \\\"targeted\\\",\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \\\"SELinuxtype\\\" to the \\\"targeted\\\" policy by modifying the\n\\\"/etc/selinux/config\\\" file to have the following line:\n\n SELINUXTYPE=targeted\n\n A reboot is required for the changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000445-GPOS-00199\"\n tag gid: \"V-71991\"\n tag rid: \"SV-86615r5_rule\"\n tag stig_id: \"RHEL-07-020220\"\n tag fix_id: \"F-78343r2_fix\"\n tag cci: [\"CCI-002165\", \"CCI-002696\"]\n tag nist: [\"AC-3 (4)\", \"SI-6 a\"]\n\n describe.one do\n describe command('sestatus') do\n its('stdout') { should match %r{^Policy\\sfrom\\sconfigs\\sfile:\\s+targeted\\n?$} }\n end\n describe command('sestatus') do\n its('stdout') { should match %r{^Loaded\\spolicy\\sname:\\s+targeted\\n?$} }\n end\n end\nend\n","desc":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","descriptions":[{"data":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \"SELinux\" is active and is enforcing the targeted policy with\nthe following command:\n\n # sestatus\n\n SELinux status: enabled\n\n SELinuxfs mount: /selinux\n\n SELinux root directory: /etc/selinux\n\n Loaded policy name: targeted\n\n Current mode: enforcing\n\n Mode from config file: enforcing\n\n Policy MLS status: enabled\n\n Policy deny_unknown status: allowed\n\n Max kernel policy version: 28\n\n If the \"Loaded policy name\" is not set to \"targeted\", this is a finding.\n\n Verify that the /etc/selinux/config file is configured to the\n\"SELINUXTYPE\" to \"targeted\":\n\n # grep -i \"selinuxtype\" /etc/selinux/config | grep -v '^#'\n\n SELINUXTYPE = targeted\n\n If no results are returned or \"SELINUXTYPE\" is not set to \"targeted\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \"SELinuxtype\" to the \"targeted\" policy by modifying the\n\"/etc/selinux/config\" file to have the following line:\n\n SELINUXTYPE=targeted\n\n A reboot is required for the changes to take effect.","label":"fix"}],"id":"V-71991","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71991.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000445-GPOS-00199","gid":"V-71991","rid":"SV-86615r5_rule","stig_id":"RHEL-07-020220","fix_id":"F-78343r2_fix","cci":["CCI-002165","CCI-002696"],"nist":["AC-3 (4)","SI-6 a"]},"title":"The Red Hat Enterprise Linux operating system must enable the SELinux\ntargeted policy.","waiver_data":{}},{"code":"control \"V-71993\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled on the command line.\"\n desc \"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active with the\nfollowing command:\n\n # systemctl status ctrl-alt-del.target\n\n ctrl-alt-del.target\n Loaded: masked (/dev/null; bad)\n Active: inactive (dead)\n\n If the ctrl-alt-del.target is not masked, this is a finding.\n\n If the ctrl-alt-del.target is active, this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to disable the Ctrl-Alt-Delete sequence for the\ncommand line with the following command:\n\n # systemctl mask ctrl-alt-del.target\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71993\"\n tag rid: \"SV-86617r5_rule\"\n tag stig_id: \"RHEL-07-020230\"\n tag fix_id: \"F-78345r6_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe systemd_service('ctrl-alt-del.target') do\n it { should_not be_running }\n it { should_not be_enabled }\n end\nend\n","desc":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","descriptions":[{"data":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active with the\nfollowing command:\n\n # systemctl status ctrl-alt-del.target\n\n ctrl-alt-del.target\n Loaded: masked (/dev/null; bad)\n Active: inactive (dead)\n\n If the ctrl-alt-del.target is not masked, this is a finding.\n\n If the ctrl-alt-del.target is active, this is a finding.","label":"check"},{"data":"Configure the system to disable the Ctrl-Alt-Delete sequence for the\ncommand line with the following command:\n\n # systemctl mask ctrl-alt-del.target","label":"fix"}],"id":"V-71993","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71993.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71993","rid":"SV-86617r5_rule","stig_id":"RHEL-07-020230","fix_id":"F-78345r6_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled on the command line.","waiver_data":{}},{"code":"control \"V-71995\" do\n title \"The Red Hat Enterprise Linux operating system must define default\npermissions for all authenticated users in such a way that the user can only\nread and modify their own files.\"\n desc \"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system defines default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Check for the value of the \\\"UMASK\\\" parameter in \\\"/etc/login.defs\\\" file\nwith the following command:\n\n Note: If the value of the \\\"UMASK\\\" parameter is set to \\\"000\\\" in\n\\\"/etc/login.defs\\\" file, the Severity is raised to a CAT I.\n\n # grep -i umask /etc/login.defs\n UMASK 077\n\n If the value for the \\\"UMASK\\\" parameter is not \\\"077\\\", or the \\\"UMASK\\\"\nparameter is missing or is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to define default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Add or edit the line for the \\\"UMASK\\\" parameter in \\\"/etc/login.defs\\\"\nfile to \\\"077\\\":\n\n UMASK 077\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00228\"\n tag gid: \"V-71995\"\n tag rid: \"SV-86619r2_rule\"\n tag stig_id: \"RHEL-07-020240\"\n tag fix_id: \"F-78347r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n\n if login_defs.read_params[\"UMASK\"].eql?('000')\n impact 0.7\n else\n impact 0.5\n end\n describe login_defs do\n its('UMASK') { should eq '077' }\n end\nend\n","desc":"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.","descriptions":[{"data":"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system defines default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Check for the value of the \"UMASK\" parameter in \"/etc/login.defs\" file\nwith the following command:\n\n Note: If the value of the \"UMASK\" parameter is set to \"000\" in\n\"/etc/login.defs\" file, the Severity is raised to a CAT I.\n\n # grep -i umask /etc/login.defs\n UMASK 077\n\n If the value for the \"UMASK\" parameter is not \"077\", or the \"UMASK\"\nparameter is missing or is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to define default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Add or edit the line for the \"UMASK\" parameter in \"/etc/login.defs\"\nfile to \"077\":\n\n UMASK 077","label":"fix"}],"id":"V-71995","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71995.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00228","gid":"V-71995","rid":"SV-86619r2_rule","stig_id":"RHEL-07-020240","fix_id":"F-78347r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must define default\npermissions for all authenticated users in such a way that the user can only\nread and modify their own files.","waiver_data":{}},{"code":"control \"V-71997\" do\n title \"The Red Hat Enterprise Linux operating system must be a vendor\nsupported release.\"\n desc \"An operating system release is considered \\\"supported\\\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the version of the operating system is vendor supported.\n\n Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n Red Hat Enterprise Linux Server release 7.4 (Maipo)\n\n Current End of Life for RHEL 7.1 is 31 March 2017.\n\n Current End of Life for RHEL 7.2 is 30 November 2017.\n\n Current End of Life for RHEL 7.3 is 30 November 2018.\n\n Current End of Life for RHEL 7.4 is 31 August 2019.\n\n Current End of Life for RHEL 7.5 is 30 April 2020.\n\n Current End of Life for RHEL 7.6 is 31 October 2020.\n\n Current End of Life for RHEL 7.7 is 30 August 2021.\n\n If the release is not supported by the vendor, this is a finding.\n \"\n desc \"fix\", \"Upgrade to a supported version of the operating system.\"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71997\"\n tag rid: \"SV-86621r5_rule\"\n tag stig_id: \"RHEL-07-020250\"\n tag fix_id: \"F-78349r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe file('/etc/redhat-release') do\n its('content') { should match %r{Release (6.7*|7.[2-9].*)}i }\n end\nend\n","desc":"An operating system release is considered \"supported\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.","descriptions":[{"data":"An operating system release is considered \"supported\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the version of the operating system is vendor supported.\n\nCheck the version of the operating system with the following command:\n\n# cat /etc/redhat-release\n\nRed Hat Enterprise Linux Server release 7.4 (Maipo)\n\nCurrent End of Life for RHEL 7.1 is 31 March 2017.\n\nCurrent End of Life for RHEL 7.2 is 30 November 2017.\n\nCurrent End of Life for RHEL 7.3 is 30 November 2018.\n\nCurrent End of Life for RHEL 7.4 is 31 August 2019.\n\nCurrent End of Life for RHEL 7.5 is 30 April 2020.\n\nCurrent End of Life for RHEL 7.6 is 31 October 2020.\n\nCurrent End of Life for RHEL 7.7 is 30 August 2021.\n\nIf the release is not supported by the vendor, this is a finding.","label":"check"},{"data":"Upgrade to a supported version of the operating system.","label":"fix"}],"id":"V-71997","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71997.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71997","rid":"SV-86621r5_rule","stig_id":"RHEL-07-020250","fix_id":"F-78349r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be a vendor\nsupported release.","waiver_data":{}},{"code":"control \"V-71999\" do\n title \"The Red Hat Enterprise Linux operating system security patches and\n updates must be installed and up to date.\"\n desc \"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.\"\n\n desc \"check\", \"Verify the operating system security patches and updates are installed and\n up to date. Updates are required to be applied with a frequency determined by\n the site or Program Management Office (PMO).\n\n Obtain the list of available package security updates from Red Hat. The URL\n for updates is https://rhn.redhat.com/errata/. It is important to note that\n updates provided by Red Hat may not be present on the system if the underlying\n packages are not installed.\n\n Check that the available package security updates have been installed on\n the system with the following command:\n\n # yum history list | more\n Loaded plugins: langpacks, product-id, subscription-manager\n ID | Command line | Date and time | Action(s) |\n Altered\n\n -------------------------------------------------------------------------------\n 70 | install aide | 2016-05-05 10:58 | Install |\n 1\n 69 | update -y | 2016-05-04 14:34 | Update | 18 EE\n 68 | install vlc | 2016-04-21 17:12 | Install |\n 21\n 67 | update -y | 2016-04-21 17:04 | Update | 7 EE\n 66 | update -y | 2016-04-15 16:47 | E, I, U |\n 84 EE\n\n If package updates have not been performed on the system within the\n timeframe that the site/program documentation requires, this is a finding.\n\n If the operating system is in non-compliance with the Information Assurance\nVulnerability Management (IAVM) process, this is a finding.\n \"\n desc \"fix\", \"Install the operating system patches or updated packages\navailable from Red Hat within 30 days or sooner as local policy dictates.\"\n impact 0.5\n tag severity: 'medium'\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71999\"\n tag rid: \"SV-86623r4_rule\"\n tag stig_id: \"RHEL-07-020260\"\n tag fix_id: \"F-78351r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if input('disconnected_system')\n describe \"The system is set to a `disconnected` state and you must validate \n the state of the system packages manually\" do \n skip \"The system is set to a `disconnected` state and you must validate \n the state of the system packages manually, or through another process, if you \n have an established update and patch process, please set this control as \n `Not Applicable` with a `caevat` via an overlay.\"\n end\n else\n updates = linux_update.updates\n package_names = updates.map { |h| h[\"name\"] }\n\n describe.one do\n describe \"List of out-of-date packages\" do\n subject { package_names }\n it { should be_empty }\n end\n\n updates.each do |update|\n describe package(update[\"name\"]) do\n its(\"version\") { should eq update[\"version\"] }\n end\n end\n end\n end\n end\n","desc":"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.","descriptions":[{"data":"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.","label":"default"},{"data":"Verify the operating system security patches and updates are installed and\n up to date. Updates are required to be applied with a frequency determined by\n the site or Program Management Office (PMO).\n\n Obtain the list of available package security updates from Red Hat. The URL\n for updates is https://rhn.redhat.com/errata/. It is important to note that\n updates provided by Red Hat may not be present on the system if the underlying\n packages are not installed.\n\n Check that the available package security updates have been installed on\n the system with the following command:\n\n # yum history list | more\n Loaded plugins: langpacks, product-id, subscription-manager\n ID | Command line | Date and time | Action(s) |\n Altered\n\n -------------------------------------------------------------------------------\n 70 | install aide | 2016-05-05 10:58 | Install |\n 1\n 69 | update -y | 2016-05-04 14:34 | Update | 18 EE\n 68 | install vlc | 2016-04-21 17:12 | Install |\n 21\n 67 | update -y | 2016-04-21 17:04 | Update | 7 EE\n 66 | update -y | 2016-04-15 16:47 | E, I, U |\n 84 EE\n\n If package updates have not been performed on the system within the\n timeframe that the site/program documentation requires, this is a finding.\n\n If the operating system is in non-compliance with the Information Assurance\nVulnerability Management (IAVM) process, this is a finding.","label":"check"},{"data":"Install the operating system patches or updated packages\navailable from Red Hat within 30 days or sooner as local policy dictates.","label":"fix"}],"id":"V-71999","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71999.rb"},"tags":{"severity":"medium","gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71999","rid":"SV-86623r4_rule","stig_id":"RHEL-07-020260","fix_id":"F-78351r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system security patches and\n updates must be installed and up to date.","waiver_data":{}},{"code":"control \"V-72001\" do\n title \"The Red Hat Enterprise Linux operating system must not have\nunnecessary accounts.\"\n desc \"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all accounts on the system are assigned to an active system,\napplication, or user account.\n\n Obtain the list of authorized system accounts from the Information System\nSecurity Officer (ISSO).\n\n Check the system accounts on the system with the following command:\n\n # more /etc/passwd\n root:x:0:0:root:/root:/bin/bash\n bin:x:1:1:bin:/bin:/sbin/nologin\n daemon:x:2:2:daemon:/sbin:/sbin/nologin\n sync:x:5:0:sync:/sbin:/bin/sync\n shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown\n halt:x:7:0:halt:/sbin:/sbin/halt\n games:x:12:100:games:/usr/games:/sbin/nologin\n gopher:x:13:30:gopher:/var/gopher:/sbin/nologin\n\n Accounts such as \\\"games\\\" and \\\"gopher\\\" are not authorized accounts as\nthey do not support authorized system functions.\n\n If the accounts on the system do not match the provided documentation, or\naccounts that do not support an authorized system function are present, this is\na finding.\n \"\n desc \"fix\", \"\n Configure the system so all accounts on the system are assigned to an\nactive system, application, or user account.\n\n Remove accounts that do not support approved system activities or that\nallow for a normal user to perform administrative-level actions.\n\n Document all authorized accounts on the system.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72001\"\n tag rid: \"SV-86625r2_rule\"\n tag stig_id: \"RHEL-07-020270\"\n tag fix_id: \"F-78353r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n known_system_accounts = input('known_system_accounts')\n user_accounts = input('user_accounts')\n\n allowed_accounts = (known_system_accounts + user_accounts).uniq\n passwd.users.each do |user|\n describe user do\n it \"is listed in allowed users.\" do\n expect(subject).to(be_in allowed_accounts)\n end\n end\n end\nend\n","desc":"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.","descriptions":[{"data":"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all accounts on the system are assigned to an active system,\napplication, or user account.\n\n Obtain the list of authorized system accounts from the Information System\nSecurity Officer (ISSO).\n\n Check the system accounts on the system with the following command:\n\n # more /etc/passwd\n root:x:0:0:root:/root:/bin/bash\n bin:x:1:1:bin:/bin:/sbin/nologin\n daemon:x:2:2:daemon:/sbin:/sbin/nologin\n sync:x:5:0:sync:/sbin:/bin/sync\n shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown\n halt:x:7:0:halt:/sbin:/sbin/halt\n games:x:12:100:games:/usr/games:/sbin/nologin\n gopher:x:13:30:gopher:/var/gopher:/sbin/nologin\n\n Accounts such as \"games\" and \"gopher\" are not authorized accounts as\nthey do not support authorized system functions.\n\n If the accounts on the system do not match the provided documentation, or\naccounts that do not support an authorized system function are present, this is\na finding.","label":"check"},{"data":"Configure the system so all accounts on the system are assigned to an\nactive system, application, or user account.\n\n Remove accounts that do not support approved system activities or that\nallow for a normal user to perform administrative-level actions.\n\n Document all authorized accounts on the system.","label":"fix"}],"id":"V-72001","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72001.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72001","rid":"SV-86625r2_rule","stig_id":"RHEL-07-020270","fix_id":"F-78353r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have\nunnecessary accounts.","waiver_data":{}},{"code":"control \"V-72003\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all Group Identifiers (GIDs) referenced in the /etc/passwd file are\ndefined in the /etc/group file.\"\n desc \"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all GIDs referenced in the \\\"/etc/passwd\\\" file are defined in the\n\\\"/etc/group\\\" file.\n\n Check that all referenced GIDs exist with the following command:\n\n # pwck -r\n\n If GIDs referenced in \\\"/etc/passwd\\\" file are returned as not defined in\n\\\"/etc/group\\\" file, this is a finding.\n \"\n desc \"fix\", \"Configure the system to define all GIDs found in the\n\\\"/etc/passwd\\\" file by modifying the \\\"/etc/group\\\" file to add any\nnon-existent group referenced in the \\\"/etc/passwd\\\" file, or change the GIDs\nreferenced in the \\\"/etc/passwd\\\" file to a group that exists in\n\\\"/etc/group\\\".\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000104-GPOS-00051\"\n tag gid: \"V-72003\"\n tag rid: \"SV-86627r2_rule\"\n tag stig_id: \"RHEL-07-020300\"\n tag fix_id: \"F-78355r1_fix\"\n tag cci: [\"CCI-000764\"]\n tag nist: [\"IA-2\"]\n\n passwd.gids.each do |gid|\n describe etc_group do\n its('gids') { should include gid.to_i }\n end\n end\nend\n","desc":"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.","descriptions":[{"data":"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all GIDs referenced in the \"/etc/passwd\" file are defined in the\n\"/etc/group\" file.\n\n Check that all referenced GIDs exist with the following command:\n\n # pwck -r\n\n If GIDs referenced in \"/etc/passwd\" file are returned as not defined in\n\"/etc/group\" file, this is a finding.","label":"check"},{"data":"Configure the system to define all GIDs found in the\n\"/etc/passwd\" file by modifying the \"/etc/group\" file to add any\nnon-existent group referenced in the \"/etc/passwd\" file, or change the GIDs\nreferenced in the \"/etc/passwd\" file to a group that exists in\n\"/etc/group\".","label":"fix"}],"id":"V-72003","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72003.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000104-GPOS-00051","gid":"V-72003","rid":"SV-86627r2_rule","stig_id":"RHEL-07-020300","fix_id":"F-78355r1_fix","cci":["CCI-000764"],"nist":["IA-2"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all Group Identifiers (GIDs) referenced in the /etc/passwd file are\ndefined in the /etc/group file.","waiver_data":{}},{"code":"control \"V-72005\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the root account must be the only account having unrestricted access to\nthe system.\"\n desc \"If an account other than root also has a User Identifier (UID) of\n\\\"0\\\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \\\"0\\\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check the system for duplicate UID \\\"0\\\" assignments with the following\ncommand:\n\n # awk -F: '$3 == 0 {print $1}' /etc/passwd\n\n If any accounts other than root have a UID of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Change the UID of any account on the system, other than root, that has a\nUID of \\\"0\\\".\n\n If the account is associated with system commands or applications, the UID\nshould be changed to one greater than \\\"0\\\" but less than \\\"1000\\\". Otherwise,\nassign a UID of greater than \\\"1000\\\" that has not already been assigned.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72005\"\n tag rid: \"SV-86629r2_rule\"\n tag stig_id: \"RHEL-07-020310\"\n tag fix_id: \"F-78357r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe passwd.uids(0) do\n its('users') { should cmp 'root' }\n its('entries.length') { should eq 1 }\n end\nend\n","desc":"If an account other than root also has a User Identifier (UID) of\n\"0\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \"0\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.","descriptions":[{"data":"If an account other than root also has a User Identifier (UID) of\n\"0\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \"0\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the system for duplicate UID \"0\" assignments with the following\ncommand:\n\n # awk -F: '$3 == 0 {print $1}' /etc/passwd\n\n If any accounts other than root have a UID of \"0\", this is a finding.","label":"check"},{"data":"Change the UID of any account on the system, other than root, that has a\nUID of \"0\".\n\n If the account is associated with system commands or applications, the UID\nshould be changed to one greater than \"0\" but less than \"1000\". Otherwise,\nassign a UID of greater than \"1000\" that has not already been assigned.","label":"fix"}],"id":"V-72005","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72005.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72005","rid":"SV-86629r2_rule","stig_id":"RHEL-07-020310","fix_id":"F-78357r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the root account must be the only account having unrestricted access to\nthe system.","waiver_data":{}},{"code":"control \"V-72007\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid owner.\"\n desc \"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \\\"UID\\\" as the UID of the un-owned\nfiles.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories on the system have a valid owner.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nouser\n\n If any files on the system do not have an assigned owner, this is a finding.\n \"\n desc \"fix\", \"\n Either remove all files and directories from the system that do not have a\nvalid user, or assign a valid user to all unowned files and directories on the\nsystem with the \\\"chown\\\" command:\n\n # chown \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72007\"\n tag rid: \"SV-86631r3_rule\"\n tag stig_id: \"RHEL-07-020320\"\n tag fix_id: \"F-78359r1_fix\"\n tag cci: [\"CCI-002165\"]\n tag nist: [\"AC-3 (4)\"]\n\n command('grep -v \"nodev\" /proc/filesystems | awk \\'NF{ print $NF }\\'').\n stdout.strip.split(\"\\n\").each do |fs|\n describe command(\"find / -xdev -xautofs -fstype #{fs} -nouser\") do\n its('stdout.strip') { should be_empty }\n end\n end\nend\n","desc":"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \"UID\" as the UID of the un-owned\nfiles.","descriptions":[{"data":"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \"UID\" as the UID of the un-owned\nfiles.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories on the system have a valid owner.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nouser\n\n If any files on the system do not have an assigned owner, this is a finding.","label":"check"},{"data":"Either remove all files and directories from the system that do not have a\nvalid user, or assign a valid user to all unowned files and directories on the\nsystem with the \"chown\" command:\n\n # chown ","label":"fix"}],"id":"V-72007","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72007.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72007","rid":"SV-86631r3_rule","stig_id":"RHEL-07-020320","fix_id":"F-78359r1_fix","cci":["CCI-002165"],"nist":["AC-3 (4)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid owner.","waiver_data":{}},{"code":"control \"V-72009\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid group owner.\"\n desc \"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories on the system have a valid group.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nogroup\n\n If any files on the system do not have an assigned group, this is a finding.\n \"\n desc \"fix\", \"\n Either remove all files and directories from the system that do not have a\nvalid group, or assign a valid group to all files and directories on the system\nwith the \\\"chgrp\\\" command:\n\n # chgrp \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72009\"\n tag rid: \"SV-86633r3_rule\"\n tag stig_id: \"RHEL-07-020330\"\n tag fix_id: \"F-78361r1_fix\"\n tag cci: [\"CCI-002165\"]\n tag nist: [\"AC-3 (4)\"]\n\n command('grep -v \"nodev\" /proc/filesystems | awk \\'NF{ print $NF }\\'').\n stdout.strip.split(\"\\n\").each do |fs|\n describe command(\"find / -xdev -xautofs -fstype #{fs} -nogroup\") do\n its('stdout.strip') { should be_empty }\n end\n end\nend\n","desc":"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.","descriptions":[{"data":"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories on the system have a valid group.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nogroup\n\n If any files on the system do not have an assigned group, this is a finding.","label":"check"},{"data":"Either remove all files and directories from the system that do not have a\nvalid group, or assign a valid group to all files and directories on the system\nwith the \"chgrp\" command:\n\n # chgrp ","label":"fix"}],"id":"V-72009","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72009.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72009","rid":"SV-86633r3_rule","stig_id":"RHEL-07-020330","fix_id":"F-78361r1_fix","cci":["CCI-002165"],"nist":["AC-3 (4)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid group owner.","waiver_data":{}},{"code":"control \"V-72011\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive users have a home directory assigned in the\n/etc/passwd file.\"\n desc \"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify local interactive users on the system have a home directory assigned.\n\n Check for missing local interactive user home directories with the\nfollowing command:\n\n # pwck -r\n user 'lp': directory '/var/spool/lpd' does not exist\n user 'news': directory '/var/spool/news' does not exist\n user 'uucp': directory '/var/spool/uucp' does not exist\n user 'smithj': directory '/home/smithj' does not exist\n\n Ask the System Administrator (SA) if any users found without home\ndirectories are local interactive users. If the SA is unable to provide a\nresponse, check for users with a User Identifier (UID) of 1000 or greater with\nthe following command:\n\n # cut -d: -f 1,3 /etc/passwd | egrep \\\":[1-4][0-9]{2}$|:[0-9]{1,2}$\\\"\n\n If any interactive users do not have a home directory assigned, this is a\nfinding.\n \"\n desc \"fix\", \"Assign home directories to all local interactive users that\ncurrently do not have a home directory assigned.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72011\"\n tag rid: \"SV-86635r2_rule\"\n tag stig_id: \"RHEL-07-020600\"\n tag fix_id: \"F-78363r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n describe directory(user_info.home) do\n it { should exist }\n end\n end\nend\n","desc":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","descriptions":[{"data":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify local interactive users on the system have a home directory assigned.\n\n Check for missing local interactive user home directories with the\nfollowing command:\n\n # pwck -r\n user 'lp': directory '/var/spool/lpd' does not exist\n user 'news': directory '/var/spool/news' does not exist\n user 'uucp': directory '/var/spool/uucp' does not exist\n user 'smithj': directory '/home/smithj' does not exist\n\n Ask the System Administrator (SA) if any users found without home\ndirectories are local interactive users. If the SA is unable to provide a\nresponse, check for users with a User Identifier (UID) of 1000 or greater with\nthe following command:\n\n # cut -d: -f 1,3 /etc/passwd | egrep \":[1-4][0-9]{2}$|:[0-9]{1,2}$\"\n\n If any interactive users do not have a home directory assigned, this is a\nfinding.","label":"check"},{"data":"Assign home directories to all local interactive users that\ncurrently do not have a home directory assigned.","label":"fix"}],"id":"V-72011","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72011.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72011","rid":"SV-86635r2_rule","stig_id":"RHEL-07-020600","fix_id":"F-78363r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive users have a home directory assigned in the\n/etc/passwd file.","waiver_data":{}},{"code":"control \"V-72013\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user accounts, upon creation, are assigned a home\ndirectory.\"\n desc \"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all local interactive users on the system are assigned a home\ndirectory upon creation.\n\n Check to see if the system is configured to create home directories for\nlocal interactive users with the following command:\n\n # grep -i create_home /etc/login.defs\n CREATE_HOME yes\n\n If the value for \\\"CREATE_HOME\\\" parameter is not set to \\\"yes\\\", the line\nis missing, or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to assign home directories to all new local\ninteractive users by setting the \\\"CREATE_HOME\\\" parameter in\n\\\"/etc/login.defs\\\" to \\\"yes\\\" as follows.\n\n CREATE_HOME yes\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72013\"\n tag rid: \"SV-86637r2_rule\"\n tag stig_id: \"RHEL-07-020610\"\n tag fix_id: \"F-78365r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe login_defs do\n its('CREATE_HOME') { should eq 'yes' }\n end\nend\n","desc":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","descriptions":[{"data":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all local interactive users on the system are assigned a home\ndirectory upon creation.\n\n Check to see if the system is configured to create home directories for\nlocal interactive users with the following command:\n\n # grep -i create_home /etc/login.defs\n CREATE_HOME yes\n\n If the value for \"CREATE_HOME\" parameter is not set to \"yes\", the line\nis missing, or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to assign home directories to all new local\ninteractive users by setting the \"CREATE_HOME\" parameter in\n\"/etc/login.defs\" to \"yes\" as follows.\n\n CREATE_HOME yes","label":"fix"}],"id":"V-72013","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72013.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72013","rid":"SV-86637r2_rule","stig_id":"RHEL-07-020610","fix_id":"F-78365r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user accounts, upon creation, are assigned a home\ndirectory.","waiver_data":{}},{"code":"control \"V-72015\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are defined in the /etc/passwd\nfile.\"\n desc \"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive\nnon-privileged users on the system with the following command:\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n\n smithj:1001:/home/smithj\n\n Note: This may miss interactive users that have been assigned a privileged\nUID. Evidence of interactive use may be obtained from a number of log files\ncontaining system logon information.\n\n Check that all referenced home directories exist with the following command:\n\n # pwck -r\n user 'smithj': directory '/home/smithj' does not exist\n\n If any home directories referenced in \\\"/etc/passwd\\\" are returned as not\ndefined, this is a finding.\n \"\n desc \"fix\", \"\n Create home directories to all local interactive users that currently do\nnot have a home directory assigned. Use the following commands to create the\nuser home directory assigned in \\\"/etc/ passwd\\\":\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\", a UID of \\\"smithj\\\", and a Group Identifier (GID) of\n\\\"users\\\" assigned in \\\"/etc/passwd\\\".\n\n # mkdir /home/smithj\n # chown smithj /home/smithj\n # chgrp users /home/smithj\n # chmod 0750 /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72015\"\n tag rid: \"SV-86639r2_rule\"\n tag stig_id: \"RHEL-07-020620\"\n tag fix_id: \"F-78367r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n describe directory(user_info.home) do\n it { should exist }\n end\n end\nend\n","desc":"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.","descriptions":[{"data":"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive\nnon-privileged users on the system with the following command:\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n\n smithj:1001:/home/smithj\n\n Note: This may miss interactive users that have been assigned a privileged\nUID. Evidence of interactive use may be obtained from a number of log files\ncontaining system logon information.\n\n Check that all referenced home directories exist with the following command:\n\n # pwck -r\n user 'smithj': directory '/home/smithj' does not exist\n\n If any home directories referenced in \"/etc/passwd\" are returned as not\ndefined, this is a finding.","label":"check"},{"data":"Create home directories to all local interactive users that currently do\nnot have a home directory assigned. Use the following commands to create the\nuser home directory assigned in \"/etc/ passwd\":\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\", a UID of \"smithj\", and a Group Identifier (GID) of\n\"users\" assigned in \"/etc/passwd\".\n\n # mkdir /home/smithj\n # chown smithj /home/smithj\n # chgrp users /home/smithj\n # chmod 0750 /home/smithj","label":"fix"}],"id":"V-72015","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72015.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72015","rid":"SV-86639r2_rule","stig_id":"RHEL-07-020620","fix_id":"F-78367r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are defined in the /etc/passwd\nfile.","waiver_data":{}},{"code":"control \"V-72017\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories have mode 0750 or less\npermissive.\"\n desc \"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users has a\nmode of \\\"0750\\\" or less permissive.\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If home directories referenced in \\\"/etc/passwd\\\" do not have a mode of\n\\\"0750\\\" or less permissive, this is a finding.\n \"\n desc \"fix\", \"\n Change the mode of interactive user's home directories to \\\"0750\\\". To\nchange the mode of a local interactive user's home directory, use the following\ncommand:\n\n Note: The example will be for the user \\\"smithj\\\".\n\n # chmod 0750 /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72017\"\n tag rid: \"SV-86641r3_rule\"\n tag stig_id: \"RHEL-07-020630\"\n tag fix_id: \"F-78369r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -maxdepth 0 -perm /027\").stdout.split(\"\\n\")\n end\n describe \"Home directories with excessive permissions\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.","descriptions":[{"data":"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users has a\nmode of \"0750\" or less permissive.\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If home directories referenced in \"/etc/passwd\" do not have a mode of\n\"0750\" or less permissive, this is a finding.","label":"check"},{"data":"Change the mode of interactive user's home directories to \"0750\". To\nchange the mode of a local interactive user's home directory, use the following\ncommand:\n\n Note: The example will be for the user \"smithj\".\n\n # chmod 0750 /home/smithj","label":"fix"}],"id":"V-72017","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72017.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72017","rid":"SV-86641r3_rule","stig_id":"RHEL-07-020630","fix_id":"F-78369r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories have mode 0750 or less\npermissive.","waiver_data":{}},{"code":"control \"V-72019\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are owned by their respective\nusers.\"\n desc \"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If any home directories referenced in \\\"/etc/passwd\\\" are not owned by the\ninteractive user, this is a finding.\n \"\n desc \"fix\", \"\n Change the owner of a local interactive user's home directories to that\nowner. To change the owner of a local interactive user's home directory, use\nthe following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\".\n\n # chown smithj /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72019\"\n tag rid: \"SV-86643r5_rule\"\n tag stig_id: \"RHEL-07-020640\"\n tag fix_id: \"F-78371r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n describe directory(user_info.home) do\n it { should exist }\n its('owner') { should eq user_info.username }\n end\n end\nend\n","desc":"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.","descriptions":[{"data":"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If any home directories referenced in \"/etc/passwd\" are not owned by the\ninteractive user, this is a finding.","label":"check"},{"data":"Change the owner of a local interactive user's home directories to that\nowner. To change the owner of a local interactive user's home directory, use\nthe following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj","label":"fix"}],"id":"V-72019","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72019.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72019","rid":"SV-86643r5_rule","stig_id":"RHEL-07-020640","fix_id":"F-78371r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are owned by their respective\nusers.","waiver_data":{}},{"code":"control \"V-72021\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are group-owned by the home\ndirectory owners primary group.\"\n desc \"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users is\ngroup-owned by that user's primary GID.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n Check the user's primary group with the following command:\n\n # grep users /etc/group\n\n users:x:250:smithj,jonesj,jacksons\n\n If the user home directory referenced in \\\"/etc/passwd\\\" is not group-owned\nby that user's primary GID, this is a finding.\n \"\n desc \"fix\", \"\n Change the group owner of a local interactive user's home directory to the\ngroup found in \\\"/etc/passwd\\\". To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\", and has a primary group of users.\n\n # chgrp users /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72021\"\n tag rid: \"SV-86645r5_rule\"\n tag stig_id: \"RHEL-07-020650\"\n tag fix_id: \"F-78373r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -maxdepth 0 -not -gid #{user_info.gid}\").stdout.split(\"\\n\")\n end\n describe \"Home directories that are not group-owned by the user's primary GID\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.","descriptions":[{"data":"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users is\ngroup-owned by that user's primary GID.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n Check the user's primary group with the following command:\n\n # grep users /etc/group\n\n users:x:250:smithj,jonesj,jacksons\n\n If the user home directory referenced in \"/etc/passwd\" is not group-owned\nby that user's primary GID, this is a finding.","label":"check"},{"data":"Change the group owner of a local interactive user's home directory to the\ngroup found in \"/etc/passwd\". To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\", and has a primary group of users.\n\n # chgrp users /home/smithj","label":"fix"}],"id":"V-72021","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72021.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72021","rid":"SV-86645r5_rule","stig_id":"RHEL-07-020650","fix_id":"F-78373r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are group-owned by the home\ndirectory owners primary group.","waiver_data":{}},{"code":"control \"V-72023\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are owned by the owner of the home directory.\"\n desc \"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories in a local interactive user's home\ndirectory are owned by the user.\n\n Check the owner of all files and directories in a local interactive user's\nhome directory with the following command:\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -lLR /home/smithj\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the home directory\nuser, this is a finding.\n \"\n desc \"fix\", \"\n Change the owner of a local interactive user's files and directories to\nthat owner. To change the owner of a local interactive user's files and\ndirectories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\".\n\n # chown smithj /home/smithj/\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72023\"\n tag rid: \"SV-86647r2_rule\"\n tag stig_id: \"RHEL-07-020660\"\n tag fix_id: \"F-78375r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -xdev -xautofs -not -user #{user_info.username}\").stdout.split(\"\\n\")\n end\n describe \"Files and directories that are not owned by the user\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.","descriptions":[{"data":"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories in a local interactive user's home\ndirectory are owned by the user.\n\n Check the owner of all files and directories in a local interactive user's\nhome directory with the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR /home/smithj\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the home directory\nuser, this is a finding.","label":"check"},{"data":"Change the owner of a local interactive user's files and directories to\nthat owner. To change the owner of a local interactive user's files and\ndirectories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj/","label":"fix"}],"id":"V-72023","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72023.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72023","rid":"SV-86647r2_rule","stig_id":"RHEL-07-020660","fix_id":"F-78375r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are owned by the owner of the home directory.","waiver_data":{}},{"code":"control \"V-72025\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are group-owned by a group of which the home directory owner is a\nmember.\"\n desc \"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories in a local interactive user home directory\nare group-owned by a group the user is a member of.\n\n Check the group owner of all files and directories in a local interactive\nuser's home directory with the following command:\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -lLR ///\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj sa 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the group home\ndirectory user, check to see if the user is a member of that group with the\nfollowing command:\n\n # grep smithj /etc/group\n sa:x:100:juan,shelley,bob,smithj\n smithj:x:521:smithj\n\n If the user is not a member of a group that group owns file(s) in a local\ninteractive user's home directory, this is a finding.\n \"\n desc \"fix\", \"\n Change the group of a local interactive user's files and directories to a\ngroup that the interactive user is a member of. To change the group owner of a\nlocal interactive user's files and directories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\" and is a member of the users group.\n\n # chgrp users /home/smithj/\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72025\"\n tag rid: \"SV-86649r2_rule\"\n tag stig_id: \"RHEL-07-020670\"\n tag fix_id: \"F-78377r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n find_args = \"\"\n user_info.groups.each { |curr_group|\n # some key files and secure dirs (like .ssh) are group owned 'root'\n find_args = find_args + \"-not -group #{curr_group} -o root\"\n }\n findings = findings + command(\"find #{user_info.home} -xdev -xautofs #{find_args}\").stdout.split(\"\\n\")\n end\n describe \"Home directory files with incorrect group ownership or not 'root' owned\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.","descriptions":[{"data":"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories in a local interactive user home directory\nare group-owned by a group the user is a member of.\n\n Check the group owner of all files and directories in a local interactive\nuser's home directory with the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR ///\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj sa 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the group home\ndirectory user, check to see if the user is a member of that group with the\nfollowing command:\n\n # grep smithj /etc/group\n sa:x:100:juan,shelley,bob,smithj\n smithj:x:521:smithj\n\n If the user is not a member of a group that group owns file(s) in a local\ninteractive user's home directory, this is a finding.","label":"check"},{"data":"Change the group of a local interactive user's files and directories to a\ngroup that the interactive user is a member of. To change the group owner of a\nlocal interactive user's files and directories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\" and is a member of the users group.\n\n # chgrp users /home/smithj/","label":"fix"}],"id":"V-72025","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72025.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72025","rid":"SV-86649r2_rule","stig_id":"RHEL-07-020670","fix_id":"F-78377r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are group-owned by a group of which the home directory owner is a\nmember.","waiver_data":{}},{"code":"control \"V-72027\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories have a mode of 0750 or less permissive.\"\n desc \"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories contained in a local interactive user home\ndirectory, excluding local initialization files, have a mode of \\\"0750\\\".\n\n Check the mode of all non-initialization files in a local interactive user\nhome directory with the following command:\n\n Files that begin with a \\\".\\\" are excluded from this requirement.\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -lLR /home/smithj\n -rwxr-x--- 1 smithj smithj 18 Mar 5 17:06 file1\n -rwxr----- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r-x--- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with a mode more permissive than \\\"0750\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Set the mode on files and directories in the local interactive user home\ndirectory with the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\" and is a member of the users group.\n\n # chmod 0750 /home/smithj/\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72027\"\n tag rid: \"SV-86651r2_rule\"\n tag stig_id: \"RHEL-07-020680\"\n tag fix_id: \"F-78379r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -xdev ! -name '.*' -perm /027 ! -type l\").stdout.split(\"\\n\")\n end\n describe \"Home directories with excessive permissions\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.","descriptions":[{"data":"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories contained in a local interactive user home\ndirectory, excluding local initialization files, have a mode of \"0750\".\n\n Check the mode of all non-initialization files in a local interactive user\nhome directory with the following command:\n\n Files that begin with a \".\" are excluded from this requirement.\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR /home/smithj\n -rwxr-x--- 1 smithj smithj 18 Mar 5 17:06 file1\n -rwxr----- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r-x--- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with a mode more permissive than \"0750\", this is a\nfinding.","label":"check"},{"data":"Set the mode on files and directories in the local interactive user home\ndirectory with the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\" and is a member of the users group.\n\n # chmod 0750 /home/smithj/","label":"fix"}],"id":"V-72027","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72027.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72027","rid":"SV-86651r2_rule","stig_id":"RHEL-07-020680","fix_id":"F-78379r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories have a mode of 0750 or less permissive.","waiver_data":{}},{"code":"control \"V-72029\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for interactive users are owned by the home\ndirectory user or root.\"\n desc \"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\\\"/home/smithj\\\" and a primary group of \\\"users\\\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.\n \"\n desc \"fix\", \"\n Set the owner of the local initialization files for interactive users to\neither the directory owner or root with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\\\"/home/smithj\\\".\n\n # chown smithj /home/smithj/.[^.]*\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72029\"\n tag rid: \"SV-86653r3_rule\"\n tag stig_id: \"RHEL-07-020690\"\n tag fix_id: \"F-78381r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -name '.*' -not -user #{user_info.username} -a -not -user root\").stdout.split(\"\\n\")\n end\n describe \"Files and Directories not owned by the user or root of the parent home directory\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","descriptions":[{"data":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\" and a primary group of \"users\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.","label":"check"},{"data":"Set the owner of the local initialization files for interactive users to\neither the directory owner or root with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj/.[^.]*","label":"fix"}],"id":"V-72029","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72029.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72029","rid":"SV-86653r3_rule","stig_id":"RHEL-07-020690","fix_id":"F-78381r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for interactive users are owned by the home\ndirectory user or root.","waiver_data":{}},{"code":"control \"V-72031\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for local interactive users are be\ngroup-owned by the users primary group or root.\"\n desc \"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\\\"/home/smithj\\\" and a primary group of \\\"users\\\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.\n \"\n desc \"fix\", \"\n Change the group owner of a local interactive user's files to the group\nfound in \\\"/etc/passwd\\\" for the user. To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\", and has a primary group of users.\n\n # chgrp users /home/smithj/.[^.]*\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72031\"\n tag rid: \"SV-86655r4_rule\"\n tag stig_id: \"RHEL-07-020700\"\n tag fix_id: \"F-78383r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n findings = findings + command(\"find #{user_info.home} -name '.*' -not -gid #{user_info.gid} -not -group root\").stdout.split(\"\\n\")\n end\n describe findings do\n its('length') { should == 0 }\n end\nend\n","desc":"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.","descriptions":[{"data":"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\" and a primary group of \"users\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.","label":"check"},{"data":"Change the group owner of a local interactive user's files to the group\nfound in \"/etc/passwd\" for the user. To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\", and has a primary group of users.\n\n # chgrp users /home/smithj/.[^.]*","label":"fix"}],"id":"V-72031","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72031.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72031","rid":"SV-86655r4_rule","stig_id":"RHEL-07-020700","fix_id":"F-78383r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for local interactive users are be\ngroup-owned by the users primary group or root.","waiver_data":{}},{"code":"control \"V-72033\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files have mode 0740 or less permissive.\"\n desc \"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that all local initialization files have a mode of \\\"0740\\\" or less\npermissive.\n\n Check the mode on all local initialization files with the following command:\n\n Note: The example will be for the \\\"smithj\\\" user, who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr----- 1 smithj users 896 Mar 10 2011 .profile\n -rwxr----- 1 smithj users 497 Jan 6 2007 .login\n -rwxr----- 1 smithj users 886 Jan 6 2007 .something\n\n If any local initialization files have a mode more permissive than\n\\\"0740\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the mode of the local initialization files to \\\"0740\\\" with the\nfollowing command:\n\n Note: The example will be for the \\\"smithj\\\" user, who has a home directory\nof \\\"/home/smithj\\\".\n\n # chmod 0740 /home/smithj/.[^.]*\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72033\"\n tag rid: \"SV-86657r3_rule\"\n tag stig_id: \"RHEL-07-020710\"\n tag fix_id: \"F-78385r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n findings = findings + command(\"find #{user_info.home} -xdev -maxdepth 1 -name '.*' -type f -perm /037\").stdout.split(\"\\n\")\n end\n describe findings do\n it { should be_empty }\n end\nend\n","desc":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","descriptions":[{"data":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all local initialization files have a mode of \"0740\" or less\npermissive.\n\n Check the mode on all local initialization files with the following command:\n\n Note: The example will be for the \"smithj\" user, who has a home directory\nof \"/home/smithj\".\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr----- 1 smithj users 896 Mar 10 2011 .profile\n -rwxr----- 1 smithj users 497 Jan 6 2007 .login\n -rwxr----- 1 smithj users 886 Jan 6 2007 .something\n\n If any local initialization files have a mode more permissive than\n\"0740\", this is a finding.","label":"check"},{"data":"Set the mode of the local initialization files to \"0740\" with the\nfollowing command:\n\n Note: The example will be for the \"smithj\" user, who has a home directory\nof \"/home/smithj\".\n\n # chmod 0740 /home/smithj/.[^.]*","label":"fix"}],"id":"V-72033","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72033.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72033","rid":"SV-86657r3_rule","stig_id":"RHEL-07-020710","fix_id":"F-78385r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files have mode 0740 or less permissive.","waiver_data":{}},{"code":"control \"V-72035\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user initialization files executable search paths\ncontain only paths that resolve to the users home directory.\"\n desc \"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that all local interactive user initialization files' executable\nsearch path statements do not contain statements that will reference a working\ndirectory other than the users' home directory.\n\n Check the executable search path statement for all local interactive user\ninitialization files in the users' home directory with the following commands:\n\n Note: The example will be for the smithj user, which has a home directory\nof \\\"/home/smithj\\\".\n\n # grep -i path /home/smithj/.*\n /home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin\n /home/smithj/.bash_profile:export PATH\n\n If any local interactive user initialization files have executable search\npath statements that include directories outside of their home directory, this\nis a finding.\n \"\n desc \"fix\", \"\n Edit the local interactive user initialization files to change any PATH\nvariable statements that reference directories other than their home directory.\n\n If a local interactive user requires path variables to reference a\ndirectory owned by the application, it must be documented with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72035\"\n tag rid: \"SV-86659r4_rule\"\n tag stig_id: \"RHEL-07-020720\"\n tag fix_id: \"F-78387r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n grep_results = command(\"grep -i path --exclude=\\\".bash_history\\\" #{user_info.home}/.*\").stdout.split(\"\\\\n\")\n grep_results.each do |result|\n result.slice! \"PATH=\"\n # Case when last value in exec search path is :\n if result[-1] == \":\" then\n result = result + \" \"\n end\n result.slice! \"$PATH:\"\n result.gsub! '$HOME', \"#{user_info.home}\"\n result.gsub! '~', \"#{user_info.home}\"\n line_arr = result.split(\":\")\n line_arr.delete_at(0)\n line_arr.each do |line|\n # Don't run test on line that exports PATH and is not commented out\n if !line.start_with?('export') && !line.start_with?('#') then\n # Case when :: found in exec search path or : found at beginning\n if line.strip.empty? then\n curr_work_dir = command(\"pwd\").stdout.gsub(\"\\n\", \"\")\n if curr_work_dir.start_with?(\"#{user_info.home}\") then\n line = curr_work_dir\n end\n end\n # This will fail if non-home directory found in path\n if !line.start_with?(user_info.home)\n findings.add(line)\n end\n end\n end\n end\n end\n describe.one do\n describe etc_fstab do\n its('home_mount_options') { should include 'nosuid' }\n end\n describe \"Initialization files that include executable search paths that include directories outside their home directories\" do\n subject { findings.to_a }\n it { should be_empty }\n end\n end\nend\n","desc":"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).","descriptions":[{"data":"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all local interactive user initialization files' executable\nsearch path statements do not contain statements that will reference a working\ndirectory other than the users' home directory.\n\n Check the executable search path statement for all local interactive user\ninitialization files in the users' home directory with the following commands:\n\n Note: The example will be for the smithj user, which has a home directory\nof \"/home/smithj\".\n\n # grep -i path /home/smithj/.*\n /home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin\n /home/smithj/.bash_profile:export PATH\n\n If any local interactive user initialization files have executable search\npath statements that include directories outside of their home directory, this\nis a finding.","label":"check"},{"data":"Edit the local interactive user initialization files to change any PATH\nvariable statements that reference directories other than their home directory.\n\n If a local interactive user requires path variables to reference a\ndirectory owned by the application, it must be documented with the ISSO.","label":"fix"}],"id":"V-72035","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72035.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72035","rid":"SV-86659r4_rule","stig_id":"RHEL-07-020720","fix_id":"F-78387r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user initialization files executable search paths\ncontain only paths that resolve to the users home directory.","waiver_data":{}},{"code":"control \"V-72037\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat local initialization files do not execute world-writable programs.\"\n if input('disable_slow_controls')\n desc \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.\"\n else\n desc \"If user start-up files execute world-writable programs, especially in\nunprotected directories, they could be maliciously modified to destroy user\nfiles or otherwise compromise the system at the user level. If the system is\ncompromised at the user level, it is easier to elevate privileges to eventually\ncompromise the system at the root and network level.\"\n end\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that local initialization files do not execute world-writable\nprograms.\n\n Check the system for world-writable files with the following command:\n\n # find / -xdev -perm -002 -type f -exec ls -ld {} \\\\; | more\n\n For all files listed, check for their presence in the local initialization\nfiles with the following commands:\n\n Note: The example will be for a system that is configured to create users'\nhome directories in the \\\"/home\\\" directory.\n\n # grep /home/*/.*\n\n If any local initialization files are found to reference world-writable\nfiles, this is a finding.\n \"\n desc \"fix\", \"\n Set the mode on files being executed by the local initialization files with\nthe following command:\n\n # chmod 0755 \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72037\"\n tag rid: \"SV-86661r2_rule\"\n tag stig_id: \"RHEL-07-020730\"\n tag fix_id: \"F-78389r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n if input('disable_slow_controls')\n describe \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.\" do\n skip \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.\"\n end\n else\n ignore_shells = non_interactive_shells.join('|')\n\n #Get home directory for users with UID >= 1000 or UID == 0 and support interactive logins.\n dotfiles = Set[]\n u = users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries\n #For each user, build and execute a find command that identifies initialization files\n #in a user's home directory.\n u.each do |user|\n dotfiles = dotfiles + command(\"find #{user.home} -xdev -maxdepth 2 ( -name '.*' ! -name '.bash_history' ) -type f\").stdout.split(\"\\n\")\n end\n ww_files = Set[]\n ww_files = command('find / -xdev -perm -002 -type f -exec ls {} \\;').stdout.lines\n\n #To reduce the number of commands ran, we use a pattern file in the grep command below\n #So we don't have too long of a grep command, we chunk the list of ww_files\n #into strings not longer than PATTERN_FILE_MAX_LENGTH\n #Based on MAX_ARG_STRLEN, /usr/include/linux/binfmts.h\n #We cut off 100 to leave room for the rest of the arguments\n PATTERN_FILE_MAX_LENGTH=command(\"getconf PAGE_SIZE\").stdout.to_i * 32 - 100\n ww_chunked=[\"\"]\n ww_files.each do |item|\n item = item.strip\n if item.length + \"\\n\".length > PATTERN_FILE_MAX_LENGTH\n raise \"Single pattern is longer than PATTERN_FILE_MAX_LENGTH\"\n end\n if ww_chunked[-1].length + \"\\n\".length + item.length > PATTERN_FILE_MAX_LENGTH\n ww_chunked.append(\"\")\n end\n ww_chunked[-1] += \"\\n\" + item # This will leave an extra newline at the beginning of chunks\n end\n ww_chunked = ww_chunked.map(&:strip) # This gets rid of the beginning newlines\n if ww_chunked[0] == \"\"\n ww_chunked = [] # If we didn't have any ww_files, this will prevent an empty grep pattern\n end\n\n #Check each dotfile for existence of each world-writeable file\n findings = Set[]\n dotfiles.each do |dotfile|\n dotfile = dotfile.strip\n ww_chunked.each do |ww_pattern_file|\n count = command(\"grep -c -f <(echo \\\"#{ww_pattern_file}\\\") \\\"#{dotfile}\\\"\").stdout.strip.to_i\n findings << dotfile if count > 0\n end\n end\n describe \"Local initialization files that are found to reference world-writable files\" do\n subject { findings.to_a }\n it { should be_empty }\n end\n end\nend\n","desc":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","descriptions":[{"data":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that local initialization files do not execute world-writable\nprograms.\n\n Check the system for world-writable files with the following command:\n\n # find / -xdev -perm -002 -type f -exec ls -ld {} \\; | more\n\n For all files listed, check for their presence in the local initialization\nfiles with the following commands:\n\n Note: The example will be for a system that is configured to create users'\nhome directories in the \"/home\" directory.\n\n # grep /home/*/.*\n\n If any local initialization files are found to reference world-writable\nfiles, this is a finding.","label":"check"},{"data":"Set the mode on files being executed by the local initialization files with\nthe following command:\n\n # chmod 0755 ","label":"fix"}],"id":"V-72037","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72037.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72037","rid":"SV-86661r2_rule","stig_id":"RHEL-07-020730","fix_id":"F-78389r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat local initialization files do not execute world-writable programs.","waiver_data":{}},{"code":"control \"V-72039\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all system device files are correctly labeled to prevent unauthorized\nmodification.\"\n desc \"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that all system device files are correctly labeled to prevent\nunauthorized modification.\n\n List all device files on the system that are incorrectly labeled with the\nfollowing commands:\n\n Note: Device files are normally found under \\\"/dev\\\", but applications may\nplace device files in other directories and may necessitate a search of the\nentire system.\n\n #find /dev -context *:device_t:* \\\\( -type c -o -type b \\\\) -printf \\\"%p %Z\\\n \\\"\n\n #find /dev -context *:unlabeled_t:* \\\\( -type c -o -type b \\\\) -printf \\\"%p\n%Z\\\n \\\"\n\n Note: There are device files, such as \\\"/dev/vmci\\\", that are used when the\noperating system is a host virtual machine. They will not be owned by a user on\nthe system and require the \\\"device_t\\\" label to operate. These device files\nare not a finding.\n\n If there is output from either of these commands, other than already noted,\nthis is a finding.\n \"\n desc \"fix\", \"\n Run the following command to determine which package owns the device file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72039\"\n tag rid: \"SV-86663r2_rule\"\n tag stig_id: \"RHEL-07-020900\"\n tag fix_id: \"F-78391r1_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n virtual_machine = input('virtual_machine')\n\n findings = Set[]\n findings = findings + command('find / -xdev -context *:device_t:* \\( -type c -o -type b \\) -printf \"%p %Z\\n\"').stdout.split(\"\\n\")\n findings = findings + command('find / -xdev -context *:unlabeled_t:* \\( -type c -o -type b \\) -printf \"%p %Z\\n\"').stdout.split(\"\\n\")\n findings = findings + command('find / -xdev -context *:vmci_device_t:* \\( -type c -o -type b \\) -printf \"%p %Z\\n\"').stdout.split(\"\\n\")\n\n describe findings do\n if virtual_machine\n its ('length') { should cmp 1 }\n its ('first') { should include '/dev/vmci' }\n else\n its ('length') { should cmp 0 }\n end\n end\nend\n","desc":"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.","descriptions":[{"data":"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all system device files are correctly labeled to prevent\nunauthorized modification.\n\n List all device files on the system that are incorrectly labeled with the\nfollowing commands:\n\n Note: Device files are normally found under \"/dev\", but applications may\nplace device files in other directories and may necessitate a search of the\nentire system.\n\n #find /dev -context *:device_t:* \\( -type c -o -type b \\) -printf \"%p %Z \"\n\n #find /dev -context *:unlabeled_t:* \\( -type c -o -type b \\) -printf \"%p\n%Z \"\n\n Note: There are device files, such as \"/dev/vmci\", that are used when the\noperating system is a host virtual machine. They will not be owned by a user on\nthe system and require the \"device_t\" label to operate. These device files\nare not a finding.\n\n If there is output from either of these commands, other than already noted,\nthis is a finding.","label":"check"},{"data":"Run the following command to determine which package owns the device file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh ","label":"fix"}],"id":"V-72039","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72039.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72039","rid":"SV-86663r2_rule","stig_id":"RHEL-07-020900","fix_id":"F-78391r1_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all system device files are correctly labeled to prevent unauthorized\nmodification.","waiver_data":{}},{"code":"control \"V-72041\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat file systems containing user home directories are mounted to prevent files\nwith the setuid and setgid bit set from being executed.\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that contain user home directories are mounted with the\n\\\"nosuid\\\" option.\n\n Find the file system(s) that contain the user home directories with the\nfollowing command:\n\n Note: If a separate file system has not been created for the user home\ndirectories (user home directories are mounted under \\\"/\\\"), this is not a\nfinding as the \\\"nosuid\\\" option cannot be used on the \\\"/\\\" system.\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n smithj:1001:/home/smithj\n thomasr:1002:/home/thomasr\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4\nrw,relatime,discard,data=ordered,nosuid 0 2\n\n If a file system found in \\\"/etc/fstab\\\" refers to the user home directory\nfile system and it does not have the \\\"nosuid\\\" option set, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"nosuid\\\" option on\nfile systems that contain user home directories.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72041\"\n tag rid: \"SV-86665r4_rule\"\n tag stig_id: \"RHEL-07-021000\"\n tag fix_id: \"F-78393r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe mount('/home') do\n its('options') { should include 'nosuid' }\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that contain user home directories are mounted with the\n\"nosuid\" option.\n\n Find the file system(s) that contain the user home directories with the\nfollowing command:\n\n Note: If a separate file system has not been created for the user home\ndirectories (user home directories are mounted under \"/\"), this is not a\nfinding as the \"nosuid\" option cannot be used on the \"/\" system.\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1001:/home/smithj\n thomasr:1002:/home/thomasr\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4\nrw,relatime,discard,data=ordered,nosuid 0 2\n\n If a file system found in \"/etc/fstab\" refers to the user home directory\nfile system and it does not have the \"nosuid\" option set, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that contain user home directories.","label":"fix"}],"id":"V-72041","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72041.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72041","rid":"SV-86665r4_rule","stig_id":"RHEL-07-021000","fix_id":"F-78393r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat file systems containing user home directories are mounted to prevent files\nwith the setuid and setgid bit set from being executed.","waiver_data":{}},{"code":"control \"V-72043\" do\n title \"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are used\nwith removable media.\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute\n\\\"setuid\\\" and \\\"setgid\\\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \\\"setuid\\\" and \\\"setguid\\\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that are used for removable media are mounted with the\n\\\"nosuid\\\" option.\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat\nnoauto,owner,ro,nosuid 0 0\n\n If a file system found in \\\"/etc/fstab\\\" refers to removable media and it\ndoes not have the \\\"nosuid\\\" option set, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"nosuid\\\" option on\nfile systems that are associated with removable media.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72043\"\n tag rid: \"SV-86667r2_rule\"\n tag stig_id: \"RHEL-07-021010\"\n tag fix_id: \"F-78395r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n non_removable_media_fs = input('non_removable_media_fs')\n\n file_systems = etc_fstab.params\n if !file_systems.nil? and !file_systems.empty?\n file_systems.each do |file_sys_line|\n if !\"#{non_removable_media_fs}\".include?(file_sys_line['file_system_type']) then\n describe file_sys_line['mount_options'] do\n it { should include 'nosuid' }\n end\n else\n describe \"File system \\\"#{file_sys_line['file_system_type']}\\\" does not correspond to removable media.\" do\n subject { \"#{non_removable_media_fs}\".include?(file_sys_line['file_system_type']) }\n it { should eq true }\n end\n end\n end\n else\n describe \"No file systems were found.\" do\n subject { file_systems.nil? }\n it { should eq true }\n end\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are used for removable media are mounted with the\n\"nosuid\" option.\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat\nnoauto,owner,ro,nosuid 0 0\n\n If a file system found in \"/etc/fstab\" refers to removable media and it\ndoes not have the \"nosuid\" option set, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that are associated with removable media.","label":"fix"}],"id":"V-72043","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72043.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72043","rid":"SV-86667r2_rule","stig_id":"RHEL-07-021010","fix_id":"F-78395r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are used\nwith removable media.","waiver_data":{}},{"code":"control \"V-72045\" do\n title \"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are\nbeing imported via Network File System (NFS).\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute\n\\\"setuid\\\" and \\\"setgid\\\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \\\"setuid\\\" and \\\"setguid\\\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that are being NFS imported are configured with the\n\\\"nosuid\\\" option.\n\n Find the file system(s) that contain the directories being exported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 0 0\n\n If a file system found in \\\"/etc/fstab\\\" refers to NFS and it does not have\nthe \\\"nosuid\\\" option set, this is a finding.\n\n Verify the NFS is mounted with the \\\"nosuid\\\" option:\n\n # mount | grep nfs | grep nosuid\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"nosuid\\\" option on\nfile systems that are being imported via NFS.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72045\"\n tag rid: \"SV-86669r2_rule\"\n tag stig_id: \"RHEL-07-021020\"\n tag fix_id: \"F-78397r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n nfs_systems = etc_fstab.nfs_file_systems.entries\n if !nfs_systems.nil? and !nfs_systems.empty?\n nfs_systems.each do |partition|\n describe partition do\n its('mount_options') { should include 'nosuid' }\n end\n end\n else\n describe \"No NFS file systems were found.\" do\n subject { nfs_systems.nil? or nfs_systems.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are being NFS imported are configured with the\n\"nosuid\" option.\n\n Find the file system(s) that contain the directories being exported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 0 0\n\n If a file system found in \"/etc/fstab\" refers to NFS and it does not have\nthe \"nosuid\" option set, this is a finding.\n\n Verify the NFS is mounted with the \"nosuid\" option:\n\n # mount | grep nfs | grep nosuid\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that are being imported via NFS.","label":"fix"}],"id":"V-72045","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72045.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72045","rid":"SV-86669r2_rule","stig_id":"RHEL-07-021020","fix_id":"F-78397r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are\nbeing imported via Network File System (NFS).","waiver_data":{}},{"code":"control \"V-72047\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all world-writable directories are group-owned by root, sys, bin, or an\napplication group.\"\n desc \"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all world-writable directories are group-owned by root, sys, bin, or\nan application group.\n\n Check the system for world-writable directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -xdev -perm -002 -type d -fstype xfs -exec ls -lLd {} \\\\;\n drwxrwxrwt 2 root root 40 Aug 26 13:07 /dev/mqueue\n drwxrwxrwt 2 root root 220 Aug 26 13:23 /dev/shm\n drwxrwxrwt 14 root root 4096 Aug 26 13:29 /tmp\n\n If any world-writable directories are not owned by root, sys, bin, or an\napplication group associated with the directory, this is a finding.\n \"\n desc \"fix\", \"\n Change the group of the world-writable directories to root with the\nfollowing command:\n\n # chgrp root \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72047\"\n tag rid: \"SV-86671r4_rule\"\n tag stig_id: \"RHEL-07-021030\"\n tag fix_id: \"F-78399r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n application_groups = input('application_groups')\n\n ww_dirs = Set[]\n partitions = etc_fstab.params.map{|partition| partition['file_system_type']}.uniq\n partitions.each do |part|\n cmd = \"find / -perm -002 -xdev -type d -fstype #{part} -exec ls -lLd {} \\\\;\"\n ww_dirs = ww_dirs + command(cmd).stdout.split(\"\\n\")\n end\n\n ww_dirs.to_a.each do |curr_dir|\n dir_arr = curr_dir.split(' ')\n describe file(dir_arr.last) do\n its('group') { should be_in [\"root\",\"sys\",\"bin\"] + application_groups }\n end\n end\nend\n","desc":"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.","descriptions":[{"data":"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all world-writable directories are group-owned by root, sys, bin, or\nan application group.\n\n Check the system for world-writable directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -xdev -perm -002 -type d -fstype xfs -exec ls -lLd {} \\;\n drwxrwxrwt 2 root root 40 Aug 26 13:07 /dev/mqueue\n drwxrwxrwt 2 root root 220 Aug 26 13:23 /dev/shm\n drwxrwxrwt 14 root root 4096 Aug 26 13:29 /tmp\n\n If any world-writable directories are not owned by root, sys, bin, or an\napplication group associated with the directory, this is a finding.","label":"check"},{"data":"Change the group of the world-writable directories to root with the\nfollowing command:\n\n # chgrp root ","label":"fix"}],"id":"V-72047","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72047.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72047","rid":"SV-86671r4_rule","stig_id":"RHEL-07-021030","fix_id":"F-78399r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all world-writable directories are group-owned by root, sys, bin, or an\napplication group.","waiver_data":{}},{"code":"control \"V-72049\" do\n title \"The Red Hat Enterprise Linux operating system must set the umask value\nto 077 for all local interactive user accounts.\"\n desc \"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \\\"0\\\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the default umask for all local interactive users is \\\"077\\\".\n\n Identify the locations of all local interactive user home directories by\nlooking at the \\\"/etc/passwd\\\" file.\n\n Check all local interactive user initialization files for interactive users\nwith the following command:\n\n Note: The example is for a system that is configured to create users home\ndirectories in the \\\"/home\\\" directory.\n\n # grep -i umask /home/*/.*\n\n If any local interactive user initialization files are found to have a\numask statement that has a value less restrictive than \\\"077\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Remove the umask statement from all local interactive user's initialization\nfiles.\n\n If the account is for an application, the requirement for a umask less\nrestrictive than \\\"077\\\" can be documented with the Information System Security\nOfficer, but the user agreement for access to the account must specify that the\nlocal interactive user must log on to their account first and then switch the\nuser to the application account with the correct option to gain the account's\nenvironment variables.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72049\"\n tag rid: \"SV-86673r2_rule\"\n tag stig_id: \"RHEL-07-021040\"\n tag fix_id: \"F-78401r3_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n non_interactive_shells = input('non_interactive_shells')\n\n # Get all interactive users\n ignore_shells = non_interactive_shells.join('|')\n\n # Get home directory for users with UID >= 1000 or UID == 0 and support interactive logins.\n findings = Set[]\n dotfiles = Set[]\n umasks = {}\n umask_findings = Set[]\n\n # Get UID_MIN from login.defs\n uid_min = 1000\n if file(\"/etc/login.defs\").exist?\n uid_min_val = command(\"grep '^UID_MIN' /etc/login.defs | grep -Po '[0-9]+'\").stdout.split(\"\\n\")\n if !uid_min_val.empty?\n uid_min = uid_min_val[0].to_i\n end\n end\n\n interactive_users = users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries\n\n # For each user, build and execute a find command that identifies initialization files\n # in a user's home directory.\n interactive_users.each do |u|\n\n # Only check if the home directory is local\n is_local = command(\"df -l #{u.home}\").exit_status\n\n if is_local == 0\n # Get user's initialization files\n dotfiles = dotfiles + command(\"find #{u.home} -xdev -maxdepth 2 ( -name '.*' ! -name '.bash_history' ) -type f\").stdout.split(\"\\n\")\n\n # Get user's umask\n umasks.store(u.username,command(\"su -c 'umask' -l #{u.username}\").stdout.chomp(\"\\n\"))\n\n # Check all local initialization files to see whether or not they are less restrictive than 077.\n dotfiles.each do |df|\n if file(df).more_permissive_than?(\"0077\")\n findings = findings + df\n end\n end\n\n # Check umask for all interactive users\n umasks.each do |key,value|\n max_mode = (\"0077\").to_i(8)\n inv_mode = 0777 ^ max_mode\n if inv_mode & (value).to_i(8) != 0\n umask_findings = umask_findings + key\n end\n end\n else\n describe \"This control skips non-local filesystems\" do\n skip \"This control has skipped the #{u.home} home directory for #{u.username} because it is not a local filesystem.\"\n end\n end\n end\n\n # Report on any interactive files that are less restrictive than 077.\n describe \"No interactive user initialization files with a less restrictive umask were found.\" do\n subject { findings.empty? }\n it { should eq true }\n end\n\n # Report on any interactive users that have a umask less restrictive than 077.\n describe \"No users were found with a less restrictive umask were found.\" do\n subject { umask_findings.empty? }\n it { should eq true }\n end\nend\n","desc":"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \"0\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.","descriptions":[{"data":"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \"0\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the default umask for all local interactive users is \"077\".\n\n Identify the locations of all local interactive user home directories by\nlooking at the \"/etc/passwd\" file.\n\n Check all local interactive user initialization files for interactive users\nwith the following command:\n\n Note: The example is for a system that is configured to create users home\ndirectories in the \"/home\" directory.\n\n # grep -i umask /home/*/.*\n\n If any local interactive user initialization files are found to have a\numask statement that has a value less restrictive than \"077\", this is a\nfinding.","label":"check"},{"data":"Remove the umask statement from all local interactive user's initialization\nfiles.\n\n If the account is for an application, the requirement for a umask less\nrestrictive than \"077\" can be documented with the Information System Security\nOfficer, but the user agreement for access to the account must specify that the\nlocal interactive user must log on to their account first and then switch the\nuser to the application account with the correct option to gain the account's\nenvironment variables.","label":"fix"}],"id":"V-72049","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72049.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72049","rid":"SV-86673r2_rule","stig_id":"RHEL-07-021040","fix_id":"F-78401r3_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must set the umask value\nto 077 for all local interactive user accounts.","waiver_data":{}},{"code":"control \"V-72051\" do\n title \"The Red Hat Enterprise Linux operating system must have cron logging\nimplemented.\"\n desc \"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that \\\"rsyslog\\\" is configured to log cron events.\n\n Check the configuration of \\\"/etc/rsyslog.conf\\\" or\n\\\"/etc/rsyslog.d/*.conf\\\" files for the cron facility with the following\ncommand:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \\\"/etc/rsyslog.conf\\\" or \\\"/etc/rsyslog.d/*.conf\\\" files.\n\n # grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n cron.* /var/log/cron.log\n\n If the command does not return a response, check for cron logging all\nfacilities by inspecting the \\\"/etc/rsyslog.conf\\\" or \\\"/etc/rsyslog.d/*.conf\\\"\nfiles.\n\n Look for the following entry:\n\n *.* /var/log/messages\n\n If \\\"rsyslog\\\" is not logging messages for the cron facility or all\nfacilities, this is a finding.\n \"\n desc \"fix\", \"\n Configure \\\"rsyslog\\\" to log all cron messages by adding or updating the\nfollowing line to \\\"/etc/rsyslog.conf\\\" or a configuration file in the\n/etc/rsyslog.d/ directory:\n\n cron.* /var/log/cron.log\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72051\"\n tag rid: \"SV-86675r2_rule\"\n tag stig_id: \"RHEL-07-021100\"\n tag fix_id: \"F-78403r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n log_pkg_path = input('log_pkg_path')\n\n describe.one do\n describe command(\"grep cron #{log_pkg_path}\") do\n its('stdout.strip') { should match %r{^cron} }\n end\n describe file(\"#{log_pkg_path}\") do\n its('content') { should match %r{^\\*\\.\\* \\/var\\/log\\/messages\\n?$} }\n its('content') { should_not match %r{^*.*\\s+~$.*^*\\.\\* \\/var\\/log\\/messages\\n?$}m }\n end\n end\nend\n","desc":"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.","descriptions":[{"data":"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that \"rsyslog\" is configured to log cron events.\n\n Check the configuration of \"/etc/rsyslog.conf\" or\n\"/etc/rsyslog.d/*.conf\" files for the cron facility with the following\ncommand:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \"/etc/rsyslog.conf\" or \"/etc/rsyslog.d/*.conf\" files.\n\n # grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n cron.* /var/log/cron.log\n\n If the command does not return a response, check for cron logging all\nfacilities by inspecting the \"/etc/rsyslog.conf\" or \"/etc/rsyslog.d/*.conf\"\nfiles.\n\n Look for the following entry:\n\n *.* /var/log/messages\n\n If \"rsyslog\" is not logging messages for the cron facility or all\nfacilities, this is a finding.","label":"check"},{"data":"Configure \"rsyslog\" to log all cron messages by adding or updating the\nfollowing line to \"/etc/rsyslog.conf\" or a configuration file in the\n/etc/rsyslog.d/ directory:\n\n cron.* /var/log/cron.log","label":"fix"}],"id":"V-72051","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72051.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72051","rid":"SV-86675r2_rule","stig_id":"RHEL-07-021100","fix_id":"F-78403r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must have cron logging\nimplemented.","waiver_data":{}},{"code":"control \"V-72053\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is owned by root.\"\n desc \"If the owner of the \\\"cron.allow\\\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"cron.allow\\\" file is owned by root.\n\n Check the owner of the \\\"cron.allow\\\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \\\"cron.allow\\\" file exists and has an owner other than root, this is\na finding.\n \"\n desc \"fix\", \"\n Set the owner on the \\\"/etc/cron.allow\\\" file to root with the following\ncommand:\n\n # chown root /etc/cron.allow\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72053\"\n tag rid: \"SV-86677r3_rule\"\n tag stig_id: \"RHEL-07-021110\"\n tag fix_id: \"F-78405r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n # case where file doesn't exist\n describe file('/etc/cron.allow') do\n it { should_not exist }\n end\n # case where file exists\n describe file('/etc/cron.allow') do\n it { should be_owned_by 'root' }\n end\n end\nend\n","desc":"If the owner of the \"cron.allow\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.","descriptions":[{"data":"If the owner of the \"cron.allow\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"cron.allow\" file is owned by root.\n\n Check the owner of the \"cron.allow\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \"cron.allow\" file exists and has an owner other than root, this is\na finding.","label":"check"},{"data":"Set the owner on the \"/etc/cron.allow\" file to root with the following\ncommand:\n\n # chown root /etc/cron.allow","label":"fix"}],"id":"V-72053","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72053.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72053","rid":"SV-86677r3_rule","stig_id":"RHEL-07-021110","fix_id":"F-78405r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is owned by root.","waiver_data":{}},{"code":"control \"V-72055\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is group-owned by root.\"\n desc \"If the group owner of the \\\"cron.allow\\\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"cron.allow\\\" file is group-owned by root.\n\n Check the group owner of the \\\"cron.allow\\\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \\\"cron.allow\\\" file exists and has a group owner other than root,\nthis is a finding.\n \"\n desc \"fix\", \"\n Set the group owner on the \\\"/etc/cron.allow\\\" file to root with the\nfollowing command:\n\n # chgrp root /etc/cron.allow\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72055\"\n tag rid: \"SV-86679r2_rule\"\n tag stig_id: \"RHEL-07-021120\"\n tag fix_id: \"F-78407r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n # case where file doesn't exist\n describe file('/etc/cron.allow') do\n it { should_not exist }\n end\n # case where file exists\n describe file('/etc/cron.allow') do\n its('group') { should eq 'root' }\n end\n end\nend\n","desc":"If the group owner of the \"cron.allow\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.","descriptions":[{"data":"If the group owner of the \"cron.allow\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"cron.allow\" file is group-owned by root.\n\n Check the group owner of the \"cron.allow\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \"cron.allow\" file exists and has a group owner other than root,\nthis is a finding.","label":"check"},{"data":"Set the group owner on the \"/etc/cron.allow\" file to root with the\nfollowing command:\n\n # chgrp root /etc/cron.allow","label":"fix"}],"id":"V-72055","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72055.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72055","rid":"SV-86679r2_rule","stig_id":"RHEL-07-021120","fix_id":"F-78407r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is group-owned by root.","waiver_data":{}},{"code":"control \"V-72057\" do\n title \"The Red Hat Enterprise Linux operating system must disable Kernel core\ndumps unless needed.\"\n desc \"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that kernel core dumps are disabled unless needed.\n\n Check the status of the \\\"kdump\\\" service with the following command:\n\n # systemctl status kdump.service\n kdump.service - Crash recovery kernel arming\n Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)\n Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago\n Main PID: 1130 (code=exited, status=0/SUCCESS)\n kernel arming.\n\n If the \\\"kdump\\\" service is active, ask the System Administrator if the use\nof the service is required and documented with the Information System Security\nOfficer (ISSO).\n\n If the service is active and is not documented, this is a finding.\n \"\n desc \"fix\", \"\n If kernel core dumps are not required, disable the \\\"kdump\\\" service with\nthe following command:\n\n # systemctl disable kdump.service\n\n If kernel core dumps are required, document the need with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72057\"\n tag rid: \"SV-86681r2_rule\"\n tag stig_id: \"RHEL-07-021300\"\n tag fix_id: \"F-78409r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe systemd_service('kdump.service') do\n it { should_not be_running }\n end\nend\n","desc":"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.","descriptions":[{"data":"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that kernel core dumps are disabled unless needed.\n\n Check the status of the \"kdump\" service with the following command:\n\n # systemctl status kdump.service\n kdump.service - Crash recovery kernel arming\n Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)\n Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago\n Main PID: 1130 (code=exited, status=0/SUCCESS)\n kernel arming.\n\n If the \"kdump\" service is active, ask the System Administrator if the use\nof the service is required and documented with the Information System Security\nOfficer (ISSO).\n\n If the service is active and is not documented, this is a finding.","label":"check"},{"data":"If kernel core dumps are not required, disable the \"kdump\" service with\nthe following command:\n\n # systemctl disable kdump.service\n\n If kernel core dumps are required, document the need with the ISSO.","label":"fix"}],"id":"V-72057","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72057.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72057","rid":"SV-86681r2_rule","stig_id":"RHEL-07-021300","fix_id":"F-78409r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must disable Kernel core\ndumps unless needed.","waiver_data":{}},{"code":"control \"V-72059\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat a separate file system is used for user home directories (such as /home or\nan equivalent).\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a separate file system/partition has been created for\nnon-privileged local interactive user home directories.\n\n Check the home directory assignment for all non-privileged users (those\nwith a UID greater than 1000) on the system with the following command:\n\n #cut -d: -f 1,3,6,7 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\" | tr \\\":\\\"\n\\\"\\\\t\\\"\n\n adamsj /home/adamsj /bin/bash\n jacksonm /home/jacksonm /bin/bash\n smithj /home/smithj /bin/bash\n\n The output of the command will give the directory/partition that contains\nthe home directories for the non-privileged users on the system (in this\nexample, /home) and users' shell. All accounts with a valid shell (such as\n/bin/bash) are considered interactive users.\n\n Check that a file system/partition has been created for the non-privileged\ninteractive users with the following command:\n\n Note: The partition of /home is used in the example.\n\n # grep /home /etc/fstab\n UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1\n2\n\n If a separate entry for the file system/partition that contains the\nnon-privileged interactive users' home directories does not exist, this is a\nfinding.\n \"\n desc \"fix\", \"Migrate the \\\"/home\\\" directory onto a separate file\nsystem/partition.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72059\"\n tag rid: \"SV-86683r2_rule\"\n tag stig_id: \"RHEL-07-021310\"\n tag fix_id: \"F-78411r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n # excluding root because its home directory is usually \"/root\" (mountpoint \"/\")\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n\n home_mount = command(%(df #{user_info.home} --output=target | tail -1)).stdout.strip\n describe user_info.username do\n context 'with mountpoint' do\n context home_mount do\n it { should_not be_empty }\n it { should_not match(%r(^/$)) }\n end\n end\n end\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for\nnon-privileged local interactive user home directories.\n\n Check the home directory assignment for all non-privileged users (those\nwith a UID greater than 1000) on the system with the following command:\n\n #cut -d: -f 1,3,6,7 /etc/passwd | egrep \":[1-4][0-9]{3}\" | tr \":\"\n\"\\t\"\n\n adamsj /home/adamsj /bin/bash\n jacksonm /home/jacksonm /bin/bash\n smithj /home/smithj /bin/bash\n\n The output of the command will give the directory/partition that contains\nthe home directories for the non-privileged users on the system (in this\nexample, /home) and users' shell. All accounts with a valid shell (such as\n/bin/bash) are considered interactive users.\n\n Check that a file system/partition has been created for the non-privileged\ninteractive users with the following command:\n\n Note: The partition of /home is used in the example.\n\n # grep /home /etc/fstab\n UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1\n2\n\n If a separate entry for the file system/partition that contains the\nnon-privileged interactive users' home directories does not exist, this is a\nfinding.","label":"check"},{"data":"Migrate the \"/home\" directory onto a separate file\nsystem/partition.","label":"fix"}],"id":"V-72059","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72059.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72059","rid":"SV-86683r2_rule","stig_id":"RHEL-07-021310","fix_id":"F-78411r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat a separate file system is used for user home directories (such as /home or\nan equivalent).","waiver_data":{}},{"code":"control \"V-72061\" do\n title \"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /var.\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a separate file system/partition has been created for \\\"/var\\\".\n\n Check that a file system/partition has been created for \\\"/var\\\" with the\nfollowing command:\n\n # grep /var /etc/fstab\n UUID=c274f65f /var ext4 noatime,nobarrier 1\n2\n\n If a separate entry for \\\"/var\\\" is not in use, this is a finding.\n \"\n desc \"fix\", \"Migrate the \\\"/var\\\" path onto a separate file system.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72061\"\n tag rid: \"SV-86685r2_rule\"\n tag stig_id: \"RHEL-07-021320\"\n tag fix_id: \"F-78413r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe mount('/var') do\n it { should be_mounted }\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for \"/var\".\n\n Check that a file system/partition has been created for \"/var\" with the\nfollowing command:\n\n # grep /var /etc/fstab\n UUID=c274f65f /var ext4 noatime,nobarrier 1\n2\n\n If a separate entry for \"/var\" is not in use, this is a finding.","label":"check"},{"data":"Migrate the \"/var\" path onto a separate file system.","label":"fix"}],"id":"V-72061","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72061.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72061","rid":"SV-86685r2_rule","stig_id":"RHEL-07-021320","fix_id":"F-78413r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /var.","waiver_data":{}},{"code":"control \"V-72063\" do\n title \"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for the system audit data path.\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Determine if the operating system is configured to have the\n\\\"/var/log/audit\\\" path is on a separate file system.\n\n # grep /var/log/audit /etc/fstab\n\n If no result is returned, or the operating system is not configured to have\n\\\"/var/log/audit\\\" on a separate file system, this is a finding.\n\n Verify that \\\"/var/log/audit\\\" is mounted on a separate file system:\n\n # mount | grep \\\"/var/log/audit\\\"\n\n If no result is returned, or \\\"/var/log/audit\\\" is not on a separate file\nsystem, this is a finding.\n \"\n desc \"fix\", \"Migrate the system audit data path onto a separate file system.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72063\"\n tag rid: \"SV-86687r6_rule\"\n tag stig_id: \"RHEL-07-021330\"\n tag fix_id: \"F-78415r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe mount('/var/log/audit') do\n it {should be_mounted}\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Determine if the operating system is configured to have the\n\"/var/log/audit\" path is on a separate file system.\n\n # grep /var/log/audit /etc/fstab\n\n If no result is returned, or the operating system is not configured to have\n\"/var/log/audit\" on a separate file system, this is a finding.\n\n Verify that \"/var/log/audit\" is mounted on a separate file system:\n\n # mount | grep \"/var/log/audit\"\n\n If no result is returned, or \"/var/log/audit\" is not on a separate file\nsystem, this is a finding.","label":"check"},{"data":"Migrate the system audit data path onto a separate file system.","label":"fix"}],"id":"V-72063","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72063.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72063","rid":"SV-86687r6_rule","stig_id":"RHEL-07-021330","fix_id":"F-78415r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for the system audit data path.","waiver_data":{}},{"code":"control \"V-72065\" do\n title \"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /tmp (or equivalent).\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a separate file system/partition has been created for \\\"/tmp\\\".\n\n Check that a file system/partition has been created for \\\"/tmp\\\" with the\nfollowing command:\n\n # systemctl is-enabled tmp.mount\n enabled\n\n If the \\\"tmp.mount\\\" service is not enabled, check to see if \\\"/tmp\\\" is\ndefined in the fstab with a device and mount point:\n\n # grep -i /tmp /etc/fstab\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /tmp ext4\nrw,relatime,discard,data=ordered,nosuid,noexec, 0 0\n\n If \\\"tmp.mount\\\" service is not enabled and the \\\"/tmp\\\" directory is not\ndefined in the fstab with a device and mount point, this is a finding.\n \"\n desc \"fix\", \"\n Start the \\\"tmp.mount\\\" service with the following command:\n\n # systemctl enable tmp.mount\n\n OR\n\n Edit the \\\"/etc/fstab\\\" file and ensure the \\\"/tmp\\\" directory is defined\nin the fstab with a device and mount point.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72065\"\n tag rid: \"SV-86689r3_rule\"\n tag stig_id: \"RHEL-07-021340\"\n tag fix_id: \"F-78417r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe systemd_service('tmp.mount') do\n it { should be_enabled }\n end\n describe etc_fstab.where { mount_point == '/tmp' } do\n its('count') { should cmp 1 }\n it 'Should have a device name specified' do\n expect(subject.device_name[0]).to_not(be_empty)\n end\n end\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for \"/tmp\".\n\n Check that a file system/partition has been created for \"/tmp\" with the\nfollowing command:\n\n # systemctl is-enabled tmp.mount\n enabled\n\n If the \"tmp.mount\" service is not enabled, check to see if \"/tmp\" is\ndefined in the fstab with a device and mount point:\n\n # grep -i /tmp /etc/fstab\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /tmp ext4\nrw,relatime,discard,data=ordered,nosuid,noexec, 0 0\n\n If \"tmp.mount\" service is not enabled and the \"/tmp\" directory is not\ndefined in the fstab with a device and mount point, this is a finding.","label":"check"},{"data":"Start the \"tmp.mount\" service with the following command:\n\n # systemctl enable tmp.mount\n\n OR\n\n Edit the \"/etc/fstab\" file and ensure the \"/tmp\" directory is defined\nin the fstab with a device and mount point.","label":"fix"}],"id":"V-72065","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72065.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72065","rid":"SV-86689r3_rule","stig_id":"RHEL-07-021340","fix_id":"F-78417r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /tmp (or equivalent).","waiver_data":{}},{"code":"control \"V-72067\" do\n title \"The Red Hat Enterprise Linux operating system must implement NIST\nFIPS-validated cryptography for the following: to provision digital signatures,\nto generate cryptographic hashes, and to protect data requiring data-at-rest\nprotections in accordance with applicable federal laws, Executive Orders,\ndirectives, policies, regulations, and standards.\"\n desc \"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system implements DoD-approved encryption to protect\nthe confidentiality of remote access sessions.\n\n Check to see if the \\\"dracut-fips\\\" package is installed with the following\ncommand:\n\n # yum list installed dracut-fips\n\n dracut-fips-033-360.el7_2.x86_64.rpm\n\n If a \\\"dracut-fips\\\" package is installed, check to see if the kernel\ncommand line is configured to use FIPS mode with the following command:\n\n Note: GRUB 2 reads its configuration from the \\\"/boot/grub2/grub.cfg\\\" file\non traditional BIOS-based machines and from the\n\\\"/boot/efi/EFI/redhat/grub.cfg\\\" file on UEFI machines.\n\n # grep fips /boot/grub2/grub.cfg\n /vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0\nrd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us\nrd.lvm.lv=rhel/root rhgb fips=1 quiet\n\n If the kernel command line is configured to use FIPS mode, check to see if\nthe system is in FIPS mode with the following command:\n\n # cat /proc/sys/crypto/fips_enabled\n 1\n\n If a \\\"dracut-fips\\\" package is not installed, the kernel command line does\nnot have a fips entry, or the system has a value of \\\"0\\\" for \\\"fips_enabled\\\"\nin \\\"/proc/sys/crypto\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement DoD-approved encryption by\ninstalling the dracut-fips package.\n\n To enable strict FIPS compliance, the fips=1 kernel option needs to be\nadded to the kernel command line during system installation so key generation\nis done with FIPS-approved algorithms and continuous monitoring tests in place.\n\n Configure the operating system to implement DoD-approved encryption by\nfollowing the steps below:\n\n The fips=1 kernel option needs to be added to the kernel command line\nduring system installation so that key generation is done with FIPS-approved\nalgorithms and continuous monitoring tests in place. Users should also ensure\nthat the system has plenty of entropy during the installation process by moving\nthe mouse around, or if no mouse is available, ensuring that many keystrokes\nare typed. The recommended amount of keystrokes is 256 and more. Less than 256\nkeystrokes may generate a non-unique key.\n\n Install the dracut-fips package with the following command:\n\n # yum install dracut-fips\n\n Recreate the \\\"initramfs\\\" file with the following command:\n\n Note: This command will overwrite the existing \\\"initramfs\\\" file.\n\n # dracut -f\n\n Modify the kernel command line of the current kernel in the \\\"grub.cfg\\\"\nfile by adding the following option to the GRUB_CMDLINE_LINUX key in the\n\\\"/etc/default/grub\\\" file and then rebuild the \\\"grub.cfg\\\" file:\n\n fips=1\n\n Changes to \\\"/etc/default/grub\\\" require rebuilding the \\\"grub.cfg\\\" file\nas follows:\n\n On BIOS-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/grub2/grub.cfg\n\n On UEFI-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg\n\n If /boot or /boot/efi reside on separate partitions, the kernel parameter\nboot= must be added to the kernel command\nline. You can identify a partition by running the df /boot or df /boot/efi\ncommand:\n\n # df /boot\n Filesystem 1K-blocks Used Available Use% Mounted on\n /dev/sda1 495844 53780 416464 12% /boot\n\n To ensure the \\\"boot=\\\" configuration option will work even if device\nnaming changes occur between boots, identify the universally unique identifier\n(UUID) of the partition with the following command:\n\n # blkid /dev/sda1\n /dev/sda1: UUID=\\\"05c000f1-a213-759e-c7a2-f11b7424c797\\\" TYPE=\\\"ext4\\\"\n\n For the example above, append the following string to the kernel command\nline:\n\n boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797\n\n Reboot the system for the changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000033-GPOS-00014\"\n tag satisfies: [\"SRG-OS-000033-GPOS-00014\", \"SRG-OS-000185-GPOS-00079\",\n\"SRG-OS-000396-GPOS-00176\", \"SRG-OS-000405-GPOS-00184\",\n\"SRG-OS-000478-GPOS-00223\"]\n tag gid: \"V-72067\"\n tag rid: \"SV-86691r4_rule\"\n tag stig_id: \"RHEL-07-021350\"\n tag fix_id: \"F-78419r3_fix\"\n tag cci: [\"CCI-000068\", \"CCI-001199\", \"CCI-002450\", \"CCI-002476\"]\n tag nist: [\"AC-17 (2)\", \"SC-28\", \"SC-13\", \"SC-28 (1)\"]\n\n describe package('dracut-fips') do\n it { should be_installed }\n end\n\n all_args = command('grubby --info=ALL | grep \"^args=\" | sed \"s/^args=//g\"').\n stdout.strip.split(\"\\n\").\n map { |s| s.sub(%r{^\"(.*)\"$}, '\\1') } # strip outer quotes if they exist\n\n all_args.each { |args|\n describe args do\n it { should match %r{\\bfips=1\\b} }\n end\n }\n\n describe file('/proc/sys/crypto/fips_enabled') do\n its('content.strip') { should cmp 1 }\n end\nend\n","desc":"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.","descriptions":[{"data":"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements DoD-approved encryption to protect\nthe confidentiality of remote access sessions.\n\n Check to see if the \"dracut-fips\" package is installed with the following\ncommand:\n\n # yum list installed dracut-fips\n\n dracut-fips-033-360.el7_2.x86_64.rpm\n\n If a \"dracut-fips\" package is installed, check to see if the kernel\ncommand line is configured to use FIPS mode with the following command:\n\n Note: GRUB 2 reads its configuration from the \"/boot/grub2/grub.cfg\" file\non traditional BIOS-based machines and from the\n\"/boot/efi/EFI/redhat/grub.cfg\" file on UEFI machines.\n\n # grep fips /boot/grub2/grub.cfg\n /vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0\nrd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us\nrd.lvm.lv=rhel/root rhgb fips=1 quiet\n\n If the kernel command line is configured to use FIPS mode, check to see if\nthe system is in FIPS mode with the following command:\n\n # cat /proc/sys/crypto/fips_enabled\n 1\n\n If a \"dracut-fips\" package is not installed, the kernel command line does\nnot have a fips entry, or the system has a value of \"0\" for \"fips_enabled\"\nin \"/proc/sys/crypto\", this is a finding.","label":"check"},{"data":"Configure the operating system to implement DoD-approved encryption by\ninstalling the dracut-fips package.\n\n To enable strict FIPS compliance, the fips=1 kernel option needs to be\nadded to the kernel command line during system installation so key generation\nis done with FIPS-approved algorithms and continuous monitoring tests in place.\n\n Configure the operating system to implement DoD-approved encryption by\nfollowing the steps below:\n\n The fips=1 kernel option needs to be added to the kernel command line\nduring system installation so that key generation is done with FIPS-approved\nalgorithms and continuous monitoring tests in place. Users should also ensure\nthat the system has plenty of entropy during the installation process by moving\nthe mouse around, or if no mouse is available, ensuring that many keystrokes\nare typed. The recommended amount of keystrokes is 256 and more. Less than 256\nkeystrokes may generate a non-unique key.\n\n Install the dracut-fips package with the following command:\n\n # yum install dracut-fips\n\n Recreate the \"initramfs\" file with the following command:\n\n Note: This command will overwrite the existing \"initramfs\" file.\n\n # dracut -f\n\n Modify the kernel command line of the current kernel in the \"grub.cfg\"\nfile by adding the following option to the GRUB_CMDLINE_LINUX key in the\n\"/etc/default/grub\" file and then rebuild the \"grub.cfg\" file:\n\n fips=1\n\n Changes to \"/etc/default/grub\" require rebuilding the \"grub.cfg\" file\nas follows:\n\n On BIOS-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/grub2/grub.cfg\n\n On UEFI-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg\n\n If /boot or /boot/efi reside on separate partitions, the kernel parameter\nboot= must be added to the kernel command\nline. You can identify a partition by running the df /boot or df /boot/efi\ncommand:\n\n # df /boot\n Filesystem 1K-blocks Used Available Use% Mounted on\n /dev/sda1 495844 53780 416464 12% /boot\n\n To ensure the \"boot=\" configuration option will work even if device\nnaming changes occur between boots, identify the universally unique identifier\n(UUID) of the partition with the following command:\n\n # blkid /dev/sda1\n /dev/sda1: UUID=\"05c000f1-a213-759e-c7a2-f11b7424c797\" TYPE=\"ext4\"\n\n For the example above, append the following string to the kernel command\nline:\n\n boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797\n\n Reboot the system for the changes to take effect.","label":"fix"}],"id":"V-72067","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72067.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000033-GPOS-00014","satisfies":["SRG-OS-000033-GPOS-00014","SRG-OS-000185-GPOS-00079","SRG-OS-000396-GPOS-00176","SRG-OS-000405-GPOS-00184","SRG-OS-000478-GPOS-00223"],"gid":"V-72067","rid":"SV-86691r4_rule","stig_id":"RHEL-07-021350","fix_id":"F-78419r3_fix","cci":["CCI-000068","CCI-001199","CCI-002450","CCI-002476"],"nist":["AC-17 (2)","SC-28","SC-13","SC-28 (1)"]},"title":"The Red Hat Enterprise Linux operating system must implement NIST\nFIPS-validated cryptography for the following: to provision digital signatures,\nto generate cryptographic hashes, and to protect data requiring data-at-rest\nprotections in accordance with applicable federal laws, Executive Orders,\ndirectives, policies, regulations, and standards.","waiver_data":{}},{"code":"control \"V-72069\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify Access Control Lists\n(ACLs).\"\n desc \"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file integrity tool is configured to verify ACLs.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \\\"aide.conf\\\" file is under the \\\"/etc\\\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \\\"aide.conf\\\" file to determine if the \\\"acl\\\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \\\"acl\\\" rule is below:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \\\"acl\\\" rule is not being used on all uncommented selection lines in\nthe \\\"/etc/aide.conf\\\" file, or ACLs are not being checked by another file\nintegrity tool, this is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to check file and directory ACLs.\n\n If AIDE is installed, ensure the \\\"acl\\\" rule is present on all uncommented\nfile and directory selection lists.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72069\"\n tag rid: \"SV-86693r3_rule\"\n tag stig_id: \"RHEL-07-021600\"\n tag fix_id: \"F-78421r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe package(\"aide\") do\n it { should be_installed }\n end\n\n findings = []\n aide_conf.where { !selection_line.start_with? '!' }.entries.each do |selection|\n unless selection.rules.include? 'acl'\n findings.append(selection.selection_line)\n end\n end\n\n describe \"List of monitored files/directories without 'acl' rule\" do\n subject { findings }\n it { should be_empty }\n end\nend\n","desc":"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.","descriptions":[{"data":"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to verify ACLs.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"acl\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"acl\" rule is below:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"acl\" rule is not being used on all uncommented selection lines in\nthe \"/etc/aide.conf\" file, or ACLs are not being checked by another file\nintegrity tool, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to check file and directory ACLs.\n\n If AIDE is installed, ensure the \"acl\" rule is present on all uncommented\nfile and directory selection lists.","label":"fix"}],"id":"V-72069","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72069.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72069","rid":"SV-86693r3_rule","stig_id":"RHEL-07-021600","fix_id":"F-78421r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify Access Control Lists\n(ACLs).","waiver_data":{}},{"code":"control \"V-72071\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify extended attributes.\"\n desc \"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file integrity tool is configured to verify extended attributes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \\\"aide.conf\\\" file is under the \\\"/etc\\\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \\\"aide.conf\\\" file to determine if the \\\"xattrs\\\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \\\"xattrs\\\" rule follows:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \\\"xattrs\\\" rule is not being used on all uncommented selection lines\nin the \\\"/etc/aide.conf\\\" file, or extended attributes are not being checked by\nanother file integrity tool, this is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to check file and directory extended\nattributes.\n\n If AIDE is installed, ensure the \\\"xattrs\\\" rule is present on all\nuncommented file and directory selection lists.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72071\"\n tag rid: \"SV-86695r3_rule\"\n tag stig_id: \"RHEL-07-021610\"\n tag fix_id: \"F-78423r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe package(\"aide\") do\n it { should be_installed }\n end\n\n findings = []\n aide_conf.where { !selection_line.start_with? '!' }.entries.each do |selection|\n unless selection.rules.include? 'xattrs'\n findings.append(selection.selection_line)\n end\n end\n\n describe \"List of monitored files/directories without 'xattrs' rule\" do\n subject { findings }\n it { should be_empty }\n end\nend\n","desc":"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.","descriptions":[{"data":"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to verify extended attributes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"xattrs\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"xattrs\" rule follows:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"xattrs\" rule is not being used on all uncommented selection lines\nin the \"/etc/aide.conf\" file, or extended attributes are not being checked by\nanother file integrity tool, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to check file and directory extended\nattributes.\n\n If AIDE is installed, ensure the \"xattrs\" rule is present on all\nuncommented file and directory selection lists.","label":"fix"}],"id":"V-72071","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72071.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72071","rid":"SV-86695r3_rule","stig_id":"RHEL-07-021610","fix_id":"F-78423r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify extended attributes.","waiver_data":{}},{"code":"control \"V-72073\" do\n title \"The Red Hat Enterprise Linux operating system must use a file\nintegrity tool that is configured to use FIPS 140-2 approved cryptographic\nhashes for validating file contents and directories.\"\n desc \"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file integrity tool is configured to use FIPS 140-2 approved\ncryptographic hashes for validating file contents and directories.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding too\nas the system cannot implement FIPS 140-2 approved cryptographic algorithms and\nhashes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \\\"aide.conf\\\" file is under the \\\"/etc\\\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \\\"aide.conf\\\" file to determine if the \\\"sha512\\\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \\\"sha512\\\" rule follows:\n\n All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \\\"sha512\\\" rule is not being used on all uncommented selection lines\nin the \\\"/etc/aide.conf\\\" file, or another file integrity tool is not using\nFIPS 140-2 approved cryptographic hashes for validating file contents and\ndirectories, this is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to use FIPS 140-2 cryptographic hashes\nfor validating file and directory contents.\n\n If AIDE is installed, ensure the \\\"sha512\\\" rule is present on all\nuncommented file and directory selection lists.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72073\"\n tag rid: \"SV-86697r3_rule\"\n tag stig_id: \"RHEL-07-021620\"\n tag fix_id: \"F-78425r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe package(\"aide\") do\n it { should be_installed }\n end\n\n exclude_patterns = input('aide_exclude_patterns')\n\n findings = aide_conf.where { !selection_line.start_with?('!') && !exclude_patterns.include?(selection_line) && !rules.include?('sha512')}\n\n describe \"List of monitored files/directories without 'sha512' rule\" do\n subject { findings.selection_lines }\n it { should be_empty }\n end\nend\n","desc":"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.","descriptions":[{"data":"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to use FIPS 140-2 approved\ncryptographic hashes for validating file contents and directories.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding too\nas the system cannot implement FIPS 140-2 approved cryptographic algorithms and\nhashes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"sha512\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"sha512\" rule follows:\n\n All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"sha512\" rule is not being used on all uncommented selection lines\nin the \"/etc/aide.conf\" file, or another file integrity tool is not using\nFIPS 140-2 approved cryptographic hashes for validating file contents and\ndirectories, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to use FIPS 140-2 cryptographic hashes\nfor validating file and directory contents.\n\n If AIDE is installed, ensure the \"sha512\" rule is present on all\nuncommented file and directory selection lists.","label":"fix"}],"id":"V-72073","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72073.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72073","rid":"SV-86697r3_rule","stig_id":"RHEL-07-021620","fix_id":"F-78425r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a file\nintegrity tool that is configured to use FIPS 140-2 approved cryptographic\nhashes for validating file contents and directories.","waiver_data":{}},{"code":"control \"V-72075\" do\n title \"The Red Hat Enterprise Linux operating system must not allow removable\nmedia to be used as the boot loader unless approved.\"\n desc \"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system is not configured to use a boot loader on removable media.\n\n Note: GRUB 2 reads its configuration from the \\\"/boot/grub2/grub.cfg\\\" file\non traditional BIOS-based machines and from the\n\\\"/boot/efi/EFI/redhat/grub.cfg\\\" file on UEFI machines.\n\n Check for the existence of alternate boot loader configuration files with\nthe following command:\n\n # find / -name grub.cfg\n /boot/grub2/grub.cfg\n\n If a \\\"grub.cfg\\\" is found in any subdirectories other than \\\"/boot/grub2\\\"\nand \\\"/boot/efi/EFI/redhat\\\", ask the System Administrator if there is\ndocumentation signed by the ISSO to approve the use of removable media as a\nboot loader.\n\n Check that the grub configuration file has the set root command in each\nmenu entry with the following commands:\n\n # grep -c menuentry /boot/grub2/grub.cfg\n 1\n # grep 'set root' /boot/grub2/grub.cfg\n set root=(hd0,1)\n\n If the system is using an alternate boot loader on removable media, and\ndocumentation does not exist approving the alternate configuration, this is a\nfinding.\n \"\n desc \"fix\", \"Remove alternate methods of booting the system from removable\nmedia or document the configuration to boot from removable media with the ISSO.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000364-GPOS-00151\"\n tag gid: \"V-72075\"\n tag rid: \"SV-86699r2_rule\"\n tag stig_id: \"RHEL-07-021700\"\n tag fix_id: \"F-78427r1_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n roots = command('grubby --info=ALL | grep \"^root=\" | sed \"s/^root=//g\"').\n stdout.strip.split(\"\\n\")\n\n blocks = roots.map { |root|\n root_file = file(root)\n root_file.symlink? ? root_file.link_path : root_file.path\n }\n\n blocks.each { |block|\n block_file = file(block)\n describe block_file do\n it { should exist }\n its('path') { should match %r{^/dev/} }\n end\n\n if block_file.exist? and block_file.path.match? %r{^/dev/}\n removable = ['/sys/block', block.sub(%r{^/dev/}, ''), 'removable'].join('/')\n describe file(removable) do\n it { should exist }\n its('content.strip') { should eq '0' }\n end\n end\n }\nend\n","desc":"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).","descriptions":[{"data":"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is not configured to use a boot loader on removable media.\n\n Note: GRUB 2 reads its configuration from the \"/boot/grub2/grub.cfg\" file\non traditional BIOS-based machines and from the\n\"/boot/efi/EFI/redhat/grub.cfg\" file on UEFI machines.\n\n Check for the existence of alternate boot loader configuration files with\nthe following command:\n\n # find / -name grub.cfg\n /boot/grub2/grub.cfg\n\n If a \"grub.cfg\" is found in any subdirectories other than \"/boot/grub2\"\nand \"/boot/efi/EFI/redhat\", ask the System Administrator if there is\ndocumentation signed by the ISSO to approve the use of removable media as a\nboot loader.\n\n Check that the grub configuration file has the set root command in each\nmenu entry with the following commands:\n\n # grep -c menuentry /boot/grub2/grub.cfg\n 1\n # grep 'set root' /boot/grub2/grub.cfg\n set root=(hd0,1)\n\n If the system is using an alternate boot loader on removable media, and\ndocumentation does not exist approving the alternate configuration, this is a\nfinding.","label":"check"},{"data":"Remove alternate methods of booting the system from removable\nmedia or document the configuration to boot from removable media with the ISSO.","label":"fix"}],"id":"V-72075","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72075.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72075","rid":"SV-86699r2_rule","stig_id":"RHEL-07-021700","fix_id":"F-78427r1_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must not allow removable\nmedia to be used as the boot loader unless approved.","waiver_data":{}},{"code":"control \"V-72077\" do\n title \"The Red Hat Enterprise Linux operating system must not have the\ntelnet-server package installed.\"\n desc \"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system is configured to disable non-essential\ncapabilities. The most secure way of ensuring a non-essential capability is\ndisabled is to not have the capability installed.\n\n The telnet service provides an unencrypted remote access service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.\n\n Check to see if the telnet-server package is installed with the following\ncommand:\n\n # yum list installed telnet-server\n\n If the telnet-server package is installed, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable non-essential capabilities by\nremoving the telnet-server package from the system with the following command:\n\n # yum remove telnet-server\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000095-GPOS-00049\"\n tag gid: \"V-72077\"\n tag rid: \"SV-86701r2_rule\"\n tag stig_id: \"RHEL-07-021710\"\n tag fix_id: \"F-78429r1_fix\"\n tag cci: [\"CCI-000381\"]\n tag nist: [\"CM-7 a\"]\n\n describe package('telnet-server') do\n it { should_not be_installed }\n end\nend\n","desc":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.","descriptions":[{"data":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is configured to disable non-essential\ncapabilities. The most secure way of ensuring a non-essential capability is\ndisabled is to not have the capability installed.\n\n The telnet service provides an unencrypted remote access service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.\n\n Check to see if the telnet-server package is installed with the following\ncommand:\n\n # yum list installed telnet-server\n\n If the telnet-server package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the telnet-server package from the system with the following command:\n\n # yum remove telnet-server","label":"fix"}],"id":"V-72077","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72077.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-72077","rid":"SV-86701r2_rule","stig_id":"RHEL-07-021710","fix_id":"F-78429r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the\ntelnet-server package installed.","waiver_data":{}},{"code":"control \"V-72079\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat auditing is configured to produce records containing information to\nestablish what type of events occurred, where the events occurred, the source\nof the events, and the outcome of the events. These audit records must also\nidentify individual identities of group account users.\"\n desc \"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system produces audit records containing information\nto establish when (date and time) the events occurred.\n\n Check to see if auditing is active by issuing the following command:\n\n # systemctl is-active auditd.service\n active\n\n If the \\\"auditd\\\" status is not active, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to produce audit records containing\ninformation to establish when (date and time) the events occurred.\n\n Enable the auditd service with the following command:\n\n # systemctl start auditd.service\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000038-GPOS-00016\"\n tag satisfies: [\"SRG-OS-000038-GPOS-00016\", \"SRG-OS-000039-GPOS-00017\",\n\"SRG-OS-000042-GPOS-00021\", \"SRG-OS-000254-GPOS-00095\",\n\"SRG-OS-000255-GPOS-00096\"]\n tag gid: \"V-72079\"\n tag rid: \"SV-86703r3_rule\"\n tag stig_id: \"RHEL-07-030000\"\n tag fix_id: \"F-78431r2_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000131\"]\n tag nist: [\"AU-2 d\", \"AU-3\"]\n\n describe service('auditd') do\n it { should be_running }\n end\nend\n","desc":"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.","descriptions":[{"data":"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system produces audit records containing information\nto establish when (date and time) the events occurred.\n\n Check to see if auditing is active by issuing the following command:\n\n # systemctl is-active auditd.service\n active\n\n If the \"auditd\" status is not active, this is a finding.","label":"check"},{"data":"Configure the operating system to produce audit records containing\ninformation to establish when (date and time) the events occurred.\n\n Enable the auditd service with the following command:\n\n # systemctl start auditd.service","label":"fix"}],"id":"V-72079","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72079.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000038-GPOS-00016","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"],"gid":"V-72079","rid":"SV-86703r3_rule","stig_id":"RHEL-07-030000","fix_id":"F-78431r2_fix","cci":["CCI-000126","CCI-000131"],"nist":["AU-2 d","AU-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat auditing is configured to produce records containing information to\nestablish what type of events occurred, where the events occurred, the source\nof the events, and the outcome of the events. These audit records must also\nidentify individual identities of group account users.","waiver_data":{}},{"code":"control \"V-72081\" do\n title \"The Red Hat Enterprise Linux operating system must shut down upon\naudit processing failure, unless availability is an overriding concern. If\navailability is a concern, the system must alert the designated staff (System\nAdministrator [SA] and Information System Security Officer [ISSO] at a minimum)\nin the event of an audit processing failure.\"\n desc \"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Confirm the audit configuration regarding how auditing processing failures\nare handled.\n\n Check to see what level \\\"auditctl\\\" is set to with following command:\n\n # auditctl -s | grep -i \\\"fail\\\"\n\n failure 2\n\n If the value of \\\"failure\\\" is set to \\\"2\\\", the system is configured to\npanic (shut down) in the event of an auditing failure.\n\n If the value of \\\"failure\\\" is set to \\\"1\\\", the system is configured to\nonly send information to the kernel log regarding the failure.\n\n If the \\\"failure\\\" setting is not set, this is a CAT I finding.\n\n If the \\\"failure\\\" setting is set to any value other than \\\"1\\\" or \\\"2\\\",\nthis is a CAT II finding.\n\n If the \\\"failure\\\" setting is set to \\\"1\\\" but the availability concern is\nnot documented or there is no monitoring of the kernel log, this is a CAT III\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to shut down in the event of an audit\nprocessing failure.\n\n Add or correct the option to shut down the operating system with the\nfollowing command:\n\n # auditctl -f 2\n\n Edit the \\\"/etc/audit/rules.d/audit.rules\\\" file and add the following line:\n\n -f 2\n\n If availability has been determined to be more important, and this decision\nis documented with the ISSO, configure the operating system to notify system\nadministration staff and ISSO staff in the event of an audit processing failure\nwith the following command:\n\n # auditctl -f 1\n\n Edit the \\\"/etc/audit/rules.d/audit.rules\\\" file and add the following line:\n\n -f 1\n\n Kernel log monitoring must also be configured to properly alert designated\nstaff.\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000046-GPOS-00022\"\n tag satisfies: [\"SRG-OS-000046-GPOS-00022\", \"SRG-OS-000047-GPOS-00023\"]\n tag gid: \"V-72081\"\n tag rid: \"SV-86705r4_rule\"\n tag stig_id: \"RHEL-07-030010\"\n tag fix_id: \"F-78433r2_fix\"\n tag cci: [\"CCI-000139\"]\n tag nist: [\"AU-5 a\"]\n\n monitor_kernel_log = input('monitor_kernel_log')\n\n if auditd.status['failure'].nil?\n impact 0.7\n elsif auditd.status['failure'].match?(%r{^1$}) && !monitor_kernel_log\n impact 0.3\n else\n impact 0.5\n end\n\n if !monitor_kernel_log\n describe auditd.status['failure'] do\n it { should match %r{^2$} }\n end\n else\n describe auditd.status['failure'] do\n it { should match %r{^(1|2)$} }\n end\n end\nend\n","desc":"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.","descriptions":[{"data":"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.","label":"default"},{"data":"","label":"rationale"},{"data":"Confirm the audit configuration regarding how auditing processing failures\nare handled.\n\n Check to see what level \"auditctl\" is set to with following command:\n\n # auditctl -s | grep -i \"fail\"\n\n failure 2\n\n If the value of \"failure\" is set to \"2\", the system is configured to\npanic (shut down) in the event of an auditing failure.\n\n If the value of \"failure\" is set to \"1\", the system is configured to\nonly send information to the kernel log regarding the failure.\n\n If the \"failure\" setting is not set, this is a CAT I finding.\n\n If the \"failure\" setting is set to any value other than \"1\" or \"2\",\nthis is a CAT II finding.\n\n If the \"failure\" setting is set to \"1\" but the availability concern is\nnot documented or there is no monitoring of the kernel log, this is a CAT III\nfinding.","label":"check"},{"data":"Configure the operating system to shut down in the event of an audit\nprocessing failure.\n\n Add or correct the option to shut down the operating system with the\nfollowing command:\n\n # auditctl -f 2\n\n Edit the \"/etc/audit/rules.d/audit.rules\" file and add the following line:\n\n -f 2\n\n If availability has been determined to be more important, and this decision\nis documented with the ISSO, configure the operating system to notify system\nadministration staff and ISSO staff in the event of an audit processing failure\nwith the following command:\n\n # auditctl -f 1\n\n Edit the \"/etc/audit/rules.d/audit.rules\" file and add the following line:\n\n -f 1\n\n Kernel log monitoring must also be configured to properly alert designated\nstaff.\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72081","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72081.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000046-GPOS-00022","satisfies":["SRG-OS-000046-GPOS-00022","SRG-OS-000047-GPOS-00023"],"gid":"V-72081","rid":"SV-86705r4_rule","stig_id":"RHEL-07-030010","fix_id":"F-78433r2_fix","cci":["CCI-000139"],"nist":["AU-5 a"]},"title":"The Red Hat Enterprise Linux operating system must shut down upon\naudit processing failure, unless availability is an overriding concern. If\navailability is a concern, the system must alert the designated staff (System\nAdministrator [SA] and Information System Security Officer [ISSO] at a minimum)\nin the event of an audit processing failure.","waiver_data":{}},{"code":"control \"V-72083\" do\n title \"The Red Hat Enterprise Linux operating system must off-load audit\nrecords onto a different system or media from the system being audited.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system off-loads audit records onto a different system\nor media from the system being audited.\n\n To determine the remote server that the records are being sent to, use the\nfollowing command:\n\n # grep -i remote_server /etc/audisp/audisp-remote.conf\n remote_server = 10.0.21.1\n\n If a remote server is not configured, or the line is commented out, ask the\nSystem Administrator to indicate how the audit logs are off-loaded to a\ndifferent system or media.\n\n If there is no evidence that the audit logs are being off-loaded to another\nsystem or media, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to off-load audit records onto a different\nsystem or media from the system being audited.\n\n Set the remote server option in \\\"/etc/audisp/audisp-remote.conf\\\" with the\nIP address of the log aggregation server.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-72083\"\n tag rid: \"SV-86707r2_rule\"\n tag stig_id: \"RHEL-07-030300\"\n tag fix_id: \"F-78435r1_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n if file('/etc/audisp/audisp-remote.conf').exist?\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('remote_server'.to_s) { should match %r{^\\S+$} }\n its('remote_server'.to_s) { should_not be_in ['localhost', '127.0.0.1'] }\n end\n else\n describe \"File '/etc/audisp/audisp-remote.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '/etc/audisp/audisp-remote.conf' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system off-loads audit records onto a different system\nor media from the system being audited.\n\n To determine the remote server that the records are being sent to, use the\nfollowing command:\n\n # grep -i remote_server /etc/audisp/audisp-remote.conf\n remote_server = 10.0.21.1\n\n If a remote server is not configured, or the line is commented out, ask the\nSystem Administrator to indicate how the audit logs are off-loaded to a\ndifferent system or media.\n\n If there is no evidence that the audit logs are being off-loaded to another\nsystem or media, this is a finding.","label":"check"},{"data":"Configure the operating system to off-load audit records onto a different\nsystem or media from the system being audited.\n\n Set the remote server option in \"/etc/audisp/audisp-remote.conf\" with the\nIP address of the log aggregation server.","label":"fix"}],"id":"V-72083","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72083.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-72083","rid":"SV-86707r2_rule","stig_id":"RHEL-07-030300","fix_id":"F-78435r1_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must off-load audit\nrecords onto a different system or media from the system being audited.","waiver_data":{}},{"code":"control \"V-72085\" do\n title \"The Red Hat Enterprise Linux operating system must encrypt the\ntransfer of audit records off-loaded onto a different system or media from the\nsystem being audited.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system encrypts audit records off-loaded onto a\ndifferent system or media from the system being audited.\n\n To determine if the transfer is encrypted, use the following command:\n\n # grep -i enable_krb5 /etc/audisp/audisp-remote.conf\n enable_krb5 = yes\n\n If the value of the \\\"enable_krb5\\\" option is not set to \\\"yes\\\" or the\nline is commented out, ask the System Administrator to indicate how the audit\nlogs are off-loaded to a different system or media.\n\n If there is no evidence that the transfer of the audit logs being\noff-loaded to another system or media is encrypted, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to encrypt the transfer of off-loaded audit\nrecords onto a different system or media from the system being audited.\n\n Uncomment the \\\"enable_krb5\\\" option in \\\"/etc/audisp/audisp-remote.conf\\\"\nand set it with the following line:\n\n enable_krb5 = yes\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-72085\"\n tag rid: \"SV-86709r2_rule\"\n tag stig_id: \"RHEL-07-030310\"\n tag fix_id: \"F-78437r1_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('enable_krb5'.to_s) { should cmp 'yes' }\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system encrypts audit records off-loaded onto a\ndifferent system or media from the system being audited.\n\n To determine if the transfer is encrypted, use the following command:\n\n # grep -i enable_krb5 /etc/audisp/audisp-remote.conf\n enable_krb5 = yes\n\n If the value of the \"enable_krb5\" option is not set to \"yes\" or the\nline is commented out, ask the System Administrator to indicate how the audit\nlogs are off-loaded to a different system or media.\n\n If there is no evidence that the transfer of the audit logs being\noff-loaded to another system or media is encrypted, this is a finding.","label":"check"},{"data":"Configure the operating system to encrypt the transfer of off-loaded audit\nrecords onto a different system or media from the system being audited.\n\n Uncomment the \"enable_krb5\" option in \"/etc/audisp/audisp-remote.conf\"\nand set it with the following line:\n\n enable_krb5 = yes","label":"fix"}],"id":"V-72085","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72085.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-72085","rid":"SV-86709r2_rule","stig_id":"RHEL-07-030310","fix_id":"F-78437r1_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must encrypt the\ntransfer of audit records off-loaded onto a different system or media from the\nsystem being audited.","waiver_data":{}},{"code":"control \"V-72087\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when the audit storage volume is\nfull.\"\n desc \"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the action the operating system takes if the disk the audit records\nare written to becomes full.\n\n To determine the action that takes place if the disk is full on the remote\nserver, use the following command:\n\n # grep -i disk_full_action /etc/audisp/audisp-remote.conf\n disk_full_action = single\n\n If the value of the \\\"disk_full_action\\\" option is not \\\"syslog\\\",\n\\\"single\\\", or \\\"halt\\\", or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the action the operating system takes if the disk the audit\nrecords are written to becomes full.\n\n Uncomment or edit the \\\"disk_full_action\\\" option in\n\\\"/etc/audisp/audisp-remote.conf\\\" and set it to \\\"syslog\\\", \\\"single\\\", or\n\\\"halt\\\", such as the following line:\n\n disk_full_action = single\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag gid: \"V-72087\"\n tag rid: \"SV-86711r3_rule\"\n tag stig_id: \"RHEL-07-030320\"\n tag fix_id: \"F-78439r4_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('disk_full_action'.to_s) { should be_in ['syslog', 'single', 'halt'] }\n end\n\n# Test matches ./inspec-profiles/controls/V-73163.rb\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('network_failure_action'.to_s) { should be_in ['syslog', 'single', 'halt'] }\n end\nend\n","desc":"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.","descriptions":[{"data":"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the action the operating system takes if the disk the audit records\nare written to becomes full.\n\n To determine the action that takes place if the disk is full on the remote\nserver, use the following command:\n\n # grep -i disk_full_action /etc/audisp/audisp-remote.conf\n disk_full_action = single\n\n If the value of the \"disk_full_action\" option is not \"syslog\",\n\"single\", or \"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the action the operating system takes if the disk the audit\nrecords are written to becomes full.\n\n Uncomment or edit the \"disk_full_action\" option in\n\"/etc/audisp/audisp-remote.conf\" and set it to \"syslog\", \"single\", or\n\"halt\", such as the following line:\n\n disk_full_action = single","label":"fix"}],"id":"V-72087","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72087.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","gid":"V-72087","rid":"SV-86711r3_rule","stig_id":"RHEL-07-030320","fix_id":"F-78439r4_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when the audit storage volume is\nfull.","waiver_data":{}},{"code":"control \"V-72089\" do\n title \"The Red Hat Enterprise Linux operating system must initiate an action\nto notify the System Administrator (SA) and Information System Security Officer\nISSO, at a minimum, when allocated audit record storage volume reaches 75% of\nthe repository maximum audit record storage capacity.\"\n desc \"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates an action to notify the SA and ISSO\n(at a minimum) when allocated audit record storage volume reaches 75 percent of\nthe repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to with the following command:\n\n # grep -iw log_file /etc/audit/auditd.conf\n log_file = /var/log/audit/audit.log\n\n Check the size of the partition that audit records are written to (with the\nexample being \\\"/var/log/audit/\\\"):\n\n # df -h /var/log/audit/\n 0.9G /var/log/audit\n\n If the audit records are not being written to a partition specifically\ncreated for audit records (in this example \\\"/var/log/audit\\\" is a separate\npartition), determine the amount of space other files in the partition are\ncurrently occupying with the following command:\n\n # du -sh \n 1.8G /var\n\n Determine what the threshold is for the system to take action when 75\npercent of the repository maximum audit record storage capacity is reached:\n\n # grep -iw space_left /etc/audit/auditd.conf\n space_left = 225\n\n If the value of the \\\"space_left\\\" keyword is not set to 25 percent of the\ntotal partition size, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate an action to notify the SA and\nISSO (at a minimum) when allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to:\n\n # grep -iw log_file /etc/audit/auditd.conf\n\n Determine the size of the partition that audit records are written to (with\nthe example being \\\"/var/log/audit/\\\"):\n\n # df -h /var/log/audit/\n\n Set the value of the \\\"space_left\\\" keyword in \\\"/etc/audit/auditd.conf\\\"\nto 25 percent of the partition size.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000343-GPOS-00134\"\n tag gid: \"V-72089\"\n tag rid: \"SV-86713r4_rule\"\n tag stig_id: \"RHEL-07-030330\"\n tag fix_id: \"F-78441r3_fix\"\n tag cci: [\"CCI-001855\"]\n tag nist: [\"AU-5 (1)\"]\n\n if((f = file(audit_log_dir = command(\"dirname #{auditd_conf.log_file}\").stdout.strip)).directory?)\n # Fetch partition sizes in 1K blocks for consistency\n partition_info = command(\"df -B 1K #{audit_log_dir}\").stdout.split(\"\\n\")\n partition_sz_arr = partition_info.last.gsub(/\\s+/m, ' ').strip.split(\" \")\n\n # Get partition size\n partition_sz = partition_sz_arr[1]\n\n # Convert to MB and get 25%\n exp_space_left = partition_sz.to_i / 1024 / 4\n\n describe auditd_conf do\n its('space_left.to_i') { should be >= exp_space_left }\n end\n else\n describe f.directory? do\n it { should be true }\n end\n end\nend\n","desc":"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.","descriptions":[{"data":"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates an action to notify the SA and ISSO\n(at a minimum) when allocated audit record storage volume reaches 75 percent of\nthe repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to with the following command:\n\n # grep -iw log_file /etc/audit/auditd.conf\n log_file = /var/log/audit/audit.log\n\n Check the size of the partition that audit records are written to (with the\nexample being \"/var/log/audit/\"):\n\n # df -h /var/log/audit/\n 0.9G /var/log/audit\n\n If the audit records are not being written to a partition specifically\ncreated for audit records (in this example \"/var/log/audit\" is a separate\npartition), determine the amount of space other files in the partition are\ncurrently occupying with the following command:\n\n # du -sh \n 1.8G /var\n\n Determine what the threshold is for the system to take action when 75\npercent of the repository maximum audit record storage capacity is reached:\n\n # grep -iw space_left /etc/audit/auditd.conf\n space_left = 225\n\n If the value of the \"space_left\" keyword is not set to 25 percent of the\ntotal partition size, this is a finding.","label":"check"},{"data":"Configure the operating system to initiate an action to notify the SA and\nISSO (at a minimum) when allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to:\n\n # grep -iw log_file /etc/audit/auditd.conf\n\n Determine the size of the partition that audit records are written to (with\nthe example being \"/var/log/audit/\"):\n\n # df -h /var/log/audit/\n\n Set the value of the \"space_left\" keyword in \"/etc/audit/auditd.conf\"\nto 25 percent of the partition size.","label":"fix"}],"id":"V-72089","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72089.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72089","rid":"SV-86713r4_rule","stig_id":"RHEL-07-030330","fix_id":"F-78441r3_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must initiate an action\nto notify the System Administrator (SA) and Information System Security Officer\nISSO, at a minimum, when allocated audit record storage volume reaches 75% of\nthe repository maximum audit record storage capacity.","waiver_data":{}},{"code":"control \"V-72091\" do\n title \"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) via email when the threshold for the repository maximum audit\nrecord storage capacity is reached.\"\n desc \"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check what action the operating system takes when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i space_left_action /etc/audit/auditd.conf\n space_left_action = email\n\n If the value of the \\\"space_left_action\\\" keyword is not set to \\\"email\\\",\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \\\"space_left_action\\\" keyword in\n\\\"/etc/audit/auditd.conf\\\" and set it to \\\"email\\\".\n\n space_left_action = email\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000343-GPOS-00134\"\n tag gid: \"V-72091\"\n tag rid: \"SV-86715r2_rule\"\n tag stig_id: \"RHEL-07-030340\"\n tag fix_id: \"F-78443r1_fix\"\n tag cci: [\"CCI-001855\"]\n tag nist: [\"AU-5 (1)\"]\n\n describe auditd_conf do\n its('space_left_action.downcase') { should cmp 'email' }\n end\nend\n","desc":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","descriptions":[{"data":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check what action the operating system takes when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i space_left_action /etc/audit/auditd.conf\n space_left_action = email\n\n If the value of the \"space_left_action\" keyword is not set to \"email\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \"space_left_action\" keyword in\n\"/etc/audit/auditd.conf\" and set it to \"email\".\n\n space_left_action = email","label":"fix"}],"id":"V-72091","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72091.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72091","rid":"SV-86715r2_rule","stig_id":"RHEL-07-030340","fix_id":"F-78443r1_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) via email when the threshold for the repository maximum audit\nrecord storage capacity is reached.","waiver_data":{}},{"code":"control \"V-72093\" do\n title \"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) when the threshold for the repository maximum audit record\nstorage capacity is reached.\"\n desc \"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the threshold for the repository maximum audit record\nstorage capacity is reached.\n\n Check what account the operating system emails when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i action_mail_acct /etc/audit/auditd.conf\n action_mail_acct = root\n\n If the value of the \\\"action_mail_acct\\\" keyword is not set to \\\"root\\\" and\nother accounts for security personnel, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \\\"action_mail_acct\\\" keyword in\n\\\"/etc/audit/auditd.conf\\\" and set it to root and any other accounts associated\nwith security personnel.\n\n action_mail_acct = root\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000343-GPOS-00134\"\n tag gid: \"V-72093\"\n tag rid: \"SV-86717r3_rule\"\n tag stig_id: \"RHEL-07-030350\"\n tag fix_id: \"F-78445r3_fix\"\n tag cci: [\"CCI-001855\"]\n tag nist: [\"AU-5 (1)\"]\n\n describe auditd_conf do\n its('action_mail_acct') { should cmp 'root' }\n end\nend\n","desc":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","descriptions":[{"data":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the threshold for the repository maximum audit record\nstorage capacity is reached.\n\n Check what account the operating system emails when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i action_mail_acct /etc/audit/auditd.conf\n action_mail_acct = root\n\n If the value of the \"action_mail_acct\" keyword is not set to \"root\" and\nother accounts for security personnel, this is a finding.","label":"check"},{"data":"Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \"action_mail_acct\" keyword in\n\"/etc/audit/auditd.conf\" and set it to root and any other accounts associated\nwith security personnel.\n\n action_mail_acct = root","label":"fix"}],"id":"V-72093","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72093.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72093","rid":"SV-86717r3_rule","stig_id":"RHEL-07-030350","fix_id":"F-78445r3_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) when the threshold for the repository maximum audit record\nstorage capacity is reached.","waiver_data":{}},{"code":"control \"V-72095\" do\n title \"The Red Hat Enterprise Linux operating system must audit all\nexecutions of privileged functions.\"\n desc \"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system audits the execution of privileged functions\nusing the following command:\n\n # grep -iw execve /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules for \\\"SUID\\\" files are not\ndefined, this is a finding.\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules for \\\"SGID\\\" files are not\ndefined, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to audit the execution of privileged\nfunctions.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000327-GPOS-00127\"\n tag gid: \"V-72095\"\n tag rid: \"SV-86719r7_rule\"\n tag stig_id: \"RHEL-07-030360\"\n tag fix_id: \"F-78447r9_fix\"\n tag cci: [\"CCI-002234\"]\n tag nist: [\"AC-6 (9)\"]\n\n # All execve calls should use 'always,exit'\n describe auditd.syscall('execve') do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n\n # Work with the SUID rules\n describe auditd.syscall('execve').where { fields.include?('euid=0') } do\n its ('arch.uniq') { should include 'b32' }\n its ('arch.uniq') { should include 'b64' }\n end\n\n # Work with the SGID rules\n describe auditd.syscall('execve').where { fields.include?('egid=0') } do\n its ('arch.uniq') { should include 'b32' }\n its ('arch.uniq') { should include 'b64' }\n end\nend\n","desc":"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.","descriptions":[{"data":"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system audits the execution of privileged functions\nusing the following command:\n\n # grep -iw execve /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n\n If both the \"b32\" and \"b64\" audit rules for \"SUID\" files are not\ndefined, this is a finding.\n\n If both the \"b32\" and \"b64\" audit rules for \"SGID\" files are not\ndefined, this is a finding.","label":"check"},{"data":"Configure the operating system to audit the execution of privileged\nfunctions.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72095","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72095.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000327-GPOS-00127","gid":"V-72095","rid":"SV-86719r7_rule","stig_id":"RHEL-07-030360","fix_id":"F-78447r9_fix","cci":["CCI-002234"],"nist":["AC-6 (9)"]},"title":"The Red Hat Enterprise Linux operating system must audit all\nexecutions of privileged functions.","waiver_data":{}},{"code":"control \"V-72097\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chown syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chown\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw chown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"chown\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72097\"\n tag rid: \"SV-86721r5_rule\"\n tag stig_id: \"RHEL-07-030370\"\n tag fix_id: \"F-78449r8_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"chown\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"chown\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw chown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"chown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72097","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72097.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72097","rid":"SV-86721r5_rule","stig_id":"RHEL-07-030370","fix_id":"F-78449r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chown syscall.","waiver_data":{}},{"code":"control \"V-72099\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchown syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchown\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchown\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72099\"\n tag rid: \"SV-86723r5_rule\"\n tag stig_id: \"RHEL-07-030380\"\n tag fix_id: \"F-78451r8_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"fchown\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchown\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72099","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72099.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72099","rid":"SV-86723r5_rule","stig_id":"RHEL-07-030380","fix_id":"F-78451r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchown syscall.","waiver_data":{}},{"code":"control \"V-72101\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lchown syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"lchown\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw lchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"lchown\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72101\"\n tag rid: \"SV-86725r5_rule\"\n tag stig_id: \"RHEL-07-030390\"\n tag fix_id: \"F-78453r8_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"lchown\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"lchown\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lchown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lchown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72101","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72101.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72101","rid":"SV-86725r5_rule","stig_id":"RHEL-07-030390","fix_id":"F-78453r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lchown syscall.","waiver_data":{}},{"code":"control \"V-72103\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchownat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchownat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fchownat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchownat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72103\"\n tag rid: \"SV-86727r5_rule\"\n tag stig_id: \"RHEL-07-030400\"\n tag fix_id: \"F-78455r7_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"fchownat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchownat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchownat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fchownat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchownat\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72103","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72103.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72103","rid":"SV-86727r5_rule","stig_id":"RHEL-07-030400","fix_id":"F-78455r7_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchownat syscall.","waiver_data":{}},{"code":"control \"V-72105\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chmod syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chmod\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing command:\n\n # grep -iw chmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"chmod\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chmod\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72105\"\n tag rid: \"SV-86729r5_rule\"\n tag stig_id: \"RHEL-07-030410\"\n tag fix_id: \"F-78457r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"chmod\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"chmod\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chmod\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw chmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"chmod\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chmod\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72105","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72105.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72105","rid":"SV-86729r5_rule","stig_id":"RHEL-07-030410","fix_id":"F-78457r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chmod syscall.","waiver_data":{}},{"code":"control \"V-72107\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmod syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmod\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing command:\n\n # grep -iw fchmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchmod\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmod\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72107\"\n tag rid: \"SV-86731r5_rule\"\n tag stig_id: \"RHEL-07-030420\"\n tag fix_id: \"F-78459r9_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fchmod\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchmod\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchmod\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw fchmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchmod\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fchmod\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72107","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72107.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72107","rid":"SV-86731r5_rule","stig_id":"RHEL-07-030420","fix_id":"F-78459r9_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmod syscall.","waiver_data":{}},{"code":"control \"V-72109\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmodat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmodat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing command:\n\n # grep -iw fchmodat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchmodat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmodat\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72109\"\n tag rid: \"SV-86733r5_rule\"\n tag stig_id: \"RHEL-07-030430\"\n tag fix_id: \"F-78461r8_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fchmodat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchmodat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchmodat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw fchmodat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchmodat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fchmodat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72109","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72109.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72109","rid":"SV-86733r5_rule","stig_id":"RHEL-07-030430","fix_id":"F-78461r8_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmodat syscall.","waiver_data":{}},{"code":"control \"V-72111\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setxattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"setxattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw setxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"setxattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"setxattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72111\"\n tag rid: \"SV-86735r5_rule\"\n tag stig_id: \"RHEL-07-030440\"\n tag fix_id: \"F-78463r8_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"setxattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"setxattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw setxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"setxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72111","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72111.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72111","rid":"SV-86735r5_rule","stig_id":"RHEL-07-030440","fix_id":"F-78463r8_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setxattr syscall.","waiver_data":{}},{"code":"control \"V-72113\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fsetxattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fsetxattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fsetxattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fsetxattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72113\"\n tag rid: \"SV-86737r5_rule\"\n tag stig_id: \"RHEL-07-030450\"\n tag fix_id: \"F-78465r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fsetxattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fsetxattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fsetxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fsetxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fsetxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72113","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72113.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72113","rid":"SV-86737r5_rule","stig_id":"RHEL-07-030450","fix_id":"F-78465r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fsetxattr syscall.","waiver_data":{}},{"code":"control \"V-72115\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lsetxattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"lsetxattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw lsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"lsetxattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"lsetxattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72115\"\n tag rid: \"SV-86739r5_rule\"\n tag stig_id: \"RHEL-07-030460\"\n tag fix_id: \"F-78467r10_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"lsetxattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"lsetxattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lsetxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lsetxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"lsetxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72115","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72115.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72115","rid":"SV-86739r5_rule","stig_id":"RHEL-07-030460","fix_id":"F-78467r10_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lsetxattr syscall.","waiver_data":{}},{"code":"control \"V-72117\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe removexattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"removexattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw removexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"removexattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"removexattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72117\"\n tag rid: \"SV-86741r5_rule\"\n tag stig_id: \"RHEL-07-030470\"\n tag fix_id: \"F-78469r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"removexattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"removexattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"removexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw removexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"removexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"removexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72117","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72117.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72117","rid":"SV-86741r5_rule","stig_id":"RHEL-07-030470","fix_id":"F-78469r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe removexattr syscall.","waiver_data":{}},{"code":"control \"V-72119\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fremovexattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fremovexattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fremovexattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fremovexattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72119\"\n tag rid: \"SV-86743r5_rule\"\n tag stig_id: \"RHEL-07-030480\"\n tag fix_id: \"F-78471r6_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fremovexattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fremovexattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fremovexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fremovexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fremovexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72119","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72119.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72119","rid":"SV-86743r5_rule","stig_id":"RHEL-07-030480","fix_id":"F-78471r6_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fremovexattr syscall.","waiver_data":{}},{"code":"control \"V-72121\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lremovexattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"lremovexattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw lremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"lremovexattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"lremovexattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72121\"\n tag rid: \"SV-86745r5_rule\"\n tag stig_id: \"RHEL-07-030490\"\n tag fix_id: \"F-78473r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"lremovexattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"lremovexattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lremovexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lremovexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"lremovexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72121","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72121.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72121","rid":"SV-86745r5_rule","stig_id":"RHEL-07-030490","fix_id":"F-78473r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lremovexattr syscall.","waiver_data":{}},{"code":"control \"V-72123\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe creat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"creat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw creat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S creat F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"creat\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"creat\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules:\n\n -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72123\"\n tag rid: \"SV-86747r5_rule\"\n tag stig_id: \"RHEL-07-030500\"\n tag fix_id: \"F-78475r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"creat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"creat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n\n if os.arch == 'x86_64'\n describe auditd.syscall(\"creat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"creat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"creat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw creat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S creat F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"creat\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"creat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules:\n\n -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72123","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72123.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72123","rid":"SV-86747r5_rule","stig_id":"RHEL-07-030500","fix_id":"F-78475r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe creat syscall.","waiver_data":{}},{"code":"control \"V-72125\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"open\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw open /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"open\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"open\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72125\"\n tag rid: \"SV-86749r5_rule\"\n tag stig_id: \"RHEL-07-030510\"\n tag fix_id: \"F-78477r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"open\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n\n if os.arch == 'x86_64'\n describe auditd.syscall(\"open\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"open\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw open /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"open\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"open\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72125","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72125.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72125","rid":"SV-86749r5_rule","stig_id":"RHEL-07-030510","fix_id":"F-78477r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open syscall.","waiver_data":{}},{"code":"control \"V-72127\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe openat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"openat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw openat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"openat\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"openat\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72127\"\n tag rid: \"SV-86751r5_rule\"\n tag stig_id: \"RHEL-07-030520\"\n tag fix_id: \"F-78479r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"openat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"openat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"openat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"openat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"openat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw openat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"openat\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"openat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72127","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72127.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72127","rid":"SV-86751r5_rule","stig_id":"RHEL-07-030520","fix_id":"F-78479r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe openat syscall.","waiver_data":{}},{"code":"control \"V-72129\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open_by_handle_at syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"open_by_handle_at\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw open_by_handle_at /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"open_by_handle_at\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"open_by_handle_at\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72129\"\n tag rid: \"SV-86753r5_rule\"\n tag stig_id: \"RHEL-07-030530\"\n tag fix_id: \"F-78481r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"open_by_handle_at\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw open_by_handle_at /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"open_by_handle_at\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"open_by_handle_at\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72129","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72129.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72129","rid":"SV-86753r5_rule","stig_id":"RHEL-07-030530","fix_id":"F-78481r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open_by_handle_at syscall.","waiver_data":{}},{"code":"control \"V-72131\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe truncate syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"truncate\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw truncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"truncate\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"truncate\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72131\"\n tag rid: \"SV-86755r5_rule\"\n tag stig_id: \"RHEL-07-030540\"\n tag fix_id: \"F-78483r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"truncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"truncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"truncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"truncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"truncate\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw truncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"truncate\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"truncate\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72131","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72131.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72131","rid":"SV-86755r5_rule","stig_id":"RHEL-07-030540","fix_id":"F-78483r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe truncate syscall.","waiver_data":{}},{"code":"control \"V-72133\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ftruncate syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"ftruncate\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw ftruncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"ftruncate\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"ftruncate\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72133\"\n tag rid: \"SV-86757r5_rule\"\n tag stig_id: \"RHEL-07-030550\"\n tag fix_id: \"F-78485r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"ftruncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"ftruncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"ftruncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"ftruncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"ftruncate\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw ftruncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"ftruncate\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"ftruncate\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72133","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72133.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72133","rid":"SV-86757r5_rule","stig_id":"RHEL-07-030550","fix_id":"F-78485r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ftruncate syscall.","waiver_data":{}},{"code":"control \"V-72135\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe semanage command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"semanage\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/sbin/semanage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"semanage\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72135\"\n tag rid: \"SV-86759r4_rule\"\n tag stig_id: \"RHEL-07-030560\"\n tag fix_id: \"F-78487r5_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/semanage'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"semanage\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/semanage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"semanage\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72135","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72135.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72135","rid":"SV-86759r4_rule","stig_id":"RHEL-07-030560","fix_id":"F-78487r5_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe semanage command.","waiver_data":{}},{"code":"control \"V-72137\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setsebool command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"setsebool\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/sbin/setsebool /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"setsebool\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72137\"\n tag rid: \"SV-86761r4_rule\"\n tag stig_id: \"RHEL-07-030570\"\n tag fix_id: \"F-78489r6_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/setsebool'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setsebool\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/setsebool /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setsebool\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72137","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72137.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72137","rid":"SV-86761r4_rule","stig_id":"RHEL-07-030570","fix_id":"F-78489r6_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setsebool command.","waiver_data":{}},{"code":"control \"V-72139\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chcon command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chcon\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/chcon /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chcon\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72139\"\n tag rid: \"SV-86763r4_rule\"\n tag stig_id: \"RHEL-07-030580\"\n tag fix_id: \"F-78491r6_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/chcon'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chcon\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/chcon /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chcon\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72139","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72139.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72139","rid":"SV-86763r4_rule","stig_id":"RHEL-07-030580","fix_id":"F-78491r6_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chcon command.","waiver_data":{}},{"code":"control \"V-72141\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setfiles command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"setfiles\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw /usr/sbin/setfiles /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"setfiles\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72141\"\n tag rid: \"SV-86765r5_rule\"\n tag stig_id: \"RHEL-07-030590\"\n tag fix_id: \"F-78493r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/setfiles'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setfiles\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw /usr/sbin/setfiles /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setfiles\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72141","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72141.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72141","rid":"SV-86765r5_rule","stig_id":"RHEL-07-030590","fix_id":"F-78493r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setfiles command.","waiver_data":{}},{"code":"control \"V-72145\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all unsuccessful account access events.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when unsuccessful\naccount access events occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommands:\n\n # grep -i /var/run/faillock /etc/audit/audit.rules\n\n -w /var/run/faillock -p wa -k logins\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when unsuccessful\naccount access events occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /var/run/faillock -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000470-GPOS-00214\",\n\"SRG-OS-000473-GPOS-00218\"]\n tag gid: \"V-72145\"\n tag rid: \"SV-86769r4_rule\"\n tag stig_id: \"RHEL-07-030610\"\n tag fix_id: \"F-78497r4_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/var/run/faillock'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when unsuccessful\naccount access events occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommands:\n\n # grep -i /var/run/faillock /etc/audit/audit.rules\n\n -w /var/run/faillock -p wa -k logins\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when unsuccessful\naccount access events occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /var/run/faillock -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72145","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72145.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000470-GPOS-00214","SRG-OS-000473-GPOS-00218"],"gid":"V-72145","rid":"SV-86769r4_rule","stig_id":"RHEL-07-030610","fix_id":"F-78497r4_fix","cci":["CCI-000126","CCI-000172","CCI-002884"],"nist":["AU-2 d","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all unsuccessful account access events.","waiver_data":{}},{"code":"control \"V-72147\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all successful account access events.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when successful account\naccess events occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -i /var/log/lastlog /etc/audit/audit.rules\n\n -w /var/log/lastlog -p wa -k logins\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when successful\naccount access events occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /var/log/lastlog -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000470-GPOS-00214\",\n\"SRG-OS-000473-GPOS-00218\"]\n tag gid: \"V-72147\"\n tag rid: \"SV-86771r3_rule\"\n tag stig_id: \"RHEL-07-030620\"\n tag fix_id: \"F-78499r3_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/var/log/lastlog'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when successful account\naccess events occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -i /var/log/lastlog /etc/audit/audit.rules\n\n -w /var/log/lastlog -p wa -k logins\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when successful\naccount access events occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /var/log/lastlog -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72147","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72147.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000470-GPOS-00214","SRG-OS-000473-GPOS-00218"],"gid":"V-72147","rid":"SV-86771r3_rule","stig_id":"RHEL-07-030620","fix_id":"F-78499r3_fix","cci":["CCI-000126","CCI-000172","CCI-002884"],"nist":["AU-2 d","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all successful account access events.","waiver_data":{}},{"code":"control \"V-72149\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe passwd command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"passwd\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/passwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"passwd\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72149\"\n tag rid: \"SV-86773r5_rule\"\n tag stig_id: \"RHEL-07-030630\"\n tag fix_id: \"F-78501r6_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/passwd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"passwd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/passwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"passwd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72149","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72149.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72149","rid":"SV-86773r5_rule","stig_id":"RHEL-07-030630","fix_id":"F-78501r6_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe passwd command.","waiver_data":{}},{"code":"control \"V-72151\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unix_chkpwd command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"unix_chkpwd\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw /usr/sbin/unix_chkpwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"unix_chkpwd\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72151\"\n tag rid: \"SV-86775r5_rule\"\n tag stig_id: \"RHEL-07-030640\"\n tag fix_id: \"F-78503r8_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/unix_chkpwd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unix_chkpwd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw /usr/sbin/unix_chkpwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unix_chkpwd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72151","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72151.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72151","rid":"SV-86775r5_rule","stig_id":"RHEL-07-030640","fix_id":"F-78503r8_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unix_chkpwd command.","waiver_data":{}},{"code":"control \"V-72153\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe gpasswd command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"gpasswd\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/gpasswd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"gpasswd\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72153\"\n tag rid: \"SV-86777r5_rule\"\n tag stig_id: \"RHEL-07-030650\"\n tag fix_id: \"F-78505r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/gpasswd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"gpasswd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/gpasswd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"gpasswd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72153","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72153.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72153","rid":"SV-86777r5_rule","stig_id":"RHEL-07-030650","fix_id":"F-78505r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe gpasswd command.","waiver_data":{}},{"code":"control \"V-72155\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chage command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chage\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/chage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chage\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72155\"\n tag rid: \"SV-86779r5_rule\"\n tag stig_id: \"RHEL-07-030660\"\n tag fix_id: \"F-78507r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/chage'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chage\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/chage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chage\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72155","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72155.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72155","rid":"SV-86779r5_rule","stig_id":"RHEL-07-030660","fix_id":"F-78507r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chage command.","waiver_data":{}},{"code":"control \"V-72157\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe userhelper command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"userhelper\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/sbin/userhelper /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"userhelper\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72157\"\n tag rid: \"SV-86781r5_rule\"\n tag stig_id: \"RHEL-07-030670\"\n tag fix_id: \"F-78509r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/userhelper'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"userhelper\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/userhelper /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"userhelper\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72157","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72157.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72157","rid":"SV-86781r5_rule","stig_id":"RHEL-07-030670","fix_id":"F-78509r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe userhelper command.","waiver_data":{}},{"code":"control \"V-72159\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe su command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"su\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/bin/su /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"su\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72159\"\n tag rid: \"SV-86783r5_rule\"\n tag stig_id: \"RHEL-07-030680\"\n tag fix_id: \"F-78511r6_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/su'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"su\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/su /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"su\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72159","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72159.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72159","rid":"SV-86783r5_rule","stig_id":"RHEL-07-030680","fix_id":"F-78511r6_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe su command.","waiver_data":{}},{"code":"control \"V-72161\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudo command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"sudo\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/bin/sudo /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"sudo\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72161\"\n tag rid: \"SV-86785r4_rule\"\n tag stig_id: \"RHEL-07-030690\"\n tag fix_id: \"F-78513r5_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/sudo'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"sudo\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/sudo /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"sudo\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72161","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72161.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72161","rid":"SV-86785r4_rule","stig_id":"RHEL-07-030690","fix_id":"F-78513r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudo command.","waiver_data":{}},{"code":"control \"V-72163\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudoers file and all files in the /etc/sudoers.d/ directory.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to access the \\\"/etc/sudoers\\\" file and files\nin the \\\"/etc/sudoers.d/\\\" directory.\n\n Check for modification of the following files being audited by performing\nthe following commands to check the file system rules in\n\\\"/etc/audit/audit.rules\\\":\n\n # grep -i \\\"/etc/sudoers\\\" /etc/audit/audit.rules\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n # grep -i \\\"/etc/sudoers.d/\\\" /etc/audit/audit.rules\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n If the commands do not return output that match the examples, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to access the \\\"/etc/sudoers\\\" file and files\nin the \\\"/etc/sudoers.d/\\\" directory.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72163\"\n tag rid: \"SV-86787r5_rule\"\n tag stig_id: \"RHEL-07-030700\"\n tag fix_id: \"F-78517r6_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_files = ['/etc/sudoers', '/etc/sudoers.d']\n\n if audit_files.any? { |audit_file| file(audit_file).exist? }\n impact 0.5\n else\n impact 0.0\n end\n\n audit_files.each do |audit_file|\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n end\n\n describe \"The #{audit_files} files do not exist\" do\n skip \"The #{audit_files} files do not exist, this requirement is Not Applicable.\"\n end if !audit_files.any? { |audit_file| file(audit_file).exist? }\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to access the \"/etc/sudoers\" file and files\nin the \"/etc/sudoers.d/\" directory.\n\n Check for modification of the following files being audited by performing\nthe following commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -i \"/etc/sudoers\" /etc/audit/audit.rules\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n # grep -i \"/etc/sudoers.d/\" /etc/audit/audit.rules\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n If the commands do not return output that match the examples, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to access the \"/etc/sudoers\" file and files\nin the \"/etc/sudoers.d/\" directory.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72163","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72163.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72163","rid":"SV-86787r5_rule","stig_id":"RHEL-07-030700","fix_id":"F-78517r6_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudoers file and all files in the /etc/sudoers.d/ directory.","waiver_data":{}},{"code":"control \"V-72165\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe newgrp command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"newgrp\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -i /usr/bin/newgrp /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"newgrp\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72165\"\n tag rid: \"SV-86789r4_rule\"\n tag stig_id: \"RHEL-07-030710\"\n tag fix_id: \"F-78519r5_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/newgrp'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"newgrp\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -i /usr/bin/newgrp /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"newgrp\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72165","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72165.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72165","rid":"SV-86789r4_rule","stig_id":"RHEL-07-030710","fix_id":"F-78519r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe newgrp command.","waiver_data":{}},{"code":"control \"V-72167\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chsh command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chsh\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -i /usr/bin/chsh /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chsh\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72167\"\n tag rid: \"SV-86791r4_rule\"\n tag stig_id: \"RHEL-07-030720\"\n tag fix_id: \"F-78521r5_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/chsh'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chsh\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -i /usr/bin/chsh /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chsh\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72167","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72167.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72167","rid":"SV-86791r4_rule","stig_id":"RHEL-07-030720","fix_id":"F-78521r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chsh command.","waiver_data":{}},{"code":"control \"V-72171\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe mount command and syscall.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"mount\\\" command and syscall occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\\\"/etc/audit/audit.rules\\\":\n\n # grep -iw \\\"mount\\\" /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"mount\\\" syscall, this is a finding.\n\n If all uses of the \\\"mount\\\" command are not being audited, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"mount\\\" command and syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72171\"\n tag rid: \"SV-86795r7_rule\"\n tag stig_id: \"RHEL-07-030740\"\n tag fix_id: \"F-78525r9_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"mount\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n\n if os.arch == 'x86_64'\n describe auditd.syscall(\"mount\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\n\n describe auditd.path(\"/usr/bin/mount\") do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"mount\" command and syscall occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -iw \"mount\" /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"mount\" syscall, this is a finding.\n\n If all uses of the \"mount\" command are not being audited, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"mount\" command and syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72171","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72171.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72171","rid":"SV-86795r7_rule","stig_id":"RHEL-07-030740","fix_id":"F-78525r9_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe mount command and syscall.","waiver_data":{}},{"code":"control \"V-72173\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe umount command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"umount\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\\\"/etc/audit/audit.rules\\\":\n\n # grep -iw \\\"/usr/bin/umount\\\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"umount\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72173\"\n tag rid: \"SV-86797r5_rule\"\n tag stig_id: \"RHEL-07-030750\"\n tag fix_id: \"F-78527r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n audit_file = '/bin/umount'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"umount\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -iw \"/usr/bin/umount\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"umount\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72173","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72173.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72173","rid":"SV-86797r5_rule","stig_id":"RHEL-07-030750","fix_id":"F-78527r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe umount command.","waiver_data":{}},{"code":"control \"V-72175\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postdrop command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"postdrop\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/sbin/postdrop /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"postdrop\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72175\"\n tag rid: \"SV-86799r4_rule\"\n tag stig_id: \"RHEL-07-030760\"\n tag fix_id: \"F-78529r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/postdrop'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"postdrop\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/sbin/postdrop /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"postdrop\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72175","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72175.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72175","rid":"SV-86799r4_rule","stig_id":"RHEL-07-030760","fix_id":"F-78529r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postdrop command.","waiver_data":{}},{"code":"control \"V-72177\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postqueue command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"postqueue\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/sbin/postqueue /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"postqueue\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72177\"\n tag rid: \"SV-86801r3_rule\"\n tag stig_id: \"RHEL-07-030770\"\n tag fix_id: \"F-78531r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/postqueue'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"postqueue\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/sbin/postqueue /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"postqueue\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72177","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72177.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72177","rid":"SV-86801r3_rule","stig_id":"RHEL-07-030770","fix_id":"F-78531r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postqueue command.","waiver_data":{}},{"code":"control \"V-72179\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ssh-keysign command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"ssh-keysign\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/libexec/openssh/ssh-keysign /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"ssh-keysign\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72179\"\n tag rid: \"SV-86803r3_rule\"\n tag stig_id: \"RHEL-07-030780\"\n tag fix_id: \"F-78533r4_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/libexec/openssh/ssh-keysign'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"ssh-keysign\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/libexec/openssh/ssh-keysign /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"ssh-keysign\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72179","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72179.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72179","rid":"SV-86803r3_rule","stig_id":"RHEL-07-030780","fix_id":"F-78533r4_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ssh-keysign command.","waiver_data":{}},{"code":"control \"V-72183\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe crontab command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"crontab\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/bin/crontab /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"crontab\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72183\"\n tag rid: \"SV-86807r3_rule\"\n tag stig_id: \"RHEL-07-030800\"\n tag fix_id: \"F-78537r4_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/crontab'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"crontab\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/crontab /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"crontab\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72183","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72183.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72183","rid":"SV-86807r3_rule","stig_id":"RHEL-07-030800","fix_id":"F-78537r4_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe crontab command.","waiver_data":{}},{"code":"control \"V-72185\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe pam_timestamp_check command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"pam_timestamp_check\\\" command\noccur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw \\\"/usr/sbin/pam_timestamp_check\\\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"pam_timestamp_check\\\" command\noccur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00215\"\n tag gid: \"V-72185\"\n tag rid: \"SV-86809r4_rule\"\n tag stig_id: \"RHEL-07-030810\"\n tag fix_id: \"F-78539r4_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n audit_file = '/sbin/pam_timestamp_check'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"pam_timestamp_check\" command\noccur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw \"/usr/sbin/pam_timestamp_check\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"pam_timestamp_check\" command\noccur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72185","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72185.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00215","gid":"V-72185","rid":"SV-86809r4_rule","stig_id":"RHEL-07-030810","fix_id":"F-78539r4_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe pam_timestamp_check command.","waiver_data":{}},{"code":"control \"V-72187\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe init_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"init_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw init_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"init_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"init_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-72187\"\n tag rid: \"SV-86811r5_rule\"\n tag stig_id: \"RHEL-07-030820\"\n tag fix_id: \"F-78541r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"init_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"init_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"init_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw init_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"init_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"init_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72187","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72187.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72187","rid":"SV-86811r5_rule","stig_id":"RHEL-07-030820","fix_id":"F-78541r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe init_module syscall.","waiver_data":{}},{"code":"control \"V-72189\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe delete_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"delete_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw delete_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"delete_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"delete_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-72189\"\n tag rid: \"SV-86813r5_rule\"\n tag stig_id: \"RHEL-07-030830\"\n tag fix_id: \"F-78543r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"delete_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"delete_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"delete_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw delete_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"delete_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"delete_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72189","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72189.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72189","rid":"SV-86813r5_rule","stig_id":"RHEL-07-030830","fix_id":"F-78543r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe delete_module syscall.","waiver_data":{}},{"code":"control \"V-72191\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe kmod command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"kmod\\\" command occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw kmod /etc/audit/audit.rules\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"kmod\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-72191\"\n tag rid: \"SV-86815r5_rule\"\n tag stig_id: \"RHEL-07-030840\"\n tag fix_id: \"F-78545r10_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n audit_file = '/usr/bin/kmod'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"kmod\" command occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw kmod /etc/audit/audit.rules\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"kmod\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72191","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72191.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72191","rid":"SV-86815r5_rule","stig_id":"RHEL-07-030840","fix_id":"F-78545r10_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe kmod command.","waiver_data":{}},{"code":"control \"V-72197\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/passwd.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/passwd\\\".\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/passwd /etc/audit/audit.rules\n\n -w /etc/passwd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/passwd\\\".\n\n Add or update the following rule \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/passwd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag satisfies: [\"SRG-OS-000004-GPOS-00004\", \"SRG-OS-000239-GPOS-00089\",\n\"SRG-OS-000240-GPOS-00090\", \"SRG-OS-000241-GPOS-00091\",\n\"SRG-OS-000303-GPOS-00120\", \"SRG-OS-000476-GPOS-00221\"]\n tag gid: \"V-72197\"\n tag rid: \"SV-86821r5_rule\"\n tag stig_id: \"RHEL-07-030870\"\n tag fix_id: \"F-78551r4_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/passwd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/passwd\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/passwd /etc/audit/audit.rules\n\n -w /etc/passwd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/passwd\".\n\n Add or update the following rule \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/passwd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72197","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72197.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","satisfies":["SRG-OS-000004-GPOS-00004","SRG-OS-000239-GPOS-00089","SRG-OS-000240-GPOS-00090","SRG-OS-000241-GPOS-00091","SRG-OS-000303-GPOS-00120","SRG-OS-000476-GPOS-00221"],"gid":"V-72197","rid":"SV-86821r5_rule","stig_id":"RHEL-07-030870","fix_id":"F-78551r4_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/passwd.","waiver_data":{}},{"code":"control \"V-72199\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rename syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"rename\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw rename /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"rename\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"rename\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72199\"\n tag rid: \"SV-86823r5_rule\"\n tag stig_id: \"RHEL-07-030880\"\n tag fix_id: \"F-78553r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"rename\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"rename\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"rename\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw rename /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"rename\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"rename\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72199","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72199.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72199","rid":"SV-86823r5_rule","stig_id":"RHEL-07-030880","fix_id":"F-78553r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rename syscall.","waiver_data":{}},{"code":"control \"V-72201\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe renameat syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"renameat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw renameat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"renameat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"renameat\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72201\"\n tag rid: \"SV-86825r5_rule\"\n tag stig_id: \"RHEL-07-030890\"\n tag fix_id: \"F-78555r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"renameat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"renameat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"renameat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw renameat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"renameat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"renameat\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72201","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72201.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72201","rid":"SV-86825r5_rule","stig_id":"RHEL-07-030890","fix_id":"F-78555r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe renameat syscall.","waiver_data":{}},{"code":"control \"V-72203\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rmdir syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"rmdir\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw rmdir /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"rmdir\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"rmdir\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72203\"\n tag rid: \"SV-86827r5_rule\"\n tag stig_id: \"RHEL-07-030900\"\n tag fix_id: \"F-78557r9_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"rmdir\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"rmdir\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"rmdir\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw rmdir /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"rmdir\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"rmdir\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72203","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72203.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72203","rid":"SV-86827r5_rule","stig_id":"RHEL-07-030900","fix_id":"F-78557r9_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rmdir syscall.","waiver_data":{}},{"code":"control \"V-72205\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlink syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlink\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw unlink /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"unlink\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlink\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72205\"\n tag rid: \"SV-86829r5_rule\"\n tag stig_id: \"RHEL-07-030910\"\n tag fix_id: \"F-78559r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"unlink\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"unlink\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unlink\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw unlink /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"unlink\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unlink\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72205","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72205.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72205","rid":"SV-86829r5_rule","stig_id":"RHEL-07-030910","fix_id":"F-78559r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlink syscall.","waiver_data":{}},{"code":"control \"V-72207\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlinkat syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlinkat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw unlinkat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"unlinkat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlinkat\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72207\"\n tag rid: \"SV-86831r5_rule\"\n tag stig_id: \"RHEL-07-030920\"\n tag fix_id: \"F-78561r10_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"unlinkat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"unlinkat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unlinkat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw unlinkat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"unlinkat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unlinkat\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72207","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72207.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72207","rid":"SV-86831r5_rule","stig_id":"RHEL-07-030920","fix_id":"F-78561r10_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlinkat syscall.","waiver_data":{}},{"code":"control \"V-72209\" do\n title \"The Red Hat Enterprise Linux operating system must send rsyslog output\nto a log aggregation server.\"\n desc \"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify \\\"rsyslog\\\" is configured to send all messages to a log aggregation\nserver.\n\n Check the configuration of \\\"rsyslog\\\" with the following command:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \\\"/etc/rsyslog.conf\\\".\n\n # grep @ /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n *.* @@logagg.site.mil\n\n If there are no lines in the \\\"/etc/rsyslog.conf\\\" or\n\\\"/etc/rsyslog.d/*.conf\\\" files that contain the \\\"@\\\" or \\\"@@\\\" symbol(s), and\nthe lines with the correct symbol(s) to send output to another system do not\ncover all \\\"rsyslog\\\" output, ask the System Administrator to indicate how the\naudit logs are off-loaded to a different system or media.\n\n If the lines are commented out or there is no evidence that the audit logs\nare being sent to another system, this is a finding.\n \"\n desc \"fix\", \"\n Modify the \\\"/etc/rsyslog.conf\\\" or an \\\"/etc/rsyslog.d/*.conf\\\" file to\ncontain a configuration line to send all \\\"rsyslog\\\" output to a log\naggregation system:\n *.* @@\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72209\"\n tag rid: \"SV-86833r2_rule\"\n tag stig_id: \"RHEL-07-031000\"\n tag fix_id: \"F-78563r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n\n if input('alternate_logs')\n describe \"An alternate logging system is used. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"An alternate logging system is used. This check must be performed manually\"\n end\n else\n describe command(\"grep @ #{input('log_pkg_path')} | grep -v \\\"^#\\\"\") do\n its('stdout.strip') { should_not be_empty }\n end\n end\nend\n","desc":"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.","descriptions":[{"data":"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify \"rsyslog\" is configured to send all messages to a log aggregation\nserver.\n\n Check the configuration of \"rsyslog\" with the following command:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \"/etc/rsyslog.conf\".\n\n # grep @ /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n *.* @@logagg.site.mil\n\n If there are no lines in the \"/etc/rsyslog.conf\" or\n\"/etc/rsyslog.d/*.conf\" files that contain the \"@\" or \"@@\" symbol(s), and\nthe lines with the correct symbol(s) to send output to another system do not\ncover all \"rsyslog\" output, ask the System Administrator to indicate how the\naudit logs are off-loaded to a different system or media.\n\n If the lines are commented out or there is no evidence that the audit logs\nare being sent to another system, this is a finding.","label":"check"},{"data":"Modify the \"/etc/rsyslog.conf\" or an \"/etc/rsyslog.d/*.conf\" file to\ncontain a configuration line to send all \"rsyslog\" output to a log\naggregation system:\n *.* @@","label":"fix"}],"id":"V-72209","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72209.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72209","rid":"SV-86833r2_rule","stig_id":"RHEL-07-031000","fix_id":"F-78563r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must send rsyslog output\nto a log aggregation server.","waiver_data":{}},{"code":"control \"V-72211\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the rsyslog daemon does not accept log messages from other servers unless\nthe server is being used for log aggregation.\"\n desc \"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the system is not accepting \\\"rsyslog\\\" messages from other\nsystems unless it is documented as a log aggregation server.\n\n Check the configuration of \\\"rsyslog\\\" with the following command:\n\n # grep imtcp /etc/rsyslog.conf\n $ModLoad imtcp\n # grep imudp /etc/rsyslog.conf\n $ModLoad imudp\n # grep imrelp /etc/rsyslog.conf\n $ModLoad imrelp\n\n If any of the above modules are being loaded in the \\\"/etc/rsyslog.conf\\\"\nfile, ask to see the documentation for the system being used for log\naggregation.\n\n If the documentation does not exist, or does not specify the server as a\nlog aggregation system, this is a finding.\n \"\n desc \"fix\", \"Modify the \\\"/etc/rsyslog.conf\\\" file to remove the \\\"ModLoad\nimtcp\\\", \\\"ModLoad imudp\\\", and \\\"ModLoad imrelp\\\" configuration lines, or\ndocument the system as being used for log aggregation.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72211\"\n tag rid: \"SV-86835r2_rule\"\n tag stig_id: \"RHEL-07-031010\"\n tag fix_id: \"F-78565r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n log_aggregation_server = input('log_aggregation_server')\n\n if log_aggregation_server\n describe file('/etc/rsyslog.conf') do\n its('content') { should match %r{^\\$ModLoad\\s+imtcp.*\\n?$} }\n end\n else\n describe.one do\n describe file('/etc/rsyslog.conf') do\n its('content') { should match %r{\\$ModLoad\\s+imtcp.*\\n?$} }\n end\n describe file('/etc/rsyslog.conf') do\n its('content') { should_not match %r{^\\$ModLoad\\s+imtcp.*\\n?$} }\n end\n end\n end\nend\n","desc":"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.","descriptions":[{"data":"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the system is not accepting \"rsyslog\" messages from other\nsystems unless it is documented as a log aggregation server.\n\n Check the configuration of \"rsyslog\" with the following command:\n\n # grep imtcp /etc/rsyslog.conf\n $ModLoad imtcp\n # grep imudp /etc/rsyslog.conf\n $ModLoad imudp\n # grep imrelp /etc/rsyslog.conf\n $ModLoad imrelp\n\n If any of the above modules are being loaded in the \"/etc/rsyslog.conf\"\nfile, ask to see the documentation for the system being used for log\naggregation.\n\n If the documentation does not exist, or does not specify the server as a\nlog aggregation system, this is a finding.","label":"check"},{"data":"Modify the \"/etc/rsyslog.conf\" file to remove the \"ModLoad\nimtcp\", \"ModLoad imudp\", and \"ModLoad imrelp\" configuration lines, or\ndocument the system as being used for log aggregation.","label":"fix"}],"id":"V-72211","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72211.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72211","rid":"SV-86835r2_rule","stig_id":"RHEL-07-031010","fix_id":"F-78565r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the rsyslog daemon does not accept log messages from other servers unless\nthe server is being used for log aggregation.","waiver_data":{}},{"code":"control \"V-72213\" do\n title \"The Red Hat Enterprise Linux operating system must use a virus scan\nprogram.\"\n desc \"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify an anti-virus solution is installed on the system. The anti-virus\nsolution may be bundled with an approved host-based security solution.\n\n If there is no anti-virus solution installed on the system, this is a\nfinding.\n \"\n desc \"fix\", \"Install an antivirus solution on the system.\"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72213\"\n tag rid: \"SV-86837r3_rule\"\n tag stig_id: \"RHEL-07-032000\"\n tag fix_id: \"F-78567r2_fix\"\n tag cci: [\"CCI-001668\"]\n tag nist: [\"SI-3 a\"]\n\n custom_antivirus = input('custom_antivirus')\n\n if ! custom_antivirus\n describe.one do\n describe service('nails') do\n it { should be_running }\n end\n describe service('clamav-daemon.socket') do\n it { should be_running }\n end\n describe service('ds_agent') do\n it { should be_running }\n end\n end\n else\n # Allow user to provide a description of their AV solution\n # for documentation.\n custom_antivirus_description = input('custom_antivirus_description')\n describe \"Antivirus: #{custom_antivirus_description}\" do\n subject { custom_antivirus_description }\n it { should_not cmp 'None' }\n end\n end\nend\n","desc":"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.","descriptions":[{"data":"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify an anti-virus solution is installed on the system. The anti-virus\nsolution may be bundled with an approved host-based security solution.\n\n If there is no anti-virus solution installed on the system, this is a\nfinding.","label":"check"},{"data":"Install an antivirus solution on the system.","label":"fix"}],"id":"V-72213","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72213.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72213","rid":"SV-86837r3_rule","stig_id":"RHEL-07-032000","fix_id":"F-78567r2_fix","cci":["CCI-001668"],"nist":["SI-3 a"]},"title":"The Red Hat Enterprise Linux operating system must use a virus scan\nprogram.","waiver_data":{}},{"code":"control \"V-72217\" do\n title \"The Red Hat Enterprise Linux operating system must limit the number of\nconcurrent sessions to 10 for all accounts and/or account types.\"\n desc \"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system limits the number of concurrent sessions to\n\\\"10\\\" for all accounts and/or account types by issuing the following command:\n\n # grep \\\"maxlogins\\\" /etc/security/limits.conf /etc/security/limits.d/*.conf\n\n * hard maxlogins 10\n\n This can be set as a global domain (with the * wildcard) but may be set\ndifferently for multiple domains.\n\n If the \\\"maxlogins\\\" item is missing, commented out, or the value is not\nset to \\\"10\\\" or less for all domains that have the \\\"maxlogins\\\" item\nassigned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to limit the number of concurrent sessions\nto \\\"10\\\" for all accounts and/or account types.\n\n Add the following line to the top of the /etc/security/limits.conf or in a\n\\\".conf\\\" file defined in /etc/security/limits.d/ :\n\n * hard maxlogins 10\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000027-GPOS-00008\"\n tag gid: \"V-72217\"\n tag rid: \"SV-86841r3_rule\"\n tag stig_id: \"RHEL-07-040000\"\n tag fix_id: \"F-78571r2_fix\"\n tag cci: [\"CCI-000054\"]\n tag nist: [\"AC-10\"]\n\n maxlogins_limit = input('maxlogins_limit')\n\n # Collect any files under limits.d if they exist\n limits_files = directory('/etc/security/limits.d').exist? ? command('ls /etc/security/limits.d/*.conf').stdout.strip.lines : []\n # Add limits.conf to the list\n limits_files.push('/etc/security/limits.conf')\n compliant_files = []\n noncompliant_files = []\n\n limits_files.each do |limits_file|\n # Get any universal limits from each file\n local_limits = limits_conf(limits_file).*\n # If we got an array (results) check further\n if local_limits.is_a?(Array)\n local_limits.each do |temp_limit|\n # For each result check if it is a 'hard' limit for 'maxlogins'\n if temp_limit.include?('hard') && temp_limit.include?('maxlogins')\n # If the limit is in range, push to compliant files\n if temp_limit[-1].to_i <= maxlogins_limit\n compliant_files.push(limits_file)\n # Otherwise add to noncompliant files\n else\n noncompliant_files.push(limits_file)\n end\n end\n end\n end\n end\n\n # It is required that at least 1 file contain compliant configuration\n describe \"Files configuring maxlogins less than or equal to #{maxlogins_limit}\" do\n subject { compliant_files.length }\n it { should be_positive }\n end\n\n # No files should set 'hard' 'maxlogins' to any noncompliant value\n describe \"Files configuring maxlogins greater than #{maxlogins_limit}\" do\n subject { noncompliant_files }\n it { should cmp [] }\n end\nend\n","desc":"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.","descriptions":[{"data":"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system limits the number of concurrent sessions to\n\"10\" for all accounts and/or account types by issuing the following command:\n\n # grep \"maxlogins\" /etc/security/limits.conf /etc/security/limits.d/*.conf\n\n * hard maxlogins 10\n\n This can be set as a global domain (with the * wildcard) but may be set\ndifferently for multiple domains.\n\n If the \"maxlogins\" item is missing, commented out, or the value is not\nset to \"10\" or less for all domains that have the \"maxlogins\" item\nassigned, this is a finding.","label":"check"},{"data":"Configure the operating system to limit the number of concurrent sessions\nto \"10\" for all accounts and/or account types.\n\n Add the following line to the top of the /etc/security/limits.conf or in a\n\".conf\" file defined in /etc/security/limits.d/ :\n\n * hard maxlogins 10","label":"fix"}],"id":"V-72217","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72217.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000027-GPOS-00008","gid":"V-72217","rid":"SV-86841r3_rule","stig_id":"RHEL-07-040000","fix_id":"F-78571r2_fix","cci":["CCI-000054"],"nist":["AC-10"]},"title":"The Red Hat Enterprise Linux operating system must limit the number of\nconcurrent sessions to 10 for all accounts and/or account types.","waiver_data":{}},{"code":"control \"V-72219\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nprohibit or restrict the use of functions, ports, protocols, and/or services,\nas defined in the Ports, Protocols, and Services Management Component Local\nService Assessment (PPSM CLSA) and vulnerability assessments.\"\n desc \"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Inspect the firewall configuration and running services to verify that it\nis configured to prohibit or restrict the use of functions, ports, protocols,\nand/or services that are unnecessary or prohibited.\n\n Check which services are currently active with the following command:\n\n # firewall-cmd --list-all\n public (default, active)\n interfaces: enp0s3\n sources:\n services: dhcpv6-client dns http https ldaps rpc-bind ssh\n ports:\n masquerade: no\n forward-ports:\n icmp-blocks:\n rich rules:\n\n Ask the System Administrator for the site or program PPSM CLSA. Verify the\nservices allowed by the firewall match the PPSM CLSA.\n\n If there are additional ports, protocols, or services that are not in the\nPPSM CLSA, or there are ports, protocols, or services that are prohibited by\nthe PPSM Category Assurance List (CAL), this is a finding.\n \"\n desc \"fix\", \"Update the host's firewall settings and/or running services to\ncomply with the PPSM CLSA for the site or program and the PPSM CAL.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000096-GPOS-00050\"\n tag satisfies: [\"SRG-OS-000096-GPOS-00050\", \"SRG-OS-000297-GPOS-00115\"]\n tag gid: \"V-72219\"\n tag rid: \"SV-86843r2_rule\"\n tag stig_id: \"RHEL-07-040100\"\n tag fix_id: \"F-78573r1_fix\"\n tag cci: [\"CCI-000382\", \"CCI-002314\"]\n tag nist: [\"CM-7 b\", \"AC-17 (1)\"]\n\n firewalld_services_deny = input('firewalld_services_deny')\n firewalld_hosts_deny = input('firewalld_hosts_deny')\n firewalld_ports_deny = input('firewalld_ports_deny')\n firewalld_zones = input('firewalld_zones')\n iptables_rules = input('iptables_rules')\n\n if service('firewalld').running?\n\n # Check that the rules specified in 'firewalld_host_deny' are not enabled\n describe firewalld do\n firewalld_hosts_deny.each do |rule|\n it { should_not have_rule_enabled(rule) }\n end\n end\n\n # Check to make sure zones are specified\n if firewalld_zones.empty?\n describe \"Firewalld zones are not specified. Check 'firewalld_zones' input.\" do\n subject { firewalld_zones.empty? }\n it { should be false }\n end\n end\n\n # Check that the services specified in 'firewalld_services_deny' and\n # ports specified in 'firewalld_ports_deny' are not enabled\n firewalld_zones.each do |zone|\n if firewalld.has_zone?(zone)\n zone_services = firewalld_services_deny[zone.to_sym]\n zone_ports = firewalld_ports_deny[zone.to_sym]\n\n if !zone_services.nil?\n describe firewalld do\n zone_services.each do |serv|\n it { should_not have_service_enabled_in_zone(serv,zone) }\n end\n end\n else\n describe \"Services for zone '#{zone}' are not specified. Check 'firewalld_services_deny' input.\" do\n subject { zone_services.nil? }\n it { should be false }\n end\n end\n\n if !zone_ports.nil?\n describe firewalld do\n zone_ports.each do |port|\n it { should_not have_port_enabled_in_zone(port,zone) }\n end\n end\n else\n describe \"Ports for zone '#{zone}' are not specified. Check 'firewalld_ports_deny' input.\" do\n subject { zone_ports.nil? }\n it { should be false }\n end\n end\n else\n describe \"Firewalld zone '#{zone}' exists\" do\n subject { firewalld.has_zone?(zone) }\n it { should be true }\n end\n end\n end\n elsif service('iptables').running?\n describe iptables do\n iptables_rules.each do |rule|\n it { should have_rule(rule) }\n end\n end\n else\n describe \"No application firewall is installed\" do\n subject { service('firewalld').running? || service('iptables').running? }\n it { should eq true }\n end\n end\nend\n","desc":"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.","descriptions":[{"data":"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.","label":"default"},{"data":"","label":"rationale"},{"data":"Inspect the firewall configuration and running services to verify that it\nis configured to prohibit or restrict the use of functions, ports, protocols,\nand/or services that are unnecessary or prohibited.\n\n Check which services are currently active with the following command:\n\n # firewall-cmd --list-all\n public (default, active)\n interfaces: enp0s3\n sources:\n services: dhcpv6-client dns http https ldaps rpc-bind ssh\n ports:\n masquerade: no\n forward-ports:\n icmp-blocks:\n rich rules:\n\n Ask the System Administrator for the site or program PPSM CLSA. Verify the\nservices allowed by the firewall match the PPSM CLSA.\n\n If there are additional ports, protocols, or services that are not in the\nPPSM CLSA, or there are ports, protocols, or services that are prohibited by\nthe PPSM Category Assurance List (CAL), this is a finding.","label":"check"},{"data":"Update the host's firewall settings and/or running services to\ncomply with the PPSM CLSA for the site or program and the PPSM CAL.","label":"fix"}],"id":"V-72219","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72219.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000096-GPOS-00050","satisfies":["SRG-OS-000096-GPOS-00050","SRG-OS-000297-GPOS-00115"],"gid":"V-72219","rid":"SV-86843r2_rule","stig_id":"RHEL-07-040100","fix_id":"F-78573r1_fix","cci":["CCI-000382","CCI-002314"],"nist":["CM-7 b","AC-17 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nprohibit or restrict the use of functions, ports, protocols, and/or services,\nas defined in the Ports, Protocols, and Services Management Component Local\nService Assessment (PPSM CLSA) and vulnerability assessments.","waiver_data":{}},{"code":"control \"V-72221\" do\n title \"The Red Hat Enterprise Linux operating system must use a FIPS 140-2\napproved cryptographic algorithm for SSH communications.\"\n desc \"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system uses mechanisms meeting the requirements of\napplicable federal laws, Executive orders, directives, policies, regulations,\nstandards, and guidance for authentication to a cryptographic module.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n The location of the \\\"sshd_config\\\" file may vary if a different daemon is\nin use.\n\n Inspect the \\\"Ciphers\\\" configuration with the following command:\n\n # grep -i ciphers /etc/ssh/sshd_config\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n If any ciphers other than \\\"aes128-ctr\\\", \\\"aes192-ctr\\\", or \\\"aes256-ctr\\\"\nare listed, the \\\"Ciphers\\\" keyword is missing, or the returned line is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure SSH to use FIPS 140-2 approved cryptographic algorithms.\n\n Add the following line (or modify the line to have the required value) to\nthe \\\"/etc/ssh/sshd_config\\\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor).\n\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000033-GPOS-00014\"\n tag satisfies: [\"SRG-OS-000033-GPOS-00014\", \"SRG-OS-000120-GPOS-00061\",\n\"SRG-OS-000125-GPOS-00065\", \"SRG-OS-000250-GPOS-00093\",\n\"SRG-OS-000393-GPOS-00173\"]\n tag gid: \"V-72221\"\n tag rid: \"SV-86845r3_rule\"\n tag stig_id: \"RHEL-07-040110\"\n tag fix_id: \"F-78575r3_fix\"\n tag cci: [\"CCI-000068\", \"CCI-000366\", \"CCI-000803\"]\n tag nist: [\"AC-17 (2)\", \"CM-6 b\", \"IA-7\"]\n\n @ciphers_array = inspec.sshd_config.params['ciphers']\n\n unless @ciphers_array.nil?\n @ciphers_array = @ciphers_array.first.split(\",\")\n end\n\n describe @ciphers_array do\n it { should be_in ['aes128-ctr', 'aes192-ctr', 'aes256-ctr'] }\n end\nend\n","desc":"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.","descriptions":[{"data":"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uses mechanisms meeting the requirements of\napplicable federal laws, Executive orders, directives, policies, regulations,\nstandards, and guidance for authentication to a cryptographic module.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n The location of the \"sshd_config\" file may vary if a different daemon is\nin use.\n\n Inspect the \"Ciphers\" configuration with the following command:\n\n # grep -i ciphers /etc/ssh/sshd_config\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n If any ciphers other than \"aes128-ctr\", \"aes192-ctr\", or \"aes256-ctr\"\nare listed, the \"Ciphers\" keyword is missing, or the returned line is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to use FIPS 140-2 approved cryptographic algorithms.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor).\n\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72221","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72221.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000033-GPOS-00014","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"],"gid":"V-72221","rid":"SV-86845r3_rule","stig_id":"RHEL-07-040110","fix_id":"F-78575r3_fix","cci":["CCI-000068","CCI-000366","CCI-000803"],"nist":["AC-17 (2)","CM-6 b","IA-7"]},"title":"The Red Hat Enterprise Linux operating system must use a FIPS 140-2\napproved cryptographic algorithm for SSH communications.","waiver_data":{}},{"code":"control \"V-72223\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with a communication session are\nterminated at the end of the session or after 10 minutes of inactivity from the\nuser at a command prompt, except to fulfill documented and validated mission\nrequirements.\"\n desc \"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system terminates all network connections associated\nwith a communications session at the end of the session or based on inactivity.\n\n Check the value of the system inactivity timeout with the following command:\n\n # grep -i tmout /etc/profile.d/*\n\n etc/profile.d/tmout.sh:TMOUT=600\n\n /etc/profile.d/tmout.sh:readonly TMOUT\n\n /etc/profile.d/tmout.sh:export TMOUT\n\n If \\\"TMOUT\\\" is not set to \\\"600\\\" or less in a script located in the\n/etc/profile.d/ directory to enforce session termination after inactivity, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to terminate all network connections\nassociated with a communications session at the end of the session or after a\nperiod of inactivity.\n\n Create a script to enforce the inactivity timeout (for example\n/etc/profile.d/tmout.sh) such as:\n\n #!/bin/bash\n\n TMOUT=600\n readonly TMOUT\n export TMOUT\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000163-GPOS-00072\"\n tag gid: \"V-72223\"\n tag rid: \"SV-86847r4_rule\"\n tag stig_id: \"RHEL-07-040160\"\n tag fix_id: \"F-78577r5_fix\"\n tag cci: [\"CCI-001133\", \"CCI-002361\"]\n tag nist: [\"SC-10\", \"AC-12\"]\n\n system_activity_timeout = input('system_activity_timeout')\n\n # Get current TMOUT environment variable (active test)\n describe 'Environment variable TMOUT' do\n subject { os_env('TMOUT').content.to_i }\n it { should be <= system_activity_timeout }\n end\n\n # Check if TMOUT is set in files (passive test)\n files = ['/etc/bashrc'] + ['/etc/profile'] + command(\"find /etc/profile.d/*\").stdout.split(\"\\n\")\n latest_val = nil\n\n files.each do |file|\n readonly = false\n\n # Skip to next file if TMOUT isn't present. Otherwise, get the last occurrence of TMOUT\n next if (values = command(\"grep -Po '.*TMOUT.*' #{file}\").stdout.split(\"\\n\")).empty?\n\n # Loop through each TMOUT match and see if set TMOUT's value or makes it readonly\n values.each_with_index { |value, index|\n\n # Skip if starts with '#' - it represents a comment\n next if !value.match(/^#/).nil?\n # If readonly and value is inline - use that value\n if !value.match(/^readonly[\\s]+TMOUT[\\s]*=[\\s]*[\\d]+$/).nil?\n latest_val = value.match(/[\\d]+/)[0].to_i\n readonly = true\n break\n # If readonly, but, value is not inline - use the most recent value\n elsif !value.match(/^readonly[\\s]+([\\w]+[\\s]+)?TMOUT[\\s]*([\\s]+[\\w]+[\\s]*)*$/).nil?\n # If the index is greater than 0, the configuraiton setting value.\n # Otherwise, the configuration setting value is in the previous file\n # and is already set in latest_val.\n if index >= 1\n latest_val = values[index - 1].match(/[\\d]+/)[0].to_i\n end\n readonly = true\n break\n # Readonly is not set use the lastest value\n else\n latest_val = value.match(/[\\d]+/)[0].to_i\n end\n }\n # Readonly is set - stop processing files\n break if readonly === true\n end\n\n if latest_val.nil?\n describe \"The TMOUT setting is configured\" do\n subject { !latest_val.nil? }\n it { should be true }\n end\n else\n describe\"The TMOUT setting is configured properly\" do\n subject { latest_val }\n it { should be <= system_activity_timeout }\n end\n end\nend\n","desc":"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system terminates all network connections associated\nwith a communications session at the end of the session or based on inactivity.\n\n Check the value of the system inactivity timeout with the following command:\n\n # grep -i tmout /etc/profile.d/*\n\n etc/profile.d/tmout.sh:TMOUT=600\n\n /etc/profile.d/tmout.sh:readonly TMOUT\n\n /etc/profile.d/tmout.sh:export TMOUT\n\n If \"TMOUT\" is not set to \"600\" or less in a script located in the\n/etc/profile.d/ directory to enforce session termination after inactivity, this\nis a finding.","label":"check"},{"data":"Configure the operating system to terminate all network connections\nassociated with a communications session at the end of the session or after a\nperiod of inactivity.\n\n Create a script to enforce the inactivity timeout (for example\n/etc/profile.d/tmout.sh) such as:\n\n #!/bin/bash\n\n TMOUT=600\n readonly TMOUT\n export TMOUT","label":"fix"}],"id":"V-72223","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72223.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","gid":"V-72223","rid":"SV-86847r4_rule","stig_id":"RHEL-07-040160","fix_id":"F-78577r5_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with a communication session are\nterminated at the end of the session or after 10 minutes of inactivity from the\nuser at a command prompt, except to fulfill documented and validated mission\nrequirements.","waiver_data":{}},{"code":"control \"V-72225\" do\n title \"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner immediately prior to, or as\npart of, remote access logon prompts.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify any publicly accessible connection to the operating system displays\nthe Standard Mandatory DoD Notice and Consent Banner before granting access to\nthe system.\n\n Check for the location of the banner file being used with the following\ncommand:\n\n # grep -i banner /etc/ssh/sshd_config\n\n banner /etc/issue\n\n This command will return the banner keyword and the name of the file that\ncontains the ssh banner (in this case \\\"/etc/issue\\\").\n\n If the line is commented out, this is a finding.\n\n View the file specified by the banner keyword to check that it matches the\ntext of the Standard Mandatory DoD Notice and Consent Banner:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n If the system does not display a graphical logon banner or the banner does\nnot match the Standard Mandatory DoD Notice and Consent Banner, this is a\nfinding.\n\n If the text in the file does not match the Standard Mandatory DoD Notice\nand Consent Banner, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the ssh.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment the banner keyword and\nconfigure it to point to a file that will contain the logon banner (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor). An example configuration line is:\n\n banner /etc/issue\n\n Either create the file containing the banner or replace the text in the\nfile with the Standard Mandatory DoD Notice and Consent Banner. The DoD\nrequired text is:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\",\n\"SRG-OS-000228-GPOS-00088\"]\n tag gid: \"V-72225\"\n tag rid: \"SV-86849r4_rule\"\n tag stig_id: \"RHEL-07-040170\"\n tag fix_id: \"F-78579r4_fix\"\n tag cci: [\"CCI-000048\", \"CCI-000050\", \"CCI-001384\", \"CCI-001385\",\n\"CCI-001386\", \"CCI-001387\", \"CCI-001388\"]\n tag nist: [\"AC-8 a\", \"AC-8 b\", \"AC-8 c 1\", \"AC-8 c 2\", \"AC-8 c 2\", \"AC-8 c\n2\", \"AC-8 c 3\"]\n\n banner_message_text_ral = input('banner_message_text_ral')\n banner_message_text_ral_limited = input('banner_message_text_ral_limited')\n\n #When Banner is commented, not found, disabled, or the specified file does not exist, this is a finding.\n banner_files = [sshd_config.banner].flatten\n\n banner_files.each do |banner_file|\n\n #Banner property is commented out.\n describe \"The SSHD Banner is not set\" do\n subject { banner_file.nil? }\n it { should be false }\n end if banner_file.nil?\n\n #Banner property is set to \"none\"\n describe \"The SSHD Banner is disabled\" do\n subject { banner_file.match(/none/i).nil? }\n it { should be true }\n end if !banner_file.nil? && !banner_file.match(/none/i).nil?\n\n #Banner property provides a path to a file, however, it does not exist.\n describe \"The SSHD Banner is set, but, the file does not exist\" do\n subject { file(banner_file).exist? }\n it { should be true }\n end if !banner_file.nil? && banner_file.match(/none/i).nil? && !file(banner_file).exist?\n\n #Banner property provides a path to a file and it exists.\n describe.one do\n banner = file(banner_file).content.gsub(%r{[\\r\\n\\s]}, '')\n clean_banner = banner_message_text_ral.gsub(%r{[\\r\\n\\s]}, '')\n clean_banner_limited = banner_message_text_ral_limited.gsub(%r{[\\r\\n\\s]}, '')\n\n describe \"The SSHD Banner is set to the standard banner and has the correct text\" do\n subject { banner }\n it { should cmp clean_banner }\n end\n\n describe \"The SSHD Banner is set to the standard limited banner and has the correct text\" do\n subject { banner }\n it { should cmp clean_banner_limited }\n end\n end if !banner_file.nil? && banner_file.match(/none/i).nil? && file(banner_file).exist?\n end\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify any publicly accessible connection to the operating system displays\nthe Standard Mandatory DoD Notice and Consent Banner before granting access to\nthe system.\n\n Check for the location of the banner file being used with the following\ncommand:\n\n # grep -i banner /etc/ssh/sshd_config\n\n banner /etc/issue\n\n This command will return the banner keyword and the name of the file that\ncontains the ssh banner (in this case \"/etc/issue\").\n\n If the line is commented out, this is a finding.\n\n View the file specified by the banner keyword to check that it matches the\ntext of the Standard Mandatory DoD Notice and Consent Banner:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n If the system does not display a graphical logon banner or the banner does\nnot match the Standard Mandatory DoD Notice and Consent Banner, this is a\nfinding.\n\n If the text in the file does not match the Standard Mandatory DoD Notice\nand Consent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the ssh.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment the banner keyword and\nconfigure it to point to a file that will contain the logon banner (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor). An example configuration line is:\n\n banner /etc/issue\n\n Either create the file containing the banner or replace the text in the\nfile with the Standard Mandatory DoD Notice and Consent Banner. The DoD\nrequired text is:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72225","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72225.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-72225","rid":"SV-86849r4_rule","stig_id":"RHEL-07-040170","fix_id":"F-78579r4_fix","cci":["CCI-000048","CCI-000050","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"],"nist":["AC-8 a","AC-8 b","AC-8 c 1","AC-8 c 2","AC-8 c 2","AC-8 c\n2","AC-8 c 3"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner immediately prior to, or as\npart of, remote access logon prompts.","waiver_data":{}},{"code":"control \"V-72227\" do\n title \"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) authentication communications.\"\n desc \"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP authentication sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \\\"sssd.service\\\" is \\\"active\\\", then LDAP is being used.\n\n Determine the \\\"id_provider\\\" the LDAP is currently using:\n\n # grep -i \\\"id_provider\\\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \\\"id_provider\\\" is set to \\\"ad\\\", this is Not Applicable.\n\n Ensure that LDAP is configured to use TLS by using the following command:\n\n # grep -i \\\"start_tls\\\" /etc/sssd/sssd.conf\n ldap_id_use_start_tls = true\n\n If the \\\"ldap_id_use_start_tls\\\" option is not \\\"true\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement cryptography to protect the\nintegrity of LDAP authentication sessions.\n\n Add or modify the following line in \\\"/etc/sssd/sssd.conf\\\":\n\n ldap_id_use_start_tls = true\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72227\"\n tag rid: \"SV-86851r4_rule\"\n tag stig_id: \"RHEL-07-040180\"\n tag fix_id: \"F-78581r2_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n sssd_id_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*id_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n pam_ldap_enabled = (!command('grep \"^[^#]*pam_ldap\\.so\" /etc/pam.d/*').stdout.strip.empty?)\n\n if !(sssd_id_ldap_enabled or pam_ldap_enabled)\n impact 0.0\n describe \"LDAP not enabled\" do\n skip \"LDAP not enabled using any known mechanisms, this control is Not Applicable.\"\n end\n end\n\n if sssd_id_ldap_enabled\n ldap_id_use_start_tls = command('grep ldap_id_use_start_tls /etc/sssd/sssd.conf')\n describe ldap_id_use_start_tls do\n its('stdout.strip') { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n\n ldap_id_use_start_tls.stdout.strip.each_line do |line|\n describe line do\n it { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n end\n end\n\n if pam_ldap_enabled\n describe command('grep -i ssl /etc/pam_ldap.conf') do\n its('stdout.strip') { should match %r{^ssl start_tls$}}\n end\n end\nend\n","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP authentication sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Ensure that LDAP is configured to use TLS by using the following command:\n\n # grep -i \"start_tls\" /etc/sssd/sssd.conf\n ldap_id_use_start_tls = true\n\n If the \"ldap_id_use_start_tls\" option is not \"true\", this is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP authentication sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_id_use_start_tls = true","label":"fix"}],"id":"V-72227","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72227.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72227","rid":"SV-86851r4_rule","stig_id":"RHEL-07-040180","fix_id":"F-78581r2_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) authentication communications.","waiver_data":{}},{"code":"control \"V-72229\" do\n title \"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.\"\n desc \"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \\\"sssd.service\\\" is \\\"active\\\", then LDAP is being used.\n\n Determine the \\\"id_provider\\\" the LDAP is currently using:\n\n # grep -i \\\"id_provider\\\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \\\"id_provider\\\" is set to \\\"ad\\\", this is Not Applicable.\n\n Verify the sssd service is configured to require the use of certificates:\n\n # grep -i tls_reqcert /etc/sssd/sssd.conf\n ldap_tls_reqcert = demand\n\n If the \\\"ldap_tls_reqcert\\\" setting is missing, commented out, or does not\nexist, this is a finding.\n\n If the \\\"ldap_tls_reqcert\\\" setting is not set to \\\"demand\\\" or \\\"hard\\\",\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \\\"/etc/sssd/sssd.conf\\\":\n\n ldap_tls_reqcert = demand\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72229\"\n tag rid: \"SV-86853r4_rule\"\n tag stig_id: \"RHEL-07-040190\"\n tag fix_id: \"F-78583r4_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n sssd_id_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*id_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n sssd_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*[a-z]*_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n pam_ldap_enabled = (!command('grep \"^[^#]*pam_ldap\\.so\" /etc/pam.d/*').stdout.strip.empty?)\n\n if !(sssd_id_ldap_enabled or sssd_ldap_enabled or pam_ldap_enabled)\n impact 0.0\n describe \"LDAP not enabled\" do\n skip \"LDAP not enabled using any known mechanisms, this control is Not Applicable.\"\n end\n end\n\n if sssd_id_ldap_enabled\n ldap_id_use_start_tls = command('grep ldap_id_use_start_tls /etc/sssd/sssd.conf')\n describe ldap_id_use_start_tls do\n its('stdout.strip') { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n\n ldap_id_use_start_tls.stdout.strip.each_line do |line|\n describe line do\n it { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n end\n end\n\n if sssd_ldap_enabled\n ldap_tls_cacertdir = command('grep -i ldap_tls_cacertdir /etc/sssd/sssd.conf').\n stdout.strip.scan(%r{^ldap_tls_cacertdir\\s*=\\s*(.*)}).last\n\n describe \"ldap_tls_cacertdir\" do\n subject { ldap_tls_cacertdir }\n it { should_not eq nil }\n end\n\n describe file(ldap_tls_cacertdir.last) do\n it { should exist }\n it { should be_directory }\n end if !ldap_tls_cacertdir.nil?\n end\n\n if pam_ldap_enabled\n tls_cacertdir = command('grep -i tls_cacertdir /etc/pam_ldap.conf').\n stdout.strip.scan(%r{^tls_cacertdir\\s+(.*)}).last\n\n describe \"tls_cacertdir\" do\n subject { tls_cacertdir }\n it { should_not eq nil }\n end\n\n describe file(tls_cacertdir.last) do\n it { should exist }\n it { should be_directory }\n end if !tls_cacertdir.nil?\n end\nend\n","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Verify the sssd service is configured to require the use of certificates:\n\n # grep -i tls_reqcert /etc/sssd/sssd.conf\n ldap_tls_reqcert = demand\n\n If the \"ldap_tls_reqcert\" setting is missing, commented out, or does not\nexist, this is a finding.\n\n If the \"ldap_tls_reqcert\" setting is not set to \"demand\" or \"hard\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_tls_reqcert = demand","label":"fix"}],"id":"V-72229","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72229.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72229","rid":"SV-86853r4_rule","stig_id":"RHEL-07-040190","fix_id":"F-78583r4_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.","waiver_data":{}},{"code":"control \"V-72231\" do\n title \"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.\"\n desc \"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \\\"sssd.service\\\" is \\\"active\\\", then LDAP is being used.\n\n Determine the \\\"id_provider\\\" that the LDAP is currently using:\n\n # grep -i \\\"id_provider\\\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \\\"id_provider\\\" is set to \\\"ad\\\", this is Not Applicable.\n\n Check the path to the X.509 certificate for peer authentication with the\nfollowing command:\n\n # grep -i tls_cacert /etc/sssd/sssd.conf\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt\n\n Verify the \\\"ldap_tls_cacert\\\" option points to a file that contains the\ntrusted CA certificate.\n\n If this file does not exist, or the option is commented out or missing,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \\\"/etc/sssd/sssd.conf\\\":\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72231\"\n tag rid: \"SV-86855r4_rule\"\n tag stig_id: \"RHEL-07-040200\"\n tag fix_id: \"F-78585r3_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n sssd_id_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*id_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n sssd_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*[a-z]*_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n pam_ldap_enabled = (!command('grep \"^[^#]*pam_ldap\\.so\" /etc/pam.d/*').stdout.strip.empty?)\n\n if !(sssd_id_ldap_enabled or sssd_ldap_enabled or pam_ldap_enabled)\n impact 0.0\n describe \"LDAP not enabled\" do\n skip \"LDAP not enabled using any known mechanisms, this control is Not Applicable.\"\n end\n end\n\n if sssd_id_ldap_enabled\n ldap_id_use_start_tls = command('grep ldap_id_use_start_tls /etc/sssd/sssd.conf')\n describe ldap_id_use_start_tls do\n its('stdout.strip') { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n\n ldap_id_use_start_tls.stdout.strip.each_line do |line|\n describe line do\n it { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n end\n end\n\n if sssd_ldap_enabled\n ldap_tls_cacert = command('grep -i ldap_tls_cacert /etc/sssd/sssd.conf').\n stdout.strip.scan(%r{^ldap_tls_cacert\\s*=\\s*(.*)}).last\n\n describe \"ldap_tls_cacert\" do\n subject { ldap_tls_cacert }\n it { should_not eq nil }\n end\n\n describe file(ldap_tls_cacert.last) do\n it { should exist }\n it { should be_file }\n end if !ldap_tls_cacert.nil?\n end\n\n if pam_ldap_enabled\n tls_cacertfile = command('grep -i tls_cacertfile /etc/pam_ldap.conf').\n stdout.strip.scan(%r{^tls_cacertfile\\s+(.*)}).last\n\n describe \"tls_cacertfile\" do\n subject { tls_cacertfile }\n it { should_not eq nil }\n end\n\n describe file(tls_cacertfile.last) do\n it { should exist }\n it { should be_file }\n end if !tls_cacertfile.nil?\n end\nend\n","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" that the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Check the path to the X.509 certificate for peer authentication with the\nfollowing command:\n\n # grep -i tls_cacert /etc/sssd/sssd.conf\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt\n\n Verify the \"ldap_tls_cacert\" option points to a file that contains the\ntrusted CA certificate.\n\n If this file does not exist, or the option is commented out or missing,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt","label":"fix"}],"id":"V-72231","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72231.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72231","rid":"SV-86855r4_rule","stig_id":"RHEL-07-040200","fix_id":"F-78585r3_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.","waiver_data":{}},{"code":"control \"V-72233\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems have SSH installed.\"\n desc \"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check to see if sshd is installed with the following command:\n\n # yum list installed \\\\*ssh\\\\*\n libssh2.x86_64 1.4.3-8.el7 @anaconda/7.1\n openssh.x86_64 6.6.1p1-11.el7 @anaconda/7.1\n openssh-server.x86_64 6.6.1p1-11.el7 @anaconda/7.1\n\n If the \\\"SSH server\\\" package is not installed, this is a finding.\n \"\n desc \"fix\", \"\n Install SSH packages onto the host with the following commands:\n\n # yum install openssh-server.x86_64\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000423-GPOS-00187\"\n tag satisfies: [\"SRG-OS-000423-GPOS-00187\", \"SRG-OS-000424-GPOS-00188\",\n\"SRG-OS-000425-GPOS-00189\", \"SRG-OS-000426-GPOS-00190\"]\n tag gid: \"V-72233\"\n tag rid: \"SV-86857r3_rule\"\n tag stig_id: \"RHEL-07-040300\"\n tag fix_id: \"F-78587r3_fix\"\n tag cci: [\"CCI-002418\", \"CCI-002420\", \"CCI-002421\", \"CCI-002422\"]\n tag nist: [\"SC-8\", \"SC-8 (2)\", \"SC-8 (1)\", \"SC-8 (2)\"]\n\n describe package('openssh-server') do\n it { should be_installed }\n end\n describe package('openssh-clients') do\n it { should be_installed }\n end\nend\n","desc":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.","descriptions":[{"data":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if sshd is installed with the following command:\n\n# yum list installed \\*ssh\\*\nlibssh2.x86_64 1.4.3-8.el7 @anaconda/7.1\nopenssh.x86_64 6.6.1p1-11.el7 @anaconda/7.1\nopenssh-server.x86_64 6.6.1p1-11.el7 @anaconda/7.1\n\nIf the \"SSH server\" package is not installed, this is a finding.","label":"check"},{"data":"Install SSH packages onto the host with the following commands:\n\n# yum install openssh-server.x86_64","label":"fix"}],"id":"V-72233","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72233.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000423-GPOS-00187","satisfies":["SRG-OS-000423-GPOS-00187","SRG-OS-000424-GPOS-00188","SRG-OS-000425-GPOS-00189","SRG-OS-000426-GPOS-00190"],"gid":"V-72233","rid":"SV-86857r3_rule","stig_id":"RHEL-07-040300","fix_id":"F-78587r3_fix","cci":["CCI-002418","CCI-002420","CCI-002421","CCI-002422"],"nist":["SC-8","SC-8 (2)","SC-8 (1)","SC-8 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems have SSH installed.","waiver_data":{}},{"code":"control \"V-72235\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems use SSH for confidentiality and integrity of\ntransmitted and received information as well as information during preparation\nfor transmission.\"\n desc \"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify SSH is loaded and active with the following command:\n\n # systemctl status sshd\n sshd.service - OpenSSH server daemon\n Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)\n Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days\nago\n Main PID: 1348 (sshd)\n CGroup: /system.slice/sshd.service\n 1053 /usr/sbin/sshd -D\n\n If \\\"sshd\\\" does not show a status of \\\"active\\\" and \\\"running\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the SSH service to automatically start after reboot with the\nfollowing command:\n\n # systemctl enable sshd.service\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000423-GPOS-00187\"\n tag satisfies: [\"SRG-OS-000423-GPOS-00187\", \"SRG-OS-000423-GPOS-00188\",\n\"SRG-OS-000423-GPOS-00189\", \"SRG-OS-000423-GPOS-00190\"]\n tag gid: \"V-72235\"\n tag rid: \"SV-86859r3_rule\"\n tag stig_id: \"RHEL-07-040310\"\n tag fix_id: \"F-78589r2_fix\"\n tag cci: [\"CCI-002418\", \"CCI-002420\", \"CCI-002421\", \"CCI-002422\"]\n tag nist: [\"SC-8\", \"SC-8 (2)\", \"SC-8 (1)\", \"SC-8 (2)\"]\n\n describe systemd_service('sshd.service') do\n it { should be_running }\n end\nend\n","desc":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.","descriptions":[{"data":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify SSH is loaded and active with the following command:\n\n # systemctl status sshd\n sshd.service - OpenSSH server daemon\n Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)\n Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days\nago\n Main PID: 1348 (sshd)\n CGroup: /system.slice/sshd.service\n 1053 /usr/sbin/sshd -D\n\n If \"sshd\" does not show a status of \"active\" and \"running\", this is a\nfinding.","label":"check"},{"data":"Configure the SSH service to automatically start after reboot with the\nfollowing command:\n\n # systemctl enable sshd.service","label":"fix"}],"id":"V-72235","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72235.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000423-GPOS-00187","satisfies":["SRG-OS-000423-GPOS-00187","SRG-OS-000423-GPOS-00188","SRG-OS-000423-GPOS-00189","SRG-OS-000423-GPOS-00190"],"gid":"V-72235","rid":"SV-86859r3_rule","stig_id":"RHEL-07-040310","fix_id":"F-78589r2_fix","cci":["CCI-002418","CCI-002420","CCI-002421","CCI-002422"],"nist":["SC-8","SC-8 (2)","SC-8 (1)","SC-8 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems use SSH for confidentiality and integrity of\ntransmitted and received information as well as information during preparation\nfor transmission.","waiver_data":{}},{"code":"control \"V-72237\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic are terminated at the\nend of the session or after 10 minutes of inactivity, except to fulfill\ndocumented and validated mission requirements.\"\n desc \"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \\\"ClientAliveInterval\\\" keyword with the\nfollowing command:\n\n # grep -iw clientaliveinterval /etc/ssh/sshd_config\n\n ClientAliveInterval 600\n\n If \\\"ClientAliveInterval\\\" is not configured, commented out, or has a value\nof \\\"0\\\", this is a finding.\n\n If \\\"ClientAliveInterval\\\" has a value that is greater than \\\"600\\\" and is\nnot documented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to automatically terminate a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \\\"/etc/ssh/sshd_config\\\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveInterval 600\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000163-GPOS-00072\"\n tag satisfies: [\"SRG-OS-000163-GPOS-00072\", \"SRG-OS-000279-GPOS-00109\"]\n tag gid: \"V-72237\"\n tag rid: \"SV-86861r4_rule\"\n tag stig_id: \"RHEL-07-040320\"\n tag fix_id: \"F-78591r2_fix\"\n tag cci: [\"CCI-001133\", \"CCI-002361\"]\n tag nist: [\"SC-10\", \"AC-12\"]\n\n client_alive_interval = input('client_alive_interval')\n\n #This may show slightly confusing results when a ClientAliveInterValue is not\n #specified. Specifically, because the value will be nil and when you try to\n #convert it to an integer using to_i it will convert it to 0 and pass the\n #<= client_alive_interval check. However, the control as a whole will still fail.\n describe sshd_config do\n its(\"ClientAliveInterval.to_i\"){should cmp >= 1}\n its(\"ClientAliveInterval.to_i\"){should cmp <= client_alive_interval}\n its(\"ClientAliveInterval\"){should_not eq nil}\n end\nend\n","desc":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \"ClientAliveInterval\" keyword with the\nfollowing command:\n\n # grep -iw clientaliveinterval /etc/ssh/sshd_config\n\n ClientAliveInterval 600\n\n If \"ClientAliveInterval\" is not configured, commented out, or has a value\nof \"0\", this is a finding.\n\n If \"ClientAliveInterval\" has a value that is greater than \"600\" and is\nnot documented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.","label":"check"},{"data":"Configure the operating system to automatically terminate a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveInterval 600\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72237","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72237.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","satisfies":["SRG-OS-000163-GPOS-00072","SRG-OS-000279-GPOS-00109"],"gid":"V-72237","rid":"SV-86861r4_rule","stig_id":"RHEL-07-040320","fix_id":"F-78591r2_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic are terminated at the\nend of the session or after 10 minutes of inactivity, except to fulfill\ndocumented and validated mission requirements.","waiver_data":{}},{"code":"control \"V-72239\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using RSA rhosts\nauthentication.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon does not allow authentication using RSA rhosts\nauthentication.\n\n To determine how the SSH daemon's \\\"RhostsRSAAuthentication\\\" option is\nset, run the following command:\n\n # grep RhostsRSAAuthentication /etc/ssh/sshd_config\n RhostsRSAAuthentication no\n\n If the value is returned as \\\"yes\\\", the returned line is commented out, or\nno output is returned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the SSH daemon to not allow authentication using RSA rhosts\nauthentication.\n\n Add the following line in \\\"/etc/ssh/sshd_config\\\", or uncomment the line\nand set the value to \\\"no\\\":\n\n RhostsRSAAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72239\"\n tag rid: \"SV-86863r4_rule\"\n tag stig_id: \"RHEL-07-040330\"\n tag fix_id: \"F-78593r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('RhostsRSAAuthentication') { should cmp 'no' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon does not allow authentication using RSA rhosts\nauthentication.\n\n To determine how the SSH daemon's \"RhostsRSAAuthentication\" option is\nset, run the following command:\n\n # grep RhostsRSAAuthentication /etc/ssh/sshd_config\n RhostsRSAAuthentication no\n\n If the value is returned as \"yes\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using RSA rhosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"no\":\n\n RhostsRSAAuthentication no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72239","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72239.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72239","rid":"SV-86863r4_rule","stig_id":"RHEL-07-040330","fix_id":"F-78593r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using RSA rhosts\nauthentication.","waiver_data":{}},{"code":"control \"V-72241\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic terminate after a\nperiod of inactivity.\"\n desc \"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \\\"ClientAliveCountMax\\\" keyword with the\nfollowing command:\n\n # grep -i clientalivecount /etc/ssh/sshd_config\n ClientAliveCountMax 0\n\n If \\\"ClientAliveCountMax\\\" is not set to \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to terminate automatically a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \\\"/etc/ssh/sshd_config\\\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveCountMax 0\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000163-GPOS-00072\"\n tag satisfies: [\"SRG-OS-000163-GPOS-00072\", \"SRG-OS-000279-GPOS-00109\"]\n tag gid: \"V-72241\"\n tag rid: \"SV-86865r4_rule\"\n tag stig_id: \"RHEL-07-040340\"\n tag fix_id: \"F-78595r4_fix\"\n tag cci: [\"CCI-001133\", \"CCI-002361\"]\n tag nist: [\"SC-10\", \"AC-12\"]\n\n if os.release.to_f >= 7.4\n impact 0.0\n describe \"The release is #{os.release}\" do\n skip \"The release is newer than 7.4; this control is Not Applicable.\"\n end\n else\n describe sshd_config do\n its('ClientAliveCountMax') { should cmp '0' }\n end\n end\nend\n","desc":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \"ClientAliveCountMax\" keyword with the\nfollowing command:\n\n # grep -i clientalivecount /etc/ssh/sshd_config\n ClientAliveCountMax 0\n\n If \"ClientAliveCountMax\" is not set to \"0\", this is a finding.","label":"check"},{"data":"Configure the operating system to terminate automatically a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveCountMax 0\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72241","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72241.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","satisfies":["SRG-OS-000163-GPOS-00072","SRG-OS-000279-GPOS-00109"],"gid":"V-72241","rid":"SV-86865r4_rule","stig_id":"RHEL-07-040340","fix_id":"F-78595r4_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic terminate after a\nperiod of inactivity.","waiver_data":{}},{"code":"control \"V-72243\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using rhosts authentication.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \\\"IgnoreRhosts\\\" option is set, run the\nfollowing command:\n\n # grep -i IgnoreRhosts /etc/ssh/sshd_config\n\n IgnoreRhosts yes\n\n If the value is returned as \\\"no\\\", the returned line is commented out, or\nno output is returned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \\\"/etc/ssh/sshd_config\\\", or uncomment the line\nand set the value to \\\"yes\\\":\n\n IgnoreRhosts yes\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72243\"\n tag rid: \"SV-86867r3_rule\"\n tag stig_id: \"RHEL-07-040350\"\n tag fix_id: \"F-78597r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('IgnoreRhosts') { should cmp 'yes' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \"IgnoreRhosts\" option is set, run the\nfollowing command:\n\n # grep -i IgnoreRhosts /etc/ssh/sshd_config\n\n IgnoreRhosts yes\n\n If the value is returned as \"no\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"yes\":\n\n IgnoreRhosts yes","label":"fix"}],"id":"V-72243","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72243.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72243","rid":"SV-86867r3_rule","stig_id":"RHEL-07-040350","fix_id":"F-78597r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using rhosts authentication.","waiver_data":{}},{"code":"control \"V-72245\" do\n title \"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon an SSH logon.\"\n desc \"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify SSH provides users with feedback on when account accesses last\noccurred.\n\n Check that \\\"PrintLastLog\\\" keyword in the sshd daemon configuration file\nis used and set to \\\"yes\\\" with the following command:\n\n # grep -i printlastlog /etc/ssh/sshd_config\n PrintLastLog yes\n\n If the \\\"PrintLastLog\\\" keyword is set to \\\"no\\\", is missing, or is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure SSH to provide users with feedback on when account accesses last\noccurred by setting the required configuration options in \\\"/etc/pam.d/sshd\\\"\nor in the \\\"sshd_config\\\" file used by the system (\\\"/etc/ssh/sshd_config\\\"\nwill be used in the example) (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor).\n\n Modify the \\\"PrintLastLog\\\" line in \\\"/etc/ssh/sshd_config\\\" to match the\nfollowing:\n\n PrintLastLog yes\n\n The SSH service must be restarted for changes to \\\"sshd_config\\\" to take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72245\"\n tag rid: \"SV-86869r3_rule\"\n tag stig_id: \"RHEL-07-040360\"\n tag fix_id: \"F-78599r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if sshd_config.params['printlastlog'] == ['yes']\n describe sshd_config do\n its('PrintLastLog') { should cmp 'yes' }\n end\n else\n describe pam('/etc/pam.d/sshd') do\n its('lines') { should match_pam_rule('session required pam_lastlog.so showfailed') }\n its('lines') { should match_pam_rule('session required pam_lastlog.so showfailed').all_without_args('silent') }\n end\n end\nend\n","desc":"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.","descriptions":[{"data":"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify SSH provides users with feedback on when account accesses last\noccurred.\n\n Check that \"PrintLastLog\" keyword in the sshd daemon configuration file\nis used and set to \"yes\" with the following command:\n\n # grep -i printlastlog /etc/ssh/sshd_config\n PrintLastLog yes\n\n If the \"PrintLastLog\" keyword is set to \"no\", is missing, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to provide users with feedback on when account accesses last\noccurred by setting the required configuration options in \"/etc/pam.d/sshd\"\nor in the \"sshd_config\" file used by the system (\"/etc/ssh/sshd_config\"\nwill be used in the example) (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor).\n\n Modify the \"PrintLastLog\" line in \"/etc/ssh/sshd_config\" to match the\nfollowing:\n\n PrintLastLog yes\n\n The SSH service must be restarted for changes to \"sshd_config\" to take\neffect.","label":"fix"}],"id":"V-72245","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72245.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72245","rid":"SV-86869r3_rule","stig_id":"RHEL-07-040360","fix_id":"F-78599r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon an SSH logon.","waiver_data":{}},{"code":"control \"V-72247\" do\n title \"The Red Hat Enterprise Linux operating system must not permit direct\nlogons to the root account using remote access via SSH.\"\n desc \"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify remote access using SSH prevents users from logging on directly as\nroot.\n\n Check that SSH prevents users from logging on directly as root with the\nfollowing command:\n\n # grep -i permitrootlogin /etc/ssh/sshd_config\n PermitRootLogin no\n\n If the \\\"PermitRootLogin\\\" keyword is set to \\\"yes\\\", is missing, or is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure SSH to stop users from logging on remotely as the root user.\n\n Edit the appropriate \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the\nline for the \\\"PermitRootLogin\\\" keyword and set its value to \\\"no\\\" (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor):\n\n PermitRootLogin no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72247\"\n tag rid: \"SV-86871r3_rule\"\n tag stig_id: \"RHEL-07-040370\"\n tag fix_id: \"F-78601r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('PermitRootLogin') { should cmp 'no' }\n end\nend\n","desc":"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.","descriptions":[{"data":"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify remote access using SSH prevents users from logging on directly as\nroot.\n\n Check that SSH prevents users from logging on directly as root with the\nfollowing command:\n\n # grep -i permitrootlogin /etc/ssh/sshd_config\n PermitRootLogin no\n\n If the \"PermitRootLogin\" keyword is set to \"yes\", is missing, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to stop users from logging on remotely as the root user.\n\n Edit the appropriate \"/etc/ssh/sshd_config\" file to uncomment or add the\nline for the \"PermitRootLogin\" keyword and set its value to \"no\" (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor):\n\n PermitRootLogin no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72247","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72247.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72247","rid":"SV-86871r3_rule","stig_id":"RHEL-07-040370","fix_id":"F-78601r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not permit direct\nlogons to the root account using remote access via SSH.","waiver_data":{}},{"code":"control \"V-72249\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using known hosts\nauthentication.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \\\"IgnoreUserKnownHosts\\\" option is set,\nrun the following command:\n\n # grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config\n\n IgnoreUserKnownHosts yes\n\n If the value is returned as \\\"no\\\", the returned line is commented out, or\nno output is returned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \\\"/etc/ssh/sshd_config\\\", or uncomment the line\nand set the value to \\\"yes\\\":\n\n IgnoreUserKnownHosts yes\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72249\"\n tag rid: \"SV-86873r3_rule\"\n tag stig_id: \"RHEL-07-040380\"\n tag fix_id: \"F-78603r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('IgnoreUserKnownHosts') { should cmp 'yes' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \"IgnoreUserKnownHosts\" option is set,\nrun the following command:\n\n # grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config\n\n IgnoreUserKnownHosts yes\n\n If the value is returned as \"no\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"yes\":\n\n IgnoreUserKnownHosts yes\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72249","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72249.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72249","rid":"SV-86873r3_rule","stig_id":"RHEL-07-040380","fix_id":"F-78603r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using known hosts\nauthentication.","waiver_data":{}},{"code":"control \"V-72251\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use the SSHv2 protocol.\"\n desc \"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon is configured to only use the SSHv2 protocol.\n\n Check that the SSH daemon is configured to only use the SSHv2 protocol with\nthe following command:\n\n # grep -i protocol /etc/ssh/sshd_config\n Protocol 2\n #Protocol 1,2\n\n If any protocol line other than \\\"Protocol 2\\\" is uncommented, this is a\nfinding.\n \"\n desc \"fix\", \"\n Remove all Protocol lines that reference version \\\"1\\\" in\n\\\"/etc/ssh/sshd_config\\\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor). The \\\"Protocol\\\" line must be as follows:\n\n Protocol 2\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000074-GPOS-00042\"\n tag satisfies: [\"SRG-OS-000074-GPOS-00042\", \"SRG-OS-000480-GPOS-00227\"]\n tag gid: \"V-72251\"\n tag rid: \"SV-86875r4_rule\"\n tag stig_id: \"RHEL-07-040390\"\n tag fix_id: \"F-78605r2_fix\"\n tag cci: [\"CCI-000197\", \"CCI-000366\"]\n tag nist: [\"IA-5 (1) (c)\", \"CM-6 b\"]\n\n if os.release.to_f >= 7.4\n impact 0.0\n describe \"The release is #{os.release}\" do\n skip \"The release is newer than 7.4; this control is Not Applicable.\"\n end\n else\n describe sshd_config do\n its('Protocol') { should cmp '2' }\n end\n end\nend\n","desc":"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.","descriptions":[{"data":"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon is configured to only use the SSHv2 protocol.\n\n Check that the SSH daemon is configured to only use the SSHv2 protocol with\nthe following command:\n\n # grep -i protocol /etc/ssh/sshd_config\n Protocol 2\n #Protocol 1,2\n\n If any protocol line other than \"Protocol 2\" is uncommented, this is a\nfinding.","label":"check"},{"data":"Remove all Protocol lines that reference version \"1\" in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor). The \"Protocol\" line must be as follows:\n\n Protocol 2\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72251","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72251.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000074-GPOS-00042","satisfies":["SRG-OS-000074-GPOS-00042","SRG-OS-000480-GPOS-00227"],"gid":"V-72251","rid":"SV-86875r4_rule","stig_id":"RHEL-07-040390","fix_id":"F-78605r2_fix","cci":["CCI-000197","CCI-000366"],"nist":["IA-5 (1) (c)","CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use the SSHv2 protocol.","waiver_data":{}},{"code":"control \"V-72253\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use Message Authentication Codes\n(MACs) employing FIPS 140-2 approved cryptographic hash algorithms.\"\n desc \"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n Check that the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers with the following command:\n\n # grep -i macs /etc/ssh/sshd_config\n MACs hmac-sha2-256,hmac-sha2-512\n\n If any ciphers other than \\\"hmac-sha2-256\\\" or \\\"hmac-sha2-512\\\" are listed\nor the returned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for the\n\\\"MACs\\\" keyword and set its value to \\\"hmac-sha2-256\\\" and/or\n\\\"hmac-sha2-512\\\" (this file may be named differently or be in a different\nlocation if using a version of SSH that is provided by a third-party vendor):\n\n MACs hmac-sha2-256,hmac-sha2-512\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72253\"\n tag rid: \"SV-86877r3_rule\"\n tag stig_id: \"RHEL-07-040400\"\n tag fix_id: \"F-78607r2_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n @macs = inspec.sshd_config.params(\"macs\")\n if @macs.nil?\n # fail fast\n describe 'The `sshd_config` setting for `MACs`' do\n subject { @macs }\n it 'should be explicitly set and not commented out' do\n expect(subject).not_to be_nil\n end\n end\n else\n @macs.first.split(\",\").each do |mac|\n describe mac do\n it { should be_in ['hmac-sha2-256', 'hmac-sha2-512'] }\n end\n end\n end\nend\n","desc":"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.","descriptions":[{"data":"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n Check that the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers with the following command:\n\n # grep -i macs /etc/ssh/sshd_config\n MACs hmac-sha2-256,hmac-sha2-512\n\n If any ciphers other than \"hmac-sha2-256\" or \"hmac-sha2-512\" are listed\nor the returned line is commented out, this is a finding.","label":"check"},{"data":"Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the\n\"MACs\" keyword and set its value to \"hmac-sha2-256\" and/or\n\"hmac-sha2-512\" (this file may be named differently or be in a different\nlocation if using a version of SSH that is provided by a third-party vendor):\n\n MACs hmac-sha2-256,hmac-sha2-512\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72253","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72253.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72253","rid":"SV-86877r3_rule","stig_id":"RHEL-07-040400","fix_id":"F-78607r2_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use Message Authentication Codes\n(MACs) employing FIPS 140-2 approved cryptographic hash algorithms.","waiver_data":{}},{"code":"control \"V-72255\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH public host key files have mode 0644 or less permissive.\"\n desc \"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH public host key files have mode \\\"0644\\\" or less permissive.\n\n Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n The following command will find all SSH public key files on the system:\n\n # find /etc/ssh -name '*.pub' -exec ls -lL {} \\\\;\n\n -rw-r--r-- 1 root root 618 Nov 28 06:43 ssh_host_dsa_key.pub\n -rw-r--r-- 1 root root 347 Nov 28 06:43 ssh_host_key.pub\n -rw-r--r-- 1 root root 238 Nov 28 06:43 ssh_host_rsa_key.pub\n\n If any file has a mode more permissive than \\\"0644\\\", this is a finding.\n \"\n desc \"fix\", \"\n Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n Change the mode of public host key files under \\\"/etc/ssh\\\" to \\\"0644\\\"\nwith the following command:\n\n # chmod 0644 /etc/ssh/*.key.pub\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72255\"\n tag rid: \"SV-86879r2_rule\"\n tag stig_id: \"RHEL-07-040410\"\n tag fix_id: \"F-78609r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n pub_files = command(\"find /etc/ssh -xdev -name '*.pub' -perm /133\").stdout.split(\"\\n\")\n if !pub_files.nil? and !pub_files.empty?\n pub_files.each do |pubfile|\n describe file(pubfile) do\n it { should_not be_executable.by('owner') }\n it { should_not be_executable.by('group') }\n it { should_not be_writable.by('group') }\n it { should_not be_executable.by('others') }\n it { should_not be_writable.by('others') }\n end\n end\n else\n describe \"No files have a more permissive mode.\" do\n subject { pub_files.nil? or pub_files.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.","descriptions":[{"data":"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH public host key files have mode \"0644\" or less permissive.\n\n Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n The following command will find all SSH public key files on the system:\n\n # find /etc/ssh -name '*.pub' -exec ls -lL {} \\;\n\n -rw-r--r-- 1 root root 618 Nov 28 06:43 ssh_host_dsa_key.pub\n -rw-r--r-- 1 root root 347 Nov 28 06:43 ssh_host_key.pub\n -rw-r--r-- 1 root root 238 Nov 28 06:43 ssh_host_rsa_key.pub\n\n If any file has a mode more permissive than \"0644\", this is a finding.","label":"check"},{"data":"Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n Change the mode of public host key files under \"/etc/ssh\" to \"0644\"\nwith the following command:\n\n # chmod 0644 /etc/ssh/*.key.pub","label":"fix"}],"id":"V-72255","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72255.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72255","rid":"SV-86879r2_rule","stig_id":"RHEL-07-040410","fix_id":"F-78609r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH public host key files have mode 0644 or less permissive.","waiver_data":{}},{"code":"control \"V-72257\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH private host key files have mode 0640 or less permissive.\"\n desc \"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH private host key files have mode \\\"0640\\\" or less permissive.\n\n The following command will find all SSH private key files on the system and\nlist their modes:\n\n # find / -name '*ssh_host*key' | xargs ls -lL\n\n -rw-r----- 1 root ssh_keys 668 Nov 28 06:43 ssh_host_dsa_key\n -rw-r----- 1 root ssh_keys 582 Nov 28 06:43 ssh_host_key\n -rw-r----- 1 root ssh_keys 887 Nov 28 06:43 ssh_host_rsa_key\n\n If any file has a mode more permissive than \\\"0640\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the mode of SSH private host key files under \\\"/etc/ssh\\\" to\n\\\"0640\\\" with the following command:\n\n # chmod 0640 /path/to/file/ssh_host*key\n\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72257\"\n tag rid: \"SV-86881r3_rule\"\n tag stig_id: \"RHEL-07-040420\"\n tag fix_id: \"F-78611r5_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n key_files = command(\"find /etc/ssh -xdev -name '*ssh_host*key'\").stdout.split(\"\\n\")\n if !key_files.nil? and !key_files.empty?\n key_files.each do |keyfile|\n describe file(keyfile) do\n it { should_not be_more_permissive_than('0640') }\n end\n end\n else\n describe \"No files have a more permissive mode.\" do\n subject { key_files.nil? or key_files.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.","descriptions":[{"data":"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH private host key files have mode \"0640\" or less permissive.\n\n The following command will find all SSH private key files on the system and\nlist their modes:\n\n # find / -name '*ssh_host*key' | xargs ls -lL\n\n -rw-r----- 1 root ssh_keys 668 Nov 28 06:43 ssh_host_dsa_key\n -rw-r----- 1 root ssh_keys 582 Nov 28 06:43 ssh_host_key\n -rw-r----- 1 root ssh_keys 887 Nov 28 06:43 ssh_host_rsa_key\n\n If any file has a mode more permissive than \"0640\", this is a finding.","label":"check"},{"data":"Configure the mode of SSH private host key files under \"/etc/ssh\" to\n\"0640\" with the following command:\n\n # chmod 0640 /path/to/file/ssh_host*key","label":"fix"}],"id":"V-72257","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72257.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72257","rid":"SV-86881r3_rule","stig_id":"RHEL-07-040420","fix_id":"F-78611r5_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH private host key files have mode 0640 or less permissive.","waiver_data":{}},{"code":"control \"V-72259\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Generic Security Service Application\nProgram Interface (GSSAPI) authentication unless needed.\"\n desc \"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not permit GSSAPI authentication unless approved.\n\n Check that the SSH daemon does not permit GSSAPI authentication with the\nfollowing command:\n\n # grep -i gssapiauth /etc/ssh/sshd_config\n GSSAPIAuthentication no\n\n If the \\\"GSSAPIAuthentication\\\" keyword is missing, is set to \\\"yes\\\" and\nis not documented with the Information System Security Officer (ISSO), or the\nreturned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"GSSAPIAuthentication\\\" keyword in \\\"/etc/ssh/sshd_config\\\"\n(this file may be named differently or be in a different location if using a\nversion of SSH that is provided by a third-party vendor) and set the value to\n\\\"no\\\":\n\n GSSAPIAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If GSSAPI authentication is required, it must be documented, to include the\nlocation of the configuration file, with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000364-GPOS-00151\"\n tag gid: \"V-72259\"\n tag rid: \"SV-86883r3_rule\"\n tag stig_id: \"RHEL-07-040430\"\n tag fix_id: \"F-78613r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n if input('gssapi_approved')\n describe sshd_config do\n its('GSSAPIAuthentication') { should cmp 'no' }\n end\n else\n impact 0.0\n describe \"GSSAPI authentication is not approved\" do\n skip \"GSSAPI authentication is not approved, this control is Not Applicable.\"\n end\n end\nend\n","desc":"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.","descriptions":[{"data":"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not permit GSSAPI authentication unless approved.\n\n Check that the SSH daemon does not permit GSSAPI authentication with the\nfollowing command:\n\n # grep -i gssapiauth /etc/ssh/sshd_config\n GSSAPIAuthentication no\n\n If the \"GSSAPIAuthentication\" keyword is missing, is set to \"yes\" and\nis not documented with the Information System Security Officer (ISSO), or the\nreturned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"GSSAPIAuthentication\" keyword in \"/etc/ssh/sshd_config\"\n(this file may be named differently or be in a different location if using a\nversion of SSH that is provided by a third-party vendor) and set the value to\n\"no\":\n\n GSSAPIAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If GSSAPI authentication is required, it must be documented, to include the\nlocation of the configuration file, with the ISSO.","label":"fix"}],"id":"V-72259","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72259.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72259","rid":"SV-86883r3_rule","stig_id":"RHEL-07-040430","fix_id":"F-78613r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Generic Security Service Application\nProgram Interface (GSSAPI) authentication unless needed.","waiver_data":{}},{"code":"control \"V-72261\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Kerberos authentication unless needed.\"\n desc \"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not permit Kerberos to authenticate passwords\nunless approved.\n\n Check that the SSH daemon does not permit Kerberos to authenticate\npasswords with the following command:\n\n # grep -i kerberosauth /etc/ssh/sshd_config\n KerberosAuthentication no\n\n If the \\\"KerberosAuthentication\\\" keyword is missing, or is set to \\\"yes\\\"\nand is not documented with the Information System Security Officer (ISSO), or\nthe returned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"KerberosAuthentication\\\" keyword in\n\\\"/etc/ssh/sshd_config\\\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \\\"no\\\":\n\n KerberosAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If Kerberos authentication is required, it must be documented, to include\nthe location of the configuration file, with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000364-GPOS-00151\"\n tag gid: \"V-72261\"\n tag rid: \"SV-86885r3_rule\"\n tag stig_id: \"RHEL-07-040440\"\n tag fix_id: \"F-78615r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n describe sshd_config do\n its('KerberosAuthentication') { should cmp 'no' }\n end\nend\n","desc":"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.","descriptions":[{"data":"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not permit Kerberos to authenticate passwords\nunless approved.\n\n Check that the SSH daemon does not permit Kerberos to authenticate\npasswords with the following command:\n\n # grep -i kerberosauth /etc/ssh/sshd_config\n KerberosAuthentication no\n\n If the \"KerberosAuthentication\" keyword is missing, or is set to \"yes\"\nand is not documented with the Information System Security Officer (ISSO), or\nthe returned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"KerberosAuthentication\" keyword in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \"no\":\n\n KerberosAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If Kerberos authentication is required, it must be documented, to include\nthe location of the configuration file, with the ISSO.","label":"fix"}],"id":"V-72261","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72261.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72261","rid":"SV-86885r3_rule","stig_id":"RHEL-07-040440","fix_id":"F-78615r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Kerberos authentication unless needed.","waiver_data":{}},{"code":"control \"V-72263\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon performs strict mode checking of home directory\nconfiguration files.\"\n desc \"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon performs strict mode checking of home directory\nconfiguration files.\n\n The location of the \\\"sshd_config\\\" file may vary if a different daemon is\nin use.\n\n Inspect the \\\"sshd_config\\\" file with the following command:\n\n # grep -i strictmodes /etc/ssh/sshd_config\n\n StrictModes yes\n\n If \\\"StrictModes\\\" is set to \\\"no\\\", is missing, or the returned line is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"StrictModes\\\" keyword in \\\"/etc/ssh/sshd_config\\\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) and set the value to \\\"yes\\\":\n\n StrictModes yes\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72263\"\n tag rid: \"SV-86887r3_rule\"\n tag stig_id: \"RHEL-07-040450\"\n tag fix_id: \"F-78617r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('StrictModes') { should cmp 'yes' }\n end\nend\n","desc":"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.","descriptions":[{"data":"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs strict mode checking of home directory\nconfiguration files.\n\n The location of the \"sshd_config\" file may vary if a different daemon is\nin use.\n\n Inspect the \"sshd_config\" file with the following command:\n\n # grep -i strictmodes /etc/ssh/sshd_config\n\n StrictModes yes\n\n If \"StrictModes\" is set to \"no\", is missing, or the returned line is\ncommented out, this is a finding.","label":"check"},{"data":"Uncomment the \"StrictModes\" keyword in \"/etc/ssh/sshd_config\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) and set the value to \"yes\":\n\n StrictModes yes\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72263","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72263.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72263","rid":"SV-86887r3_rule","stig_id":"RHEL-07-040450","fix_id":"F-78617r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon performs strict mode checking of home directory\nconfiguration files.","waiver_data":{}},{"code":"control \"V-72265\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon uses privilege separation.\"\n desc \"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon performs privilege separation.\n\n Check that the SSH daemon performs privilege separation with the following\ncommand:\n\n # grep -i usepriv /etc/ssh/sshd_config\n\n UsePrivilegeSeparation sandbox\n\n If the \\\"UsePrivilegeSeparation\\\" keyword is set to \\\"no\\\", is missing, or\nthe returned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"UsePrivilegeSeparation\\\" keyword in\n\\\"/etc/ssh/sshd_config\\\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \\\"sandbox\\\" or \\\"yes\\\":\n\n UsePrivilegeSeparation sandbox\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72265\"\n tag rid: \"SV-86889r3_rule\"\n tag stig_id: \"RHEL-07-040460\"\n tag fix_id: \"F-78619r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe sshd_config do\n its('UsePrivilegeSeparation') { should cmp 'sandbox' }\n end\n describe sshd_config do\n its('UsePrivilegeSeparation') { should cmp 'yes' }\n end\n end\nend\n","desc":"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.","descriptions":[{"data":"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs privilege separation.\n\n Check that the SSH daemon performs privilege separation with the following\ncommand:\n\n # grep -i usepriv /etc/ssh/sshd_config\n\n UsePrivilegeSeparation sandbox\n\n If the \"UsePrivilegeSeparation\" keyword is set to \"no\", is missing, or\nthe returned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"UsePrivilegeSeparation\" keyword in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \"sandbox\" or \"yes\":\n\n UsePrivilegeSeparation sandbox\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72265","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72265.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72265","rid":"SV-86889r3_rule","stig_id":"RHEL-07-040460","fix_id":"F-78619r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon uses privilege separation.","waiver_data":{}},{"code":"control \"V-72267\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow compression or only allows compression after\nsuccessful authentication.\"\n desc \"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon performs compression after a user successfully\nauthenticates.\n\n Check that the SSH daemon performs compression after a user successfully\nauthenticates with the following command:\n\n # grep -i compression /etc/ssh/sshd_config\n Compression delayed\n\n If the \\\"Compression\\\" keyword is set to \\\"yes\\\", is missing, or the\nreturned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"Compression\\\" keyword in \\\"/etc/ssh/sshd_config\\\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) on the system and set the\nvalue to \\\"delayed\\\" or \\\"no\\\":\n\n Compression no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72267\"\n tag rid: \"SV-86891r3_rule\"\n tag stig_id: \"RHEL-07-040470\"\n tag fix_id: \"F-78621r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe sshd_config do\n its('Compression') { should cmp 'delayed' }\n end\n describe sshd_config do\n its('Compression') { should cmp 'no' }\n end\n end\nend\n","desc":"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.","descriptions":[{"data":"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs compression after a user successfully\nauthenticates.\n\n Check that the SSH daemon performs compression after a user successfully\nauthenticates with the following command:\n\n # grep -i compression /etc/ssh/sshd_config\n Compression delayed\n\n If the \"Compression\" keyword is set to \"yes\", is missing, or the\nreturned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"Compression\" keyword in \"/etc/ssh/sshd_config\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) on the system and set the\nvalue to \"delayed\" or \"no\":\n\n Compression no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72267","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72267.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72267","rid":"SV-86891r3_rule","stig_id":"RHEL-07-040470","fix_id":"F-78621r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow compression or only allows compression after\nsuccessful authentication.","waiver_data":{}},{"code":"control \"V-72269\" do\n title \"The Red Hat Enterprise Linux operating system must, for networked\nsystems, synchronize clocks with a server that is synchronized to one of the\nredundant United States Naval Observatory (USNO) time servers, a time server\ndesignated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global\nPositioning System (GPS).\"\n desc \"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check to see if NTP is running in continuous mode:\n\n # ps -ef | grep ntp\n\n If NTP is not running, check to see if \\\"chronyd\\\" is running in continuous\nmode:\n\n # ps -ef | grep chronyd\n\n If NTP or \\\"chronyd\\\" is not running, this is a finding.\n\n If the NTP process is found, then check the \\\"ntp.conf\\\" file for the\n\\\"maxpoll\\\" option setting:\n\n # grep maxpoll /etc/ntp.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is set to \\\"17\\\" or is not set, this is a finding.\n\n If the file does not exist, check the \\\"/etc/cron.daily\\\" subdirectory for\na crontab file controlling the execution of the \\\"ntpd -q\\\" command.\n\n # grep -i \\\"ntpd -q\\\" /etc/cron.daily/*\n # ls -al /etc/cron.* | grep ntp\n\n ntp\n\n If a crontab file does not exist in the \\\"/etc/cron.daily\\\" that executes\nthe \\\"ntpd -q\\\" command, this is a finding.\n\n If the \\\"chronyd\\\" process is found, then check the \\\"chrony.conf\\\" file\nfor the \\\"maxpoll\\\" option setting:\n\n # grep maxpoll /etc/chrony.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is not set or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the \\\"/etc/ntp.conf\\\" or \\\"/etc/chrony.conf\\\" file and add or update\nan entry to define \\\"maxpoll\\\" to \\\"10\\\" as follows:\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If NTP was running and \\\"maxpoll\\\" was updated, the NTP service must be\nrestarted:\n\n # systemctl restart ntpd\n\n If NTP was not running, it must be started:\n\n # systemctl start ntpd\n\n If \\\"chronyd\\\" was running and \\\"maxpoll\\\" was updated, the service must be\nrestarted:\n\n # systemctl restart chronyd.service\n\n If \\\"chronyd\\\" was not running, it must be started:\n\n # systemctl start chronyd.service\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000355-GPOS-00143\"\n tag satisfies: [\"SRG-OS-000355-GPOS-00143\", \"SRG-OS-000356-GPOS-00144\"]\n tag gid: \"V-72269\"\n tag rid: \"SV-86893r5_rule\"\n tag stig_id: \"RHEL-07-040500\"\n tag fix_id: \"F-78623r5_fix\"\n tag cci: [\"CCI-001891\", \"CCI-002046\"]\n tag nist: [\"AU-8 (1) (a)\", \"AU-8 (1) (b)\"]\n\n # Either ntpd or chronyd should be running\n describe.one do\n [service('ntpd'), service('chronyd')].each do |time_service|\n describe time_service do\n it { should be_running }\n it { should be_enabled }\n it { should be_installed }\n end\n end\n end\n\n if service('ntpd').installed?\n time_service = service('ntpd')\n time_sources = ntp_conf('/etc/ntp.conf').server\n max_poll_values = time_sources.map { |val| val.match?(/.*maxpoll.*/) ? val.gsub(/.*maxpoll\\s+(\\d+)(\\s+.*|$)/,'\\1').to_i : 99 }\n ntpdate_crons = command('grep -l \"ntpd -q\" /etc/cron.daily/*').stdout.strip.lines\n\n describe \"ntpd time sources list\" do\n subject { time_sources }\n it { should_not be_empty }\n end\n\n describe.one do\n # Case where maxpoll empty\n describe \"Daily cron jobs for 'ntpd -q'\" do\n subject { ntpdate_crons }\n it { should_not be_empty }\n end\n # All time sources must contain valid maxpoll entries\n describe \"ntpd maxpoll values (99=maxpoll absent)\" do\n subject { max_poll_values }\n it { should all be < 17 }\n end\n end\n end\n\n if service('chronyd').installed?\n time_service = service('chronyd')\n time_sources = ntp_conf('/etc/chrony.conf').server\n max_poll_values = time_sources.map { |val| val.match?(/.*maxpoll.*/) ? val.gsub(/.*maxpoll\\s+(\\d+)(\\s+.*|$)/,'\\1').to_i : 99 }\n\n describe \"chronyd time sources list\" do\n subject { time_sources }\n it { should_not be_empty }\n end\n \n # All time sources must contain valid maxpoll entries\n describe \"chronyd maxpoll values (99=maxpoll absent)\" do\n subject { max_poll_values }\n it { should all be < 17 }\n end\n end\nend\n","desc":"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).","descriptions":[{"data":"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if NTP is running in continuous mode:\n\n # ps -ef | grep ntp\n\n If NTP is not running, check to see if \"chronyd\" is running in continuous\nmode:\n\n # ps -ef | grep chronyd\n\n If NTP or \"chronyd\" is not running, this is a finding.\n\n If the NTP process is found, then check the \"ntp.conf\" file for the\n\"maxpoll\" option setting:\n\n # grep maxpoll /etc/ntp.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is set to \"17\" or is not set, this is a finding.\n\n If the file does not exist, check the \"/etc/cron.daily\" subdirectory for\na crontab file controlling the execution of the \"ntpd -q\" command.\n\n # grep -i \"ntpd -q\" /etc/cron.daily/*\n # ls -al /etc/cron.* | grep ntp\n\n ntp\n\n If a crontab file does not exist in the \"/etc/cron.daily\" that executes\nthe \"ntpd -q\" command, this is a finding.\n\n If the \"chronyd\" process is found, then check the \"chrony.conf\" file\nfor the \"maxpoll\" option setting:\n\n # grep maxpoll /etc/chrony.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is not set or the line is commented out, this is a finding.","label":"check"},{"data":"Edit the \"/etc/ntp.conf\" or \"/etc/chrony.conf\" file and add or update\nan entry to define \"maxpoll\" to \"10\" as follows:\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If NTP was running and \"maxpoll\" was updated, the NTP service must be\nrestarted:\n\n # systemctl restart ntpd\n\n If NTP was not running, it must be started:\n\n # systemctl start ntpd\n\n If \"chronyd\" was running and \"maxpoll\" was updated, the service must be\nrestarted:\n\n # systemctl restart chronyd.service\n\n If \"chronyd\" was not running, it must be started:\n\n # systemctl start chronyd.service","label":"fix"}],"id":"V-72269","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72269.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000355-GPOS-00143","satisfies":["SRG-OS-000355-GPOS-00143","SRG-OS-000356-GPOS-00144"],"gid":"V-72269","rid":"SV-86893r5_rule","stig_id":"RHEL-07-040500","fix_id":"F-78623r5_fix","cci":["CCI-001891","CCI-002046"],"nist":["AU-8 (1) (a)","AU-8 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must, for networked\nsystems, synchronize clocks with a server that is synchronized to one of the\nredundant United States Naval Observatory (USNO) time servers, a time server\ndesignated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global\nPositioning System (GPS).","waiver_data":{}},{"code":"control \"V-72273\" do\n title \"The Red Hat Enterprise Linux operating system must enable an\napplication firewall, if available.\"\n desc \"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enabled an application firewall.\n\n Check to see if \\\"firewalld\\\" is installed with the following command:\n\n # yum list installed firewalld\n firewalld-0.3.9-11.el7.noarch.rpm\n\n If the \\\"firewalld\\\" package is not installed, ask the System Administrator\nif another firewall application (such as iptables) is installed.\n\n If an application firewall is not installed, this is a finding.\n\n Check to see if the firewall is loaded and active with the following\ncommand:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago\n\n If \\\"firewalld\\\" does not show a status of \\\"loaded\\\" and \\\"active\\\", this\nis a finding.\n\n Check the state of the firewall:\n\n # firewall-cmd --state\n running\n\n If \\\"firewalld\\\" does not show a state of \\\"running\\\", this is a finding.\n \"\n desc \"fix\", \"\n Ensure the operating system's application firewall is enabled.\n\n Install the \\\"firewalld\\\" package, if it is not on the system, with the\nfollowing command:\n\n # yum install firewalld\n\n Start the firewall via \\\"systemctl\\\" with the following command:\n\n # systemctl start firewalld\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag satisfies: [\"SRG-OS-000480-GPOS-00227\", \"SRG-OS-000480-GPOS-00231\",\n\"SRG-OS-000480-GPOS-00232\"]\n tag gid: \"V-72273\"\n tag rid: \"SV-86897r2_rule\"\n tag stig_id: \"RHEL-07-040520\"\n tag fix_id: \"F-78627r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe package('firewalld') do\n it { should be_installed }\n end\n describe package('iptables') do\n it { should be_installed }\n end\n end\n describe.one do\n describe systemd_service('firewalld.service') do\n it { should be_running }\n end\n\tdescribe systemd_service('iptables.service') do\n it { should be_running }\n end\n end\nend\n","desc":"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.","descriptions":[{"data":"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enabled an application firewall.\n\n Check to see if \"firewalld\" is installed with the following command:\n\n # yum list installed firewalld\n firewalld-0.3.9-11.el7.noarch.rpm\n\n If the \"firewalld\" package is not installed, ask the System Administrator\nif another firewall application (such as iptables) is installed.\n\n If an application firewall is not installed, this is a finding.\n\n Check to see if the firewall is loaded and active with the following\ncommand:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago\n\n If \"firewalld\" does not show a status of \"loaded\" and \"active\", this\nis a finding.\n\n Check the state of the firewall:\n\n # firewall-cmd --state\n running\n\n If \"firewalld\" does not show a state of \"running\", this is a finding.","label":"check"},{"data":"Ensure the operating system's application firewall is enabled.\n\n Install the \"firewalld\" package, if it is not on the system, with the\nfollowing command:\n\n # yum install firewalld\n\n Start the firewall via \"systemctl\" with the following command:\n\n # systemctl start firewalld","label":"fix"}],"id":"V-72273","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72273.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","satisfies":["SRG-OS-000480-GPOS-00227","SRG-OS-000480-GPOS-00231","SRG-OS-000480-GPOS-00232"],"gid":"V-72273","rid":"SV-86897r2_rule","stig_id":"RHEL-07-040520","fix_id":"F-78627r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must enable an\napplication firewall, if available.","waiver_data":{}},{"code":"control \"V-72275\" do\n title \"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon logon.\"\n desc \"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify users are provided with feedback on when account accesses last\noccurred.\n\n Check that \\\"pam_lastlog\\\" is used and not silent with the following\ncommand:\n\n # grep pam_lastlog /etc/pam.d/postlogin\n session required pam_lastlog.so showfailed\n\n If \\\"pam_lastlog\\\" is missing from \\\"/etc/pam.d/postlogin\\\" file, or the\nsilent option is present, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to provide users with feedback on when\naccount accesses last occurred by setting the required configuration options in\n\\\"/etc/pam.d/postlogin\\\".\n\n Add the following line to the top of \\\"/etc/pam.d/postlogin\\\":\n\n session required pam_lastlog.so showfailed\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72275\"\n tag rid: \"SV-86899r4_rule\"\n tag stig_id: \"RHEL-07-040530\"\n tag fix_id: \"F-78629r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe pam('/etc/pam.d/postlogin') do\n its('lines') { should match_pam_rule('session .* pam_lastlog.so showfailed') }\n end\n\n describe.one do\n describe sshd_config do\n its('PrintLastLog') { should cmp 'yes' }\n end\n\n describe pam('/etc/pam.d/postlogin') do\n its('lines') { should match_pam_rule('session .* pam_lastlog.so showfailed').all_without_args('silent') }\n end\n end\nend\n","desc":"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.","descriptions":[{"data":"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify users are provided with feedback on when account accesses last\noccurred.\n\n Check that \"pam_lastlog\" is used and not silent with the following\ncommand:\n\n # grep pam_lastlog /etc/pam.d/postlogin\n session required pam_lastlog.so showfailed\n\n If \"pam_lastlog\" is missing from \"/etc/pam.d/postlogin\" file, or the\nsilent option is present, this is a finding.","label":"check"},{"data":"Configure the operating system to provide users with feedback on when\naccount accesses last occurred by setting the required configuration options in\n\"/etc/pam.d/postlogin\".\n\n Add the following line to the top of \"/etc/pam.d/postlogin\":\n\n session required pam_lastlog.so showfailed","label":"fix"}],"id":"V-72275","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72275.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72275","rid":"SV-86899r4_rule","stig_id":"RHEL-07-040530","fix_id":"F-78629r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon logon.","waiver_data":{}},{"code":"control \"V-72277\" do\n title \"The Red Hat Enterprise Linux operating system must not contain .shosts\nfiles.\"\n desc \"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify there are no \\\".shosts\\\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name '*.shosts'\n\n If any \\\".shosts\\\" files are found on the system, this is a finding.\n \"\n desc \"fix\", \"\n Remove any found \\\".shosts\\\" files from the system.\n\n # rm /[path]/[to]/[file]/.shosts\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72277\"\n tag rid: \"SV-86901r2_rule\"\n tag stig_id: \"RHEL-07-040540\"\n tag fix_id: \"F-78631r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe command(\"find / -xdev -xautofs -name '*.shosts'\") do\n its('stdout.strip') { should be_empty }\n end\nend\n","desc":"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.","descriptions":[{"data":"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify there are no \".shosts\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name '*.shosts'\n\n If any \".shosts\" files are found on the system, this is a finding.","label":"check"},{"data":"Remove any found \".shosts\" files from the system.\n\n# rm /[path]/[to]/[file]/.shosts","label":"fix"}],"id":"V-72277","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72277.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72277","rid":"SV-86901r2_rule","stig_id":"RHEL-07-040540","fix_id":"F-78631r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not contain .shosts\nfiles.","waiver_data":{}},{"code":"control \"V-72279\" do\n title \"The Red Hat Enterprise Linux operating system must not contain\nshosts.equiv files.\"\n desc \"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify there are no \\\"shosts.equiv\\\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name shosts.equiv\n\n If any \\\"shosts.equiv\\\" files are found on the system, this is a finding.\n \"\n desc \"fix\", \"\n Remove any found \\\"shosts.equiv\\\" files from the system.\n\n # rm /[path]/[to]/[file]/shosts.equiv\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72279\"\n tag rid: \"SV-86903r2_rule\"\n tag stig_id: \"RHEL-07-040550\"\n tag fix_id: \"F-78633r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe command('find / -xdev -xautofs -name shosts.equiv') do\n its('stdout.strip') { should be_empty }\n end\nend\n","desc":"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.","descriptions":[{"data":"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify there are no \"shosts.equiv\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name shosts.equiv\n\n If any \"shosts.equiv\" files are found on the system, this is a finding.","label":"check"},{"data":"Remove any found \"shosts.equiv\" files from the system.\n\n# rm /[path]/[to]/[file]/shosts.equiv","label":"fix"}],"id":"V-72279","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72279.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72279","rid":"SV-86903r2_rule","stig_id":"RHEL-07-040550","fix_id":"F-78633r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not contain\nshosts.equiv files.","waiver_data":{}},{"code":"control \"V-72281\" do\n title \"For Red Hat Enterprise Linux operating systems using DNS resolution,\nat least two name servers must be configured.\"\n desc \"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Determine whether the system is using local or DNS name resolution with the\nfollowing command:\n\n # grep hosts /etc/nsswitch.conf\n hosts: files dns\n\n If the DNS entry is missing from the host's line in the\n\\\"/etc/nsswitch.conf\\\" file, the \\\"/etc/resolv.conf\\\" file must be empty.\n\n Verify the \\\"/etc/resolv.conf\\\" file is empty with the following command:\n\n # ls -al /etc/resolv.conf\n -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf\n\n If local host authentication is being used and the \\\"/etc/resolv.conf\\\"\nfile is not empty, this is a finding.\n\n If the DNS entry is found on the host's line of the \\\"/etc/nsswitch.conf\\\"\nfile, verify the operating system is configured to use two or more name servers\nfor DNS resolution.\n\n Determine the name servers used by the system with the following command:\n\n # grep nameserver /etc/resolv.conf\n nameserver 192.168.1.2\n nameserver 192.168.1.3\n\n If less than two lines are returned that are not commented out, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to use two or more name servers for DNS\nresolution.\n\n Edit the \\\"/etc/resolv.conf\\\" file to uncomment or add the two or more\n\\\"nameserver\\\" option lines with the IP address of local authoritative name\nservers. If local host resolution is being performed, the \\\"/etc/resolv.conf\\\"\nfile must be empty. An empty \\\"/etc/resolv.conf\\\" file can be created as\nfollows:\n\n # echo -n > /etc/resolv.conf\n\n And then make the file immutable with the following command:\n\n # chattr +i /etc/resolv.conf\n\n If the \\\"/etc/resolv.conf\\\" file must be mutable, the required\nconfiguration must be documented with the Information System Security Officer\n(ISSO) and the file must be verified by the system file integrity tool.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72281\"\n tag rid: \"SV-86905r2_rule\"\n tag stig_id: \"RHEL-07-040600\"\n tag fix_id: \"F-78635r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n dns_in_host_line = parse_config_file(\"/etc/nsswitch.conf\",\n {\n comment_char: '#',\n assignment_regex: /^\\s*([^:]*?)\\s*:\\s*(.*?)\\s*$/,\n }\n ).params['hosts'].include?('dns')\n\n describe \"If `local` resolution is being used, a `hosts` entry in /etc/nsswitch.conf having `dns`\" do\n subject { dns_in_host_line }\n it { should be false }\n end if !dns_in_host_line\n\n describe \"If `local` resoultion is being used, the /etc/resolv.conf file should\" do\n subject { parse_config_file(\"/etc/resolv.conf\", { comment_char: '#'}).params }\n it { should be_empty }\n end if !dns_in_host_line\n\n nameservers = parse_config_file(\"/etc/resolv.conf\",\n { comment_char: '#'}\n ).params.keys.grep(/nameserver/)\n\n describe \"The system's nameservers: #{nameservers}\" do\n subject { nameservers }\n it { should_not be nil }\n end if dns_in_host_line\n\n describe \"The number of nameservers\" do\n subject { nameservers.count }\n it { should cmp >= 2 }\n end if dns_in_host_line\nend\n","desc":"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.","descriptions":[{"data":"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.","label":"default"},{"data":"","label":"rationale"},{"data":"Determine whether the system is using local or DNS name resolution with the\nfollowing command:\n\n # grep hosts /etc/nsswitch.conf\n hosts: files dns\n\n If the DNS entry is missing from the host's line in the\n\"/etc/nsswitch.conf\" file, the \"/etc/resolv.conf\" file must be empty.\n\n Verify the \"/etc/resolv.conf\" file is empty with the following command:\n\n # ls -al /etc/resolv.conf\n -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf\n\n If local host authentication is being used and the \"/etc/resolv.conf\"\nfile is not empty, this is a finding.\n\n If the DNS entry is found on the host's line of the \"/etc/nsswitch.conf\"\nfile, verify the operating system is configured to use two or more name servers\nfor DNS resolution.\n\n Determine the name servers used by the system with the following command:\n\n # grep nameserver /etc/resolv.conf\n nameserver 192.168.1.2\n nameserver 192.168.1.3\n\n If less than two lines are returned that are not commented out, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to use two or more name servers for DNS\nresolution.\n\n Edit the \"/etc/resolv.conf\" file to uncomment or add the two or more\n\"nameserver\" option lines with the IP address of local authoritative name\nservers. If local host resolution is being performed, the \"/etc/resolv.conf\"\nfile must be empty. An empty \"/etc/resolv.conf\" file can be created as\nfollows:\n\n # echo -n > /etc/resolv.conf\n\n And then make the file immutable with the following command:\n\n # chattr +i /etc/resolv.conf\n\n If the \"/etc/resolv.conf\" file must be mutable, the required\nconfiguration must be documented with the Information System Security Officer\n(ISSO) and the file must be verified by the system file integrity tool.","label":"fix"}],"id":"V-72281","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72281.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72281","rid":"SV-86905r2_rule","stig_id":"RHEL-07-040600","fix_id":"F-78635r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"For Red Hat Enterprise Linux operating systems using DNS resolution,\nat least two name servers must be configured.","waiver_data":{}},{"code":"control \"V-72283\" do\n title \"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets.\"\n desc \"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not accept IPv4 source-routed packets.\n\n # grep net.ipv4.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv4.conf.all.accept_source_route = 0\n\n If \\\" net.ipv4.conf.all.accept_source_route \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.accept_source_route\n net.ipv4.conf.all.accept_source_route = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl -system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72283\"\n tag rid: \"SV-86907r2_rule\"\n tag stig_id: \"RHEL-07-040610\"\n tag fix_id: \"F-78637r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.accept_source_route') do\n its('value') { should eq 0 }\n end\nend\n","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not accept IPv4 source-routed packets.\n\n # grep net.ipv4.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv4.conf.all.accept_source_route = 0\n\n If \" net.ipv4.conf.all.accept_source_route \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.accept_source_route\n net.ipv4.conf.all.accept_source_route = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl -system","label":"fix"}],"id":"V-72283","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72283.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72283","rid":"SV-86907r2_rule","stig_id":"RHEL-07-040610","fix_id":"F-78637r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets.","waiver_data":{}},{"code":"control \"V-72285\" do\n title \"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets by default.\"\n desc \"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not accept IPv4 source-routed packets by default.\n\n # grep net.ipv4.conf.default.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n net.ipv4.conf.default.accept_source_route = 0\n\n If \\\" net.ipv4.conf.default.accept_source_route \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.accept_source_route\n net.ipv4.conf.default.accept_source_route = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72285\"\n tag rid: \"SV-86909r2_rule\"\n tag stig_id: \"RHEL-07-040620\"\n tag fix_id: \"F-78639r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.accept_source_route') do\n its('value') { should eq 0 }\n end\nend\n","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not accept IPv4 source-routed packets by default.\n\n # grep net.ipv4.conf.default.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n net.ipv4.conf.default.accept_source_route = 0\n\n If \" net.ipv4.conf.default.accept_source_route \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.accept_source_route\n net.ipv4.conf.default.accept_source_route = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72285","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72285.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72285","rid":"SV-86909r2_rule","stig_id":"RHEL-07-040620","fix_id":"F-78639r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets by default.","waiver_data":{}},{"code":"control \"V-72287\" do\n title \"The Red Hat Enterprise Linux operating system must not respond to\nInternet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP)\nechoes sent to a broadcast address.\"\n desc \"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast\naddress.\n\n # grep net.ipv4.icmp_echo_ignore_broadcasts /etc/sysctl.conf /etc/sysctl.d/*\n\n If \\\" net.ipv4.icmp_echo_ignore_broadcasts\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"1\\\", this is a finding.\n\n Check that the operating system implements the\n\\\"icmp_echo_ignore_broadcasts\\\" variable with the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.icmp_echo_ignore_broadcasts\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n If the returned line does not have a value of \\\"1\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72287\"\n tag rid: \"SV-86911r2_rule\"\n tag stig_id: \"RHEL-07-040630\"\n tag fix_id: \"F-78641r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.icmp_echo_ignore_broadcasts') do\n its('value') { should eq 1 }\n end\nend\n","desc":"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.","descriptions":[{"data":"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast\naddress.\n\n # grep net.ipv4.icmp_echo_ignore_broadcasts /etc/sysctl.conf /etc/sysctl.d/*\n\n If \" net.ipv4.icmp_echo_ignore_broadcasts\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the\n\"icmp_echo_ignore_broadcasts\" variable with the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.icmp_echo_ignore_broadcasts\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72287","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72287.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72287","rid":"SV-86911r2_rule","stig_id":"RHEL-07-040630","fix_id":"F-78641r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not respond to\nInternet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP)\nechoes sent to a broadcast address.","waiver_data":{}},{"code":"control \"V-72289\" do\n title \"The Red Hat Enterprise Linux operating system must prevent Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages from being accepted.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system will not accept IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.default.accept_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \\\" net.ipv4.conf.default.accept_redirects \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the value of the\n\\\"accept_redirects\\\" variables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.accept_redirects'\n net.ipv4.conf.default.accept_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to not accept IPv4 ICMP redirect messages by adding the\nfollowing line to \\\"/etc/sysctl.conf\\\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72289\"\n tag rid: \"SV-86913r3_rule\"\n tag stig_id: \"RHEL-07-040640\"\n tag fix_id: \"F-78643r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.accept_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system will not accept IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.default.accept_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \" net.ipv4.conf.default.accept_redirects \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the value of the\n\"accept_redirects\" variables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.accept_redirects'\n net.ipv4.conf.default.accept_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to not accept IPv4 ICMP redirect messages by adding the\nfollowing line to \"/etc/sysctl.conf\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72289","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72289.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72289","rid":"SV-86913r3_rule","stig_id":"RHEL-07-040640","fix_id":"F-78643r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages from being accepted.","waiver_data":{}},{"code":"control \"V-72291\" do\n title \"The Red Hat Enterprise Linux operating system must not allow\ninterfaces to perform Internet Protocol version 4 (IPv4) Internet Control\nMessage Protocol (ICMP) redirects by default.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n # grep 'net.ipv4.conf.default.send_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \\\"net.ipv4.conf.default.send_redirects\\\" is not configured in the\n\\\"/etc/sysctl.conf\\\" file or in the /etc/sysctl.d/ directory, is commented out\nor does not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the \\\"default send_redirects\\\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.send_redirects'\n\n net.ipv4.conf.default.send_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72291\"\n tag rid: \"SV-86915r4_rule\"\n tag stig_id: \"RHEL-07-040650\"\n tag fix_id: \"F-78645r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.send_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n # grep 'net.ipv4.conf.default.send_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \"net.ipv4.conf.default.send_redirects\" is not configured in the\n\"/etc/sysctl.conf\" file or in the /etc/sysctl.d/ directory, is commented out\nor does not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"default send_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.send_redirects'\n\n net.ipv4.conf.default.send_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Configure the system to not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72291","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72291.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72291","rid":"SV-86915r4_rule","stig_id":"RHEL-07-040650","fix_id":"F-78645r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow\ninterfaces to perform Internet Protocol version 4 (IPv4) Internet Control\nMessage Protocol (ICMP) redirects by default.","waiver_data":{}},{"code":"control \"V-72293\" do\n title \"The Red Hat Enterprise Linux operating system must not send Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not send IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.send_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \\\"net.ipv4.conf.all.send_redirects\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the \\\"all send_redirects\\\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.send_redirects'\n\n net.ipv4.conf.all.send_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to not allow interfaces to perform IPv4 ICMP\nredirects.\n\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72293\"\n tag rid: \"SV-86917r3_rule\"\n tag stig_id: \"RHEL-07-040660\"\n tag fix_id: \"F-78647r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.send_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not send IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.send_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \"net.ipv4.conf.all.send_redirects\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"all send_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.send_redirects'\n\n net.ipv4.conf.all.send_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Configure the system to not allow interfaces to perform IPv4 ICMP\nredirects.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72293","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72293.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72293","rid":"SV-86917r3_rule","stig_id":"RHEL-07-040660","fix_id":"F-78647r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not send Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.","waiver_data":{}},{"code":"control \"V-72295\" do\n title \"Network interfaces configured on the Red Hat Enterprise Linux\noperating system must not be in promiscuous mode.\"\n desc \"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify network interfaces are not in promiscuous mode unless approved by\nthe ISSO and documented.\n\n Check for the status with the following command:\n\n # ip link | grep -i promisc\n\n If network interfaces are found on the system in promiscuous mode and their\nuse has not been approved by the ISSO and documented, this is a finding.\n \"\n desc \"fix\", \"\n Configure network interfaces to turn off promiscuous mode unless approved\nby the ISSO and documented.\n\n Set the promiscuous mode of an interface to off with the following command:\n\n #ip link set dev multicast off promisc off\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72295\"\n tag rid: \"SV-86919r2_rule\"\n tag stig_id: \"RHEL-07-040670\"\n tag fix_id: \"F-78649r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe command(\"ip link | grep -i promisc\") do\n its('stdout.strip') { should match %r{^$} }\n end\nend\n","desc":"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.","descriptions":[{"data":"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify network interfaces are not in promiscuous mode unless approved by\nthe ISSO and documented.\n\n Check for the status with the following command:\n\n # ip link | grep -i promisc\n\n If network interfaces are found on the system in promiscuous mode and their\nuse has not been approved by the ISSO and documented, this is a finding.","label":"check"},{"data":"Configure network interfaces to turn off promiscuous mode unless approved\nby the ISSO and documented.\n\n Set the promiscuous mode of an interface to off with the following command:\n\n #ip link set dev multicast off promisc off","label":"fix"}],"id":"V-72295","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72295.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72295","rid":"SV-86919r2_rule","stig_id":"RHEL-07-040670","fix_id":"F-78649r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"Network interfaces configured on the Red Hat Enterprise Linux\noperating system must not be in promiscuous mode.","waiver_data":{}},{"code":"control \"V-72297\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nprevent unrestricted mail relaying.\"\n desc \"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system is configured to prevent unrestricted mail relaying.\n\n Determine if \\\"postfix\\\" is installed with the following commands:\n\n # yum list installed postfix\n postfix-2.6.6-6.el7.x86_64.rpm\n\n If postfix is not installed, this is Not Applicable.\n\n If postfix is installed, determine if it is configured to reject\nconnections from unknown or untrusted networks with the following command:\n\n # postconf -n smtpd_client_restrictions\n smtpd_client_restrictions = permit_mynetworks, reject\n\n If the \\\"smtpd_client_restrictions\\\" parameter contains any entries other\nthan \\\"permit_mynetworks\\\" and \\\"reject\\\", this is a finding.\n \"\n desc \"fix\", \"\n If \\\"postfix\\\" is installed, modify the \\\"/etc/postfix/main.cf\\\" file to\nrestrict client connections to the local network with the following command:\n\n # postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72297\"\n tag rid: \"SV-86921r3_rule\"\n tag stig_id: \"RHEL-07-040680\"\n tag fix_id: \"F-78651r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n # Only permit_mynetworks and reject should be allowed\n describe.one do\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+permit_mynetworks,\\s*reject\\s*$} }\n end\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+permit_mynetworks\\s*$} }\n end\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+reject\\s*$} }\n end\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+reject,\\s*permit_mynetworks\\s*$} }\n end\n end if package('postfix').installed?\n\n describe \"The `postfix` package is not installed\" do\n skip \"The `postfix` package is not installed, this control is Not Applicable\"\n end if !package('postfix').installed?\nend\n","desc":"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.","descriptions":[{"data":"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is configured to prevent unrestricted mail relaying.\n\n Determine if \"postfix\" is installed with the following commands:\n\n # yum list installed postfix\n postfix-2.6.6-6.el7.x86_64.rpm\n\n If postfix is not installed, this is Not Applicable.\n\n If postfix is installed, determine if it is configured to reject\nconnections from unknown or untrusted networks with the following command:\n\n # postconf -n smtpd_client_restrictions\n smtpd_client_restrictions = permit_mynetworks, reject\n\n If the \"smtpd_client_restrictions\" parameter contains any entries other\nthan \"permit_mynetworks\" and \"reject\", this is a finding.","label":"check"},{"data":"If \"postfix\" is installed, modify the \"/etc/postfix/main.cf\" file to\nrestrict client connections to the local network with the following command:\n\n # postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'","label":"fix"}],"id":"V-72297","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72297.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72297","rid":"SV-86921r3_rule","stig_id":"RHEL-07-040680","fix_id":"F-78651r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nprevent unrestricted mail relaying.","waiver_data":{}},{"code":"control \"V-72299\" do\n title \"The Red Hat Enterprise Linux operating system must not have a File\nTransfer Protocol (FTP) server package installed unless needed.\"\n desc \"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify an FTP server has not been installed on the system.\n\n Check to see if an FTP server has been installed with the following\ncommands:\n\n # yum list installed vsftpd\n\n vsftpd-3.0.2.el7.x86_64.rpm\n\n If \\\"vsftpd\\\" is installed and is not documented with the Information\nSystem Security Officer (ISSO) as an operational requirement, this is a finding.\n \"\n desc \"fix\", \"\n Document the \\\"vsftpd\\\" package with the ISSO as an operational requirement\nor remove it from the system with the following command:\n\n # yum remove vsftpd\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72299\"\n tag rid: \"SV-86923r3_rule\"\n tag stig_id: \"RHEL-07-040690\"\n tag fix_id: \"F-78653r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe package('vsftpd') do\n it { should_not be_installed }\n end\n describe parse_config_file('/etc/vsftpd/vsftpd.conf') do\n its('ssl_enable') { should cmp 'YES' }\n its('force_anon_data_ssl') { should cmp 'YES' }\n its('force_anon_logins_ssl') { should cmp 'YES' }\n its('force_local_data_ssl') { should cmp 'YES' }\n its('force_local_logins_ssl') { should cmp 'YES' }\n end\n end\nend\n","desc":"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.","descriptions":[{"data":"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify an FTP server has not been installed on the system.\n\n Check to see if an FTP server has been installed with the following\ncommands:\n\n # yum list installed vsftpd\n\n vsftpd-3.0.2.el7.x86_64.rpm\n\n If \"vsftpd\" is installed and is not documented with the Information\nSystem Security Officer (ISSO) as an operational requirement, this is a finding.","label":"check"},{"data":"Document the \"vsftpd\" package with the ISSO as an operational requirement\nor remove it from the system with the following command:\n\n # yum remove vsftpd","label":"fix"}],"id":"V-72299","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72299.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72299","rid":"SV-86923r3_rule","stig_id":"RHEL-07-040690","fix_id":"F-78653r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have a File\nTransfer Protocol (FTP) server package installed unless needed.","waiver_data":{}},{"code":"control \"V-72301\" do\n title \"The Red Hat Enterprise Linux operating system must not have the\nTrivial File Transfer Protocol (TFTP) server package installed if not required\nfor operational support.\"\n desc \"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify a TFTP server has not been installed on the system.\n\n Check to see if a TFTP server has been installed with the following command:\n\n # yum list installed tftp-server\n tftp-server-0.49-9.el7.x86_64.rpm\n\n If TFTP is installed and the requirement for TFTP is not documented with\nthe ISSO, this is a finding.\n \"\n desc \"fix\", \"\n Remove the TFTP package from the system with the following command:\n\n # yum remove tftp-server\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72301\"\n tag rid: \"SV-86925r2_rule\"\n tag stig_id: \"RHEL-07-040700\"\n tag fix_id: \"F-78655r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n describe package('tftp-server') do\n it { should_not be_installed }\n end\nend\n","desc":"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.","descriptions":[{"data":"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify a TFTP server has not been installed on the system.\n\n Check to see if a TFTP server has been installed with the following command:\n\n # yum list installed tftp-server\n tftp-server-0.49-9.el7.x86_64.rpm\n\n If TFTP is installed and the requirement for TFTP is not documented with\nthe ISSO, this is a finding.","label":"check"},{"data":"Remove the TFTP package from the system with the following command:\n\n# yum remove tftp-server","label":"fix"}],"id":"V-72301","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72301.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72301","rid":"SV-86925r2_rule","stig_id":"RHEL-07-040700","fix_id":"F-78655r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must not have the\nTrivial File Transfer Protocol (TFTP) server package installed if not required\nfor operational support.","waiver_data":{}},{"code":"control \"V-72303\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat remote X connections for interactive users are encrypted.\"\n desc \"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify remote X connections for interactive users are encrypted.\n\n Check that remote X connections are encrypted with the following command:\n\n # grep -i x11forwarding /etc/ssh/sshd_config | grep -v \\\"^#\\\"\n\n X11Forwarding yes\n\n If the \\\"X11Forwarding\\\" keyword is set to \\\"no\\\" or is missing, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure SSH to encrypt connections for interactive users.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for the\n\\\"X11Forwarding\\\" keyword and set its value to \\\"yes\\\" (this file may be named\ndifferently or be in a different location if using a version of SSH that is\nprovided by a third-party vendor):\n\n X11Forwarding yes\n\n The SSH service must be restarted for changes to take effect:\n\n # systemctl restart sshd\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72303\"\n tag rid: \"SV-86927r4_rule\"\n tag stig_id: \"RHEL-07-040710\"\n tag fix_id: \"F-78657r6_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('X11Forwarding') { should cmp 'yes' }\n end\nend\n","desc":"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.","descriptions":[{"data":"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify remote X connections for interactive users are encrypted.\n\n Check that remote X connections are encrypted with the following command:\n\n # grep -i x11forwarding /etc/ssh/sshd_config | grep -v \"^#\"\n\n X11Forwarding yes\n\n If the \"X11Forwarding\" keyword is set to \"no\" or is missing, this is a\nfinding.","label":"check"},{"data":"Configure SSH to encrypt connections for interactive users.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the\n\"X11Forwarding\" keyword and set its value to \"yes\" (this file may be named\ndifferently or be in a different location if using a version of SSH that is\nprovided by a third-party vendor):\n\n X11Forwarding yes\n\n The SSH service must be restarted for changes to take effect:\n\n # systemctl restart sshd","label":"fix"}],"id":"V-72303","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72303.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72303","rid":"SV-86927r4_rule","stig_id":"RHEL-07-040710","fix_id":"F-78657r6_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat remote X connections for interactive users are encrypted.","waiver_data":{}},{"code":"control \"V-72305\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP\ndaemon is configured to operate in secure mode.\"\n desc \"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the TFTP daemon is configured to operate in secure mode.\n\n Check to see if a TFTP server has been installed with the following\ncommands:\n\n # yum list installed tftp-server\n tftp-server.x86_64 x.x-x.el7 rhel-7-server-rpms\n\n If a TFTP server is not installed, this is Not Applicable.\n\n If a TFTP server is installed, check for the server arguments with the\nfollowing command:\n\n # grep server_args /etc/xinetd.d/tftp\n server_args = -s /var/lib/tftpboot\n\n If the \\\"server_args\\\" line does not have a \\\"-s\\\" option and a\nsubdirectory is not assigned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the TFTP daemon to operate in secure mode by adding the following\nline to \\\"/etc/xinetd.d/tftp\\\" (or modify the line to have the required value):\n\n server_args = -s /var/lib/tftpboot\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72305\"\n tag rid: \"SV-86929r3_rule\"\n tag stig_id: \"RHEL-07-040720\"\n tag fix_id: \"F-78659r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if package('tftp-server').installed?\n impact 0.5\n describe command('grep server_args /etc/xinetd.d/tftp') do\n its('stdout.strip') { should match %r{^\\s*server_args\\s+=\\s+(-s|--secure)\\s(\\/\\S+)$} }\n end\n else\n impact 0.0\n describe \"The TFTP package is not installed\" do\n skip \"If a TFTP server is not installed, this is Not Applicable.\"\n end\n end\nend\n","desc":"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.","descriptions":[{"data":"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the TFTP daemon is configured to operate in secure mode.\n\n Check to see if a TFTP server has been installed with the following\ncommands:\n\n # yum list installed tftp-server\n tftp-server.x86_64 x.x-x.el7 rhel-7-server-rpms\n\n If a TFTP server is not installed, this is Not Applicable.\n\n If a TFTP server is installed, check for the server arguments with the\nfollowing command:\n\n # grep server_args /etc/xinetd.d/tftp\n server_args = -s /var/lib/tftpboot\n\n If the \"server_args\" line does not have a \"-s\" option and a\nsubdirectory is not assigned, this is a finding.","label":"check"},{"data":"Configure the TFTP daemon to operate in secure mode by adding the following\nline to \"/etc/xinetd.d/tftp\" (or modify the line to have the required value):\n\n server_args = -s /var/lib/tftpboot","label":"fix"}],"id":"V-72305","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72305.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72305","rid":"SV-86929r3_rule","stig_id":"RHEL-07-040720","fix_id":"F-78659r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP\ndaemon is configured to operate in secure mode.","waiver_data":{}},{"code":"control \"V-72307\" do\n title \"The Red Hat Enterprise Linux operating system must not have an X\nWindows display manager installed unless approved.\"\n desc \"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that if the system has X Windows System installed, it is authorized.\n\n Check for the X11 package with the following command:\n\n # rpm -qa | grep xorg | grep server\n\n Ask the System Administrator if use of the X Windows System is an\noperational requirement.\n\n If the use of X Windows on the system is not documented with the\nInformation System Security Officer (ISSO), this is a finding.\n \"\n desc \"fix\", \"\n Document the requirement for an X Windows server with the ISSO or remove\nthe related packages with the following commands:\n\n # rpm -e xorg-x11-server-common\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72307\"\n tag rid: \"SV-86931r4_rule\"\n tag stig_id: \"RHEL-07-040730\"\n tag fix_id: \"F-78661r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n x11_enabled = input('x11_enabled')\n\n describe package('xorg-x11-server-common') do\n it { should_not be_installed }\n end if !x11_enabled\n\n describe package('xorg-x11-server-common') do\n it { should be_installed }\n end if x11_enabled\nend\n","desc":"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.","descriptions":[{"data":"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that if the system has X Windows System installed, it is authorized.\n\n Check for the X11 package with the following command:\n\n # rpm -qa | grep xorg | grep server\n\n Ask the System Administrator if use of the X Windows System is an\noperational requirement.\n\n If the use of X Windows on the system is not documented with the\nInformation System Security Officer (ISSO), this is a finding.","label":"check"},{"data":"Document the requirement for an X Windows server with the ISSO or remove\nthe related packages with the following commands:\n\n # rpm -e xorg-x11-server-common","label":"fix"}],"id":"V-72307","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72307.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72307","rid":"SV-86931r4_rule","stig_id":"RHEL-07-040730","fix_id":"F-78661r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have an X\nWindows display manager installed unless approved.","waiver_data":{}},{"code":"control \"V-72309\" do\n title \"The Red Hat Enterprise Linux operating system must not be performing\npacket forwarding unless the system is a router.\"\n desc \"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system is not performing packet forwarding, unless the system is\na router.\n\n # grep net.ipv4.ip_forward /etc/sysctl.conf /etc/sysctl.d/*\n\n net.ipv4.ip_forward = 0\n\n If \\\"net.ipv4.ip_forward\\\" is not configured in the /etc/sysctl.conf file\nor in the /etc/sysctl.d/ directory, is commented out, or does not have a value\nof \\\"0\\\", this is a finding.\n\n Check that the operating system does not implement IP forwarding using the\nfollowing command:\n\n # /sbin/sysctl -a | grep net.ipv4.ip_forward\n net.ipv4.ip_forward = 0\n\n If IP forwarding value is \\\"1\\\" and the system is hosting any application,\ndatabase, or web servers, this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.ip_forward = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72309\"\n tag rid: \"SV-86933r2_rule\"\n tag stig_id: \"RHEL-07-040740\"\n tag fix_id: \"F-78663r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.ip_forward') do\n its('value') { should eq 0 }\n end\nend\n","desc":"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.","descriptions":[{"data":"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is not performing packet forwarding, unless the system is\na router.\n\n # grep net.ipv4.ip_forward /etc/sysctl.conf /etc/sysctl.d/*\n\n net.ipv4.ip_forward = 0\n\n If \"net.ipv4.ip_forward\" is not configured in the /etc/sysctl.conf file\nor in the /etc/sysctl.d/ directory, is commented out, or does not have a value\nof \"0\", this is a finding.\n\n Check that the operating system does not implement IP forwarding using the\nfollowing command:\n\n # /sbin/sysctl -a | grep net.ipv4.ip_forward\n net.ipv4.ip_forward = 0\n\n If IP forwarding value is \"1\" and the system is hosting any application,\ndatabase, or web servers, this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.ip_forward = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72309","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72309.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72309","rid":"SV-86933r2_rule","stig_id":"RHEL-07-040740","fix_id":"F-78663r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not be performing\npacket forwarding unless the system is a router.","waiver_data":{}},{"code":"control \"V-72311\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the Network File System (NFS) is configured to use RPCSEC_GSS.\"\n desc \"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify \\\"AUTH_GSS\\\" is being used to authenticate NFS mounts.\n\n To check if the system is importing an NFS file system, look for any\nentries in the \\\"/etc/fstab\\\" file that have a file system type of \\\"nfs\\\" with\nthe following command:\n\n # cat /etc/fstab | grep nfs\n 192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=krb5:krb5i:krb5p\n\n If the system is mounting file systems via NFS and has the sec option\nwithout the \\\"krb5:krb5i:krb5p\\\" settings, the \\\"sec\\\" option has the \\\"sys\\\"\nsetting, or the \\\"sec\\\" option is missing, this is a finding.\n \"\n desc \"fix\", \"\n Update the \\\"/etc/fstab\\\" file so the option \\\"sec\\\" is defined for each\nNFS mounted file system and the \\\"sec\\\" option does not have the \\\"sys\\\"\nsetting.\n\n Ensure the \\\"sec\\\" option is defined as \\\"krb5:krb5i:krb5p\\\".\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72311\"\n tag rid: \"SV-86935r4_rule\"\n tag stig_id: \"RHEL-07-040750\"\n tag fix_id: \"F-78665r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n nfs_systems = etc_fstab.nfs_file_systems.entries\n if !nfs_systems.nil? and !nfs_systems.empty?\n nfs_systems.each do |file_system|\n describe file_system do\n its ('mount_options') { should include 'sec=krb5:krb5i:krb5p' }\n end\n end\n else\n describe \"No NFS file systems were found.\" do\n subject { nfs_systems.nil? or nfs_systems.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.","descriptions":[{"data":"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify \"AUTH_GSS\" is being used to authenticate NFS mounts.\n\n To check if the system is importing an NFS file system, look for any\nentries in the \"/etc/fstab\" file that have a file system type of \"nfs\" with\nthe following command:\n\n # cat /etc/fstab | grep nfs\n 192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=krb5:krb5i:krb5p\n\n If the system is mounting file systems via NFS and has the sec option\nwithout the \"krb5:krb5i:krb5p\" settings, the \"sec\" option has the \"sys\"\nsetting, or the \"sec\" option is missing, this is a finding.","label":"check"},{"data":"Update the \"/etc/fstab\" file so the option \"sec\" is defined for each\nNFS mounted file system and the \"sec\" option does not have the \"sys\"\nsetting.\n\n Ensure the \"sec\" option is defined as \"krb5:krb5i:krb5p\".","label":"fix"}],"id":"V-72311","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72311.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72311","rid":"SV-86935r4_rule","stig_id":"RHEL-07-040750","fix_id":"F-78665r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the Network File System (NFS) is configured to use RPCSEC_GSS.","waiver_data":{}},{"code":"control \"V-72313\" do\n title \"SNMP community strings on the Red Hat Enterprise Linux operating\nsystem must be changed from the default.\"\n desc \"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a system using SNMP is not using default community strings.\n\n Check to see if the \\\"/etc/snmp/snmpd.conf\\\" file exists with the following\ncommand:\n\n # ls -al /etc/snmp/snmpd.conf\n -rw------- 1 root root 52640 Mar 12 11:08 snmpd.conf\n\n If the file does not exist, this is Not Applicable.\n\n If the file does exist, check for the default community strings with the\nfollowing commands:\n\n # grep public /etc/snmp/snmpd.conf\n # grep private /etc/snmp/snmpd.conf\n\n If either of these commands returns any output, this is a finding.\n \"\n desc \"fix\", \"If the \\\"/etc/snmp/snmpd.conf\\\" file exists, modify any lines\nthat contain a community string value of \\\"public\\\" or \\\"private\\\" to another\nstring value.\"\n\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72313\"\n tag rid: \"SV-86937r2_rule\"\n tag stig_id: \"RHEL-07-040800\"\n tag fix_id: \"F-78667r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if file('/etc/snmp/snmpd.conf').exist?\n impact 0.7\n processed = []\n to_process = ['/etc/snmp/snmpd.conf']\n\n while !to_process.empty?\n in_process = to_process.pop\n next if processed.include? in_process\n processed.push in_process\n\n if file(in_process).directory?\n to_process.concat(\n command(\"find #{in_process} -maxdepth 1 -mindepth 1 -name '*.conf'\").\n stdout.strip.split(\"\\n\").\n select { |f| file(f).file? }\n )\n elsif file(in_process).file?\n to_process.concat(\n command(\"grep -E '^\\\\s*includeFile\\\\s+' #{in_process} | sed 's/^[[:space:]]*includeFile[[:space:]]*//g'\").\n stdout.strip.split(%r{\\n+}).\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n select { |f| file(f).file? }\n )\n to_process.concat(\n command(\"grep -E '^\\\\s*includeDir\\\\s+' #{in_process} | sed 's/^[[:space:]]*includeDir[[:space:]]*//g'\").\n stdout.strip.split(%r{\\n+}).\n map { |f| f.start_with?('/') ? f : File.join('/', f) }. # relative dirs are treated as absolute\n select { |f| file(f).directory? }\n )\n end\n end\n\n config_files = processed.select { |f| file(f).file? }\n\n config_files.each do |config|\n describe file(config) do\n its('content') { should_not match %r{^[^#]*(public|private)} }\n end\n end\n else\n impact 0.0\n describe \"The `snmpd.conf` does not exist\" do\n skip \"The snmpd.conf file does not exist, this control is Not Applicable\"\n end\n end\nend\n","desc":"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.","descriptions":[{"data":"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a system using SNMP is not using default community strings.\n\n Check to see if the \"/etc/snmp/snmpd.conf\" file exists with the following\ncommand:\n\n # ls -al /etc/snmp/snmpd.conf\n -rw------- 1 root root 52640 Mar 12 11:08 snmpd.conf\n\n If the file does not exist, this is Not Applicable.\n\n If the file does exist, check for the default community strings with the\nfollowing commands:\n\n # grep public /etc/snmp/snmpd.conf\n # grep private /etc/snmp/snmpd.conf\n\n If either of these commands returns any output, this is a finding.","label":"check"},{"data":"If the \"/etc/snmp/snmpd.conf\" file exists, modify any lines\nthat contain a community string value of \"public\" or \"private\" to another\nstring value.","label":"fix"}],"id":"V-72313","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72313.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72313","rid":"SV-86937r2_rule","stig_id":"RHEL-07-040800","fix_id":"F-78667r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"SNMP community strings on the Red Hat Enterprise Linux operating\nsystem must be changed from the default.","waiver_data":{}},{"code":"control \"V-72315\" do\n title \"The Red Hat Enterprise Linux operating system access control program\nmust be configured to grant or deny system access to specific hosts and\nservices.\"\n desc \"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If the \\\"firewalld\\\" package is not installed, ask the System Administrator\n(SA) if another firewall application (such as iptables) is installed. If an\napplication firewall is not installed, this is a finding.\n\n Verify the system's access control program is configured to grant or deny\nsystem access to specific hosts.\n\n Check to see if \\\"firewalld\\\" is active with the following command:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago\n\n If \\\"firewalld\\\" is active, check to see if it is configured to grant or\ndeny access to specific hosts or services with the following commands:\n\n # firewall-cmd --get-default-zone\n public\n\n # firewall-cmd --list-all --zone=public\n public (active)\n target: default\n icmp-block-inversion: no\n interfaces: eth0\n sources:\n services: mdns ssh\n ports:\n protocols:\n masquerade: no\n forward-ports:\n icmp-blocks:\n\n If \\\"firewalld\\\" is not active, determine whether \\\"tcpwrappers\\\" is being\nused by checking whether the \\\"hosts.allow\\\" and \\\"hosts.deny\\\" files are empty\nwith the following commands:\n\n # ls -al /etc/hosts.allow\n rw-r----- 1 root root 9 Aug 2 23:13 /etc/hosts.allow\n\n # ls -al /etc/hosts.deny\n -rw-r----- 1 root root 9 Apr 9 2007 /etc/hosts.deny\n\n If \\\"firewalld\\\" and \\\"tcpwrappers\\\" are not installed, configured, and\nactive, ask the SA if another access control program (such as iptables) is\ninstalled and active. Ask the SA to show that the running configuration grants\nor denies access to specific hosts or services.\n\n If \\\"firewalld\\\" is active and is not configured to grant access to\nspecific hosts or \\\"tcpwrappers\\\" is not configured to grant or deny access to\nspecific hosts, this is a finding.\n \"\n desc \"fix\", \"\n If \\\"firewalld\\\" is installed and active on the system, configure rules for\nallowing specific services and hosts.\n\n If \\\"firewalld\\\" is not \\\"active\\\", enable \\\"tcpwrappers\\\" by configuring\n\\\"/etc/hosts.allow\\\" and \\\"/etc/hosts.deny\\\" to allow or deny access to\nspecific hosts.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72315\"\n tag rid: \"SV-86939r3_rule\"\n tag stig_id: \"RHEL-07-040810\"\n tag fix_id: \"F-78669r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n firewalld_services = input('firewalld_services')\n firewalld_hosts_allow = input('firewalld_hosts_allow')\n firewalld_hosts_deny = input('firewalld_hosts_deny')\n firewalld_ports_allow = input('firewalld_ports_allow')\n firewalld_ports_deny = input('firewalld_ports_deny')\n tcpwrappers_allow = input('tcpwrappers_allow')\n tcpwrappers_deny = input('tcpwrappers_deny')\n iptable_rules = input('iptables_rules')\n\n if service('firewalld').running?\n @default_zone = firewalld.default_zone\n\n describe firewalld.where{ zone = @default_zone } do\n its('services') { should be_in firewalld_services }\n end\n\n describe firewalld do\n firewalld_hosts_allow.each do |rule|\n it { should have_rule_enabled(rule) }\n end\n firewalld_hosts_deny.each do |rule|\n it { should_not have_rule_enabled(rule) }\n end\n firewalld_ports_allow.each do |port|\n it { should have_port_enabled_in_zone(port) }\n end\n firewalld_ports_deny.each do |port|\n it { should_not have_port_enabled_in_zone(port) }\n end\n end\n elsif service('iptables').running?\n describe iptables do\n iptable_rules.each do |rule|\n it { should have_rule(rule) }\n end\n end\n else\n describe package('tcp_wrappers') do\n it { should be_installed }\n end\n tcpwrappers_allow.each do |rule|\n describe etc_hosts_allow.where { daemon == rule['daemon'] } do\n its('client_list') { should be rule['client_list'] }\n its('options') { should be rule['options'] }\n end\n end\n tcpwrappers_deny.each do |rule|\n describe etc_hosts_deny.where { daemon == rule['daemon'] } do\n its('client_list') { should be rule['client_list'] }\n its('options') { should be rule['options'] }\n end\n end\n end\nend\n","desc":"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.","descriptions":[{"data":"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.","label":"default"},{"data":"","label":"rationale"},{"data":"If the \"firewalld\" package is not installed, ask the System Administrator\n(SA) if another firewall application (such as iptables) is installed. If an\napplication firewall is not installed, this is a finding.\n\n Verify the system's access control program is configured to grant or deny\nsystem access to specific hosts.\n\n Check to see if \"firewalld\" is active with the following command:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago\n\n If \"firewalld\" is active, check to see if it is configured to grant or\ndeny access to specific hosts or services with the following commands:\n\n # firewall-cmd --get-default-zone\n public\n\n # firewall-cmd --list-all --zone=public\n public (active)\n target: default\n icmp-block-inversion: no\n interfaces: eth0\n sources:\n services: mdns ssh\n ports:\n protocols:\n masquerade: no\n forward-ports:\n icmp-blocks:\n\n If \"firewalld\" is not active, determine whether \"tcpwrappers\" is being\nused by checking whether the \"hosts.allow\" and \"hosts.deny\" files are empty\nwith the following commands:\n\n # ls -al /etc/hosts.allow\n rw-r----- 1 root root 9 Aug 2 23:13 /etc/hosts.allow\n\n # ls -al /etc/hosts.deny\n -rw-r----- 1 root root 9 Apr 9 2007 /etc/hosts.deny\n\n If \"firewalld\" and \"tcpwrappers\" are not installed, configured, and\nactive, ask the SA if another access control program (such as iptables) is\ninstalled and active. Ask the SA to show that the running configuration grants\nor denies access to specific hosts or services.\n\n If \"firewalld\" is active and is not configured to grant access to\nspecific hosts or \"tcpwrappers\" is not configured to grant or deny access to\nspecific hosts, this is a finding.","label":"check"},{"data":"If \"firewalld\" is installed and active on the system, configure rules for\nallowing specific services and hosts.\n\n If \"firewalld\" is not \"active\", enable \"tcpwrappers\" by configuring\n\"/etc/hosts.allow\" and \"/etc/hosts.deny\" to allow or deny access to\nspecific hosts.","label":"fix"}],"id":"V-72315","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72315.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72315","rid":"SV-86939r3_rule","stig_id":"RHEL-07-040810","fix_id":"F-78669r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system access control program\nmust be configured to grant or deny system access to specific hosts and\nservices.","waiver_data":{}},{"code":"control \"V-72317\" do\n title \"The Red Hat Enterprise Linux operating system must not have\nunauthorized IP tunnels configured.\"\n desc \"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not have unauthorized IP tunnels configured.\n\n Check to see if \\\"libreswan\\\" is installed with the following command:\n\n # yum list installed libreswan\n libreswan.x86-64 3.20-5.el7_4\n\n If \\\"libreswan\\\" is installed, check to see if the \\\"IPsec\\\" service is\nactive with the following command:\n\n # systemctl status ipsec\n ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec\n Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)\n Active: inactive (dead)\n\n If the \\\"IPsec\\\" service is active, check to see if any tunnels are\nconfigured in \\\"/etc/ipsec.conf\\\" and \\\"/etc/ipsec.d/\\\" with the following\ncommands:\n\n # grep -iw conn /etc/ipsec.conf /etc/ipsec.d/*.conf\n\n If there are indications that a \\\"conn\\\" parameter is configured for a\ntunnel, ask the System Administrator if the tunnel is documented with the ISSO.\n\n If \\\"libreswan\\\" is installed, \\\"IPsec\\\" is active, and an undocumented\ntunnel is active, this is a finding.\n \"\n desc \"fix\", \"Remove all unapproved tunnels from the system, or document them\nwith the ISSO.\"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72317\"\n tag rid: \"SV-86941r2_rule\"\n tag stig_id: \"RHEL-07-040820\"\n tag fix_id: \"F-78671r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n approved_tunnels = input('approved_tunnels')\n\n if package('libreswan').installed? && service('ipsec.service').running?\n impact 0.5\n processed = []\n to_process = ['/etc/ipsec.conf']\n\n while !to_process.empty?\n in_process = to_process.pop\n next if processed.include? in_process\n processed.push in_process\n\n to_process.concat(\n command(\"grep -E '^\\\\s*include\\\\s+' #{in_process} | sed 's/^[[:space:]]*include[[:space:]]*//g'\").\n stdout.strip.split(%r{\\s*\\n+\\s*}).\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n map { |f|\n dir = f.sub(%r{[^/]*[\\*\\?\\[].*$}, '') # gets the longest ancestor path which doesn't contain wildcards\n command(\"find #{dir} -wholename '#{f}'\").stdout.strip.split(\"\\n\")\n }.\n flatten.\n select { |f| file(f).file? }\n )\n end\n\n conn_grep = processed.map do |conf|\n command(\"grep -E '^\\\\s*conn\\\\s+' #{conf}\").\n stdout.strip.split(%r{\\s*\\n\\s*})\n end.flatten\n\n describe conn_grep do\n it { should all(be_in approved_tunnels) }\n end\n else\n impact 0.0\n describe \"The system does not have libreswan installed or the ipsec.service isn't running\" do\n skip \"The system does not have libreswan installed or the ipsec.service isn't running, this requirement is Not Applicable.\"\n end\n end\nend\n","desc":"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).","descriptions":[{"data":"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not have unauthorized IP tunnels configured.\n\n Check to see if \"libreswan\" is installed with the following command:\n\n # yum list installed libreswan\n libreswan.x86-64 3.20-5.el7_4\n\n If \"libreswan\" is installed, check to see if the \"IPsec\" service is\nactive with the following command:\n\n # systemctl status ipsec\n ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec\n Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)\n Active: inactive (dead)\n\n If the \"IPsec\" service is active, check to see if any tunnels are\nconfigured in \"/etc/ipsec.conf\" and \"/etc/ipsec.d/\" with the following\ncommands:\n\n # grep -iw conn /etc/ipsec.conf /etc/ipsec.d/*.conf\n\n If there are indications that a \"conn\" parameter is configured for a\ntunnel, ask the System Administrator if the tunnel is documented with the ISSO.\n\n If \"libreswan\" is installed, \"IPsec\" is active, and an undocumented\ntunnel is active, this is a finding.","label":"check"},{"data":"Remove all unapproved tunnels from the system, or document them\nwith the ISSO.","label":"fix"}],"id":"V-72317","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72317.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72317","rid":"SV-86941r2_rule","stig_id":"RHEL-07-040820","fix_id":"F-78671r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have\nunauthorized IP tunnels configured.","waiver_data":{}},{"code":"control \"V-72319\" do\n title \"The Red Hat Enterprise Linux operating system must not forward IPv6\nsource-routed packets.\"\n desc \"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If IPv6 is not enabled, the key will not exist, and this is Not Applicable.\n\n Verify the system does not accept IPv6 source-routed packets.\n\n # grep net.ipv6.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv6.conf.all.accept_source_route = 0\n\n If \\\"net.ipv6.conf.all.accept_source_route\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv6.conf.all.accept_source_route\n net.ipv6.conf.all.accept_source_route = 0\n\n If the returned lines do not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter, if IPv6 is enabled, by\nadding the following line to \\\"/etc/sysctl.conf\\\" or a configuration file in\nthe /etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv6.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72319\"\n tag rid: \"SV-86943r2_rule\"\n tag stig_id: \"RHEL-07-040830\"\n tag fix_id: \"F-78673r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe kernel_parameter('net.ipv6.conf.all.accept_source_route') do\n its('value') { should eq 0 }\n end\n\t# If IPv6 is disabled in the kernel it will return NIL\n describe kernel_parameter('net.ipv6.conf.all.accept_source_route') do\n its('value') { should eq nil }\n end\n end\nend\n","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"If IPv6 is not enabled, the key will not exist, and this is Not Applicable.\n\n Verify the system does not accept IPv6 source-routed packets.\n\n # grep net.ipv6.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv6.conf.all.accept_source_route = 0\n\n If \"net.ipv6.conf.all.accept_source_route\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv6.conf.all.accept_source_route\n net.ipv6.conf.all.accept_source_route = 0\n\n If the returned lines do not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter, if IPv6 is enabled, by\nadding the following line to \"/etc/sysctl.conf\" or a configuration file in\nthe /etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv6.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72319","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72319.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72319","rid":"SV-86943r2_rule","stig_id":"RHEL-07-040830","fix_id":"F-78673r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward IPv6\nsource-routed packets.","waiver_data":{}},{"code":"control \"V-72417\" do\n title \"The Red Hat Enterprise Linux operating system must have the required\n packages for multifactor authentication installed.\"\n\n desc \"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).\"\n\n desc \"check\", \"\n Verify the operating system has the packages required for multifactor\n authentication installed.\n\n Check for the presence of the packages required to support multifactor\n authentication with the following commands:\n\n # yum list installed esc\n esc-1.1.0-26.el7.noarch.rpm\n\n # yum list installed pam_pkcs11\n pam_pkcs11-0.6.2-14.el7.noarch.rpm\n\n If the \\\"esc\\\" and \\\"pam_pkcs11\\\" packages are not installed, this is a\n finding.\"\n\n desc \"fix\", \"\n Configure the operating system to implement multifactor authentication by\n installing the required packages.\n\n Install the \\\"esc\\\" and \\\"pam_pkcs11\\\" packages on the system with the\n following command:\n\n # yum install esc pam_pkcs11\"\n\n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00160\", \"SRG-OS-000375-GPOS-00161\", \"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-72417\"\n tag rid: \"SV-87041r4_rule\"\n tag stig_id: \"RHEL-07-041001\"\n tag fix_id: \"F-78769r4_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n mfa_pkg_list = input('mfa_pkg_list')\n smart_card_status = input('smart_card_status')\n\n if smart_card_status.eql?('disabled')\n impact 0.0\n describe \"The system is not smartcard enabled thus this control is Not Applicable\" do\n skip \"The system is not using Smartcards / PIVs to fulfil the MFA requirement, this control is Not Applicable.\"\n end \n elsif mfa_pkg_list.empty?\n describe \"The required Smartcard packages have not beed defined, plese define them in your `inputs`.\" do\n subject { mfa_pkg_list }\n it { should_not be_empty }\n end\n else\n mfa_pkg_list.each do |pkg|\n describe \"The package\" do\n subject { package(\"#{pkg}\") }\n it { should be_installed }\n end\n end\n end\nend\n","desc":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","label":"default"},{"data":"Verify the operating system has the packages required for multifactor\nauthentication installed.\n\nCheck for the presence of the packages required to support multifactor\nauthentication with the following commands:\n\n# yum list installed esc\nesc-1.1.0-26.el7.noarch.rpm\n\n# yum list installed pam_pkcs11\npam_pkcs11-0.6.2-14.el7.noarch.rpm\n\nIf the \"esc\" and \"pam_pkcs11\" packages are not installed, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to implement multifactor authentication by\ninstalling the required packages.\n\nInstall the \"esc\" and \"pam_pkcs11\" packages on the system with the\nfollowing command:\n\n# yum install esc pam_pkcs11","label":"fix"}],"id":"V-72417","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72417.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72417","rid":"SV-87041r4_rule","stig_id":"RHEL-07-041001","fix_id":"F-78769r4_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must have the required\n packages for multifactor authentication installed.","waiver_data":{}},{"code":"control \"V-72427\" do\n title \"The Red Hat Enterprise Linux operating system must implement\n multifactor authentication for access to privileged accounts via pluggable\n authentication modules (PAM).\"\n desc \"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system implements multifactor authentication for\n remote access to privileged accounts via pluggable authentication modules (PAM).\n\n Check the \\\"/etc/sssd/sssd.conf\\\" file for the authentication services that\n are being used with the following command:\n\n # grep services /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf\n\n services = nss, pam\n\n If the \\\"pam\\\" service is not present on all \\\"services\\\" lines, this is a\n finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement multifactor authentication for\n remote access to privileged accounts via pluggable authentication modules (PAM).\n\n Modify all of the services lines in \\\"/etc/sssd/sssd.conf\\\" or in\n configuration files found under \\\"/etc/sssd/conf.d\\\" to include pam.\"\n\n impact 0.5 \n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00160\", \"SRG-OS-000375-GPOS-00161\",\n\"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-72427\"\n tag rid: \"SV-87051r4_rule\"\n tag stig_id: \"RHEL-07-041002\"\n tag fix_id: \"F-78779r3_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n unless package('sssd').installed?\n impact 0.0\n describe \"The SSSD Package is not installed on the system\" do\n skip \"This control is Not Appliciable without the SSSD Package installed.\"\n end\n else\n if (!(sssd_files = command(\"find /etc/sssd -name *.conf\").stdout.split(\"\\n\")).empty?)\n sssd_files.each do |file|\n describe.one do\n describe parse_config_file(file) do\n its('services') { should include 'pam' }\n end if package('sssd').installed?\n describe command(\"grep -i -E 'services(\\s)*=(\\s)*(.+*)pam' #{file}\") do\n its('stdout.strip') { should include 'pam' }\n end if package('sssd').installed?\n end if package('sssd').installed?\n end\n else\n describe \"The set of SSSD configuration files\" do\n subject { sssd_files.to_a }\n it { should_not be_empty }\n end\n end\n end\nend\n","desc":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements multifactor authentication for\nremote access to privileged accounts via pluggable authentication modules (PAM).\n\n Check the \"/etc/sssd/sssd.conf\" file for the authentication services that\nare being used with the following command:\n\n # grep services /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf\n\n services = nss, pam\n\n If the \"pam\" service is not present on all \"services\" lines, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to implement multifactor authentication for\nremote access to privileged accounts via pluggable authentication modules (PAM).\n\n Modify all of the services lines in \"/etc/sssd/sssd.conf\" or in\nconfiguration files found under \"/etc/sssd/conf.d\" to include pam.","label":"fix"}],"id":"V-72427","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72427.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72427","rid":"SV-87051r4_rule","stig_id":"RHEL-07-041002","fix_id":"F-78779r3_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must implement\n multifactor authentication for access to privileged accounts via pluggable\n authentication modules (PAM).","waiver_data":{}},{"code":"control 'V-72433' do\n title \"The Red Hat Enterprise Linux operating system must implement\ncertificate status checking for PKI authentication.\"\n desc \"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).\n\n\n \"\n desc 'rationale', ''\n desc 'check', \"\n Verify the operating system implements certificate status checking for PKI\nauthentication.\n\n Check to see if Online Certificate Status Protocol (OCSP) is enabled on the\nsystem with the following command:\n\n # grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -v \\\"^#\\\"\n\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n\n There should be at least three lines returned.\n\n If \\\"ocsp_on\\\" is not present in all uncommented \\\"cert_policy\\\" lines in\n\\\"/etc/pam_pkcs11/pam_pkcs11.conf\\\", this is a finding.\n \"\n desc 'fix', \"\n Configure the operating system to do certificate status checking for PKI\nauthentication.\n\n Modify all of the \\\"cert_policy\\\" lines in\n\\\"/etc/pam_pkcs11/pam_pkcs11.conf\\\" to include \\\"ocsp_on\\\".\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00160\", \"SRG-OS-000375-GPOS-00161\",\n\"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-72433\"\n tag rid: \"SV-87057r5_rule\"\n tag stig_id: \"RHEL-07-041003\"\n tag fix_id: \"F-78785r3_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n smart_card_status = input('smart_card_status')\n\n if smart_card_status.eql?('enabled')\n impact 0.5\n if (pam_file = file('/etc/pam_pkcs11/pam_pkcs11.conf')).exist?\n cert_policy_lines = pam_file.content.nil? ? [] :\n pam_file.content.lines.grep(/^(?!.+#).*cert_policy/i)\n if cert_policy_lines.length < 3\n describe 'should contain at least 3 cert policy lines' do\n subject { cert_policy_lines.length }\n it { should >= 3 }\n end\n else\n describe 'each cert policy line should include oscp_on' do\n cert_policy_lines.each do |line|\n subject { line }\n it { should match %r{=[^;]*ocsp_on}i }\n end\n end\n end\n else\n describe pam_file do\n it { should exist }\n end\n end\n else\n impact 0.0\n describe 'The system is not smartcard enabled' do\n skip 'The system is not using Smartcards / PIVs to fulfil the MFA requirement, this control is Not Applicable.'\n end\n end\nend\n","desc":"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements certificate status checking for PKI\nauthentication.\n\n Check to see if Online Certificate Status Protocol (OCSP) is enabled on the\nsystem with the following command:\n\n # grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -v \"^#\"\n\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n\n There should be at least three lines returned.\n\n If \"ocsp_on\" is not present in all uncommented \"cert_policy\" lines in\n\"/etc/pam_pkcs11/pam_pkcs11.conf\", this is a finding.","label":"check"},{"data":"Configure the operating system to do certificate status checking for PKI\nauthentication.\n\n Modify all of the \"cert_policy\" lines in\n\"/etc/pam_pkcs11/pam_pkcs11.conf\" to include \"ocsp_on\".","label":"fix"}],"id":"V-72433","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72433.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72433","rid":"SV-87057r5_rule","stig_id":"RHEL-07-041003","fix_id":"F-78785r3_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncertificate status checking for PKI authentication.","waiver_data":{}},{"code":"control \"V-73155\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\n overriding the screensaver lock-delay setting for the graphical user interface.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding a screensaver\n lock after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\n Applicable. The screen program must be installed to lock sessions on the\n console.\n\n Determine which profile the system database is using with the following\n command:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock delay setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\n the path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\n other than \\\"local\\\" is being used.\n\n # grep -i lock-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-delay\n\n If the command does not return a result, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a\n screensaver lock after a 15-minute period of inactivity for graphical user\n interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\n does not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\n if the system is using another database in \\\"/etc/dconf/profile/user\\\", the\n file should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock delay:\n\n /org/gnome/desktop/screensaver/lock-delay\n \"\n\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-73155\"\n tag rid: \"SV-87807r4_rule\"\n tag stig_id: \"RHEL-07-010081\"\n tag fix_id: \"F-79601r2_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n unless package('gnome-desktop3').installed?\n impact 0.0\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n else\n describe command(\"gsettings writable org.gnome.desktop.screensaver lock-delay\") do\n its('stdout.strip') { should cmp 'false' }\n end\n end\n end\n","desc":"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding a screensaver\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock delay setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i lock-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-delay\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock delay:\n\n /org/gnome/desktop/screensaver/lock-delay","label":"fix"}],"id":"V-73155","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73155.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-73155","rid":"SV-87807r4_rule","stig_id":"RHEL-07-010081","fix_id":"F-79601r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\n overriding the screensaver lock-delay setting for the graphical user interface.","waiver_data":{}},{"code":"control \"V-73157\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the session idle-delay setting for the graphical user interface.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding session idle\ndelay after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the session idle delay setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nthe path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\nother than \\\"local\\\" is being used.\n\n # grep -i idle-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/session/idle-delay\n\n If the command does not return a result, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a session\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nif the system is using another database in /etc/dconf/profile/user, the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the session idle delay:\n\n /org/gnome/desktop/session/idle-delay\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-73157\"\n tag rid: \"SV-87809r4_rule\"\n tag stig_id: \"RHEL-07-010082\"\n tag fix_id: \"F-79603r1_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n unless package('gnome-desktop3').installed?\n impact 0.0\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n else\n describe command(\"gsettings writable org.gnome.desktop.session idle-delay\") do\n its('stdout.strip') { should cmp 'false' }\n end\n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding session idle\ndelay after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the session idle delay setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i idle-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/session/idle-delay\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a session\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in /etc/dconf/profile/user, the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the session idle delay:\n\n /org/gnome/desktop/session/idle-delay","label":"fix"}],"id":"V-73157","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73157.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-73157","rid":"SV-87809r4_rule","stig_id":"RHEL-07-010082","fix_id":"F-79603r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the session idle-delay setting for the graphical user interface.","waiver_data":{}},{"code":"control \"V-73159\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, pwquality\nmust be used.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \\\"pwquality\\\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system uses \\\"pwquality\\\" to enforce the password\ncomplexity rules.\n\n Check for the use of \\\"pwquality\\\" with the following command:\n\n # cat /etc/pam.d/system-auth | grep pam_pwquality\n\n password required pam_pwquality.so retry=3\n\n If the command does not return an uncommented line containing the value\n\\\"pam_pwquality.so\\\", this is a finding.\n\n If the value of \\\"retry\\\" is set to \\\"0\\\" or greater than \\\"3\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to use \\\"pwquality\\\" to enforce password\ncomplexity rules.\n\n Add the following line to \\\"/etc/pam.d/system-auth\\\" (or modify the line to\nhave the required value):\n\n password required pam_pwquality.so retry=3\n\n Note: The value of \\\"retry\\\" should be between \\\"1\\\" and \\\"3\\\".\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000069-GPOS-00037\"\n tag gid: \"V-73159\"\n tag rid: \"SV-87811r4_rule\"\n tag stig_id: \"RHEL-07-010119\"\n tag fix_id: \"F-79605r5_fix\"\n tag cci: [\"CCI-000192\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n max_retry = input('max_retry')\n\n describe pam('/etc/pam.d/passwd') do\n its('lines') { should match_pam_rule('password (required|requisite) pam_pwquality.so') }\n its('lines') { should match_pam_rule('password (required|requisite) pam_pwquality.so').all_with_integer_arg('retry', '>=', 1) }\n its('lines') { should match_pam_rule('password (required|requisite) pam_pwquality.so').all_with_integer_arg('retry', '<=', max_retry) }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \"pwquality\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \"pwquality\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uses \"pwquality\" to enforce the password\ncomplexity rules.\n\n Check for the use of \"pwquality\" with the following command:\n\n # cat /etc/pam.d/system-auth | grep pam_pwquality\n\n password required pam_pwquality.so retry=3\n\n If the command does not return an uncommented line containing the value\n\"pam_pwquality.so\", this is a finding.\n\n If the value of \"retry\" is set to \"0\" or greater than \"3\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to use \"pwquality\" to enforce password\ncomplexity rules.\n\n Add the following line to \"/etc/pam.d/system-auth\" (or modify the line to\nhave the required value):\n\n password required pam_pwquality.so retry=3\n\n Note: The value of \"retry\" should be between \"1\" and \"3\".","label":"fix"}],"id":"V-73159","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73159.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-73159","rid":"SV-87811r4_rule","stig_id":"RHEL-07-010119","fix_id":"F-79605r5_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, pwquality\nmust be used.","waiver_data":{}},{"code":"control \"V-73161\" do\n title \"The Red Hat Enterprise Linux operating system must prevent binary\nfiles from being executed on file systems that are being imported via Network\nFile System (NFS).\"\n desc \"The \\\"noexec\\\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that are being NFS imported are configured with the\n\\\"noexec\\\" option.\n\n Find the file system(s) that contain the directories being imported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,noexec 0 0\n\n If a file system found in \\\"/etc/fstab\\\" refers to NFS and it does not have\nthe \\\"noexec\\\" option set, and use of NFS imported binaries is not documented\nwith the Information System Security Officer (ISSO) as an operational\nrequirement, this is a finding.\n\n Verify the NFS is mounted with the \\\"noexec\\\"option:\n\n # mount | grep nfs | grep noexec\n If no results are returned and use of NFS imported binaries is not\ndocumented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"noexec\\\" option on\nfile systems that are being imported via NFS.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-73161\"\n tag rid: \"SV-87813r2_rule\"\n tag stig_id: \"RHEL-07-021021\"\n tag fix_id: \"F-79607r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n nfs_systems = etc_fstab.nfs_file_systems.entries\n if !nfs_systems.nil? and !nfs_systems.empty?\n nfs_systems.each do |file_system|\n describe file_system do\n its ('mount_options') { should include 'noexec' }\n end\n end\n else\n describe \"No NFS file systems were found.\" do\n subject { nfs_systems.nil? or nfs_systems.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","descriptions":[{"data":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are being NFS imported are configured with the\n\"noexec\" option.\n\n Find the file system(s) that contain the directories being imported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,noexec 0 0\n\n If a file system found in \"/etc/fstab\" refers to NFS and it does not have\nthe \"noexec\" option set, and use of NFS imported binaries is not documented\nwith the Information System Security Officer (ISSO) as an operational\nrequirement, this is a finding.\n\n Verify the NFS is mounted with the \"noexec\"option:\n\n # mount | grep nfs | grep noexec\n If no results are returned and use of NFS imported binaries is not\ndocumented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"noexec\" option on\nfile systems that are being imported via NFS.","label":"fix"}],"id":"V-73161","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73161.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-73161","rid":"SV-87813r2_rule","stig_id":"RHEL-07-021021","fix_id":"F-79607r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent binary\nfiles from being executed on file systems that are being imported via Network\nFile System (NFS).","waiver_data":{}},{"code":"control \"V-73163\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when there is an error sending\naudit records to a remote system.\"\n desc \"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the action the operating system takes if there is an error sending\naudit records to a remote system.\n\n Check the action that takes place if there is an error sending audit\nrecords to a remote system with the following command:\n\n # grep -i network_failure_action /etc/audisp/audisp-remote.conf\n network_failure_action = syslog\n\n If the value of the \\\"network_failure_action\\\" option is not \\\"syslog\\\",\n\\\"single\\\", or \\\"halt\\\", or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the action the operating system takes if there is an error\nsending audit records to a remote system.\n\n Uncomment the \\\"network_failure_action\\\" option in\n\\\"/etc/audisp/audisp-remote.conf\\\" and set it to \\\"syslog\\\", \\\"single\\\", or\n\\\"halt\\\".\n\n network_failure_action = syslog\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag gid: \"V-73163\"\n tag rid: \"SV-87815r3_rule\"\n tag stig_id: \"RHEL-07-030321\"\n tag fix_id: \"F-79609r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('network_failure_action'.to_s) { should be_in ['syslog', 'single', 'halt'] }\n end\nend\n","desc":"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.","descriptions":[{"data":"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the action the operating system takes if there is an error sending\naudit records to a remote system.\n\n Check the action that takes place if there is an error sending audit\nrecords to a remote system with the following command:\n\n # grep -i network_failure_action /etc/audisp/audisp-remote.conf\n network_failure_action = syslog\n\n If the value of the \"network_failure_action\" option is not \"syslog\",\n\"single\", or \"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the action the operating system takes if there is an error\nsending audit records to a remote system.\n\n Uncomment the \"network_failure_action\" option in\n\"/etc/audisp/audisp-remote.conf\" and set it to \"syslog\", \"single\", or\n\"halt\".\n\n network_failure_action = syslog","label":"fix"}],"id":"V-73163","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73163.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","gid":"V-73163","rid":"SV-87815r3_rule","stig_id":"RHEL-07-030321","fix_id":"F-79609r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when there is an error sending\naudit records to a remote system.","waiver_data":{}},{"code":"control \"V-73165\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/group.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/group\\\".\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/group /etc/audit/audit.rules\n\n -w /etc/group -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/group\\\".\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/group -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73165\"\n tag rid: \"SV-87817r3_rule\"\n tag stig_id: \"RHEL-07-030871\"\n tag fix_id: \"F-79611r3_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/group'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\n\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/group\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/group /etc/audit/audit.rules\n\n -w /etc/group -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/group\".\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/group -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73165","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73165.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73165","rid":"SV-87817r3_rule","stig_id":"RHEL-07-030871","fix_id":"F-79611r3_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/group.","waiver_data":{}},{"code":"control \"V-73167\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/gshadow.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/gshadow\\\".\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/gshadow /etc/audit/audit.rules\n\n -w /etc/gshadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/gshadow\\\".\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/gshadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73167\"\n tag rid: \"SV-87819r4_rule\"\n tag stig_id: \"RHEL-07-030872\"\n tag fix_id: \"F-79613r3_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/gshadow'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\n\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/gshadow\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/gshadow /etc/audit/audit.rules\n\n -w /etc/gshadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/gshadow\".\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/gshadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73167","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73167.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73167","rid":"SV-87819r4_rule","stig_id":"RHEL-07-030872","fix_id":"F-79613r3_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/gshadow.","waiver_data":{}},{"code":"control \"V-73171\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/shadow.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/shadow /etc/audit/audit.rules\n\n -w /etc/shadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Add or update the following file system rule in\n\\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/shadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73171\"\n tag rid: \"SV-87823r4_rule\"\n tag stig_id: \"RHEL-07-030873\"\n tag fix_id: \"F-79617r4_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/shadow'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\n\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/shadow /etc/audit/audit.rules\n\n -w /etc/shadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Add or update the following file system rule in\n\"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/shadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73171","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73171.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73171","rid":"SV-87823r4_rule","stig_id":"RHEL-07-030873","fix_id":"F-79617r4_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/shadow.","waiver_data":{}},{"code":"control \"V-73173\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/opasswd.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/security/opasswd /etc/audit/audit.rules\n\n -w /etc/security/opasswd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Add or update the following file system rule in\n\\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/security/opasswd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect:\n # systemctl restart auditd\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73173\"\n tag rid: \"SV-87825r5_rule\"\n tag stig_id: \"RHEL-07-030874\"\n tag fix_id: \"F-79619r6_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/security/opasswd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/security/opasswd /etc/audit/audit.rules\n\n -w /etc/security/opasswd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Add or update the following file system rule in\n\"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/security/opasswd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect:\n # systemctl restart auditd","label":"fix"}],"id":"V-73173","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73173.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73173","rid":"SV-87825r5_rule","stig_id":"RHEL-07-030874","fix_id":"F-79619r6_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/opasswd.","waiver_data":{}},{"code":"control \"V-73175\" do\n title \"The Red Hat Enterprise Linux operating system must ignore Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system ignores IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.accept_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \\\" net.ipv4.conf.all.accept_redirects \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the \\\"accept_redirects\\\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.accept_redirects'\n\n net.ipv4.conf.all.accept_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to ignore IPv4 ICMP redirect messages by adding the\nfollowing line to \\\"/etc/sysctl.conf\\\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-73175\"\n tag rid: \"SV-87827r4_rule\"\n tag stig_id: \"RHEL-07-040641\"\n tag fix_id: \"F-79621r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.accept_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system ignores IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.accept_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \" net.ipv4.conf.all.accept_redirects \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"accept_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.accept_redirects'\n\n net.ipv4.conf.all.accept_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to ignore IPv4 ICMP redirect messages by adding the\nfollowing line to \"/etc/sysctl.conf\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-73175","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73175.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-73175","rid":"SV-87827r4_rule","stig_id":"RHEL-07-040641","fix_id":"F-79621r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must ignore Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages.","waiver_data":{}},{"code":"control \"V-73177\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all wireless network adapters are disabled.\"\n desc \"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that there are no wireless interfaces configured on the system.\n\n This is N/A for systems that do not have wireless network adapters.\n\n Check for the presence of active wireless interfaces with the following\ncommand:\n\n # nmcli device\n DEVICE TYPE STATE\n eth0 ethernet connected\n wlp3s0 wifi disconnected\n lo loopback unmanaged\n\n If a wireless interface is configured and its use on the system is not\ndocumented with the Information System Security Officer (ISSO), this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the system to disable all wireless network interfaces with the\nfollowing command:\n\n #nmcli radio wifi off\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000424-GPOS-00188\"\n tag gid: \"V-73177\"\n tag rid: \"SV-87829r2_rule\"\n tag stig_id: \"RHEL-07-041010\"\n tag fix_id: \"F-79623r1_fix\"\n tag cci: [\"CCI-001443\", \"CCI-001444\", \"CCI-002418\"]\n tag nist: [\"AC-18 (1)\", \"AC-18 (1)\", \"SC-8\"]\n\n describe command('nmcli device') do\n its('stdout.strip') { should_not match %r{wifi connected} }\n end\nend\n","desc":"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.","descriptions":[{"data":"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that there are no wireless interfaces configured on the system.\n\n This is N/A for systems that do not have wireless network adapters.\n\n Check for the presence of active wireless interfaces with the following\ncommand:\n\n # nmcli device\n DEVICE TYPE STATE\n eth0 ethernet connected\n wlp3s0 wifi disconnected\n lo loopback unmanaged\n\n If a wireless interface is configured and its use on the system is not\ndocumented with the Information System Security Officer (ISSO), this is a\nfinding.","label":"check"},{"data":"Configure the system to disable all wireless network interfaces with the\nfollowing command:\n\n #nmcli radio wifi off","label":"fix"}],"id":"V-73177","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73177.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000424-GPOS-00188","gid":"V-73177","rid":"SV-87829r2_rule","stig_id":"RHEL-07-041010","fix_id":"F-79623r1_fix","cci":["CCI-001443","CCI-001444","CCI-002418"],"nist":["AC-18 (1)","AC-18 (1)","SC-8"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all wireless network adapters are disabled.","waiver_data":{}},{"code":"control \"V-77819\" do\n title \"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate users using multifactor authentication via a graphical\nuser logon.\"\n desc \"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system uniquely identifies and authenticates users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Determine which profile the system database is using with the following\ncommand:\n\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Note: The example is using the database local for the system, so the path\nis \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database other\nthan local is being used.\n\n # grep enable-smartcard-authentication /etc/dconf/db/local.d/*\n\n enable-smartcard-authentication=true\n\n If \\\"enable-smartcard-authentication\\\" is set to \\\"false\\\" or the keyword\nis missing, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to uniquely identify and authenticate users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example is using the database local for the system, so if the\nsystem is using another database in \\\"/etc/dconf/profile/user\\\", the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/00-defaults\n\n Edit \\\"[org/gnome/login-screen]\\\" and add or update the following line:\n enable-smartcard-authentication=true\n\n Update the system databases:\n # dconf update\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00161\", \"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-77819\"\n tag rid: \"SV-92515r2_rule\"\n tag stig_id: \"RHEL-07-010061\"\n tag fix_id: \"F-84519r4_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n multifactor_enabled = input('multifactor_enabled')\n dconf_user = input('dconf_user')\n\n if package('gnome-desktop3').installed? && (package('pcsc-lite').installed? || package('esc').installed?)\n impact 0.5\n if !dconf_user.nil? && command('whoami').stdout.strip == 'root'\n describe command(\"sudo -u #{dconf_user} dconf read /org/gnome/login-screen/enable-smartcard-authentication\") do\n its('stdout.strip') { should eq multifactor_enabled.to_s }\n end\n else\n describe command(\"dconf read /org/gnome/login-screen/enable-smartcard-authentication\") do\n its('stdout.strip') { should eq multifactor_enabled.to_s }\n end\n end\n else\n impact 0.0\n if !package('gnome-desktop3').installed?\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n end\n\n if !package('pcsc-lite').installed?\n describe \"The pcsc-lite package is not installed\" do\n skip \"The pcsc-lite package is not installed, this control is Not Applicable.\"\n end\n end\n if !package('esc').installed?\n describe \"The esc package is not installed\" do\n skip \"The esc package is not installed, this control is Not Applicable.\"\n end\n end\n end\nend\n","desc":"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.","descriptions":[{"data":"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uniquely identifies and authenticates users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Determine which profile the system database is using with the following\ncommand:\n\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Note: The example is using the database local for the system, so the path\nis \"/etc/dconf/db/local.d\". This path must be modified if a database other\nthan local is being used.\n\n # grep enable-smartcard-authentication /etc/dconf/db/local.d/*\n\n enable-smartcard-authentication=true\n\n If \"enable-smartcard-authentication\" is set to \"false\" or the keyword\nis missing, this is a finding.","label":"check"},{"data":"Configure the operating system to uniquely identify and authenticate users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example is using the database local for the system, so if the\nsystem is using another database in \"/etc/dconf/profile/user\", the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/00-defaults\n\n Edit \"[org/gnome/login-screen]\" and add or update the following line:\n enable-smartcard-authentication=true\n\n Update the system databases:\n # dconf update","label":"fix"}],"id":"V-77819","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77819.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-77819","rid":"SV-92515r2_rule","stig_id":"RHEL-07-010061","fix_id":"F-84519r4_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate users using multifactor authentication via a graphical\nuser logon.","waiver_data":{}},{"code":"control \"V-77821\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the Datagram Congestion Control Protocol (DCCP) kernel module is disabled\nunless required.\"\n desc \"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system disables the ability to load the DCCP kernel\nmodule.\n\n # grep -r dccp /etc/modprobe.d/* | grep -i \\\"/bin/true\\\" | grep -v \\\"^#\\\"\n\n install dccp /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of DCCP is not documented with the Information System Security Officer\n(ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use the DCCP kernel\nmodule.\n\n Check to see if the DCCP kernel module is disabled with the following\ncommand:\n\n # grep -i dccp /etc/modprobe.d/* | grep -i \\\"blacklist\\\" | grep -v \\\"^#\\\"\n\n blacklist dccp\n\n If the command does not return any output or the output is not \\\"blacklist\ndccp\\\", and use of the dccp kernel module is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable the ability to use the DCCP\nkernel module.\n\n Create a file under \\\"/etc/modprobe.d\\\" with the following command:\n\n # touch /etc/modprobe.d/dccp.conf\n\n Add the following line to the created file:\n\n install dccp /bin/true\n\n Ensure that the DCCP module is blacklisted:\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist dccp\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000378-GPOS-00163\"\n tag gid: \"V-77821\"\n tag rid: \"SV-92517r3_rule\"\n tag stig_id: \"RHEL-07-020101\"\n tag fix_id: \"F-84521r3_fix\"\n tag cci: [\"CCI-001958\"]\n tag nist: [\"IA-3\"]\n\n describe kernel_module('dccp') do\n it { should_not be_loaded }\n it { should be_blacklisted }\n end\nend\n","desc":"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.","descriptions":[{"data":"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system disables the ability to load the DCCP kernel\nmodule.\n\n # grep -r dccp /etc/modprobe.d/* | grep -i \"/bin/true\" | grep -v \"^#\"\n\n install dccp /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of DCCP is not documented with the Information System Security Officer\n(ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use the DCCP kernel\nmodule.\n\n Check to see if the DCCP kernel module is disabled with the following\ncommand:\n\n # grep -i dccp /etc/modprobe.d/* | grep -i \"blacklist\" | grep -v \"^#\"\n\n blacklist dccp\n\n If the command does not return any output or the output is not \"blacklist\ndccp\", and use of the dccp kernel module is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to use the DCCP\nkernel module.\n\n Create a file under \"/etc/modprobe.d\" with the following command:\n\n # touch /etc/modprobe.d/dccp.conf\n\n Add the following line to the created file:\n\n install dccp /bin/true\n\n Ensure that the DCCP module is blacklisted:\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist dccp","label":"fix"}],"id":"V-77821","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77821.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000378-GPOS-00163","gid":"V-77821","rid":"SV-92517r3_rule","stig_id":"RHEL-07-020101","fix_id":"F-84521r3_fix","cci":["CCI-001958"],"nist":["IA-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the Datagram Congestion Control Protocol (DCCP) kernel module is disabled\nunless required.","waiver_data":{}},{"code":"control \"V-77823\" do\n title \"The Red Hat Enterprise Linux operating system must require\nauthentication upon booting into single-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must require authentication upon booting into\nsingle-user and maintenance modes.\n\n Check that the operating system requires authentication upon booting into\nsingle-user mode with the following command:\n\n # grep -i execstart /usr/lib/systemd/system/rescue.service | grep -i sulogin\n\n ExecStart=-/bin/sh -c \\\"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\\\"\n\n If \\\"ExecStart\\\" does not have \\\"/usr/sbin/sulogin\\\" as an option, this is\na finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require authentication upon booting into\nsingle-user and maintenance modes.\n\n Add or modify the \\\"ExecStart\\\" line in\n\\\"/usr/lib/systemd/system/rescue.service\\\" to include \\\"/usr/sbin/sulogin\\\":\n\n ExecStart=-/bin/sh -c \\\"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\\\"\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-77823\"\n tag rid: \"SV-92519r2_rule\"\n tag stig_id: \"RHEL-07-010481\"\n tag fix_id: \"F-84523r2_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n describe command(\"grep -i execstart /usr/lib/systemd/system/rescue.service\") do\n its('stdout.strip') { should match %r{/usr/sbin/sulogin} }\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must require authentication upon booting into\nsingle-user and maintenance modes.\n\n Check that the operating system requires authentication upon booting into\nsingle-user mode with the following command:\n\n # grep -i execstart /usr/lib/systemd/system/rescue.service | grep -i sulogin\n\n ExecStart=-/bin/sh -c \"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\"\n\n If \"ExecStart\" does not have \"/usr/sbin/sulogin\" as an option, this is\na finding.","label":"check"},{"data":"Configure the operating system to require authentication upon booting into\nsingle-user and maintenance modes.\n\n Add or modify the \"ExecStart\" line in\n\"/usr/lib/systemd/system/rescue.service\" to include \"/usr/sbin/sulogin\":\n\n ExecStart=-/bin/sh -c \"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\"","label":"fix"}],"id":"V-77823","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77823.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-77823","rid":"SV-92519r2_rule","stig_id":"RHEL-07-010481","fix_id":"F-84523r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"The Red Hat Enterprise Linux operating system must require\nauthentication upon booting into single-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-77825\" do\n title \"The Red Hat Enterprise Linux operating system must implement virtual\naddress space randomization.\"\n desc \"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system implements virtual address space randomization.\n\n # grep kernel.randomize_va_space /etc/sysctl.conf /etc/sysctl.d/*\n\n kernel.randomize_va_space = 2\n\n If \\\"kernel.randomize_va_space\\\" is not configured in the /etc/sysctl.conf\nfile or in the /etc/sysctl.d/ directory, is commented out or does not have a\nvalue of \\\"2\\\", this is a finding.\n\n Check that the operating system implements virtual address space\nrandomization with the following command:\n\n # /sbin/sysctl -a | grep kernel.randomize_va_space\n\n kernel.randomize_va_space = 2\n\n If \\\"kernel.randomize_va_space\\\" does not have a value of \\\"2\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system implement virtual address space\nrandomization.\n\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a config file in the /etc/sysctl.d/ directory\n(or modify the line to have the required value):\n\n kernel.randomize_va_space = 2\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-77825\"\n tag rid: \"SV-92521r2_rule\"\n tag stig_id: \"RHEL-07-040201\"\n tag fix_id: \"F-84531r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n randomize_va_space = input('randomize_va_space')\n\n describe kernel_parameter('kernel.randomize_va_space') do\n its('value') { should eq randomize_va_space }\n end\nend\n","desc":"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.","descriptions":[{"data":"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements virtual address space randomization.\n\n # grep kernel.randomize_va_space /etc/sysctl.conf /etc/sysctl.d/*\n\n kernel.randomize_va_space = 2\n\n If \"kernel.randomize_va_space\" is not configured in the /etc/sysctl.conf\nfile or in the /etc/sysctl.d/ directory, is commented out or does not have a\nvalue of \"2\", this is a finding.\n\n Check that the operating system implements virtual address space\nrandomization with the following command:\n\n # /sbin/sysctl -a | grep kernel.randomize_va_space\n\n kernel.randomize_va_space = 2\n\n If \"kernel.randomize_va_space\" does not have a value of \"2\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system implement virtual address space\nrandomization.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a config file in the /etc/sysctl.d/ directory\n(or modify the line to have the required value):\n\n kernel.randomize_va_space = 2\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-77825","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77825.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-77825","rid":"SV-92521r2_rule","stig_id":"RHEL-07-040201","fix_id":"F-84531r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must implement virtual\naddress space randomization.","waiver_data":{}},{"code":"control \"V-78995\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver lock-enabled setting for the graphical user\ninterface.\"\n desc \"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding the screensaver\nlock-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock-enabled setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nthe path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\nother than \\\"local\\\" is being used.\n\n # grep -i lock-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-enabled\n\n If the command does not return a result, this is a finding.\n\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nif the system is using another database in \\\"/etc/dconf/profile/user\\\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock-enabled setting:\n\n /org/gnome/desktop/screensaver/lock-enabled\n\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-78995\"\n tag rid: \"SV-93701r3_rule\"\n tag stig_id: \"RHEL-07-010062\"\n tag fix_id: \"F-85745r1_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n describe command(\"gsettings writable org.gnome.desktop.screensaver lock-enabled\") do\n its('stdout.strip') { should cmp 'false' }\n end\n else\n impact 0.0\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n end \nend\n","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding the screensaver\nlock-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock-enabled setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i lock-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-enabled\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock-enabled setting:\n\n /org/gnome/desktop/screensaver/lock-enabled","label":"fix"}],"id":"V-78995","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78995.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-78995","rid":"SV-93701r3_rule","stig_id":"RHEL-07-010062","fix_id":"F-85745r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver lock-enabled setting for the graphical user\ninterface.","waiver_data":{}},{"code":"control \"V-78997\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver idle-activation-enabled setting for the graphical\nuser interface.\"\n desc \"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding the screensaver\nidle-activation-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the idle-activation-enabled setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nthe path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\nother than \\\"local\\\" is being used.\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/idle-activation-enabled\n\n If the command does not return a result, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nif the system is using another database in \\\"/etc/dconf/profile/user\\\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver idle-activation-enabled setting:\n\n /org/gnome/desktop/screensaver/idle-activation-enabled\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-78997\"\n tag rid: \"SV-93703r2_rule\"\n tag stig_id: \"RHEL-07-010101\"\n tag fix_id: \"F-85747r1_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n impact 0.5\n else\n impact 0.0\n end\n\n describe command(\"gsettings writable org.gnome.desktop.screensaver idle-activation-enabled\") do\n its('stdout.strip') { should cmp 'false' }\n end if package('gnome-desktop3').installed?\n\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end if !package('gnome-desktop3').installed?\nend\n","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding the screensaver\nidle-activation-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the idle-activation-enabled setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/idle-activation-enabled\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver idle-activation-enabled setting:\n\n /org/gnome/desktop/screensaver/idle-activation-enabled","label":"fix"}],"id":"V-78997","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78997.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-78997","rid":"SV-93703r2_rule","stig_id":"RHEL-07-010101","fix_id":"F-85747r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver idle-activation-enabled setting for the graphical\nuser interface.","waiver_data":{}},{"code":"control \"V-78999\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe create_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"create_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw create_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"create_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"create_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-78999\"\n tag rid: \"SV-93705r3_rule\"\n tag stig_id: \"RHEL-07-030819\"\n tag fix_id: \"F-85749r4_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"create_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"create_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"create_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw create_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"create_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"create_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-78999","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78999.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-78999","rid":"SV-93705r3_rule","stig_id":"RHEL-07-030819","fix_id":"F-85749r4_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe create_module syscall.","waiver_data":{}},{"code":"control \"V-79001\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe finit_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"finit_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw finit_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"finit_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"finit_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-79001\"\n tag rid: \"SV-93707r3_rule\"\n tag stig_id: \"RHEL-07-030821\"\n tag fix_id: \"F-85751r3_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"finit_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"finit_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"finit_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw finit_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"finit_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"finit_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-79001","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-79001.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-79001","rid":"SV-93707r3_rule","stig_id":"RHEL-07-030821","fix_id":"F-85751r3_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe finit_module syscall.","waiver_data":{}},{"code":"control \"V-81003\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing\npasswords.\"\n desc \"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that /etc/pam.d/passwd is configured to use /etc/pam.d/system-auth\nwhen changing passwords:\n\n # cat /etc/pam.d/passwd | grep -i substack | grep -i system-auth\n password substack system-auth\n\n If no results are returned, the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure PAM to utilize /etc/pam.d/system-auth when changing passwords.\n\n Add the following line to \\\"/etc/pam.d/passwd\\\" (or modify the line to have\nthe required value):\n\n password substack system-auth\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000069-GPOS-00037\"\n tag gid: \"V-81003\"\n tag rid: \"SV-95715r1_rule\"\n tag stig_id: \"RHEL-07-010118\"\n tag fix_id: \"F-87837r1_fix\"\n tag cci: [\"CCI-000192\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n # Get the content of /etc/pam.d/passwd as an array\n pam_passwd_content = file('/etc/pam.d/passwd').content.strip.split(\"\\n\")\n # Make a new array of any line matching the target pattern:\n # /password\\s+substack\\s+system-auth\n matching_lines = pam_passwd_content.select { |i| i.match(/password\\s+substack\\s+system-auth/) }\n\n describe '/etc/pam.d/passwd' do\n subject { matching_lines }\n it 'substacks system-auth' do\n expect(subject.length).to(eql 1)\n end\n end\nend\n","desc":"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.","descriptions":[{"data":"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that /etc/pam.d/passwd is configured to use /etc/pam.d/system-auth\nwhen changing passwords:\n\n # cat /etc/pam.d/passwd | grep -i substack | grep -i system-auth\n password substack system-auth\n\n If no results are returned, the line is commented out, this is a finding.","label":"check"},{"data":"Configure PAM to utilize /etc/pam.d/system-auth when changing passwords.\n\n Add the following line to \"/etc/pam.d/passwd\" (or modify the line to have\nthe required value):\n\n password substack system-auth","label":"fix"}],"id":"V-81003","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81003.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-81003","rid":"SV-95715r1_rule","stig_id":"RHEL-07-010118","fix_id":"F-87837r1_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing\npasswords.","waiver_data":{}},{"code":"control \"V-81005\" do\n title \"Red Hat Enterprise Linux operating systems version 7.2 or newer with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use UEFI, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -iw grub2_password /boot/grub2/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \\\"grub.pbkdf2.sha512\\\", this is a\nfinding.\n\n Verify that the \\\"root\\\" account is set as the \\\"superusers\\\":\n\n # grep -iw \\\"superusers\\\" /boot/grub2/grub.cfg\n set superusers=\\\"root\\\"\n export superusers\n\n If \\\"superusers\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/grub2/grub.cfg file and add or modify the following lines in\nthe \\\"### BEGIN /etc/grub.d/01_users ###\\\" section:\n\n set superusers=\\\"root\\\"\n export superusers\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-81005\"\n tag rid: \"SV-95717r1_rule\"\n tag stig_id: \"RHEL-07-010482\"\n tag fix_id: \"F-87839r2_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n if file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running UEFI\" do\n skip \"The System is running UEFI, this control is Not Applicable.\"\n end\n else\n unless os[:release] >= \"7.2\"\n impact 0.0\n describe \"System running version of RHEL prior to 7.2\" do\n skip \"The System is running an outdated version of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n input('grub_user_boot_files').each do |grub_user_file|\n describe parse_config_file(grub_user_file) do\n its('GRUB2_PASSWORD') { should include \"grub.pbkdf2.sha512\"}\n end\n end\n\n describe parse_config_file(input('grub_main_cfg')) do\n its('set superusers') { should cmp '\"root\"' } \n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use UEFI, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -iw grub2_password /boot/grub2/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \"grub.pbkdf2.sha512\", this is a\nfinding.\n\n Verify that the \"root\" account is set as the \"superusers\":\n\n # grep -iw \"superusers\" /boot/grub2/grub.cfg\n set superusers=\"root\"\n export superusers\n\n If \"superusers\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/grub2/grub.cfg file and add or modify the following lines in\nthe \"### BEGIN /etc/grub.d/01_users ###\" section:\n\n set superusers=\"root\"\n export superusers","label":"fix"}],"id":"V-81005","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81005.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-81005","rid":"SV-95717r1_rule","stig_id":"RHEL-07-010482","fix_id":"F-87839r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems version 7.2 or newer with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-81007\" do\n title \"Red Hat Enterprise Linux operating systems version 7.2 or newer using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use BIOS, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \\\"grub.pbkdf2.sha512\\\", this is a\nfinding.\n\n Verify that the \\\"root\\\" account is set as the \\\"superusers\\\":\n\n # grep -iw \\\"superusers\\\" /boot/efi/EFI/redhat/grub.cfg\n set superusers=\\\"root\\\"\n export superusers\n\n If \\\"superusers\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/efi/EFI/redhat/grub.cfg file and add or modify the following\nlines in the \\\"### BEGIN /etc/grub.d/01_users ###\\\" section:\n\n set superusers=\\\"root\\\"\n export superusers\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-81007\"\n tag rid: \"SV-95719r1_rule\"\n tag stig_id: \"RHEL-07-010491\"\n tag fix_id: \"F-87841r2_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n unless file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running BIOS\" do\n skip \"The System is running BIOS, this control is Not Applicable.\"\n end\n else\n unless os[:release] >= \"7.2\"\n impact 0.0\n describe \"System running version of RHEL prior to 7.2\" do\n skip \"The System is running an outdated version of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n input('grub_uefi_user_boot_files').each do |grub_user_file|\n describe parse_config_file(grub_user_file) do\n its('GRUB2_PASSWORD') { should include \"grub.pbkdf2.sha512\"}\n end\n end\n\n describe parse_config_file(input('grub_uefi_main_cfg')) do\n its('set superusers') { should cmp '\"root\"' } \n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use BIOS, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \"grub.pbkdf2.sha512\", this is a\nfinding.\n\n Verify that the \"root\" account is set as the \"superusers\":\n\n # grep -iw \"superusers\" /boot/efi/EFI/redhat/grub.cfg\n set superusers=\"root\"\n export superusers\n\n If \"superusers\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/efi/EFI/redhat/grub.cfg file and add or modify the following\nlines in the \"### BEGIN /etc/grub.d/01_users ###\" section:\n\n set superusers=\"root\"\n export superusers","label":"fix"}],"id":"V-81007","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81007.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-81007","rid":"SV-95719r1_rule","stig_id":"RHEL-07-010491","fix_id":"F-87841r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems version 7.2 or newer using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-81009\" do\n title \"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nodev option.\"\n desc \"The \\\"nodev\\\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"nodev\\\" option is configured for /dev/shm:\n\n\n # cat /etc/fstab | grep /dev/shm\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \\\"nodev\\\" option is not listed, this is\na finding.\n\n Verify \\\"/dev/shm\\\" is mounted with the \\\"nodev\\\" option:\n\n # mount | grep \\\"/dev/shm\\\" | grep nodev\n\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the system so that /dev/shm is mounted with the\n\\\"nodev\\\" option.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000368-GPOS-00154\"\n tag gid: \"V-81009\"\n tag rid: \"SV-95721r2_rule\"\n tag stig_id: \"RHEL-07-021022\"\n tag fix_id: \"F-87843r2_fix\"\n tag cci: [\"CCI-001764\"]\n tag nist: [\"CM-7 (2)\"]\n\n describe mount('/dev/shm') do\n its('options') { should include 'nodev' }\n end\nend\n","desc":"The \"nodev\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","descriptions":[{"data":"The \"nodev\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"nodev\" option is configured for /dev/shm:\n\n\n # cat /etc/fstab | grep /dev/shm\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"nodev\" option is not listed, this is\na finding.\n\n Verify \"/dev/shm\" is mounted with the \"nodev\" option:\n\n # mount | grep \"/dev/shm\" | grep nodev\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"nodev\" option.","label":"fix"}],"id":"V-81009","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81009.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81009","rid":"SV-95721r2_rule","stig_id":"RHEL-07-021022","fix_id":"F-87843r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nodev option.","waiver_data":{}},{"code":"control \"V-81011\" do\n title \"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nosuid option.\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute\n\\\"setuid\\\" and \\\"setgid\\\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \\\"setuid\\\" and \\\"setguid\\\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"nosuid\\\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \\\"nosuid\\\" option is not listed, this\nis a finding.\n\n Verify \\\"/dev/shm\\\" is mounted with the \\\"nosuid\\\" option:\n\n # mount | grep \\\"/dev/shm\\\" | grep nosuid\n\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the system so that /dev/shm is mounted with the\n\\\"nosuid\\\" option.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000368-GPOS-00154\"\n tag gid: \"V-81011\"\n tag rid: \"SV-95723r2_rule\"\n tag stig_id: \"RHEL-07-021023\"\n tag fix_id: \"F-87845r2_fix\"\n tag cci: [\"CCI-001764\"]\n tag nist: [\"CM-7 (2)\"]\n\n describe mount('/dev/shm') do\n its('options') { should include 'nosuid' }\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"nosuid\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"nosuid\" option is not listed, this\nis a finding.\n\n Verify \"/dev/shm\" is mounted with the \"nosuid\" option:\n\n # mount | grep \"/dev/shm\" | grep nosuid\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"nosuid\" option.","label":"fix"}],"id":"V-81011","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81011.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81011","rid":"SV-95723r2_rule","stig_id":"RHEL-07-021023","fix_id":"F-87845r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nosuid option.","waiver_data":{}},{"code":"control \"V-81013\" do\n title \"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe noexec option.\"\n desc \"The \\\"noexec\\\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"noexec\\\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \\\"noexec\\\" option is not listed, this\nis a finding.\n\n Verify \\\"/dev/shm\\\" is mounted with the \\\"noexec\\\" option:\n\n # mount | grep \\\"/dev/shm\\\" | grep noexec\n\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the system so that /dev/shm is mounted with the\n\\\"noexec\\\" option.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000368-GPOS-00154\"\n tag gid: \"V-81013\"\n tag rid: \"SV-95725r2_rule\"\n tag stig_id: \"RHEL-07-021024\"\n tag fix_id: \"F-87847r2_fix\"\n tag cci: [\"CCI-001764\"]\n tag nist: [\"CM-7 (2)\"]\n\n describe mount('/dev/shm') do\n its('options') { should include 'noexec' }\n end\nend\n","desc":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","descriptions":[{"data":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"noexec\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"noexec\" option is not listed, this\nis a finding.\n\n Verify \"/dev/shm\" is mounted with the \"noexec\" option:\n\n # mount | grep \"/dev/shm\" | grep noexec\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"noexec\" option.","label":"fix"}],"id":"V-81013","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81013.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81013","rid":"SV-95725r2_rule","stig_id":"RHEL-07-021024","fix_id":"F-87847r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe noexec option.","waiver_data":{}},{"code":"control \"V-81015\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nuse the au-remote plugin.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \\\"au-remote\\\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the \\\"au-remote\\\" plugin is active on the system:\n\n # grep \\\"active\\\" /etc/audisp/plugins.d/au-remote.conf\n\n active = yes\n\n If the \\\"active\\\" setting is not set to \\\"yes\\\", or the line is commented\nout, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/plugins.d/au-remote.conf file and change the value of\n\\\"active\\\" to \\\"yes\\\".\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81015\"\n tag rid: \"SV-95727r1_rule\"\n tag stig_id: \"RHEL-07-030200\"\n tag fix_id: \"F-87849r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n test_file = '/etc/audisp/plugins.d/au-remote.conf'\n\n if file(test_file).exist?\n describe parse_config_file(test_file) do\n its('active') { should match %r{yes$} }\n end\n else\n describe \"File '#{test_file}' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '#{test_file}' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the \"au-remote\" plugin is active on the system:\n\n # grep \"active\" /etc/audisp/plugins.d/au-remote.conf\n\n active = yes\n\n If the \"active\" setting is not set to \"yes\", or the line is commented\nout, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/plugins.d/au-remote.conf file and change the value of\n\"active\" to \"yes\".\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81015","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81015.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81015","rid":"SV-95727r1_rule","stig_id":"RHEL-07-030200","fix_id":"F-87849r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nuse the au-remote plugin.","waiver_data":{}},{"code":"control \"V-81017\" do\n title \"The Red Hat Enterprise Linux operating system must configure the\nau-remote plugin to off-load audit logs using the audisp-remote daemon.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \\\"au-remote\\\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the \\\"au-remote\\\" plugin is configured to always off-load audit logs\nusing the audisp-remote daemon:\n\n # cat /etc/audisp/plugins.d/au-remote.conf | grep -v \\\"^#\\\"\n\n active = yes\n direction = out\n path = /sbin/audisp-remote\n type = always\n format = string\n\n If the \\\"direction\\\" setting is not set to \\\"out\\\", or the line is\ncommented out, this is a finding.\n\n If the \\\"path\\\" setting is not set to \\\"/sbin/audisp-remote\\\", or the line\nis commented out, this is a finding.\n\n If the \\\"type\\\" setting is not set to \\\"always\\\", or the line is commented\nout, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/plugins.d/au-remote.conf file and add or update the\nfollowing values:\n\n direction = out\n path = /sbin/audisp-remote\n type = always\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81017\"\n tag rid: \"SV-95729r1_rule\"\n tag stig_id: \"RHEL-07-030201\"\n tag fix_id: \"F-87851r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n test_file = '/etc/audisp/plugins.d/au-remote.conf'\n\n if file(test_file).exist?\n describe parse_config_file(test_file) do\n its('direction') { should match %r{out$} }\n its('path') { should match %r{/sbin/audisp-remote$} }\n its('type') { should match %r{always$} }\n end\n else\n describe \"File '#{test_file}' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '#{test_file}' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the \"au-remote\" plugin is configured to always off-load audit logs\nusing the audisp-remote daemon:\n\n # cat /etc/audisp/plugins.d/au-remote.conf | grep -v \"^#\"\n\n active = yes\n direction = out\n path = /sbin/audisp-remote\n type = always\n format = string\n\n If the \"direction\" setting is not set to \"out\", or the line is\ncommented out, this is a finding.\n\n If the \"path\" setting is not set to \"/sbin/audisp-remote\", or the line\nis commented out, this is a finding.\n\n If the \"type\" setting is not set to \"always\", or the line is commented\nout, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/plugins.d/au-remote.conf file and add or update the\nfollowing values:\n\n direction = out\n path = /sbin/audisp-remote\n type = always\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81017","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81017.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81017","rid":"SV-95729r1_rule","stig_id":"RHEL-07-030201","fix_id":"F-87851r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must configure the\nau-remote plugin to off-load audit logs using the audisp-remote daemon.","waiver_data":{}},{"code":"control \"V-81019\" do\n title \"The Red Hat Enterprise Linux operating system must take appropriate\naction when the audisp-remote buffer is full.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the audisp daemon is configured to take an appropriate action when\nthe internal queue is full:\n\n # grep \\\"overflow_action\\\" /etc/audisp/audispd.conf\n\n overflow_action = syslog\n\n If the \\\"overflow_action\\\" option is not \\\"syslog\\\", \\\"single\\\", or\n\\\"halt\\\", or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/audispd.conf file and add or update the\n\\\"overflow_action\\\" option:\n\n overflow_action = syslog\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81019\"\n tag rid: \"SV-95731r1_rule\"\n tag stig_id: \"RHEL-07-030210\"\n tag fix_id: \"F-87853r3_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n if file('/etc/audisp/audispd.conf').exist?\n describe parse_config_file('/etc/audisp/audispd.conf') do\n its('overflow_action') { should match %r{syslog$|single$|halt$}i }\n end\n else\n describe \"File '/etc/audisp/audispd.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '/etc/audisp/audispd.conf' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the audisp daemon is configured to take an appropriate action when\nthe internal queue is full:\n\n # grep \"overflow_action\" /etc/audisp/audispd.conf\n\n overflow_action = syslog\n\n If the \"overflow_action\" option is not \"syslog\", \"single\", or\n\"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/audispd.conf file and add or update the\n\"overflow_action\" option:\n\n overflow_action = syslog\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81019","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81019.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81019","rid":"SV-95731r1_rule","stig_id":"RHEL-07-030210","fix_id":"F-87853r3_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must take appropriate\naction when the audisp-remote buffer is full.","waiver_data":{}},{"code":"control \"V-81021\" do\n title \"The Red Hat Enterprise Linux operating system must label all\noff-loaded audit logs before sending them to the central log server.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the audisp daemon is configured to label all off-loaded audit logs:\n\n # grep \\\"name_format\\\" /etc/audisp/audispd.conf\n\n name_format = hostname\n\n If the \\\"name_format\\\" option is not \\\"hostname\\\", \\\"fqd\\\", or \\\"numeric\\\",\nor the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/audispd.conf file and add or update the\n\\\"name_format\\\" option:\n\n name_format = hostname\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81021\"\n tag rid: \"SV-95733r1_rule\"\n tag stig_id: \"RHEL-07-030211\"\n tag fix_id: \"F-87855r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n if file('/etc/audisp/audispd.conf').exist?\n describe parse_config_file('/etc/audisp/audispd.conf') do\n its('name_format') { should match %r{^hostname$|^fqd$|^numeric$}i }\n end\n else\n describe \"File '/etc/audisp/audispd.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '/etc/audisp/audispd.conf' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the audisp daemon is configured to label all off-loaded audit logs:\n\n # grep \"name_format\" /etc/audisp/audispd.conf\n\n name_format = hostname\n\n If the \"name_format\" option is not \"hostname\", \"fqd\", or \"numeric\",\nor the line is commented out, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/audispd.conf file and add or update the\n\"name_format\" option:\n\n name_format = hostname\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81021","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81021.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81021","rid":"SV-95733r1_rule","stig_id":"RHEL-07-030211","fix_id":"F-87855r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must label all\noff-loaded audit logs before sending them to the central log server.","waiver_data":{}},{"code":"control \"V-92251\" do\n title \"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible on all interfaces.\"\n desc \"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.all.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.all.rp_filter = 1\n\n If \\\"net.ipv4.conf.all.rp_filter\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"1\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.rp_filter\n net.ipv4.conf.all.rp_filter = 1\n\n If the returned line does not have a value of \\\"1\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-92251\"\n tag rid: \"SV-102353r1_rule\"\n tag stig_id: \"RHEL-07-040611\"\n tag fix_id: \"F-98473r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.rp_filter') do\n its('value') { should eq 1 }\n end\nend\n","desc":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","descriptions":[{"data":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.all.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.all.rp_filter = 1\n\n If \"net.ipv4.conf.all.rp_filter\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.rp_filter\n net.ipv4.conf.all.rp_filter = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-92251","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92251.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-92251","rid":"SV-102353r1_rule","stig_id":"RHEL-07-040611","fix_id":"F-98473r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible on all interfaces.","waiver_data":{}},{"code":"control \"V-92253\" do\n title \"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible by default.\"\n desc \"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.default.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.default.rp_filter = 1\n\n If \\\"net.ipv4.conf.default.rp_filter\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"1\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.rp_filter\n net.ipv4.conf.default.rp_filter = 1\n\n If the returned line does not have a value of \\\"1\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-92253\"\n tag rid: \"SV-102355r1_rule\"\n tag stig_id: \"RHEL-07-040612\"\n tag fix_id: \"F-98475r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.rp_filter') do\n its('value') { should eq 1 }\n end\nend\n","desc":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","descriptions":[{"data":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.default.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.default.rp_filter = 1\n\n If \"net.ipv4.conf.default.rp_filter\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.rp_filter\n net.ipv4.conf.default.rp_filter = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-92253","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92253.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-92253","rid":"SV-102355r1_rule","stig_id":"RHEL-07-040612","fix_id":"F-98475r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible by default.","waiver_data":{}},{"code":"control \"V-92255\" do\n title \"The Red Hat Enterprise Linux operating system must have a host-based\nintrusion detection tool installed.\"\n desc \"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Ask the SA or ISSO if a host-based intrusion detection application is\nloaded on the system. Per OPORD 16-0080, the preferred intrusion detection\nsystem is McAfee HBSS available through the U.S. Cyber Command (USCYBERCOM).\n\n If another host-based intrusion detection application is in use, such as\nSELinux, this must be documented and approved by the local Authorizing Official.\n\n Procedure:\n Examine the system to determine if the Host Intrusion Prevention System\n(HIPS) is installed:\n\n # rpm -qa | grep MFEhiplsm\n\n Verify that the McAfee HIPS module is active on the system:\n\n # ps -ef | grep -i “hipclient”\n\n If the MFEhiplsm package is not installed, check for another intrusion\ndetection system:\n\n # find / -name \n\n Where is the name of the primary application daemon to\ndetermine if the application is loaded on the system.\n\n Determine if the application is active on the system:\n\n # ps -ef | grep -i \n\n If the MFEhiplsm package is not installed and an alternate host-based\nintrusion detection application has not been documented for use, this is a\nfinding.\n\n If no host-based intrusion detection system is installed and running on the\nsystem, this is a finding.\n \"\n desc \"fix\", \"\n Install and enable the latest McAfee HIPS package, available from\nUSCYBERCOM.\n\n Note: If the system does not support the McAfee HIPS package, install and\nenable a supported intrusion detection system application and document its use\nwith the Authorizing Official.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000196\"\n tag gid: \"V-92255\"\n tag rid: \"SV-102357r1_rule\"\n tag stig_id: \"RHEL-07-020019\"\n tag fix_id: \"F-98477r1_fix\"\n tag cci: [\"CCI-001263\"]\n tag nist: [\"SI-4 (5)\"]\n\n custom_hips = input('custom_hips')\n\n if ! custom_hips\n describe package('MFEhiplsm') do\n it { should be_installed }\n end\n describe processes(/hipclient/) do\n it { should exist }\n end\n else\n # Special case for SELinux\n sel_mode = command('getenforce').stdout.strip\n custom_hips_daemon = input('custom_hips_daemon')\n max_daemon_processes = input('max_daemon_processes')\n\n describe.one do\n describe \"SELinux mode\" do\n subject { sel_mode }\n it { should cmp 'Enforcing' }\n end\n describe processes(/#{custom_hips_daemon}/) do\n it { should exist }\n its('count') { should be < max_daemon_processes }\n end\n end\n end\nend\n","desc":"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.","descriptions":[{"data":"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.","label":"default"},{"data":"","label":"rationale"},{"data":"Ask the SA or ISSO if a host-based intrusion detection application is\nloaded on the system. Per OPORD 16-0080, the preferred intrusion detection\nsystem is McAfee HBSS available through the U.S. Cyber Command (USCYBERCOM).\n\n If another host-based intrusion detection application is in use, such as\nSELinux, this must be documented and approved by the local Authorizing Official.\n\n Procedure:\n Examine the system to determine if the Host Intrusion Prevention System\n(HIPS) is installed:\n\n # rpm -qa | grep MFEhiplsm\n\n Verify that the McAfee HIPS module is active on the system:\n\n # ps -ef | grep -i “hipclient”\n\n If the MFEhiplsm package is not installed, check for another intrusion\ndetection system:\n\n # find / -name \n\n Where is the name of the primary application daemon to\ndetermine if the application is loaded on the system.\n\n Determine if the application is active on the system:\n\n # ps -ef | grep -i \n\n If the MFEhiplsm package is not installed and an alternate host-based\nintrusion detection application has not been documented for use, this is a\nfinding.\n\n If no host-based intrusion detection system is installed and running on the\nsystem, this is a finding.","label":"check"},{"data":"Install and enable the latest McAfee HIPS package, available from\nUSCYBERCOM.\n\n Note: If the system does not support the McAfee HIPS package, install and\nenable a supported intrusion detection system application and document its use\nwith the Authorizing Official.","label":"fix"}],"id":"V-92255","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92255.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000196","gid":"V-92255","rid":"SV-102357r1_rule","stig_id":"RHEL-07-020019","fix_id":"F-98477r1_fix","cci":["CCI-001263"],"nist":["SI-4 (5)"]},"title":"The Red Hat Enterprise Linux operating system must have a host-based\nintrusion detection tool installed.","waiver_data":{}},{"code":"control \"V-94843\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled in the GUI.\"\n desc \"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active in the GUI with\nthe following command:\n\n # grep logout /etc/dconf/local.d/*\n\n logout=''\n\n If \\\"logout\\\" is not set to use two single quotations, or is missing, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the system to disable the Ctrl-Alt-Delete sequence for the GUI\nwith the following command:\n\n # touch /etc/dconf/db/local.d/00-disable-CAD\n\n Add the setting to disable the Ctrl-Alt-Delete sequence for GNOME:\n\n [org/gnome/settings-daemon/plugins/media-keys]\n logout=''\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-94843\"\n tag rid: \"SV-104673r1_rule\"\n tag stig_id: \"RHEL-07-020231\"\n tag fix_id: \"F-100967r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n unless package('gnome-settings-daemon').installed?\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n else \n describe command(\"gsettings get org.gnome.settings-daemon.media-keys logout\") do\n its('stdout.strip') { should cmp \"''\" }\n end \n end\nend\n","desc":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","descriptions":[{"data":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active in the GUI with\nthe following command:\n\n # grep logout /etc/dconf/local.d/*\n\n logout=''\n\n If \"logout\" is not set to use two single quotations, or is missing, this\nis a finding.","label":"check"},{"data":"Configure the system to disable the Ctrl-Alt-Delete sequence for the GUI\nwith the following command:\n\n # touch /etc/dconf/db/local.d/00-disable-CAD\n\n Add the setting to disable the Ctrl-Alt-Delete sequence for GNOME:\n\n [org/gnome/settings-daemon/plugins/media-keys]\n logout=''","label":"fix"}],"id":"V-94843","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-94843.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-94843","rid":"SV-104673r1_rule","stig_id":"RHEL-07-020231","fix_id":"F-100967r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled in the GUI.","waiver_data":{}}],"copyright_email":".","depends":[{"name":"example-inspec-overlay-profile-against-rhel7-stig-baseline-profile","status":"loaded","url":"https://github.com/ejaronne/example-inspec-overlay-profile-against-rhel7-stig-baseline-profile/archive/main.tar.gz"}],"groups":[{"controls":["V-71849"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71849.rb"},{"controls":["V-71855"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71855.rb"},{"controls":["V-71859"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71859.rb"},{"controls":["V-71861"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71861.rb"},{"controls":["V-71863"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71863.rb"},{"controls":["V-71891"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71891.rb"},{"controls":["V-71893"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71893.rb"},{"controls":["V-71897"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71897.rb"},{"controls":["V-71899"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71899.rb"},{"controls":["V-71901"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71901.rb"},{"controls":["V-71903"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71903.rb"},{"controls":["V-71905"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71905.rb"},{"controls":["V-71907"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71907.rb"},{"controls":["V-71909"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71909.rb"},{"controls":["V-71911"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71911.rb"},{"controls":["V-71913"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71913.rb"},{"controls":["V-71915"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71915.rb"},{"controls":["V-71917"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71917.rb"},{"controls":["V-71919"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71919.rb"},{"controls":["V-71921"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71921.rb"},{"controls":["V-71923"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71923.rb"},{"controls":["V-71925"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71925.rb"},{"controls":["V-71927"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71927.rb"},{"controls":["V-71929"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71929.rb"},{"controls":["V-71931"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71931.rb"},{"controls":["V-71933"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71933.rb"},{"controls":["V-71935"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71935.rb"},{"controls":["V-71937"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71937.rb"},{"controls":["V-71939"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71939.rb"},{"controls":["V-71941"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71941.rb"},{"controls":["V-71943"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71943.rb"},{"controls":["V-71945"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71945.rb"},{"controls":["V-71947"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71947.rb"},{"controls":["V-71949"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71949.rb"},{"controls":["V-71951"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71951.rb"},{"controls":["V-71953"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71953.rb"},{"controls":["V-71955"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71955.rb"},{"controls":["V-71957"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71957.rb"},{"controls":["V-71959"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71959.rb"},{"controls":["V-71961"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71961.rb"},{"controls":["V-71963"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71963.rb"},{"controls":["V-71965"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71965.rb"},{"controls":["V-71967"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71967.rb"},{"controls":["V-71969"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71969.rb"},{"controls":["V-71971"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71971.rb"},{"controls":["V-71973"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71973.rb"},{"controls":["V-71975"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71975.rb"},{"controls":["V-71977"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71977.rb"},{"controls":["V-71979"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71979.rb"},{"controls":["V-71983"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71983.rb"},{"controls":["V-71985"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71985.rb"},{"controls":["V-71987"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71987.rb"},{"controls":["V-71989"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71989.rb"},{"controls":["V-71991"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71991.rb"},{"controls":["V-71993"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71993.rb"},{"controls":["V-71995"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71995.rb"},{"controls":["V-71997"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71997.rb"},{"controls":["V-71999"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71999.rb"},{"controls":["V-72001"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72001.rb"},{"controls":["V-72003"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72003.rb"},{"controls":["V-72005"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72005.rb"},{"controls":["V-72007"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72007.rb"},{"controls":["V-72009"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72009.rb"},{"controls":["V-72011"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72011.rb"},{"controls":["V-72013"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72013.rb"},{"controls":["V-72015"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72015.rb"},{"controls":["V-72017"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72017.rb"},{"controls":["V-72019"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72019.rb"},{"controls":["V-72021"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72021.rb"},{"controls":["V-72023"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72023.rb"},{"controls":["V-72025"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72025.rb"},{"controls":["V-72027"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72027.rb"},{"controls":["V-72029"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72029.rb"},{"controls":["V-72031"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72031.rb"},{"controls":["V-72033"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72033.rb"},{"controls":["V-72035"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72035.rb"},{"controls":["V-72037"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72037.rb"},{"controls":["V-72039"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72039.rb"},{"controls":["V-72041"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72041.rb"},{"controls":["V-72043"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72043.rb"},{"controls":["V-72045"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72045.rb"},{"controls":["V-72047"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72047.rb"},{"controls":["V-72049"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72049.rb"},{"controls":["V-72051"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72051.rb"},{"controls":["V-72053"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72053.rb"},{"controls":["V-72055"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72055.rb"},{"controls":["V-72057"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72057.rb"},{"controls":["V-72059"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72059.rb"},{"controls":["V-72061"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72061.rb"},{"controls":["V-72063"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72063.rb"},{"controls":["V-72065"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72065.rb"},{"controls":["V-72067"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72067.rb"},{"controls":["V-72069"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72069.rb"},{"controls":["V-72071"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72071.rb"},{"controls":["V-72073"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72073.rb"},{"controls":["V-72075"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72075.rb"},{"controls":["V-72077"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72077.rb"},{"controls":["V-72079"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72079.rb"},{"controls":["V-72081"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72081.rb"},{"controls":["V-72083"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72083.rb"},{"controls":["V-72085"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72085.rb"},{"controls":["V-72087"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72087.rb"},{"controls":["V-72089"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72089.rb"},{"controls":["V-72091"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72091.rb"},{"controls":["V-72093"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72093.rb"},{"controls":["V-72095"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72095.rb"},{"controls":["V-72097"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72097.rb"},{"controls":["V-72099"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72099.rb"},{"controls":["V-72101"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72101.rb"},{"controls":["V-72103"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72103.rb"},{"controls":["V-72105"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72105.rb"},{"controls":["V-72107"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72107.rb"},{"controls":["V-72109"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72109.rb"},{"controls":["V-72111"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72111.rb"},{"controls":["V-72113"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72113.rb"},{"controls":["V-72115"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72115.rb"},{"controls":["V-72117"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72117.rb"},{"controls":["V-72119"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72119.rb"},{"controls":["V-72121"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72121.rb"},{"controls":["V-72123"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72123.rb"},{"controls":["V-72125"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72125.rb"},{"controls":["V-72127"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72127.rb"},{"controls":["V-72129"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72129.rb"},{"controls":["V-72131"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72131.rb"},{"controls":["V-72133"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72133.rb"},{"controls":["V-72135"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72135.rb"},{"controls":["V-72137"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72137.rb"},{"controls":["V-72139"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72139.rb"},{"controls":["V-72141"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72141.rb"},{"controls":["V-72145"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72145.rb"},{"controls":["V-72147"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72147.rb"},{"controls":["V-72149"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72149.rb"},{"controls":["V-72151"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72151.rb"},{"controls":["V-72153"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72153.rb"},{"controls":["V-72155"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72155.rb"},{"controls":["V-72157"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72157.rb"},{"controls":["V-72159"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72159.rb"},{"controls":["V-72161"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72161.rb"},{"controls":["V-72163"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72163.rb"},{"controls":["V-72165"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72165.rb"},{"controls":["V-72167"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72167.rb"},{"controls":["V-72171"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72171.rb"},{"controls":["V-72173"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72173.rb"},{"controls":["V-72175"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72175.rb"},{"controls":["V-72177"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72177.rb"},{"controls":["V-72179"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72179.rb"},{"controls":["V-72183"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72183.rb"},{"controls":["V-72185"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72185.rb"},{"controls":["V-72187"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72187.rb"},{"controls":["V-72189"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72189.rb"},{"controls":["V-72191"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72191.rb"},{"controls":["V-72197"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72197.rb"},{"controls":["V-72199"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72199.rb"},{"controls":["V-72201"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72201.rb"},{"controls":["V-72203"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72203.rb"},{"controls":["V-72205"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72205.rb"},{"controls":["V-72207"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72207.rb"},{"controls":["V-72209"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72209.rb"},{"controls":["V-72211"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72211.rb"},{"controls":["V-72213"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72213.rb"},{"controls":["V-72217"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72217.rb"},{"controls":["V-72219"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72219.rb"},{"controls":["V-72221"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72221.rb"},{"controls":["V-72223"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72223.rb"},{"controls":["V-72225"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72225.rb"},{"controls":["V-72227"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72227.rb"},{"controls":["V-72229"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72229.rb"},{"controls":["V-72231"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72231.rb"},{"controls":["V-72233"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72233.rb"},{"controls":["V-72235"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72235.rb"},{"controls":["V-72237"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72237.rb"},{"controls":["V-72239"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72239.rb"},{"controls":["V-72241"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72241.rb"},{"controls":["V-72243"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72243.rb"},{"controls":["V-72245"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72245.rb"},{"controls":["V-72247"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72247.rb"},{"controls":["V-72249"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72249.rb"},{"controls":["V-72251"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72251.rb"},{"controls":["V-72253"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72253.rb"},{"controls":["V-72255"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72255.rb"},{"controls":["V-72257"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72257.rb"},{"controls":["V-72259"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72259.rb"},{"controls":["V-72261"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72261.rb"},{"controls":["V-72263"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72263.rb"},{"controls":["V-72265"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72265.rb"},{"controls":["V-72267"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72267.rb"},{"controls":["V-72269"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72269.rb"},{"controls":["V-72273"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72273.rb"},{"controls":["V-72275"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72275.rb"},{"controls":["V-72277"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72277.rb"},{"controls":["V-72279"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72279.rb"},{"controls":["V-72281"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72281.rb"},{"controls":["V-72283"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72283.rb"},{"controls":["V-72285"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72285.rb"},{"controls":["V-72287"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72287.rb"},{"controls":["V-72289"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72289.rb"},{"controls":["V-72291"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72291.rb"},{"controls":["V-72293"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72293.rb"},{"controls":["V-72295"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72295.rb"},{"controls":["V-72297"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72297.rb"},{"controls":["V-72299"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72299.rb"},{"controls":["V-72301"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72301.rb"},{"controls":["V-72303"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72303.rb"},{"controls":["V-72305"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72305.rb"},{"controls":["V-72307"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72307.rb"},{"controls":["V-72309"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72309.rb"},{"controls":["V-72311"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72311.rb"},{"controls":["V-72313"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72313.rb"},{"controls":["V-72315"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72315.rb"},{"controls":["V-72317"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72317.rb"},{"controls":["V-72319"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72319.rb"},{"controls":["V-72417"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72417.rb"},{"controls":["V-72427"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72427.rb"},{"controls":["V-72433"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72433.rb"},{"controls":["V-73155"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73155.rb"},{"controls":["V-73157"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73157.rb"},{"controls":["V-73159"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73159.rb"},{"controls":["V-73161"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73161.rb"},{"controls":["V-73163"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73163.rb"},{"controls":["V-73165"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73165.rb"},{"controls":["V-73167"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73167.rb"},{"controls":["V-73171"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73171.rb"},{"controls":["V-73173"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73173.rb"},{"controls":["V-73175"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73175.rb"},{"controls":["V-73177"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73177.rb"},{"controls":["V-77819"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77819.rb"},{"controls":["V-77821"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77821.rb"},{"controls":["V-77823"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77823.rb"},{"controls":["V-77825"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77825.rb"},{"controls":["V-78995"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78995.rb"},{"controls":["V-78997"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78997.rb"},{"controls":["V-78999"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78999.rb"},{"controls":["V-79001"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-79001.rb"},{"controls":["V-81003"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81003.rb"},{"controls":["V-81005"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81005.rb"},{"controls":["V-81007"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81007.rb"},{"controls":["V-81009"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81009.rb"},{"controls":["V-81011"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81011.rb"},{"controls":["V-81013"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81013.rb"},{"controls":["V-81015"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81015.rb"},{"controls":["V-81017"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81017.rb"},{"controls":["V-81019"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81019.rb"},{"controls":["V-81021"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81021.rb"},{"controls":["V-92251"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92251.rb"},{"controls":["V-92253"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92253.rb"},{"controls":["V-92255"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92255.rb"},{"controls":["V-94843"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-94843.rb"}],"license":"Apache-2.0","maintainer":"Example project2","name":"second-layer-example-inspec-overlay-profile-against-1st-layer-example-inspec-overlay-profile","sha256":"fc0f6db0597cff55669b412aa860907e4eaf1f8fb9ffe549853dcbf8d6a0a4ca","status":"loaded","status_message":"","summary":"Example InSpec profile using dependency feature, aka 'overlay'","supports":[],"title":"second-layer-example-inspec-overlay-profile-against-1st-layer-example-inspec-overlay-profile","version":"2.6.1"},{"attributes":[],"controls":[{"code":"","desc":"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.","descriptions":[{"data":"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file permissions, ownership, and group membership of system\nfiles and commands match the vendor values.\n\n Check the default file permissions, ownership, and group membership of\nsystem files and commands with the following command:\n\n # for i in `rpm -Va | egrep -i '^\\.[M|U|G|.]{8}' | cut -d \" \" -f4,5`;do\nfor j in `rpm -qf $i`;do rpm -ql $j --dump | cut -d \" \" -f1,5,6,7 | grep\n$i;done;done\n\n /var/log/gdm 040755 root root\n /etc/audisp/audisp-remote.conf 0100640 root root\n /usr/bin/passwd 0104755 root root\n\n For each file returned, verify the current permissions, ownership, and\ngroup membership:\n # ls -la \n\n -rw-------. 1 root root 133 Jan 11 13:25 /etc/audisp/audisp-remote.conf\n\n If the file is more permissive than the default permissions, this is a\nfinding.\n\n If the file is not owned by the default owner and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.\n\n If the file is not a member of the default group and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.","label":"check"},{"data":"Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n Reset the user and group ownership of files within a package with the\nfollowing command:\n\n #rpm --setugids \n\n\n Reset the permissions of files within a package with the following command:\n\n #rpm --setperms ","label":"fix"}],"id":"V-71849","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71849.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000257-GPOS-00098","satisfies":["SRG-OS-000257-GPOS-00098","SRG-OS-000278-GPOS-00108"],"gid":"V-71849","rid":"SV-86473r4_rule","stig_id":"RHEL-07-010010","fix_id":"F-78201r4_fix","cci":["CCI-001494","CCI-001496","CCI-002165","CCI-002235"],"nist":["AU-9","AU-9 (3)","AC-3 (4)","AC-6 (10)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file permissions, ownership, and group membership of system files and\ncommands match the vendor values.","waiver_data":{}},{"code":"","desc":"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the cryptographic hash of system files and commands match the vendor\nvalues.\n\n Check the cryptographic hash of system files and commands with the\nfollowing command:\n\n Note: System configuration files (indicated by a \"c\" in the second\ncolumn) are expected to change over time. Unusual modifications should be\ninvestigated through the system audit log.\n\n # rpm -Va --noconfig | grep '^..5'\n\n If there is any output from the command for system files or binaries, this\nis a finding.","label":"check"},{"data":"Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh ","label":"fix"}],"id":"V-71855","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71855.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71855","rid":"SV-86479r4_rule","stig_id":"RHEL-07-010020","fix_id":"F-78207r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cryptographic hash of system files and commands matches vendor values.","waiver_data":{}},{"code":"","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a graphical\nuser logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the operating system displays a banner at the logon screen\nwith the following command:\n\n # grep banner-message-enable /etc/dconf/db/local.d/*\n banner-message-enable=true\n\n If \"banner-message-enable\" is set to \"false\" or is missing, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/01-banner-message\n\n Add the following line to the [org/gnome/login-screen] section of the\n\"/etc/dconf/db/local.d/01-banner-message\":\n\n [org/gnome/login-screen]\n banner-message-enable=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71859","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71859.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-71859","rid":"SV-86483r4_rule","stig_id":"RHEL-07-010030","fix_id":"F-78211r4_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a graphical user logon.","waiver_data":{}},{"code":"","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the approved Standard Mandatory DoD\nNotice and Consent Banner before granting access to the operating system via a\ngraphical user logon.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Check that the operating system displays the exact approved Standard\nMandatory DoD Notice and Consent Banner text with the command:\n # grep banner-message-text /etc/dconf/db/local.d/*\n banner-message-text=\n 'You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(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\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \" \" characters are for formatting only. They will not be displayed on the\nGUI.\n If the banner does not match the approved Standard Mandatory DoD Notice and\nConsent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the approved Standard Mandatory\nDoD Notice and Consent Banner before granting access to the system.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n # touch /etc/dconf/db/local.d/01-banner-message\n Add the following line to the [org/gnome/login-screen] section of the\n\"/etc/dconf/db/local.d/01-banner-message\":\n [org/gnome/login-screen]\n banner-message-enable=true\n banner-message-text='You are accessing a U.S. Government (USG) Information\nSystem (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(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\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \" \" characters are for formatting only. They will not be displayed on the\nGUI.\n Run the following command to update the database:\n # dconf update","label":"fix"}],"id":"V-71861","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71861.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-71861","rid":"SV-86485r4_rule","stig_id":"RHEL-07-010040","fix_id":"F-78213r5_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\napproved Standard Mandatory DoD Notice and Consent Banner before granting local\nor remote access to the system via a graphical user logon.","waiver_data":{}},{"code":"","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a command\nline user logon.\n\n Check to see if the operating system displays a banner at the command line\nlogon screen with the following command:\n\n # more /etc/issue\n\n The command should return the following text:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n If the operating system does not display a graphical logon banner or the\nbanner does not match the Standard Mandatory DoD Notice and Consent Banner,\nthis is a finding.\n\n If the text in the \"/etc/issue\" file does not match the Standard\nMandatory DoD Notice and Consent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the command line by\nediting the \"/etc/issue\" file.\n\n Replace the default text with the Standard Mandatory DoD Notice and Consent\nBanner. The DoD required text is:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"fix"}],"id":"V-71863","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71863.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007"],"gid":"V-71863","rid":"SV-86487r3_rule","stig_id":"RHEL-07-010050","fix_id":"F-78217r2_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a command line user logon.","waiver_data":{}},{"code":"","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enables a user's session lock until that user\nre-establishes access using established identification and authentication\nprocedures. The screen program must be installed to lock sessions on the\nconsole.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the screen lock is enabled with the following command:\n\n # grep -i lock-enabled /etc/dconf/db/local.d/*\n lock-enabled=true\n\n If the \"lock-enabled\" setting is missing or is not set to \"true\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to enable a user's session lock until that\nuser re-establishes access using established identification and authentication\nprocedures.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following example:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit the \"[org/gnome/desktop/screensaver]\" section of the database file\nand add or update the following lines:\n\n # Set this to true to lock the screen when the screensaver activates\n lock-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71891","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71891.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000028-GPOS-00009","satisfies":["SRG-OS-000028-GPOS-00009","SRG-OS-000030-GPOS-00011"],"gid":"V-71891","rid":"SV-86515r6_rule","stig_id":"RHEL-07-010060","fix_id":"F-78243r9_fix","cci":["CCI-000056"],"nist":["AC-11 b"]},"title":"The Red Hat Enterprise Linux operating system must enable a user\nsession lock until that user re-establishes access using established\nidentification and authentication procedures.","waiver_data":{}},{"code":"","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if GNOME is configured to display a screensaver after a 15\nminute delay with the following command:\n\n # grep -i idle-delay /etc/dconf/db/local.d/*\n idle-delay=uint32 900\n\n If the \"idle-delay\" setting is missing or is not set to \"900\" or less,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to initiate a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit /etc/dconf/db/local.d/00-screensaver and add or update the following\nlines:\n\n [org/gnome/desktop/session]\n # Set the lock time out to 900 seconds before the session is considered idle\n idle-delay=uint32 900\n\n You must include the \"uint32\" along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71893","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71893.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71893","rid":"SV-86517r5_rule","stig_id":"RHEL-07-010070","fix_id":"F-78245r5_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a\nscreensaver after a 15-minute period of inactivity for graphical user\ninterfaces.","waiver_data":{}},{"code":"","desc":": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.","descriptions":[{"data":": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system has the screen package installed.\n\n Check to see if the screen package is installed with the following command:\n\n # yum list installed screen\n screen-4.3.1-3-x86_64.rpm\n\n If the screen package is not installed, check to see if the tmux package is\ninstalled with the following command:\n\n #yum list installed tmux\n tmux-1.8-4.el7.x86_64.rpm\n\n If either the screen package or the tmux package is not installed, this is\na finding.","label":"check"},{"data":"Install the screen package to allow the initiation of a session lock after\na 15-minute period of inactivity.\n\n Install the screen program (if it is not on the system) with the following\ncommand:\n\n # yum install screen\n\n OR\n\n Install the tmux program (if it is not on the system) with the following\ncommand:\n\n #yum install tmux","label":"fix"}],"id":"V-71897","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71897.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71897","rid":"SV-86521r3_rule","stig_id":"RHEL-07-010090","fix_id":"F-78249r3_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must have the screen\npackage installed.","waiver_data":{}},{"code":"","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have a Graphical User Interface installed,\nthis requirement is Not Applicable.\n\n Check for the session lock settings with the following commands:\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/*\n\n idle-activation-enabled=true\n\n If \"idle-activation-enabled\" is not set to \"true\", this is a finding.","label":"check"},{"data":"Configure the operating system to initiate a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable screensaver locking after 15 minutes of\ninactivity:\n\n [org/gnome/desktop/screensaver]\n\n idle-activation-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71899","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71899.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71899","rid":"SV-86523r5_rule","stig_id":"RHEL-07-010100","fix_id":"F-78251r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a session\nlock for the screensaver after a period of inactivity for graphical user\ninterfaces.","waiver_data":{}},{"code":"","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a session lock a for graphical user\ninterfaces when the screensaver is activated.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n If GNOME is installed, check to see a session lock occurs when the\nscreensaver is activated with the following command:\n\n # grep -i lock-delay /etc/dconf/db/local.d/*\n lock-delay=uint32 5\n\n If the \"lock-delay\" setting is missing, or is not set to \"5\" or less,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to initiate a session lock for graphical\nuser interfaces when a screensaver is activated.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable session locking when a screensaver is activated:\n\n [org/gnome/desktop/screensaver]\n lock-delay=uint32 5\n\n The \"uint32\" must be included along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71901","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71901.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71901","rid":"SV-86525r3_rule","stig_id":"RHEL-07-010110","fix_id":"F-78253r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a session\nlock for graphical user interfaces when the screensaver is activated.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of upper-case characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"ucredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep ucredit /etc/security/pwquality.conf\n ucredit = -1\n\n If the value of \"ucredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one upper-case character be used by setting the \"ucredit\"\noption.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n ucredit = -1","label":"fix"}],"id":"V-71903","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71903.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-71903","rid":"SV-86527r3_rule","stig_id":"RHEL-07-010120","fix_id":"F-78255r1_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one upper-case character.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of lower-case characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"lcredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep lcredit /etc/security/pwquality.conf\n lcredit = -1\n\n If the value of \"lcredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the system to require at least one lower-case character when\ncreating or changing a password.\n\n Add or modify the following line\n in \"/etc/security/pwquality.conf\":\n\n lcredit = -1","label":"fix"}],"id":"V-71905","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71905.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000070-GPOS-00038","gid":"V-71905","rid":"SV-86529r5_rule","stig_id":"RHEL-07-010130","fix_id":"F-78257r6_fix","cci":["CCI-000193"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one lower-case character.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of numeric characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"dcredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep dcredit /etc/security/pwquality.conf\n dcredit = -1\n\n If the value of \"dcredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one numeric character be used by setting the \"dcredit\" option.\n\n Add the following line to /etc/security/pwquality.conf (or modify the line\nto have the required value):\n\n dcredit = -1","label":"fix"}],"id":"V-71907","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71907.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000071-GPOS-00039","gid":"V-71907","rid":"SV-86531r3_rule","stig_id":"RHEL-07-010140","fix_id":"F-78259r1_fix","cci":["CCI-000194"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are assigned, the new password\nmust contain at least one numeric character.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces password complexity by requiring that\nat least one special character be used.\n\n Note: The value to require a number of special characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"ocredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep ocredit /etc/security/pwquality.conf\n ocredit=-1\n\n If the value of \"ocredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one special character be used by setting the \"ocredit\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n ocredit = -1","label":"fix"}],"id":"V-71909","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71909.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000266-GPOS-00101","gid":"V-71909","rid":"SV-86533r2_rule","stig_id":"RHEL-07-010150","fix_id":"F-78261r2_fix","cci":["CCI-001619"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one special character.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"difok\" option sets the number of characters in a password that must\nnot be present in the old password.\n\n Check for the value of the \"difok\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep difok /etc/security/pwquality.conf\n difok = 8\n\n If the value of \"difok\" is set to less than \"8\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of at least eight of\nthe total number of characters when passwords are changed by setting the\n\"difok\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n difok = 8","label":"fix"}],"id":"V-71911","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71911.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71911","rid":"SV-86535r2_rule","stig_id":"RHEL-07-010160","fix_id":"F-78263r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of eight of the total number of\ncharacters must be changed.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"minclass\" option sets the minimum number of required classes of\ncharacters for the new password (digits, upper-case, lower-case, others).\n\n Check for the value of the \"minclass\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep minclass /etc/security/pwquality.conf\n minclass = 4\n\n If the value of \"minclass\" is set to less than \"4\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of at least four\ncharacter classes when passwords are changed by setting the \"minclass\" option.\n\n Add the following line to \"/etc/security/pwquality.conf conf\" (or modify\nthe line to have the required value):\n\n minclass = 4","label":"fix"}],"id":"V-71913","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71913.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71913","rid":"SV-86537r2_rule","stig_id":"RHEL-07-010170","fix_id":"F-78265r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of four character classes must be\nchanged.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"maxrepeat\" option sets the maximum number of allowed same\nconsecutive characters in a new password.\n\n Check for the value of the \"maxrepeat\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep maxrepeat /etc/security/pwquality.conf\n maxrepeat = 3\n\n If the value of \"maxrepeat\" is set to more than \"3\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of the number of\nrepeating consecutive characters when passwords are changed by setting the\n\"maxrepeat\" option.\n\n Add the following line to \"/etc/security/pwquality.conf conf\" (or modify\nthe line to have the required value):\n\n maxrepeat = 3","label":"fix"}],"id":"V-71915","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71915.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71915","rid":"SV-86539r3_rule","stig_id":"RHEL-07-010180","fix_id":"F-78267r2_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating consecutive characters\nmust not be more than three characters.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"maxclassrepeat\" option sets the maximum number of allowed same\nconsecutive characters in the same class in the new password.\n\n Check for the value of the \"maxclassrepeat\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep maxclassrepeat /etc/security/pwquality.conf\n maxclassrepeat = 4\n\n If the value of \"maxclassrepeat\" is set to more than \"4\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to require the change of the number of\nrepeating characters of the same character class when passwords are changed by\nsetting the \"maxclassrepeat\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" conf (or modify\nthe line to have the required value):\n\n maxclassrepeat = 4","label":"fix"}],"id":"V-71917","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71917.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71917","rid":"SV-86541r2_rule","stig_id":"RHEL-07-010190","fix_id":"F-78269r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating characters of the same\ncharacter class must not be more than four characters.","waiver_data":{}},{"code":"","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the PAM system service is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep password /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n Outcome should look like following:\n /etc/pam.d/system-auth-ac:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n /etc/pam.d/password-auth:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n\n If the \"/etc/pam.d/system-auth\" and \"/etc/pam.d/password-auth\"\nconfiguration files allow for password hashes other than SHA512 to be used,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add the following line in \"/etc/pam.d/system-auth\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Add the following line in \"/etc/pam.d/password-auth\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71919","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71919.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71919","rid":"SV-86543r3_rule","stig_id":"RHEL-07-010200","fix_id":"F-78271r4_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the PAM system service is configured to store only encrypted\nrepresentations of passwords.","waiver_data":{}},{"code":"","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system's shadow file is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep -i encrypt /etc/login.defs\n ENCRYPT_METHOD SHA512\n\n If the \"/etc/login.defs\" configuration file does not exist or allows for\npassword hashes other than SHA512 to be used, this is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \"/etc/login.defs\":\n\n ENCRYPT_METHOD SHA512","label":"fix"}],"id":"V-71921","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71921.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71921","rid":"SV-86545r2_rule","stig_id":"RHEL-07-010210","fix_id":"F-78273r1_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nuse the shadow file to store only encrypted representations of passwords.","waiver_data":{}},{"code":"","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the user and group account administration utilities are configured\nto store only encrypted representations of passwords. The strength of\nencryption that must be used to hash passwords for all accounts is \"SHA512\".\n\n Check that the system is configured to create \"SHA512\" hashed passwords\nwith the following command:\n\n # grep -i sha512 /etc/libuser.conf\n\n crypt_style = sha512\n\n If the \"crypt_style\" variable is not set to \"sha512\", is not in the\ndefaults section, is commented out, or does not exist, this is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \"/etc/libuser.conf\" in the [defaults]\nsection:\n\n crypt_style = sha512","label":"fix"}],"id":"V-71923","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71923.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71923","rid":"SV-86547r3_rule","stig_id":"RHEL-07-010220","fix_id":"F-78275r1_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat user and group account administration utilities are configured to store\nonly encrypted representations of passwords.","waiver_data":{}},{"code":"","desc":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","descriptions":[{"data":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces 24 hours/1 day as the minimum password\nlifetime for new user accounts.\n\n Check for the value of \"PASS_MIN_DAYS\" in \"/etc/login.defs\" with the\nfollowing command:\n\n # grep -i pass_min_days /etc/login.defs\n PASS_MIN_DAYS 1\n\n If the \"PASS_MIN_DAYS\" parameter value is not \"1\" or greater, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce 24 hours/1 day as the minimum\npassword lifetime.\n\n Add the following line in \"/etc/login.defs\" (or modify the line to have\nthe required value):\n\n PASS_MIN_DAYS 1","label":"fix"}],"id":"V-71925","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71925.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000075-GPOS-00043","gid":"V-71925","rid":"SV-86549r2_rule","stig_id":"RHEL-07-010230","fix_id":"F-78277r1_fix","cci":["CCI-000198"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 24 hours/1 day minimum\nlifetime.","waiver_data":{}},{"code":"","desc":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","descriptions":[{"data":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Check whether the minimum time period between password changes for each\nuser account is one day or greater.\n\n # awk -F: '$4 < 1 {print $1 \" \" $4}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.","label":"check"},{"data":"Configure non-compliant accounts to enforce a 24 hours/1 day minimum\npassword lifetime:\n\n # chage -m 1 [user]","label":"fix"}],"id":"V-71927","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71927.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000075-GPOS-00043","gid":"V-71927","rid":"SV-86551r2_rule","stig_id":"RHEL-07-010240","fix_id":"F-78279r1_fix","cci":["CCI-000198"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are restricted to a 24 hours/1 day minimum lifetime.","waiver_data":{}},{"code":"","desc":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","descriptions":[{"data":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system enforces a 60-day maximum password lifetime\nrestriction for new user accounts.\n\n Check for the value of \"PASS_MAX_DAYS\" in \"/etc/login.defs\" with the\nfollowing command:\n\n # grep -i pass_max_days /etc/login.defs\n PASS_MAX_DAYS 60\n\n If the \"PASS_MAX_DAYS\" parameter value is not 60 or less, or is commented\nout, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce a 60-day maximum password\nlifetime restriction.\n\n Add the following line in \"/etc/login.defs\" (or modify the line to have\nthe required value):\n\n PASS_MAX_DAYS 60","label":"fix"}],"id":"V-71929","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71929.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000076-GPOS-00044","gid":"V-71929","rid":"SV-86553r2_rule","stig_id":"RHEL-07-010250","fix_id":"F-78281r1_fix","cci":["CCI-000199"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 60-day maximum lifetime.","waiver_data":{}},{"code":"","desc":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","descriptions":[{"data":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Check whether the maximum time period for existing passwords is restricted\nto 60 days.\n\n # awk -F: '$5 > 60 {print $1 \" \" $5}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.","label":"check"},{"data":"Configure non-compliant accounts to enforce a 60-day maximum password\nlifetime restriction.\n\n # chage -M 60 [user]","label":"fix"}],"id":"V-71931","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71931.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000076-GPOS-00044","gid":"V-71931","rid":"SV-86555r3_rule","stig_id":"RHEL-07-010260","fix_id":"F-78283r1_fix","cci":["CCI-000199"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat existing passwords are restricted to a 60-day maximum lifetime.","waiver_data":{}},{"code":" control \"V-71933\" do\n impact 0.0\n desc 'caveat', 'This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords'\n describe 'This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords' do\n skip 'This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords'\n end\n end \n","desc":"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.","descriptions":[{"data":"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prohibits password reuse for a minimum of five\ngenerations.\n\n Check for the value of the \"remember\" argument in\n\"/etc/pam.d/system-auth\" and \"/etc/pam.d/password-auth\" with the following\ncommand:\n\n # grep -i remember /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n If the line containing the \"pam_pwhistory.so\" line does not have the\n\"remember\" module argument set, is commented out, or the value of the\n\"remember\" module argument is set to less than \"5\", this is a finding.","label":"check"},{"data":"Configure the operating system to prohibit password reuse for a minimum of\nfive generations.\n\n Add the following line in \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" (or modify the line to have the required value):\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"},{"data":"This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords","label":"caveat"}],"id":"V-71933","impact":0,"refs":[{"ref":[]}],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71933.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000077-GPOS-00045","gid":"V-71933","rid":"SV-86557r3_rule","stig_id":"RHEL-07-010270","fix_id":"F-78285r3_fix","cci":["CCI-000200"],"nist":["IA-5 (1) (e)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are prohibited from reuse for a minimum of five generations.","waiver_data":{}},{"code":"","desc":"The shorter the password, the lower the number of possible\ncombinations that need to be tested before the password is compromised.\n\n Password complexity, or strength, is a measure of the effectiveness of a\npassword in resisting attempts at guessing and brute-force attacks. Password\nlength is one factor of several that helps to determine strength and how long\nit takes to crack a password. Use of more characters in a password helps to\nexponentially increase the time and/or resources required to compromise the\npassword.","descriptions":[{"data":"The shorter the password, the lower the number of possible\ncombinations that need to be tested before the password is compromised.\n\n Password complexity, or strength, is a measure of the effectiveness of a\npassword in resisting attempts at guessing and brute-force attacks. Password\nlength is one factor of several that helps to determine strength and how long\nit takes to crack a password. Use of more characters in a password helps to\nexponentially increase the time and/or resources required to compromise the\npassword.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces a minimum 24-character password\nlength. The \"minlen\" option sets the minimum number of characters in a new\npassword.\n\t\tCheck for the value of the \"minlen\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\t\t# grep minlen /etc/security/pwquality.conf\n\t\tminlen = 24\n\t\tIf the command does not return a \"minlen\" value of 24 or greater, this is\na finding.","label":"check"},{"data":"Configure operating system to enforce a minimum 24-character password\nlength.\n\t\tAdd the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\t\tminlen = 24","label":"fix"},{"data":"The project2 requires more secure password length of 24 characters as approved on 1/12/2022","label":"caveat"}],"id":"V-71935","impact":0.5,"refs":[{"ref":[]}],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71935.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000078-GPOS-00046","gid":"V-71935","rid":"SV-86559r2_rule","stig_id":"RHEL-07-010280","fix_id":"F-78287r1_fix","cci":["CCI-000205"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\n\tthat passwords are a minimum of 24 characters in length.","waiver_data":{}},{"code":"","desc":"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.","descriptions":[{"data":"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.","label":"default"},{"data":"","label":"rationale"},{"data":"To verify that null passwords cannot be used, run the following command:\n\n # grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n If this produces any output, it may be possible to log on with accounts\nwith empty passwords.\n\n If null passwords can be used, this is a finding.","label":"check"},{"data":"If an account is configured for password authentication but does not have\nan assigned password, it may be possible to log on to the account without\nauthenticating.\n\n Remove any instances of the \"nullok\" option in \"/etc/pam.d/system-auth\"\nand \"/etc/pam.d/password-auth\" to prevent logons with empty passwords.\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71937","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71937.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71937","rid":"SV-86561r3_rule","stig_id":"RHEL-07-010290","fix_id":"F-78289r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have accounts\nconfigured with blank or null passwords.","waiver_data":{}},{"code":"","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"To determine how the SSH daemon's \"PermitEmptyPasswords\" option is set,\nrun the following command:\n\n # grep -i PermitEmptyPasswords /etc/ssh/sshd_config\n PermitEmptyPasswords no\n\n If no line, a commented line, or a line indicating the value \"no\" is\nreturned, the required value is set.\n\n If the required value is not set, this is a finding.","label":"check"},{"data":"To explicitly disallow remote logon from accounts with empty passwords, add\nor correct the following line in \"/etc/ssh/sshd_config\":\n\n PermitEmptyPasswords no\n\n The SSH service must be restarted for changes to take effect. Any accounts\nwith empty passwords should be disabled immediately, and PAM configuration\nshould prevent users from being able to assign themselves empty passwords.","label":"fix"}],"id":"V-71939","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71939.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000106-GPOS-00053","gid":"V-71939","rid":"SV-86563r3_rule","stig_id":"RHEL-07-010300","fix_id":"F-78291r2_fix","cci":["CCI-000766"],"nist":["IA-2 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using an empty password.","waiver_data":{}},{"code":"","desc":"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.","descriptions":[{"data":"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system disables account identifiers (individuals,\ngroups, roles, and devices) after the password expires with the following\ncommand:\n\n # grep -i inactive /etc/default/useradd\n INACTIVE=0\n\n If the value is not set to \"0\", is commented out, or is not defined, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable account identifiers (individuals,\ngroups, roles, and devices) after the password expires.\n\n Add the following line to \"/etc/default/useradd\" (or modify the line to\nhave the required value):\n\n INACTIVE=0","label":"fix"}],"id":"V-71941","impact":0.5,"refs":[],"results":[],"source_location":{"line":1,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71941.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000118-GPOS-00060","gid":"V-71941","rid":"SV-86565r2_rule","stig_id":"RHEL-07-010310","fix_id":"F-78293r1_fix","cci":["CCI-000795"],"nist":["IA-4 e"]},"title":"The Red Hat Enterprise Linux operating system must disable account\nidentifiers (individuals, groups, roles, and devices) if the password expires.","waiver_data":{}},{"code":" control 'V-71943' do\n\ttitle \"The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 60 minutes after TEN unsuccessful logon attempts within a 120-minute timeframe.\"\n\t desc 'caveat', 'The project needs to set this to TEN since we have an approved risk-based decision on 10/2/2021 allowing it'\n\t desc 'check', \"\n\t Check that the system locks an account for a minimum of 60 minutes after\n\tTEN unsuccessful logon attempts within a period of 120 minutes with the\n\tfollowing command:\n\t # grep pam_faillock.so /etc/pam.d/password-auth\n\t auth required pam_faillock.so preauth silent audit deny=10 even_deny_root\n\tfail_interval=7200 unlock_time=3600\n\t auth [default=die] pam_faillock.so authfail audit deny=10 even_deny_root\n\tfail_interval=7200 unlock_time=3600\n\t account required pam_faillock.so\n\t If the \\\"deny\\\" parameter is set to \\\"0\\\" or a value less than \\\"10\\\" on\n\tboth \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module, or is missing from\n\tthese lines, this is a finding.\n\t If the \\\"even_deny_root\\\" parameter is not set on both \\\"auth\\\" lines with\n\tthe \\\"pam_faillock.so\\\" module, or is missing from these lines, this is a\n\tfinding.\n\t If the \\\"fail_interval\\\" parameter is set to \\\"0\\\" or is set to a value\n\tless than \\\"7200\\\" on both \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module,\n\tor is missing from these lines, this is a finding.\n\t If the \\\"unlock_time\\\" parameter is not set to \\\"0\\\", \\\"never\\\", or is set\n\tto a value less than \\\"3600\\\" on both \\\"auth\\\" lines with the\n\t\\\"pam_faillock.so\\\" module, or is missing from these lines, this is a finding.\n\t Note: The maximum configurable value for \\\"unlock_time\\\" is \\\"604800\\\".\n\t If any line referencing the \\\"pam_faillock.so\\\" module is commented out,\n\tthis is a finding.\n\t # grep pam_faillock.so /etc/pam.d/system-auth\n\t auth required pam_faillock.so preauth silent audit deny=10 even_deny_root\n\tfail_interval=7200 unlock_time=3600\n\t auth [default=die] pam_faillock.so authfail audit deny=10 even_deny_root\n\tfail_interval=7200 unlock_time=3600\n\t account required pam_faillock.so\n\t If the \\\"deny\\\" parameter is set to \\\"0\\\" or a value less than \\\"10\\\" on\n\tboth \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module, or is missing from\n\tthese lines, this is a finding.\n\t If the \\\"even_deny_root\\\" parameter is not set on both \\\"auth\\\" lines with\n\tthe \\\"pam_faillock.so\\\" module, or is missing from these lines, this is a\n\tfinding.\n\t If the \\\"fail_interval\\\" parameter is set to \\\"0\\\" or is set to a value\n\tless than \\\"7200\\\" on both \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module,\n\tor is missing from these lines, this is a finding.\n\t If the \\\"unlock_time\\\" parameter is not set to \\\"0\\\", \\\"never\\\", or is set\n\tto a value less than \\\"3600\\\" on both \\\"auth\\\" lines with the\n\t\\\"pam_faillock.so\\\" module or is missing from these lines, this is a finding.\n\t Note: The maximum configurable value for \\\"unlock_time\\\" is \\\"604800\\\".\n\t If any line referencing the \\\"pam_faillock.so\\\" module is commented out,\n\tthis is a finding.\n\t \"\n\t desc 'fix', \"\n\t Configure the ACME operating system to lock an account for 60 minutes\n\twhen TEN unsuccessful logon attempts in 120 minutes are made.\n\t Modify the first three lines of the auth section and the first line of the\n\taccount section of the \\\"/etc/pam.d/system-auth\\\" and\n\t\\\"/etc/pam.d/password-auth\\\" files to match the following lines:\n\t auth required pam_faillock.so preauth silent audit deny=10 even_deny_root\n\tfail_interval=7200 unlock_time=3600\n\t auth sufficient pam_unix.so try_first_pass\n\t auth [default=die] pam_faillock.so authfail audit deny=10 even_deny_root\n\tfail_interval=7200 unlock_time=3600\n\t account required pam_faillock.so\n\t Note: Manual changes to the listed files may be overwritten by the\n\t\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\n\tthe configurations listed in this requirement.\n\t \"\n\tend\n","desc":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as\nbrute-forcing, is reduced. Limits are imposed by locking the account.","descriptions":[{"data":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as\nbrute-forcing, is reduced. Limits are imposed by locking the account.","label":"default"},{"data":"","label":"rationale"},{"data":"Check that the system locks an account for a minimum of 60 minutes after\n20 unsuccessful logon attempts within a period of 120 minutes with the\nfollowing command:\n\t\t# grep pam_faillock.so /etc/pam.d/password-auth\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tIf the \"deny\" parameter is set to \"0\" or a value less than \"20\" on\nboth \"auth\" lines with the \"pam_faillock.so\" module, or is missing from\nthese lines, this is a finding.\n\t\tIf the \"even_deny_root\" parameter is not set on both \"auth\" lines with\nthe \"pam_faillock.so\" module, or is missing from these lines, this is a\nfinding.\n\t\tIf the \"fail_interval\" parameter is set to \"0\" or is set to a value\nless than \"7200\" on both \"auth\" lines with the \"pam_faillock.so\" module,\nor is missing from these lines, this is a finding.\n\t\tIf the \"unlock_time\" parameter is not set to \"0\", \"never\", or is set\nto a value less than \"3600\" on both \"auth\" lines with the\n\"pam_faillock.so\" module, or is missing from these lines, this is a finding.\n\t\tNote: The maximum configurable value for \"unlock_time\" is \"604800\".\n\t\tIf any line referencing the \"pam_faillock.so\" module is commented out,\nthis is a finding.\n\t\t# grep pam_faillock.so /etc/pam.d/system-auth\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tIf the \"deny\" parameter is set to \"0\" or a value less than \"20\" on\nboth \"auth\" lines with the \"pam_faillock.so\" module, or is missing from\nthese lines, this is a finding.\n\t\tIf the \"even_deny_root\" parameter is not set on both \"auth\" lines with\nthe \"pam_faillock.so\" module, or is missing from these lines, this is a\nfinding.\n\t\tIf the \"fail_interval\" parameter is set to \"0\" or is set to a value\nless than \"7200\" on both \"auth\" lines with the \"pam_faillock.so\" module,\nor is missing from these lines, this is a finding.\n\t\tIf the \"unlock_time\" parameter is not set to \"0\", \"never\", or is set\nto a value less than \"3600\" on both \"auth\" lines with the\n\"pam_faillock.so\" module or is missing from these lines, this is a finding.\n\t\tNote: The maximum configurable value for \"unlock_time\" is \"604800\".\n\t\tIf any line referencing the \"pam_faillock.so\" module is commented out,\nthis is a finding.","label":"check"},{"data":"Configure the ACME operating system to lock an account for 60 minutes\nwhen 20 unsuccessful logon attempts in 120 minutes are made.\n\t\tModify the first three lines of the auth section and the first line of the\naccount section of the \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" files to match the following lines:\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth sufficient pam_unix.so try_first_pass\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tNote: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"},{"data":"The project2 needs to set this to 20 since we have an approved risk-based decision on 2/1/2022 allowing it","label":"caveat"}],"id":"V-71943","impact":0.5,"refs":[{"ref":[]},{"ref":[]}],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71943.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000329-GPOS-00128","satisfies":["SRG-OS-000329-GPOS-00128","SRG-OS-000021-GPOS-00005"],"gid":"V-71943","rid":"SV-86567r5_rule","stig_id":"RHEL-07-010320","fix_id":"F-78295r5_fix","cci":["CCI-000044","CCI-002236","CCI-002237","CCI-002238"],"nist":["AC-7 a","AC-7 b","AC-7 b","AC-7 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 60 minutes after 20 unsuccessful logon attempts within a 120-minute timeframe.","waiver_data":{}},{"code":"","desc":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.","descriptions":[{"data":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically locks the root account until it\nis released by an administrator when three unsuccessful logon attempts in 15\nminutes are made.\n\n # grep pam_faillock.so /etc/pam.d/password-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \"even_deny_root\" setting is not defined on both lines with the\n\"pam_faillock.so\" module, is commented out, or is missing from a line, this\nis a finding.\n\n # grep pam_faillock.so /etc/pam.d/system-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \"even_deny_root\" setting is not defined on both lines with the\n\"pam_faillock.so\" module, is commented out, or is missing from a line, this\nis a finding.","label":"check"},{"data":"Configure the operating system to lock automatically the root account until\nthe locked account is released by an administrator when three unsuccessful\nlogon attempts in 15 minutes are made.\n\n Modify the first three lines of the auth section and the first line of the\naccount section of the \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" files to match the following lines:\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth sufficient pam_unix.so try_first_pass\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71945","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71945.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000329-GPOS-00128","satisfies":["SRG-OS-000329-GPOS-00128","SRG-OS-000021-GPOS-00005"],"gid":"V-71945","rid":"SV-86569r4_rule","stig_id":"RHEL-07-010330","fix_id":"F-78297r3_fix","cci":["CCI-002238"],"nist":["AC-7 b"]},"title":"The Red Hat Enterprise Linux operating system must lock the associated\naccount after three unsuccessful root logon attempts are made within a\n15-minute period.","waiver_data":{}},{"code":"","desc":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.","descriptions":[{"data":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system requires users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" and \"/etc/sudoers.d/*\"\nfiles with the following command:\n\n # grep -i nopasswd /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \"NOPASSWD\" tag, this is a finding.","label":"check"},{"data":"Configure the operating system to require users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" file with the following\ncommand:\n # visudo\n\n Remove any occurrences of \"NOPASSWD\" tags in the file.\n\n Check the configuration of the /etc/sudoers.d/* files with the following\ncommand:\n # grep -i nopasswd /etc/sudoers.d/*\n\n Remove any occurrences of \"NOPASSWD\" tags in the file.","label":"fix"}],"id":"V-71947","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71947.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000373-GPOS-00156","satisfies":["SRG-OS-000373-GPOS-00156","SRG-OS-000373-GPOS-00157","SRG-OS-000373-GPOS-00158"],"gid":"V-71947","rid":"SV-86571r3_rule","stig_id":"RHEL-07-010340","fix_id":"F-78299r2_fix","cci":["CCI-002038"],"nist":["IA-11"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat users must provide a password for privilege escalation.","waiver_data":{}},{"code":"","desc":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.","descriptions":[{"data":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system requires users to reauthenticate for privilege\nescalation.\n\n Check the configuration of the \"/etc/sudoers\" and \"/etc/sudoers.d/*\"\nfiles with the following command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \"!authenticate\" tag, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to require users to reauthenticate for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" file with the following\ncommand:\n\n # visudo\n Remove any occurrences of \"!authenticate\" tags in the file.\n\n Check the configuration of the \"/etc/sudoers.d/*\" files with the\nfollowing command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n Remove any occurrences of \"!authenticate\" tags in the file(s).","label":"fix"}],"id":"V-71949","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71949.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000373-GPOS-00156","satisfies":["SRG-OS-000373-GPOS-00156","SRG-OS-000373-GPOS-00157","SRG-OS-000373-GPOS-00158"],"gid":"V-71949","rid":"SV-86573r3_rule","stig_id":"RHEL-07-010350","fix_id":"F-78301r3_fix","cci":["CCI-002038"],"nist":["IA-11"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat users must re-authenticate for privilege escalation.","waiver_data":{}},{"code":"","desc":"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.","descriptions":[{"data":"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces a delay of at least four seconds\nbetween console logon prompts following a failed logon attempt.\n\n Check the value of the \"fail_delay\" parameter in the \"/etc/login.defs\"\nfile with the following command:\n\n # grep -i fail_delay /etc/login.defs\n FAIL_DELAY 4\n\n If the value of \"FAIL_DELAY\" is not set to \"4\" or greater, or the line\nis commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce a delay of at least four seconds\nbetween logon prompts following a failed console logon attempt.\n\n Modify the \"/etc/login.defs\" file to set the \"FAIL_DELAY\" parameter to\n\"4\" or greater:\n\n FAIL_DELAY 4","label":"fix"}],"id":"V-71951","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71951.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00226","gid":"V-71951","rid":"SV-86575r2_rule","stig_id":"RHEL-07-010430","fix_id":"F-78303r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the delay between logon prompts following a failed console logon attempt\nis at least four seconds.","waiver_data":{}},{"code":"","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow an unattended or automatic logon\nto the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \"AutomaticLoginEnable\" in the\n\"/etc/gdm/custom.conf\" file with the following command:\n\n # grep -i automaticloginenable /etc/gdm/custom.conf\n AutomaticLoginEnable=false\n\n If the value of \"AutomaticLoginEnable\" is not set to \"false\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to not allow an unattended or automatic\nlogon to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \"AutomaticLoginEnable\" parameter in the\n[daemon] section of the \"/etc/gdm/custom.conf\" file to \"false\":\n\n [daemon]\n AutomaticLoginEnable=false","label":"fix"}],"id":"V-71953","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71953.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71953","rid":"SV-86577r2_rule","stig_id":"RHEL-07-010440","fix_id":"F-78305r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow an\nunattended or automatic logon to the system via a graphical user interface.","waiver_data":{}},{"code":"","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow an unrestricted logon to the\nsystem via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \"TimedLoginEnable\" parameter in\n\"/etc/gdm/custom.conf\" file with the following command:\n\n # grep -i timedloginenable /etc/gdm/custom.conf\n TimedLoginEnable=false\n\n If the value of \"TimedLoginEnable\" is not set to \"false\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to not allow an unrestricted account to log\non to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \"TimedLoginEnable\" parameter in the [daemon]\nsection of the \"/etc/gdm/custom.conf\" file to \"false\":\n\n [daemon]\n TimedLoginEnable=false","label":"fix"}],"id":"V-71955","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71955.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71955","rid":"SV-86579r3_rule","stig_id":"RHEL-07-010450","fix_id":"F-78307r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow an\nunrestricted logon to the system.","waiver_data":{}},{"code":"","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow users to override environment\nvariables to the SSH daemon.\n\n Check for the value of the \"PermitUserEnvironment\" keyword with the\nfollowing command:\n\n # grep -i permituserenvironment /etc/ssh/sshd_config\n PermitUserEnvironment no\n\n If the \"PermitUserEnvironment\" keyword is not set to \"no\", is missing,\nor is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to not allow users to override environment\nvariables to the SSH daemon.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for\n\"PermitUserEnvironment\" keyword and set the value to \"no\":\n\n PermitUserEnvironment no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-71957","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71957.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71957","rid":"SV-86581r3_rule","stig_id":"RHEL-07-010460","fix_id":"F-78309r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow users to\noverride SSH environment variables.","waiver_data":{}},{"code":"","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow a non-certificate trusted host\nSSH logon to the system.\n\n Check for the value of the \"HostbasedAuthentication\" keyword with the\nfollowing command:\n\n # grep -i hostbasedauthentication /etc/ssh/sshd_config\n HostbasedAuthentication no\n\n If the \"HostbasedAuthentication\" keyword is not set to \"no\", is\nmissing, or is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to not allow a non-certificate trusted host\nSSH logon to the system.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for\n\"HostbasedAuthentication\" keyword and set the value to \"no\":\n\n HostbasedAuthentication no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-71959","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71959.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71959","rid":"SV-86583r3_rule","stig_id":"RHEL-07-010470","fix_id":"F-78311r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow a\nnon-certificate trusted host SSH logon to the system.","waiver_data":{}},{"code":"","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use UEFI, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -i password_pbkdf2 /boot/grub2/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \"password_pbkdf2\", this is\na finding.\n\n If the \"superusers-account\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \"/etc/grub.d/40_custom\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\"root\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \"grub.conf\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/grub2/grub.cfg","label":"fix"}],"id":"V-71961","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71961.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-71961","rid":"SV-86585r6_rule","stig_id":"RHEL-07-010480","fix_id":"F-78313r3_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems prior to version 7.2 with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.","waiver_data":{}},{"code":"","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use BIOS, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -i password /boot/efi/EFI/redhat/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \"password_pbkdf2\", this is\na finding.\n\n If the \"superusers-account\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \"/etc/grub.d/40_custom\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\"root\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \"grub.conf\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg","label":"fix"}],"id":"V-71963","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71963.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-71963","rid":"SV-86587r4_rule","stig_id":"RHEL-07-010490","fix_id":"F-78315r3_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems prior to version 7.2 using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.","waiver_data":{}},{"code":"","desc":"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.","descriptions":[{"data":"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system requires multifactor authentication to uniquely\nidentify organizational users using multifactor authentication.\n\n Check to see if smartcard authentication is enforced on the system:\n\n # authconfig --test | grep \"pam_pkcs11 is enabled\"\n\n If no results are returned, this is a finding.\n\n # authconfig --test | grep \"smartcard removal action\"\n\n If \"smartcard removal action\" is blank, this is a finding.\n\n # authconfig --test | grep \"smartcard module\"\n\n If \"smartcard module\" is blank, this is a finding.","label":"check"},{"data":"Configure the operating system to require individuals to be authenticated\nwith a multifactor authenticator.\n\n Enable smartcard logons with the following commands:\n\n # authconfig --enablesmartcard --smartcardaction=0 --update\n # authconfig --enablerequiresmartcard -update\n\n Modify the \"/etc/pam_pkcs11/pkcs11_eventmgr.conf\" file to uncomment the\nfollowing line:\n\n #/usr/X11R6/bin/xscreensaver-command -lock\n\n Modify the \"/etc/pam_pkcs11/pam_pkcs11.conf\" file to use the cackey\nmodule if required.","label":"fix"}],"id":"V-71965","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71965.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000104-GPOS-00051","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"],"gid":"V-71965","rid":"SV-86589r2_rule","stig_id":"RHEL-07-010500","fix_id":"F-78317r3_fix","cci":["CCI-000766"],"nist":["IA-2 (2)"]},"title":"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate organizational users (or processes acting on behalf of\norganizational users) using multifactor authentication.","waiver_data":{}},{"code":"","desc":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.","descriptions":[{"data":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if the rsh-server package is installed with the following\ncommand:\n\n # yum list installed rsh-server\n\n If the rsh-server package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the rsh-server package from the system with the following command:\n\n # yum remove rsh-server","label":"fix"}],"id":"V-71967","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71967.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-71967","rid":"SV-86591r2_rule","stig_id":"RHEL-07-020000","fix_id":"F-78319r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the\nrsh-server package installed.","waiver_data":{}},{"code":"","desc":"Removing the \"ypserv\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.","descriptions":[{"data":"Removing the \"ypserv\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.","label":"default"},{"data":"","label":"rationale"},{"data":"The NIS service provides an unencrypted authentication service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n Check to see if the \"ypserve\" package is installed with the following\ncommand:\n\n # yum list installed ypserv\n\n If the \"ypserv\" package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the \"ypserv\" package from the system with the following command:\n\n # yum remove ypserv","label":"fix"}],"id":"V-71969","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71969.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-71969","rid":"SV-86593r2_rule","stig_id":"RHEL-07-020010","fix_id":"F-78321r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the ypserv\npackage installed.","waiver_data":{}},{"code":"","desc":"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.","descriptions":[{"data":"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system prevents non-privileged users from executing\nprivileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Get a list of authorized users (other than System Administrator and guest\naccounts) for the system.\n\n Check the list against the system by using the following command:\n\n # semanage login -l | more\n Login Name SELinux User MLS/MCS Range Service\n __default__ user_u s0-s0:c0.c1023 *\n root unconfined_u s0-s0:c0.c1023 *\n system_u system_u s0-s0:c0.c1023 *\n joe staff_u s0-s0:c0.c1023 *\n\n All administrators must be mapped to the \"sysadm_u\" or \"staff_u\" users\nrole.\n\n All authorized non-administrative users must be mapped to the \"user_u\"\nrole.\n\n If they are not mapped in this way, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent non-privileged users from\nexecuting privileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Use the following command to map a new user to the \"sysdam_u\" role:\n\n #semanage login -a -s sysadm_u \n\n Use the following command to map an existing user to the \"sysdam_u\" role:\n\n #semanage login -m -s sysadm_u \n\n Use the following command to map a new user to the \"staff_u\" role:\n\n #semanage login -a -s staff_u \n\n Use the following command to map an existing user to the \"staff_u\" role:\n\n #semanage login -m -s staff_u \n\n Use the following command to map a new user to the \"user_u\" role:\n\n # semanage login -a -s user_u \n\n Use the following command to map an existing user to the \"user_u\" role:\n\n # semanage login -m -s user_u ","label":"fix"}],"id":"V-71971","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71971.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000324-GPOS-00125","gid":"V-71971","rid":"SV-86595r2_rule","stig_id":"RHEL-07-020020","fix_id":"F-78323r1_fix","cci":["CCI-002165","CCI-002235"],"nist":["AC-3 (4)","AC-6 (10)"]},"title":"The Red Hat Enterprise Linux operating system must prevent\nnon-privileged users from executing privileged functions to include disabling,\ncircumventing, or altering implemented security safeguards/countermeasures.","waiver_data":{}},{"code":"","desc":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","descriptions":[{"data":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system routinely checks the baseline configuration for\nunauthorized changes.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed at least once per\nweek.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running daily or weekly on the system\nthat executes AIDE daily to scan for changes to the system baseline. The\ncommand used in the example will use a daily occurrence.\n\n Check the cron directories for a script file controlling the execution of\nthe file integrity application. For example, if AIDE is installed on the\nsystem, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 29 Nov 22 2015 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n If the file integrity application does not exist, or a script file\ncontrolling the execution of the file integrity application does not exist,\nthis is a finding.","label":"check"},{"data":"Configure the file integrity tool to run automatically on the system at\nleast weekly. The following example output is generic. It will set cron to run\nAIDE daily, but other file integrity tools may be used:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil","label":"fix"}],"id":"V-71973","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71973.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000363-GPOS-00150","gid":"V-71973","rid":"SV-86597r2_rule","stig_id":"RHEL-07-020030","fix_id":"F-78325r2_fix","cci":["CCI-001744"],"nist":["CM-3 (5)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat a file integrity tool verifies the baseline operating system configuration\nat least weekly.","waiver_data":{}},{"code":"","desc":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","descriptions":[{"data":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system notifies designated personnel if baseline\nconfigurations are changed in an unauthorized manner.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed and notify\nspecified individuals via email or an alert.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running routinely on the system that\nexecutes AIDE to scan for changes to the system baseline. The commands used in\nthe example will use a daily occurrence.\n\n Check the cron directories for a \"crontab\" script file controlling the\nexecution of the file integrity application. For example, if AIDE is installed\non the system, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 32 Jul 1 2011 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n AIDE does not have a configuration that will send a notification, so the\ncron job uses the mail application on the system to email the results of the\nfile integrity run as in the following example:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil\n\n If the file integrity application does not notify designated personnel of\nchanges, this is a finding.","label":"check"},{"data":"Configure the operating system to notify designated personnel if baseline\nconfigurations are changed in an unauthorized manner. The AIDE tool can be\nconfigured to email designated personnel with the use of the cron system.\n\n The following example output is generic. It will set cron to run AIDE daily\nand to send email at the completion of the analysis.\n\n # more /etc/cron.daily/aide\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil","label":"fix"}],"id":"V-71975","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71975.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000363-GPOS-00150","gid":"V-71975","rid":"SV-86599r2_rule","stig_id":"RHEL-07-020040","fix_id":"F-78327r3_fix","cci":["CCI-001744"],"nist":["CM-3 (5)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat designated personnel are notified if baseline configurations are changed\nin an unauthorized manner.","waiver_data":{}},{"code":"","desc":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","descriptions":[{"data":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components from a repository without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of packages from a repository prior\nto install with the following command:\n\n # grep gpgcheck /etc/yum.conf\n gpgcheck=1\n\n If \"gpgcheck\" is not set to \"1\", or if options are missing or commented\nout, ask the System Administrator how the certificates for patches and other\noperating system components are verified.\n\n If there is no process to validate certificates that is approved by the\norganization, this is a finding.","label":"check"},{"data":"Configure the operating system to verify the signature of packages from a\nrepository prior to install by setting the following option in the\n\"/etc/yum.conf\" file:\n\n gpgcheck=1","label":"fix"}],"id":"V-71977","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71977.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000366-GPOS-00153","gid":"V-71977","rid":"SV-86601r2_rule","stig_id":"RHEL-07-020050","fix_id":"F-78329r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components from a repository without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.","waiver_data":{}},{"code":"","desc":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","descriptions":[{"data":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components of local packages without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of local packages prior to install\nwith the following command:\n\n # grep localpkg_gpgcheck /etc/yum.conf\n localpkg_gpgcheck=1\n\n If \"localpkg_gpgcheck\" is not set to \"1\", or if options are missing or\ncommented out, ask the System Administrator how the signatures of local\npackages and other operating system components are verified.\n\n If there is no process to validate the signatures of local packages that is\napproved by the organization, this is a finding.","label":"check"},{"data":"Configure the operating system to verify the signature of local packages\nprior to install by setting the following option in the \"/etc/yum.conf\" file:\n\n localpkg_gpgcheck=1","label":"fix"}],"id":"V-71979","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71979.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000366-GPOS-00153","gid":"V-71979","rid":"SV-86603r2_rule","stig_id":"RHEL-07-020060","fix_id":"F-78331r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components of local packages without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.","waiver_data":{}},{"code":"","desc":"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.","descriptions":[{"data":"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.","label":"default"},{"data":"","label":"rationale"},{"data":"If there is an HBSS with a Device Control Module and a Data Loss Prevention\nmechanism, this requirement is not applicable.\n\n Verify the operating system disables the ability to load the USB Storage\nkernel module.\n\n # grep -r usb-storage /etc/modprobe.d/* | grep -i \"/bin/true\" | grep -v\n\"^#\"\n\n install usb-storage /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of USB Storage is not documented with the Information System Security\nOfficer (ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use USB mass storage\ndevices.\n\n Check to see if USB mass storage is disabled with the following command:\n\n # grep usb-storage /etc/modprobe.d/* | grep -i \"blacklist\" | grep -v\n\"^#\"\n blacklist usb-storage\n\n If the command does not return any output or the output is not \"blacklist\nusb-storage\", and use of USB storage devices is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to use the USB\nStorage kernel module.\n\n Create a file under \"/etc/modprobe.d\" with the following command:\n\n # touch /etc/modprobe.d/usb-storage.conf\n\n Add the following line to the created file:\n\n install usb-storage /bin/true\n\n Configure the operating system to disable the ability to use USB mass\nstorage devices.\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist usb-storage","label":"fix"}],"id":"V-71983","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71983.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000114-GPOS-00059","satisfies":["SRG-OS-000114-GPOS-00059","SRG-OS-000378-GPOS-00163","SRG-OS-000480-GPOS-00227"],"gid":"V-71983","rid":"SV-86607r4_rule","stig_id":"RHEL-07-020100","fix_id":"F-78335r4_fix","cci":["CCI-000366","CCI-000778","CCI-001958"],"nist":["CM-6 b","IA-3","IA-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\ndisable USB mass storage.","waiver_data":{}},{"code":"","desc":"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.","descriptions":[{"data":"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system disables the ability to automount devices.\n\n Check to see if automounter service is active with the following command:\n\n # systemctl status autofs\n autofs.service - Automounts filesystems on demand\n Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)\n Active: inactive (dead)\n\n If the \"autofs\" status is set to \"active\" and is not documented with\nthe Information System Security Officer (ISSO) as an operational requirement,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to automount devices.\n\n Turn off the automount service with the following commands:\n\n # systemctl stop autofs\n # systemctl disable autofs\n\n If \"autofs\" is required for Network File System (NFS), it must be\ndocumented with the ISSO.","label":"fix"}],"id":"V-71985","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71985.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000114-GPOS-00059","satisfies":["SRG-OS-000114-GPOS-00059","SRG-OS-000378-GPOS-00163","SRG-OS-000480-GPOS-00227"],"gid":"V-71985","rid":"SV-86609r2_rule","stig_id":"RHEL-07-020110","fix_id":"F-78337r2_fix","cci":["CCI-000366","CCI-000778","CCI-001958"],"nist":["CM-6 b","IA-3","IA-3"]},"title":"The Red Hat Enterprise Linux operating system must disable the file\nsystem automounter unless required.","waiver_data":{}},{"code":"","desc":"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.","descriptions":[{"data":"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system removes all software components after updated\nversions have been installed.\n\n Check if yum is configured to remove unneeded packages with the following\ncommand:\n\n # grep -i clean_requirements_on_remove /etc/yum.conf\n clean_requirements_on_remove=1\n\n If \"clean_requirements_on_remove\" is not set to \"1\", \"True\", or\n\"yes\", or is not set in \"/etc/yum.conf\", this is a finding.","label":"check"},{"data":"Configure the operating system to remove all software components after\nupdated versions have been installed.\n\n Set the \"clean_requirements_on_remove\" option to \"1\" in the\n\"/etc/yum.conf\" file:\n\n clean_requirements_on_remove=1","label":"fix"}],"id":"V-71987","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71987.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000437-GPOS-00194","gid":"V-71987","rid":"SV-86611r2_rule","stig_id":"RHEL-07-020200","fix_id":"F-78339r1_fix","cci":["CCI-002617"],"nist":["SI-2 (6)"]},"title":"The Red Hat Enterprise Linux operating system must remove all software\ncomponents after updated versions have been installed.","waiver_data":{}},{"code":"","desc":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","descriptions":[{"data":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \"SELinux\" is active and in \"Enforcing\" mode with the following\ncommand:\n\n # getenforce\n Enforcing\n\n If \"SELinux\" is not active and not in \"Enforcing\" mode, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \"SELinux\" status and the \"Enforcing\" mode by modifying the\n\"/etc/selinux/config\" file to have the following line:\n\n SELINUX=enforcing\n\n A reboot is required for the changes to take effect.","label":"fix"}],"id":"V-71989","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71989.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000445-GPOS-00199","gid":"V-71989","rid":"SV-86613r3_rule","stig_id":"RHEL-07-020210","fix_id":"F-78341r2_fix","cci":["CCI-002165","CCI-002696"],"nist":["AC-3 (4)","SI-6 a"]},"title":"The Red Hat Enterprise Linux operating system must enable SELinux.","waiver_data":{}},{"code":"","desc":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","descriptions":[{"data":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \"SELinux\" is active and is enforcing the targeted policy with\nthe following command:\n\n # sestatus\n\n SELinux status: enabled\n\n SELinuxfs mount: /selinux\n\n SELinux root directory: /etc/selinux\n\n Loaded policy name: targeted\n\n Current mode: enforcing\n\n Mode from config file: enforcing\n\n Policy MLS status: enabled\n\n Policy deny_unknown status: allowed\n\n Max kernel policy version: 28\n\n If the \"Loaded policy name\" is not set to \"targeted\", this is a finding.\n\n Verify that the /etc/selinux/config file is configured to the\n\"SELINUXTYPE\" to \"targeted\":\n\n # grep -i \"selinuxtype\" /etc/selinux/config | grep -v '^#'\n\n SELINUXTYPE = targeted\n\n If no results are returned or \"SELINUXTYPE\" is not set to \"targeted\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \"SELinuxtype\" to the \"targeted\" policy by modifying the\n\"/etc/selinux/config\" file to have the following line:\n\n SELINUXTYPE=targeted\n\n A reboot is required for the changes to take effect.","label":"fix"}],"id":"V-71991","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71991.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000445-GPOS-00199","gid":"V-71991","rid":"SV-86615r5_rule","stig_id":"RHEL-07-020220","fix_id":"F-78343r2_fix","cci":["CCI-002165","CCI-002696"],"nist":["AC-3 (4)","SI-6 a"]},"title":"The Red Hat Enterprise Linux operating system must enable the SELinux\ntargeted policy.","waiver_data":{}},{"code":"","desc":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","descriptions":[{"data":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active with the\nfollowing command:\n\n # systemctl status ctrl-alt-del.target\n\n ctrl-alt-del.target\n Loaded: masked (/dev/null; bad)\n Active: inactive (dead)\n\n If the ctrl-alt-del.target is not masked, this is a finding.\n\n If the ctrl-alt-del.target is active, this is a finding.","label":"check"},{"data":"Configure the system to disable the Ctrl-Alt-Delete sequence for the\ncommand line with the following command:\n\n # systemctl mask ctrl-alt-del.target","label":"fix"}],"id":"V-71993","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71993.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71993","rid":"SV-86617r5_rule","stig_id":"RHEL-07-020230","fix_id":"F-78345r6_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled on the command line.","waiver_data":{}},{"code":"","desc":"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.","descriptions":[{"data":"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system defines default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Check for the value of the \"UMASK\" parameter in \"/etc/login.defs\" file\nwith the following command:\n\n Note: If the value of the \"UMASK\" parameter is set to \"000\" in\n\"/etc/login.defs\" file, the Severity is raised to a CAT I.\n\n # grep -i umask /etc/login.defs\n UMASK 077\n\n If the value for the \"UMASK\" parameter is not \"077\", or the \"UMASK\"\nparameter is missing or is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to define default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Add or edit the line for the \"UMASK\" parameter in \"/etc/login.defs\"\nfile to \"077\":\n\n UMASK 077","label":"fix"}],"id":"V-71995","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71995.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00228","gid":"V-71995","rid":"SV-86619r2_rule","stig_id":"RHEL-07-020240","fix_id":"F-78347r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must define default\npermissions for all authenticated users in such a way that the user can only\nread and modify their own files.","waiver_data":{}},{"code":"","desc":"An operating system release is considered \"supported\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.","descriptions":[{"data":"An operating system release is considered \"supported\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the version of the operating system is vendor supported.\n\nCheck the version of the operating system with the following command:\n\n# cat /etc/redhat-release\n\nRed Hat Enterprise Linux Server release 7.4 (Maipo)\n\nCurrent End of Life for RHEL 7.1 is 31 March 2017.\n\nCurrent End of Life for RHEL 7.2 is 30 November 2017.\n\nCurrent End of Life for RHEL 7.3 is 30 November 2018.\n\nCurrent End of Life for RHEL 7.4 is 31 August 2019.\n\nCurrent End of Life for RHEL 7.5 is 30 April 2020.\n\nCurrent End of Life for RHEL 7.6 is 31 October 2020.\n\nCurrent End of Life for RHEL 7.7 is 30 August 2021.\n\nIf the release is not supported by the vendor, this is a finding.","label":"check"},{"data":"Upgrade to a supported version of the operating system.","label":"fix"}],"id":"V-71997","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71997.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71997","rid":"SV-86621r5_rule","stig_id":"RHEL-07-020250","fix_id":"F-78349r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be a vendor\nsupported release.","waiver_data":{}},{"code":"","desc":"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.","descriptions":[{"data":"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.","label":"default"},{"data":"Verify the operating system security patches and updates are installed and\n up to date. Updates are required to be applied with a frequency determined by\n the site or Program Management Office (PMO).\n\n Obtain the list of available package security updates from Red Hat. The URL\n for updates is https://rhn.redhat.com/errata/. It is important to note that\n updates provided by Red Hat may not be present on the system if the underlying\n packages are not installed.\n\n Check that the available package security updates have been installed on\n the system with the following command:\n\n # yum history list | more\n Loaded plugins: langpacks, product-id, subscription-manager\n ID | Command line | Date and time | Action(s) |\n Altered\n\n -------------------------------------------------------------------------------\n 70 | install aide | 2016-05-05 10:58 | Install |\n 1\n 69 | update -y | 2016-05-04 14:34 | Update | 18 EE\n 68 | install vlc | 2016-04-21 17:12 | Install |\n 21\n 67 | update -y | 2016-04-21 17:04 | Update | 7 EE\n 66 | update -y | 2016-04-15 16:47 | E, I, U |\n 84 EE\n\n If package updates have not been performed on the system within the\n timeframe that the site/program documentation requires, this is a finding.\n\n If the operating system is in non-compliance with the Information Assurance\nVulnerability Management (IAVM) process, this is a finding.","label":"check"},{"data":"Install the operating system patches or updated packages\navailable from Red Hat within 30 days or sooner as local policy dictates.","label":"fix"}],"id":"V-71999","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71999.rb"},"tags":{"severity":"medium","gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71999","rid":"SV-86623r4_rule","stig_id":"RHEL-07-020260","fix_id":"F-78351r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system security patches and\n updates must be installed and up to date.","waiver_data":{}},{"code":"","desc":"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.","descriptions":[{"data":"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all accounts on the system are assigned to an active system,\napplication, or user account.\n\n Obtain the list of authorized system accounts from the Information System\nSecurity Officer (ISSO).\n\n Check the system accounts on the system with the following command:\n\n # more /etc/passwd\n root:x:0:0:root:/root:/bin/bash\n bin:x:1:1:bin:/bin:/sbin/nologin\n daemon:x:2:2:daemon:/sbin:/sbin/nologin\n sync:x:5:0:sync:/sbin:/bin/sync\n shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown\n halt:x:7:0:halt:/sbin:/sbin/halt\n games:x:12:100:games:/usr/games:/sbin/nologin\n gopher:x:13:30:gopher:/var/gopher:/sbin/nologin\n\n Accounts such as \"games\" and \"gopher\" are not authorized accounts as\nthey do not support authorized system functions.\n\n If the accounts on the system do not match the provided documentation, or\naccounts that do not support an authorized system function are present, this is\na finding.","label":"check"},{"data":"Configure the system so all accounts on the system are assigned to an\nactive system, application, or user account.\n\n Remove accounts that do not support approved system activities or that\nallow for a normal user to perform administrative-level actions.\n\n Document all authorized accounts on the system.","label":"fix"}],"id":"V-72001","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72001.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72001","rid":"SV-86625r2_rule","stig_id":"RHEL-07-020270","fix_id":"F-78353r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have\nunnecessary accounts.","waiver_data":{}},{"code":"","desc":"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.","descriptions":[{"data":"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all GIDs referenced in the \"/etc/passwd\" file are defined in the\n\"/etc/group\" file.\n\n Check that all referenced GIDs exist with the following command:\n\n # pwck -r\n\n If GIDs referenced in \"/etc/passwd\" file are returned as not defined in\n\"/etc/group\" file, this is a finding.","label":"check"},{"data":"Configure the system to define all GIDs found in the\n\"/etc/passwd\" file by modifying the \"/etc/group\" file to add any\nnon-existent group referenced in the \"/etc/passwd\" file, or change the GIDs\nreferenced in the \"/etc/passwd\" file to a group that exists in\n\"/etc/group\".","label":"fix"}],"id":"V-72003","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72003.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000104-GPOS-00051","gid":"V-72003","rid":"SV-86627r2_rule","stig_id":"RHEL-07-020300","fix_id":"F-78355r1_fix","cci":["CCI-000764"],"nist":["IA-2"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all Group Identifiers (GIDs) referenced in the /etc/passwd file are\ndefined in the /etc/group file.","waiver_data":{}},{"code":"","desc":"If an account other than root also has a User Identifier (UID) of\n\"0\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \"0\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.","descriptions":[{"data":"If an account other than root also has a User Identifier (UID) of\n\"0\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \"0\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the system for duplicate UID \"0\" assignments with the following\ncommand:\n\n # awk -F: '$3 == 0 {print $1}' /etc/passwd\n\n If any accounts other than root have a UID of \"0\", this is a finding.","label":"check"},{"data":"Change the UID of any account on the system, other than root, that has a\nUID of \"0\".\n\n If the account is associated with system commands or applications, the UID\nshould be changed to one greater than \"0\" but less than \"1000\". Otherwise,\nassign a UID of greater than \"1000\" that has not already been assigned.","label":"fix"}],"id":"V-72005","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72005.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72005","rid":"SV-86629r2_rule","stig_id":"RHEL-07-020310","fix_id":"F-78357r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the root account must be the only account having unrestricted access to\nthe system.","waiver_data":{}},{"code":"","desc":"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \"UID\" as the UID of the un-owned\nfiles.","descriptions":[{"data":"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \"UID\" as the UID of the un-owned\nfiles.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories on the system have a valid owner.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nouser\n\n If any files on the system do not have an assigned owner, this is a finding.","label":"check"},{"data":"Either remove all files and directories from the system that do not have a\nvalid user, or assign a valid user to all unowned files and directories on the\nsystem with the \"chown\" command:\n\n # chown ","label":"fix"}],"id":"V-72007","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72007.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72007","rid":"SV-86631r3_rule","stig_id":"RHEL-07-020320","fix_id":"F-78359r1_fix","cci":["CCI-002165"],"nist":["AC-3 (4)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid owner.","waiver_data":{}},{"code":"","desc":"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.","descriptions":[{"data":"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories on the system have a valid group.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nogroup\n\n If any files on the system do not have an assigned group, this is a finding.","label":"check"},{"data":"Either remove all files and directories from the system that do not have a\nvalid group, or assign a valid group to all files and directories on the system\nwith the \"chgrp\" command:\n\n # chgrp ","label":"fix"}],"id":"V-72009","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72009.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72009","rid":"SV-86633r3_rule","stig_id":"RHEL-07-020330","fix_id":"F-78361r1_fix","cci":["CCI-002165"],"nist":["AC-3 (4)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid group owner.","waiver_data":{}},{"code":"","desc":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","descriptions":[{"data":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify local interactive users on the system have a home directory assigned.\n\n Check for missing local interactive user home directories with the\nfollowing command:\n\n # pwck -r\n user 'lp': directory '/var/spool/lpd' does not exist\n user 'news': directory '/var/spool/news' does not exist\n user 'uucp': directory '/var/spool/uucp' does not exist\n user 'smithj': directory '/home/smithj' does not exist\n\n Ask the System Administrator (SA) if any users found without home\ndirectories are local interactive users. If the SA is unable to provide a\nresponse, check for users with a User Identifier (UID) of 1000 or greater with\nthe following command:\n\n # cut -d: -f 1,3 /etc/passwd | egrep \":[1-4][0-9]{2}$|:[0-9]{1,2}$\"\n\n If any interactive users do not have a home directory assigned, this is a\nfinding.","label":"check"},{"data":"Assign home directories to all local interactive users that\ncurrently do not have a home directory assigned.","label":"fix"}],"id":"V-72011","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72011.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72011","rid":"SV-86635r2_rule","stig_id":"RHEL-07-020600","fix_id":"F-78363r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive users have a home directory assigned in the\n/etc/passwd file.","waiver_data":{}},{"code":"","desc":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","descriptions":[{"data":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all local interactive users on the system are assigned a home\ndirectory upon creation.\n\n Check to see if the system is configured to create home directories for\nlocal interactive users with the following command:\n\n # grep -i create_home /etc/login.defs\n CREATE_HOME yes\n\n If the value for \"CREATE_HOME\" parameter is not set to \"yes\", the line\nis missing, or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to assign home directories to all new local\ninteractive users by setting the \"CREATE_HOME\" parameter in\n\"/etc/login.defs\" to \"yes\" as follows.\n\n CREATE_HOME yes","label":"fix"}],"id":"V-72013","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72013.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72013","rid":"SV-86637r2_rule","stig_id":"RHEL-07-020610","fix_id":"F-78365r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user accounts, upon creation, are assigned a home\ndirectory.","waiver_data":{}},{"code":"","desc":"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.","descriptions":[{"data":"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive\nnon-privileged users on the system with the following command:\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n\n smithj:1001:/home/smithj\n\n Note: This may miss interactive users that have been assigned a privileged\nUID. Evidence of interactive use may be obtained from a number of log files\ncontaining system logon information.\n\n Check that all referenced home directories exist with the following command:\n\n # pwck -r\n user 'smithj': directory '/home/smithj' does not exist\n\n If any home directories referenced in \"/etc/passwd\" are returned as not\ndefined, this is a finding.","label":"check"},{"data":"Create home directories to all local interactive users that currently do\nnot have a home directory assigned. Use the following commands to create the\nuser home directory assigned in \"/etc/ passwd\":\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\", a UID of \"smithj\", and a Group Identifier (GID) of\n\"users\" assigned in \"/etc/passwd\".\n\n # mkdir /home/smithj\n # chown smithj /home/smithj\n # chgrp users /home/smithj\n # chmod 0750 /home/smithj","label":"fix"}],"id":"V-72015","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72015.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72015","rid":"SV-86639r2_rule","stig_id":"RHEL-07-020620","fix_id":"F-78367r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are defined in the /etc/passwd\nfile.","waiver_data":{}},{"code":"","desc":"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.","descriptions":[{"data":"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users has a\nmode of \"0750\" or less permissive.\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If home directories referenced in \"/etc/passwd\" do not have a mode of\n\"0750\" or less permissive, this is a finding.","label":"check"},{"data":"Change the mode of interactive user's home directories to \"0750\". To\nchange the mode of a local interactive user's home directory, use the following\ncommand:\n\n Note: The example will be for the user \"smithj\".\n\n # chmod 0750 /home/smithj","label":"fix"}],"id":"V-72017","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72017.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72017","rid":"SV-86641r3_rule","stig_id":"RHEL-07-020630","fix_id":"F-78369r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories have mode 0750 or less\npermissive.","waiver_data":{}},{"code":"","desc":"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.","descriptions":[{"data":"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If any home directories referenced in \"/etc/passwd\" are not owned by the\ninteractive user, this is a finding.","label":"check"},{"data":"Change the owner of a local interactive user's home directories to that\nowner. To change the owner of a local interactive user's home directory, use\nthe following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj","label":"fix"}],"id":"V-72019","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72019.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72019","rid":"SV-86643r5_rule","stig_id":"RHEL-07-020640","fix_id":"F-78371r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are owned by their respective\nusers.","waiver_data":{}},{"code":"","desc":"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.","descriptions":[{"data":"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users is\ngroup-owned by that user's primary GID.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n Check the user's primary group with the following command:\n\n # grep users /etc/group\n\n users:x:250:smithj,jonesj,jacksons\n\n If the user home directory referenced in \"/etc/passwd\" is not group-owned\nby that user's primary GID, this is a finding.","label":"check"},{"data":"Change the group owner of a local interactive user's home directory to the\ngroup found in \"/etc/passwd\". To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\", and has a primary group of users.\n\n # chgrp users /home/smithj","label":"fix"}],"id":"V-72021","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72021.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72021","rid":"SV-86645r5_rule","stig_id":"RHEL-07-020650","fix_id":"F-78373r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are group-owned by the home\ndirectory owners primary group.","waiver_data":{}},{"code":"","desc":"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.","descriptions":[{"data":"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories in a local interactive user's home\ndirectory are owned by the user.\n\n Check the owner of all files and directories in a local interactive user's\nhome directory with the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR /home/smithj\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the home directory\nuser, this is a finding.","label":"check"},{"data":"Change the owner of a local interactive user's files and directories to\nthat owner. To change the owner of a local interactive user's files and\ndirectories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj/","label":"fix"}],"id":"V-72023","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72023.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72023","rid":"SV-86647r2_rule","stig_id":"RHEL-07-020660","fix_id":"F-78375r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are owned by the owner of the home directory.","waiver_data":{}},{"code":"","desc":"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.","descriptions":[{"data":"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories in a local interactive user home directory\nare group-owned by a group the user is a member of.\n\n Check the group owner of all files and directories in a local interactive\nuser's home directory with the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR ///\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj sa 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the group home\ndirectory user, check to see if the user is a member of that group with the\nfollowing command:\n\n # grep smithj /etc/group\n sa:x:100:juan,shelley,bob,smithj\n smithj:x:521:smithj\n\n If the user is not a member of a group that group owns file(s) in a local\ninteractive user's home directory, this is a finding.","label":"check"},{"data":"Change the group of a local interactive user's files and directories to a\ngroup that the interactive user is a member of. To change the group owner of a\nlocal interactive user's files and directories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\" and is a member of the users group.\n\n # chgrp users /home/smithj/","label":"fix"}],"id":"V-72025","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72025.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72025","rid":"SV-86649r2_rule","stig_id":"RHEL-07-020670","fix_id":"F-78377r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are group-owned by a group of which the home directory owner is a\nmember.","waiver_data":{}},{"code":"","desc":"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.","descriptions":[{"data":"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories contained in a local interactive user home\ndirectory, excluding local initialization files, have a mode of \"0750\".\n\n Check the mode of all non-initialization files in a local interactive user\nhome directory with the following command:\n\n Files that begin with a \".\" are excluded from this requirement.\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR /home/smithj\n -rwxr-x--- 1 smithj smithj 18 Mar 5 17:06 file1\n -rwxr----- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r-x--- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with a mode more permissive than \"0750\", this is a\nfinding.","label":"check"},{"data":"Set the mode on files and directories in the local interactive user home\ndirectory with the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\" and is a member of the users group.\n\n # chmod 0750 /home/smithj/","label":"fix"}],"id":"V-72027","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72027.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72027","rid":"SV-86651r2_rule","stig_id":"RHEL-07-020680","fix_id":"F-78379r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories have a mode of 0750 or less permissive.","waiver_data":{}},{"code":"","desc":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","descriptions":[{"data":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\" and a primary group of \"users\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.","label":"check"},{"data":"Set the owner of the local initialization files for interactive users to\neither the directory owner or root with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj/.[^.]*","label":"fix"}],"id":"V-72029","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72029.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72029","rid":"SV-86653r3_rule","stig_id":"RHEL-07-020690","fix_id":"F-78381r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for interactive users are owned by the home\ndirectory user or root.","waiver_data":{}},{"code":"","desc":"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.","descriptions":[{"data":"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\" and a primary group of \"users\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.","label":"check"},{"data":"Change the group owner of a local interactive user's files to the group\nfound in \"/etc/passwd\" for the user. To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\", and has a primary group of users.\n\n # chgrp users /home/smithj/.[^.]*","label":"fix"}],"id":"V-72031","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72031.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72031","rid":"SV-86655r4_rule","stig_id":"RHEL-07-020700","fix_id":"F-78383r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for local interactive users are be\ngroup-owned by the users primary group or root.","waiver_data":{}},{"code":"","desc":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","descriptions":[{"data":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all local initialization files have a mode of \"0740\" or less\npermissive.\n\n Check the mode on all local initialization files with the following command:\n\n Note: The example will be for the \"smithj\" user, who has a home directory\nof \"/home/smithj\".\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr----- 1 smithj users 896 Mar 10 2011 .profile\n -rwxr----- 1 smithj users 497 Jan 6 2007 .login\n -rwxr----- 1 smithj users 886 Jan 6 2007 .something\n\n If any local initialization files have a mode more permissive than\n\"0740\", this is a finding.","label":"check"},{"data":"Set the mode of the local initialization files to \"0740\" with the\nfollowing command:\n\n Note: The example will be for the \"smithj\" user, who has a home directory\nof \"/home/smithj\".\n\n # chmod 0740 /home/smithj/.[^.]*","label":"fix"}],"id":"V-72033","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72033.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72033","rid":"SV-86657r3_rule","stig_id":"RHEL-07-020710","fix_id":"F-78385r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files have mode 0740 or less permissive.","waiver_data":{}},{"code":"","desc":"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).","descriptions":[{"data":"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all local interactive user initialization files' executable\nsearch path statements do not contain statements that will reference a working\ndirectory other than the users' home directory.\n\n Check the executable search path statement for all local interactive user\ninitialization files in the users' home directory with the following commands:\n\n Note: The example will be for the smithj user, which has a home directory\nof \"/home/smithj\".\n\n # grep -i path /home/smithj/.*\n /home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin\n /home/smithj/.bash_profile:export PATH\n\n If any local interactive user initialization files have executable search\npath statements that include directories outside of their home directory, this\nis a finding.","label":"check"},{"data":"Edit the local interactive user initialization files to change any PATH\nvariable statements that reference directories other than their home directory.\n\n If a local interactive user requires path variables to reference a\ndirectory owned by the application, it must be documented with the ISSO.","label":"fix"}],"id":"V-72035","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72035.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72035","rid":"SV-86659r4_rule","stig_id":"RHEL-07-020720","fix_id":"F-78387r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user initialization files executable search paths\ncontain only paths that resolve to the users home directory.","waiver_data":{}},{"code":"","desc":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","descriptions":[{"data":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that local initialization files do not execute world-writable\nprograms.\n\n Check the system for world-writable files with the following command:\n\n # find / -xdev -perm -002 -type f -exec ls -ld {} \\; | more\n\n For all files listed, check for their presence in the local initialization\nfiles with the following commands:\n\n Note: The example will be for a system that is configured to create users'\nhome directories in the \"/home\" directory.\n\n # grep /home/*/.*\n\n If any local initialization files are found to reference world-writable\nfiles, this is a finding.","label":"check"},{"data":"Set the mode on files being executed by the local initialization files with\nthe following command:\n\n # chmod 0755 ","label":"fix"}],"id":"V-72037","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72037.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72037","rid":"SV-86661r2_rule","stig_id":"RHEL-07-020730","fix_id":"F-78389r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat local initialization files do not execute world-writable programs.","waiver_data":{}},{"code":"","desc":"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.","descriptions":[{"data":"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all system device files are correctly labeled to prevent\nunauthorized modification.\n\n List all device files on the system that are incorrectly labeled with the\nfollowing commands:\n\n Note: Device files are normally found under \"/dev\", but applications may\nplace device files in other directories and may necessitate a search of the\nentire system.\n\n #find /dev -context *:device_t:* \\( -type c -o -type b \\) -printf \"%p %Z \"\n\n #find /dev -context *:unlabeled_t:* \\( -type c -o -type b \\) -printf \"%p\n%Z \"\n\n Note: There are device files, such as \"/dev/vmci\", that are used when the\noperating system is a host virtual machine. They will not be owned by a user on\nthe system and require the \"device_t\" label to operate. These device files\nare not a finding.\n\n If there is output from either of these commands, other than already noted,\nthis is a finding.","label":"check"},{"data":"Run the following command to determine which package owns the device file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh ","label":"fix"}],"id":"V-72039","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72039.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72039","rid":"SV-86663r2_rule","stig_id":"RHEL-07-020900","fix_id":"F-78391r1_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all system device files are correctly labeled to prevent unauthorized\nmodification.","waiver_data":{}},{"code":"","desc":"The \"nosuid\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that contain user home directories are mounted with the\n\"nosuid\" option.\n\n Find the file system(s) that contain the user home directories with the\nfollowing command:\n\n Note: If a separate file system has not been created for the user home\ndirectories (user home directories are mounted under \"/\"), this is not a\nfinding as the \"nosuid\" option cannot be used on the \"/\" system.\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1001:/home/smithj\n thomasr:1002:/home/thomasr\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4\nrw,relatime,discard,data=ordered,nosuid 0 2\n\n If a file system found in \"/etc/fstab\" refers to the user home directory\nfile system and it does not have the \"nosuid\" option set, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that contain user home directories.","label":"fix"}],"id":"V-72041","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72041.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72041","rid":"SV-86665r4_rule","stig_id":"RHEL-07-021000","fix_id":"F-78393r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat file systems containing user home directories are mounted to prevent files\nwith the setuid and setgid bit set from being executed.","waiver_data":{}},{"code":"","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are used for removable media are mounted with the\n\"nosuid\" option.\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat\nnoauto,owner,ro,nosuid 0 0\n\n If a file system found in \"/etc/fstab\" refers to removable media and it\ndoes not have the \"nosuid\" option set, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that are associated with removable media.","label":"fix"}],"id":"V-72043","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72043.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72043","rid":"SV-86667r2_rule","stig_id":"RHEL-07-021010","fix_id":"F-78395r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are used\nwith removable media.","waiver_data":{}},{"code":"","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are being NFS imported are configured with the\n\"nosuid\" option.\n\n Find the file system(s) that contain the directories being exported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 0 0\n\n If a file system found in \"/etc/fstab\" refers to NFS and it does not have\nthe \"nosuid\" option set, this is a finding.\n\n Verify the NFS is mounted with the \"nosuid\" option:\n\n # mount | grep nfs | grep nosuid\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that are being imported via NFS.","label":"fix"}],"id":"V-72045","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72045.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72045","rid":"SV-86669r2_rule","stig_id":"RHEL-07-021020","fix_id":"F-78397r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are\nbeing imported via Network File System (NFS).","waiver_data":{}},{"code":"","desc":"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.","descriptions":[{"data":"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all world-writable directories are group-owned by root, sys, bin, or\nan application group.\n\n Check the system for world-writable directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -xdev -perm -002 -type d -fstype xfs -exec ls -lLd {} \\;\n drwxrwxrwt 2 root root 40 Aug 26 13:07 /dev/mqueue\n drwxrwxrwt 2 root root 220 Aug 26 13:23 /dev/shm\n drwxrwxrwt 14 root root 4096 Aug 26 13:29 /tmp\n\n If any world-writable directories are not owned by root, sys, bin, or an\napplication group associated with the directory, this is a finding.","label":"check"},{"data":"Change the group of the world-writable directories to root with the\nfollowing command:\n\n # chgrp root ","label":"fix"}],"id":"V-72047","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72047.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72047","rid":"SV-86671r4_rule","stig_id":"RHEL-07-021030","fix_id":"F-78399r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all world-writable directories are group-owned by root, sys, bin, or an\napplication group.","waiver_data":{}},{"code":"","desc":"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \"0\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.","descriptions":[{"data":"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \"0\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the default umask for all local interactive users is \"077\".\n\n Identify the locations of all local interactive user home directories by\nlooking at the \"/etc/passwd\" file.\n\n Check all local interactive user initialization files for interactive users\nwith the following command:\n\n Note: The example is for a system that is configured to create users home\ndirectories in the \"/home\" directory.\n\n # grep -i umask /home/*/.*\n\n If any local interactive user initialization files are found to have a\numask statement that has a value less restrictive than \"077\", this is a\nfinding.","label":"check"},{"data":"Remove the umask statement from all local interactive user's initialization\nfiles.\n\n If the account is for an application, the requirement for a umask less\nrestrictive than \"077\" can be documented with the Information System Security\nOfficer, but the user agreement for access to the account must specify that the\nlocal interactive user must log on to their account first and then switch the\nuser to the application account with the correct option to gain the account's\nenvironment variables.","label":"fix"}],"id":"V-72049","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72049.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72049","rid":"SV-86673r2_rule","stig_id":"RHEL-07-021040","fix_id":"F-78401r3_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must set the umask value\nto 077 for all local interactive user accounts.","waiver_data":{}},{"code":"","desc":"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.","descriptions":[{"data":"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that \"rsyslog\" is configured to log cron events.\n\n Check the configuration of \"/etc/rsyslog.conf\" or\n\"/etc/rsyslog.d/*.conf\" files for the cron facility with the following\ncommand:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \"/etc/rsyslog.conf\" or \"/etc/rsyslog.d/*.conf\" files.\n\n # grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n cron.* /var/log/cron.log\n\n If the command does not return a response, check for cron logging all\nfacilities by inspecting the \"/etc/rsyslog.conf\" or \"/etc/rsyslog.d/*.conf\"\nfiles.\n\n Look for the following entry:\n\n *.* /var/log/messages\n\n If \"rsyslog\" is not logging messages for the cron facility or all\nfacilities, this is a finding.","label":"check"},{"data":"Configure \"rsyslog\" to log all cron messages by adding or updating the\nfollowing line to \"/etc/rsyslog.conf\" or a configuration file in the\n/etc/rsyslog.d/ directory:\n\n cron.* /var/log/cron.log","label":"fix"}],"id":"V-72051","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72051.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72051","rid":"SV-86675r2_rule","stig_id":"RHEL-07-021100","fix_id":"F-78403r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must have cron logging\nimplemented.","waiver_data":{}},{"code":"","desc":"If the owner of the \"cron.allow\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.","descriptions":[{"data":"If the owner of the \"cron.allow\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"cron.allow\" file is owned by root.\n\n Check the owner of the \"cron.allow\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \"cron.allow\" file exists and has an owner other than root, this is\na finding.","label":"check"},{"data":"Set the owner on the \"/etc/cron.allow\" file to root with the following\ncommand:\n\n # chown root /etc/cron.allow","label":"fix"}],"id":"V-72053","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72053.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72053","rid":"SV-86677r3_rule","stig_id":"RHEL-07-021110","fix_id":"F-78405r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is owned by root.","waiver_data":{}},{"code":"","desc":"If the group owner of the \"cron.allow\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.","descriptions":[{"data":"If the group owner of the \"cron.allow\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"cron.allow\" file is group-owned by root.\n\n Check the group owner of the \"cron.allow\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \"cron.allow\" file exists and has a group owner other than root,\nthis is a finding.","label":"check"},{"data":"Set the group owner on the \"/etc/cron.allow\" file to root with the\nfollowing command:\n\n # chgrp root /etc/cron.allow","label":"fix"}],"id":"V-72055","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72055.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72055","rid":"SV-86679r2_rule","stig_id":"RHEL-07-021120","fix_id":"F-78407r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is group-owned by root.","waiver_data":{}},{"code":"","desc":"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.","descriptions":[{"data":"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that kernel core dumps are disabled unless needed.\n\n Check the status of the \"kdump\" service with the following command:\n\n # systemctl status kdump.service\n kdump.service - Crash recovery kernel arming\n Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)\n Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago\n Main PID: 1130 (code=exited, status=0/SUCCESS)\n kernel arming.\n\n If the \"kdump\" service is active, ask the System Administrator if the use\nof the service is required and documented with the Information System Security\nOfficer (ISSO).\n\n If the service is active and is not documented, this is a finding.","label":"check"},{"data":"If kernel core dumps are not required, disable the \"kdump\" service with\nthe following command:\n\n # systemctl disable kdump.service\n\n If kernel core dumps are required, document the need with the ISSO.","label":"fix"}],"id":"V-72057","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72057.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72057","rid":"SV-86681r2_rule","stig_id":"RHEL-07-021300","fix_id":"F-78409r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must disable Kernel core\ndumps unless needed.","waiver_data":{}},{"code":"","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for\nnon-privileged local interactive user home directories.\n\n Check the home directory assignment for all non-privileged users (those\nwith a UID greater than 1000) on the system with the following command:\n\n #cut -d: -f 1,3,6,7 /etc/passwd | egrep \":[1-4][0-9]{3}\" | tr \":\"\n\"\\t\"\n\n adamsj /home/adamsj /bin/bash\n jacksonm /home/jacksonm /bin/bash\n smithj /home/smithj /bin/bash\n\n The output of the command will give the directory/partition that contains\nthe home directories for the non-privileged users on the system (in this\nexample, /home) and users' shell. All accounts with a valid shell (such as\n/bin/bash) are considered interactive users.\n\n Check that a file system/partition has been created for the non-privileged\ninteractive users with the following command:\n\n Note: The partition of /home is used in the example.\n\n # grep /home /etc/fstab\n UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1\n2\n\n If a separate entry for the file system/partition that contains the\nnon-privileged interactive users' home directories does not exist, this is a\nfinding.","label":"check"},{"data":"Migrate the \"/home\" directory onto a separate file\nsystem/partition.","label":"fix"}],"id":"V-72059","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72059.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72059","rid":"SV-86683r2_rule","stig_id":"RHEL-07-021310","fix_id":"F-78411r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat a separate file system is used for user home directories (such as /home or\nan equivalent).","waiver_data":{}},{"code":"","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for \"/var\".\n\n Check that a file system/partition has been created for \"/var\" with the\nfollowing command:\n\n # grep /var /etc/fstab\n UUID=c274f65f /var ext4 noatime,nobarrier 1\n2\n\n If a separate entry for \"/var\" is not in use, this is a finding.","label":"check"},{"data":"Migrate the \"/var\" path onto a separate file system.","label":"fix"}],"id":"V-72061","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72061.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72061","rid":"SV-86685r2_rule","stig_id":"RHEL-07-021320","fix_id":"F-78413r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /var.","waiver_data":{}},{"code":"","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Determine if the operating system is configured to have the\n\"/var/log/audit\" path is on a separate file system.\n\n # grep /var/log/audit /etc/fstab\n\n If no result is returned, or the operating system is not configured to have\n\"/var/log/audit\" on a separate file system, this is a finding.\n\n Verify that \"/var/log/audit\" is mounted on a separate file system:\n\n # mount | grep \"/var/log/audit\"\n\n If no result is returned, or \"/var/log/audit\" is not on a separate file\nsystem, this is a finding.","label":"check"},{"data":"Migrate the system audit data path onto a separate file system.","label":"fix"}],"id":"V-72063","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72063.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72063","rid":"SV-86687r6_rule","stig_id":"RHEL-07-021330","fix_id":"F-78415r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for the system audit data path.","waiver_data":{}},{"code":"","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for \"/tmp\".\n\n Check that a file system/partition has been created for \"/tmp\" with the\nfollowing command:\n\n # systemctl is-enabled tmp.mount\n enabled\n\n If the \"tmp.mount\" service is not enabled, check to see if \"/tmp\" is\ndefined in the fstab with a device and mount point:\n\n # grep -i /tmp /etc/fstab\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /tmp ext4\nrw,relatime,discard,data=ordered,nosuid,noexec, 0 0\n\n If \"tmp.mount\" service is not enabled and the \"/tmp\" directory is not\ndefined in the fstab with a device and mount point, this is a finding.","label":"check"},{"data":"Start the \"tmp.mount\" service with the following command:\n\n # systemctl enable tmp.mount\n\n OR\n\n Edit the \"/etc/fstab\" file and ensure the \"/tmp\" directory is defined\nin the fstab with a device and mount point.","label":"fix"}],"id":"V-72065","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72065.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72065","rid":"SV-86689r3_rule","stig_id":"RHEL-07-021340","fix_id":"F-78417r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /tmp (or equivalent).","waiver_data":{}},{"code":"","desc":"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.","descriptions":[{"data":"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements DoD-approved encryption to protect\nthe confidentiality of remote access sessions.\n\n Check to see if the \"dracut-fips\" package is installed with the following\ncommand:\n\n # yum list installed dracut-fips\n\n dracut-fips-033-360.el7_2.x86_64.rpm\n\n If a \"dracut-fips\" package is installed, check to see if the kernel\ncommand line is configured to use FIPS mode with the following command:\n\n Note: GRUB 2 reads its configuration from the \"/boot/grub2/grub.cfg\" file\non traditional BIOS-based machines and from the\n\"/boot/efi/EFI/redhat/grub.cfg\" file on UEFI machines.\n\n # grep fips /boot/grub2/grub.cfg\n /vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0\nrd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us\nrd.lvm.lv=rhel/root rhgb fips=1 quiet\n\n If the kernel command line is configured to use FIPS mode, check to see if\nthe system is in FIPS mode with the following command:\n\n # cat /proc/sys/crypto/fips_enabled\n 1\n\n If a \"dracut-fips\" package is not installed, the kernel command line does\nnot have a fips entry, or the system has a value of \"0\" for \"fips_enabled\"\nin \"/proc/sys/crypto\", this is a finding.","label":"check"},{"data":"Configure the operating system to implement DoD-approved encryption by\ninstalling the dracut-fips package.\n\n To enable strict FIPS compliance, the fips=1 kernel option needs to be\nadded to the kernel command line during system installation so key generation\nis done with FIPS-approved algorithms and continuous monitoring tests in place.\n\n Configure the operating system to implement DoD-approved encryption by\nfollowing the steps below:\n\n The fips=1 kernel option needs to be added to the kernel command line\nduring system installation so that key generation is done with FIPS-approved\nalgorithms and continuous monitoring tests in place. Users should also ensure\nthat the system has plenty of entropy during the installation process by moving\nthe mouse around, or if no mouse is available, ensuring that many keystrokes\nare typed. The recommended amount of keystrokes is 256 and more. Less than 256\nkeystrokes may generate a non-unique key.\n\n Install the dracut-fips package with the following command:\n\n # yum install dracut-fips\n\n Recreate the \"initramfs\" file with the following command:\n\n Note: This command will overwrite the existing \"initramfs\" file.\n\n # dracut -f\n\n Modify the kernel command line of the current kernel in the \"grub.cfg\"\nfile by adding the following option to the GRUB_CMDLINE_LINUX key in the\n\"/etc/default/grub\" file and then rebuild the \"grub.cfg\" file:\n\n fips=1\n\n Changes to \"/etc/default/grub\" require rebuilding the \"grub.cfg\" file\nas follows:\n\n On BIOS-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/grub2/grub.cfg\n\n On UEFI-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg\n\n If /boot or /boot/efi reside on separate partitions, the kernel parameter\nboot= must be added to the kernel command\nline. You can identify a partition by running the df /boot or df /boot/efi\ncommand:\n\n # df /boot\n Filesystem 1K-blocks Used Available Use% Mounted on\n /dev/sda1 495844 53780 416464 12% /boot\n\n To ensure the \"boot=\" configuration option will work even if device\nnaming changes occur between boots, identify the universally unique identifier\n(UUID) of the partition with the following command:\n\n # blkid /dev/sda1\n /dev/sda1: UUID=\"05c000f1-a213-759e-c7a2-f11b7424c797\" TYPE=\"ext4\"\n\n For the example above, append the following string to the kernel command\nline:\n\n boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797\n\n Reboot the system for the changes to take effect.","label":"fix"}],"id":"V-72067","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72067.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000033-GPOS-00014","satisfies":["SRG-OS-000033-GPOS-00014","SRG-OS-000185-GPOS-00079","SRG-OS-000396-GPOS-00176","SRG-OS-000405-GPOS-00184","SRG-OS-000478-GPOS-00223"],"gid":"V-72067","rid":"SV-86691r4_rule","stig_id":"RHEL-07-021350","fix_id":"F-78419r3_fix","cci":["CCI-000068","CCI-001199","CCI-002450","CCI-002476"],"nist":["AC-17 (2)","SC-28","SC-13","SC-28 (1)"]},"title":"The Red Hat Enterprise Linux operating system must implement NIST\nFIPS-validated cryptography for the following: to provision digital signatures,\nto generate cryptographic hashes, and to protect data requiring data-at-rest\nprotections in accordance with applicable federal laws, Executive Orders,\ndirectives, policies, regulations, and standards.","waiver_data":{}},{"code":"","desc":"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.","descriptions":[{"data":"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to verify ACLs.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"acl\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"acl\" rule is below:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"acl\" rule is not being used on all uncommented selection lines in\nthe \"/etc/aide.conf\" file, or ACLs are not being checked by another file\nintegrity tool, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to check file and directory ACLs.\n\n If AIDE is installed, ensure the \"acl\" rule is present on all uncommented\nfile and directory selection lists.","label":"fix"}],"id":"V-72069","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72069.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72069","rid":"SV-86693r3_rule","stig_id":"RHEL-07-021600","fix_id":"F-78421r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify Access Control Lists\n(ACLs).","waiver_data":{}},{"code":"","desc":"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.","descriptions":[{"data":"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to verify extended attributes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"xattrs\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"xattrs\" rule follows:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"xattrs\" rule is not being used on all uncommented selection lines\nin the \"/etc/aide.conf\" file, or extended attributes are not being checked by\nanother file integrity tool, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to check file and directory extended\nattributes.\n\n If AIDE is installed, ensure the \"xattrs\" rule is present on all\nuncommented file and directory selection lists.","label":"fix"}],"id":"V-72071","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72071.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72071","rid":"SV-86695r3_rule","stig_id":"RHEL-07-021610","fix_id":"F-78423r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify extended attributes.","waiver_data":{}},{"code":"","desc":"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.","descriptions":[{"data":"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to use FIPS 140-2 approved\ncryptographic hashes for validating file contents and directories.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding too\nas the system cannot implement FIPS 140-2 approved cryptographic algorithms and\nhashes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"sha512\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"sha512\" rule follows:\n\n All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"sha512\" rule is not being used on all uncommented selection lines\nin the \"/etc/aide.conf\" file, or another file integrity tool is not using\nFIPS 140-2 approved cryptographic hashes for validating file contents and\ndirectories, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to use FIPS 140-2 cryptographic hashes\nfor validating file and directory contents.\n\n If AIDE is installed, ensure the \"sha512\" rule is present on all\nuncommented file and directory selection lists.","label":"fix"}],"id":"V-72073","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72073.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72073","rid":"SV-86697r3_rule","stig_id":"RHEL-07-021620","fix_id":"F-78425r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a file\nintegrity tool that is configured to use FIPS 140-2 approved cryptographic\nhashes for validating file contents and directories.","waiver_data":{}},{"code":"","desc":"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).","descriptions":[{"data":"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is not configured to use a boot loader on removable media.\n\n Note: GRUB 2 reads its configuration from the \"/boot/grub2/grub.cfg\" file\non traditional BIOS-based machines and from the\n\"/boot/efi/EFI/redhat/grub.cfg\" file on UEFI machines.\n\n Check for the existence of alternate boot loader configuration files with\nthe following command:\n\n # find / -name grub.cfg\n /boot/grub2/grub.cfg\n\n If a \"grub.cfg\" is found in any subdirectories other than \"/boot/grub2\"\nand \"/boot/efi/EFI/redhat\", ask the System Administrator if there is\ndocumentation signed by the ISSO to approve the use of removable media as a\nboot loader.\n\n Check that the grub configuration file has the set root command in each\nmenu entry with the following commands:\n\n # grep -c menuentry /boot/grub2/grub.cfg\n 1\n # grep 'set root' /boot/grub2/grub.cfg\n set root=(hd0,1)\n\n If the system is using an alternate boot loader on removable media, and\ndocumentation does not exist approving the alternate configuration, this is a\nfinding.","label":"check"},{"data":"Remove alternate methods of booting the system from removable\nmedia or document the configuration to boot from removable media with the ISSO.","label":"fix"}],"id":"V-72075","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72075.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72075","rid":"SV-86699r2_rule","stig_id":"RHEL-07-021700","fix_id":"F-78427r1_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must not allow removable\nmedia to be used as the boot loader unless approved.","waiver_data":{}},{"code":"","desc":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.","descriptions":[{"data":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is configured to disable non-essential\ncapabilities. The most secure way of ensuring a non-essential capability is\ndisabled is to not have the capability installed.\n\n The telnet service provides an unencrypted remote access service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.\n\n Check to see if the telnet-server package is installed with the following\ncommand:\n\n # yum list installed telnet-server\n\n If the telnet-server package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the telnet-server package from the system with the following command:\n\n # yum remove telnet-server","label":"fix"}],"id":"V-72077","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72077.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-72077","rid":"SV-86701r2_rule","stig_id":"RHEL-07-021710","fix_id":"F-78429r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the\ntelnet-server package installed.","waiver_data":{}},{"code":"","desc":"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.","descriptions":[{"data":"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system produces audit records containing information\nto establish when (date and time) the events occurred.\n\n Check to see if auditing is active by issuing the following command:\n\n # systemctl is-active auditd.service\n active\n\n If the \"auditd\" status is not active, this is a finding.","label":"check"},{"data":"Configure the operating system to produce audit records containing\ninformation to establish when (date and time) the events occurred.\n\n Enable the auditd service with the following command:\n\n # systemctl start auditd.service","label":"fix"}],"id":"V-72079","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72079.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000038-GPOS-00016","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"],"gid":"V-72079","rid":"SV-86703r3_rule","stig_id":"RHEL-07-030000","fix_id":"F-78431r2_fix","cci":["CCI-000126","CCI-000131"],"nist":["AU-2 d","AU-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat auditing is configured to produce records containing information to\nestablish what type of events occurred, where the events occurred, the source\nof the events, and the outcome of the events. These audit records must also\nidentify individual identities of group account users.","waiver_data":{}},{"code":"","desc":"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.","descriptions":[{"data":"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.","label":"default"},{"data":"","label":"rationale"},{"data":"Confirm the audit configuration regarding how auditing processing failures\nare handled.\n\n Check to see what level \"auditctl\" is set to with following command:\n\n # auditctl -s | grep -i \"fail\"\n\n failure 2\n\n If the value of \"failure\" is set to \"2\", the system is configured to\npanic (shut down) in the event of an auditing failure.\n\n If the value of \"failure\" is set to \"1\", the system is configured to\nonly send information to the kernel log regarding the failure.\n\n If the \"failure\" setting is not set, this is a CAT I finding.\n\n If the \"failure\" setting is set to any value other than \"1\" or \"2\",\nthis is a CAT II finding.\n\n If the \"failure\" setting is set to \"1\" but the availability concern is\nnot documented or there is no monitoring of the kernel log, this is a CAT III\nfinding.","label":"check"},{"data":"Configure the operating system to shut down in the event of an audit\nprocessing failure.\n\n Add or correct the option to shut down the operating system with the\nfollowing command:\n\n # auditctl -f 2\n\n Edit the \"/etc/audit/rules.d/audit.rules\" file and add the following line:\n\n -f 2\n\n If availability has been determined to be more important, and this decision\nis documented with the ISSO, configure the operating system to notify system\nadministration staff and ISSO staff in the event of an audit processing failure\nwith the following command:\n\n # auditctl -f 1\n\n Edit the \"/etc/audit/rules.d/audit.rules\" file and add the following line:\n\n -f 1\n\n Kernel log monitoring must also be configured to properly alert designated\nstaff.\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72081","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72081.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000046-GPOS-00022","satisfies":["SRG-OS-000046-GPOS-00022","SRG-OS-000047-GPOS-00023"],"gid":"V-72081","rid":"SV-86705r4_rule","stig_id":"RHEL-07-030010","fix_id":"F-78433r2_fix","cci":["CCI-000139"],"nist":["AU-5 a"]},"title":"The Red Hat Enterprise Linux operating system must shut down upon\naudit processing failure, unless availability is an overriding concern. If\navailability is a concern, the system must alert the designated staff (System\nAdministrator [SA] and Information System Security Officer [ISSO] at a minimum)\nin the event of an audit processing failure.","waiver_data":{}},{"code":"","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system off-loads audit records onto a different system\nor media from the system being audited.\n\n To determine the remote server that the records are being sent to, use the\nfollowing command:\n\n # grep -i remote_server /etc/audisp/audisp-remote.conf\n remote_server = 10.0.21.1\n\n If a remote server is not configured, or the line is commented out, ask the\nSystem Administrator to indicate how the audit logs are off-loaded to a\ndifferent system or media.\n\n If there is no evidence that the audit logs are being off-loaded to another\nsystem or media, this is a finding.","label":"check"},{"data":"Configure the operating system to off-load audit records onto a different\nsystem or media from the system being audited.\n\n Set the remote server option in \"/etc/audisp/audisp-remote.conf\" with the\nIP address of the log aggregation server.","label":"fix"}],"id":"V-72083","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72083.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-72083","rid":"SV-86707r2_rule","stig_id":"RHEL-07-030300","fix_id":"F-78435r1_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must off-load audit\nrecords onto a different system or media from the system being audited.","waiver_data":{}},{"code":"","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system encrypts audit records off-loaded onto a\ndifferent system or media from the system being audited.\n\n To determine if the transfer is encrypted, use the following command:\n\n # grep -i enable_krb5 /etc/audisp/audisp-remote.conf\n enable_krb5 = yes\n\n If the value of the \"enable_krb5\" option is not set to \"yes\" or the\nline is commented out, ask the System Administrator to indicate how the audit\nlogs are off-loaded to a different system or media.\n\n If there is no evidence that the transfer of the audit logs being\noff-loaded to another system or media is encrypted, this is a finding.","label":"check"},{"data":"Configure the operating system to encrypt the transfer of off-loaded audit\nrecords onto a different system or media from the system being audited.\n\n Uncomment the \"enable_krb5\" option in \"/etc/audisp/audisp-remote.conf\"\nand set it with the following line:\n\n enable_krb5 = yes","label":"fix"}],"id":"V-72085","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72085.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-72085","rid":"SV-86709r2_rule","stig_id":"RHEL-07-030310","fix_id":"F-78437r1_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must encrypt the\ntransfer of audit records off-loaded onto a different system or media from the\nsystem being audited.","waiver_data":{}},{"code":"","desc":"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.","descriptions":[{"data":"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the action the operating system takes if the disk the audit records\nare written to becomes full.\n\n To determine the action that takes place if the disk is full on the remote\nserver, use the following command:\n\n # grep -i disk_full_action /etc/audisp/audisp-remote.conf\n disk_full_action = single\n\n If the value of the \"disk_full_action\" option is not \"syslog\",\n\"single\", or \"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the action the operating system takes if the disk the audit\nrecords are written to becomes full.\n\n Uncomment or edit the \"disk_full_action\" option in\n\"/etc/audisp/audisp-remote.conf\" and set it to \"syslog\", \"single\", or\n\"halt\", such as the following line:\n\n disk_full_action = single","label":"fix"}],"id":"V-72087","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72087.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","gid":"V-72087","rid":"SV-86711r3_rule","stig_id":"RHEL-07-030320","fix_id":"F-78439r4_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when the audit storage volume is\nfull.","waiver_data":{}},{"code":"","desc":"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.","descriptions":[{"data":"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates an action to notify the SA and ISSO\n(at a minimum) when allocated audit record storage volume reaches 75 percent of\nthe repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to with the following command:\n\n # grep -iw log_file /etc/audit/auditd.conf\n log_file = /var/log/audit/audit.log\n\n Check the size of the partition that audit records are written to (with the\nexample being \"/var/log/audit/\"):\n\n # df -h /var/log/audit/\n 0.9G /var/log/audit\n\n If the audit records are not being written to a partition specifically\ncreated for audit records (in this example \"/var/log/audit\" is a separate\npartition), determine the amount of space other files in the partition are\ncurrently occupying with the following command:\n\n # du -sh \n 1.8G /var\n\n Determine what the threshold is for the system to take action when 75\npercent of the repository maximum audit record storage capacity is reached:\n\n # grep -iw space_left /etc/audit/auditd.conf\n space_left = 225\n\n If the value of the \"space_left\" keyword is not set to 25 percent of the\ntotal partition size, this is a finding.","label":"check"},{"data":"Configure the operating system to initiate an action to notify the SA and\nISSO (at a minimum) when allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to:\n\n # grep -iw log_file /etc/audit/auditd.conf\n\n Determine the size of the partition that audit records are written to (with\nthe example being \"/var/log/audit/\"):\n\n # df -h /var/log/audit/\n\n Set the value of the \"space_left\" keyword in \"/etc/audit/auditd.conf\"\nto 25 percent of the partition size.","label":"fix"}],"id":"V-72089","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72089.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72089","rid":"SV-86713r4_rule","stig_id":"RHEL-07-030330","fix_id":"F-78441r3_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must initiate an action\nto notify the System Administrator (SA) and Information System Security Officer\nISSO, at a minimum, when allocated audit record storage volume reaches 75% of\nthe repository maximum audit record storage capacity.","waiver_data":{}},{"code":"","desc":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","descriptions":[{"data":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check what action the operating system takes when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i space_left_action /etc/audit/auditd.conf\n space_left_action = email\n\n If the value of the \"space_left_action\" keyword is not set to \"email\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \"space_left_action\" keyword in\n\"/etc/audit/auditd.conf\" and set it to \"email\".\n\n space_left_action = email","label":"fix"}],"id":"V-72091","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72091.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72091","rid":"SV-86715r2_rule","stig_id":"RHEL-07-030340","fix_id":"F-78443r1_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) via email when the threshold for the repository maximum audit\nrecord storage capacity is reached.","waiver_data":{}},{"code":"","desc":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","descriptions":[{"data":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the threshold for the repository maximum audit record\nstorage capacity is reached.\n\n Check what account the operating system emails when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i action_mail_acct /etc/audit/auditd.conf\n action_mail_acct = root\n\n If the value of the \"action_mail_acct\" keyword is not set to \"root\" and\nother accounts for security personnel, this is a finding.","label":"check"},{"data":"Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \"action_mail_acct\" keyword in\n\"/etc/audit/auditd.conf\" and set it to root and any other accounts associated\nwith security personnel.\n\n action_mail_acct = root","label":"fix"}],"id":"V-72093","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72093.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72093","rid":"SV-86717r3_rule","stig_id":"RHEL-07-030350","fix_id":"F-78445r3_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) when the threshold for the repository maximum audit record\nstorage capacity is reached.","waiver_data":{}},{"code":"","desc":"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.","descriptions":[{"data":"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system audits the execution of privileged functions\nusing the following command:\n\n # grep -iw execve /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n\n If both the \"b32\" and \"b64\" audit rules for \"SUID\" files are not\ndefined, this is a finding.\n\n If both the \"b32\" and \"b64\" audit rules for \"SGID\" files are not\ndefined, this is a finding.","label":"check"},{"data":"Configure the operating system to audit the execution of privileged\nfunctions.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72095","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72095.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000327-GPOS-00127","gid":"V-72095","rid":"SV-86719r7_rule","stig_id":"RHEL-07-030360","fix_id":"F-78447r9_fix","cci":["CCI-002234"],"nist":["AC-6 (9)"]},"title":"The Red Hat Enterprise Linux operating system must audit all\nexecutions of privileged functions.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw chown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"chown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72097","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72097.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72097","rid":"SV-86721r5_rule","stig_id":"RHEL-07-030370","fix_id":"F-78449r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chown syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72099","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72099.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72099","rid":"SV-86723r5_rule","stig_id":"RHEL-07-030380","fix_id":"F-78451r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchown syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lchown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lchown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72101","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72101.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72101","rid":"SV-86725r5_rule","stig_id":"RHEL-07-030390","fix_id":"F-78453r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lchown syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchownat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fchownat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchownat\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72103","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72103.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72103","rid":"SV-86727r5_rule","stig_id":"RHEL-07-030400","fix_id":"F-78455r7_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchownat syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chmod\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw chmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"chmod\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chmod\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72105","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72105.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72105","rid":"SV-86729r5_rule","stig_id":"RHEL-07-030410","fix_id":"F-78457r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chmod syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchmod\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw fchmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchmod\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fchmod\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72107","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72107.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72107","rid":"SV-86731r5_rule","stig_id":"RHEL-07-030420","fix_id":"F-78459r9_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmod syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchmodat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw fchmodat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchmodat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fchmodat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72109","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72109.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72109","rid":"SV-86733r5_rule","stig_id":"RHEL-07-030430","fix_id":"F-78461r8_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmodat syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw setxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"setxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72111","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72111.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72111","rid":"SV-86735r5_rule","stig_id":"RHEL-07-030440","fix_id":"F-78463r8_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setxattr syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fsetxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fsetxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fsetxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72113","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72113.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72113","rid":"SV-86737r5_rule","stig_id":"RHEL-07-030450","fix_id":"F-78465r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fsetxattr syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lsetxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lsetxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"lsetxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72115","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72115.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72115","rid":"SV-86739r5_rule","stig_id":"RHEL-07-030460","fix_id":"F-78467r10_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lsetxattr syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"removexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw removexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"removexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"removexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72117","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72117.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72117","rid":"SV-86741r5_rule","stig_id":"RHEL-07-030470","fix_id":"F-78469r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe removexattr syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fremovexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fremovexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fremovexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72119","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72119.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72119","rid":"SV-86743r5_rule","stig_id":"RHEL-07-030480","fix_id":"F-78471r6_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fremovexattr syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lremovexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lremovexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"lremovexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72121","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72121.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72121","rid":"SV-86745r5_rule","stig_id":"RHEL-07-030490","fix_id":"F-78473r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lremovexattr syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"creat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw creat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S creat F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"creat\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"creat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules:\n\n -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72123","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72123.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72123","rid":"SV-86747r5_rule","stig_id":"RHEL-07-030500","fix_id":"F-78475r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe creat syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"open\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw open /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"open\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"open\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72125","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72125.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72125","rid":"SV-86749r5_rule","stig_id":"RHEL-07-030510","fix_id":"F-78477r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"openat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw openat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"openat\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"openat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72127","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72127.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72127","rid":"SV-86751r5_rule","stig_id":"RHEL-07-030520","fix_id":"F-78479r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe openat syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"open_by_handle_at\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw open_by_handle_at /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"open_by_handle_at\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"open_by_handle_at\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72129","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72129.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72129","rid":"SV-86753r5_rule","stig_id":"RHEL-07-030530","fix_id":"F-78481r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open_by_handle_at syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"truncate\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw truncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"truncate\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"truncate\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72131","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72131.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72131","rid":"SV-86755r5_rule","stig_id":"RHEL-07-030540","fix_id":"F-78483r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe truncate syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"ftruncate\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw ftruncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"ftruncate\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"ftruncate\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72133","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72133.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72133","rid":"SV-86757r5_rule","stig_id":"RHEL-07-030550","fix_id":"F-78485r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ftruncate syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"semanage\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/semanage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"semanage\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72135","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72135.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72135","rid":"SV-86759r4_rule","stig_id":"RHEL-07-030560","fix_id":"F-78487r5_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe semanage command.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setsebool\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/setsebool /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setsebool\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72137","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72137.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72137","rid":"SV-86761r4_rule","stig_id":"RHEL-07-030570","fix_id":"F-78489r6_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setsebool command.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chcon\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/chcon /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chcon\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72139","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72139.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72139","rid":"SV-86763r4_rule","stig_id":"RHEL-07-030580","fix_id":"F-78491r6_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chcon command.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setfiles\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw /usr/sbin/setfiles /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setfiles\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72141","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72141.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72141","rid":"SV-86765r5_rule","stig_id":"RHEL-07-030590","fix_id":"F-78493r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setfiles command.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when unsuccessful\naccount access events occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommands:\n\n # grep -i /var/run/faillock /etc/audit/audit.rules\n\n -w /var/run/faillock -p wa -k logins\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when unsuccessful\naccount access events occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /var/run/faillock -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72145","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72145.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000470-GPOS-00214","SRG-OS-000473-GPOS-00218"],"gid":"V-72145","rid":"SV-86769r4_rule","stig_id":"RHEL-07-030610","fix_id":"F-78497r4_fix","cci":["CCI-000126","CCI-000172","CCI-002884"],"nist":["AU-2 d","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all unsuccessful account access events.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when successful account\naccess events occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -i /var/log/lastlog /etc/audit/audit.rules\n\n -w /var/log/lastlog -p wa -k logins\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when successful\naccount access events occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /var/log/lastlog -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72147","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72147.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000470-GPOS-00214","SRG-OS-000473-GPOS-00218"],"gid":"V-72147","rid":"SV-86771r3_rule","stig_id":"RHEL-07-030620","fix_id":"F-78499r3_fix","cci":["CCI-000126","CCI-000172","CCI-002884"],"nist":["AU-2 d","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all successful account access events.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"passwd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/passwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"passwd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72149","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72149.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72149","rid":"SV-86773r5_rule","stig_id":"RHEL-07-030630","fix_id":"F-78501r6_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe passwd command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unix_chkpwd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw /usr/sbin/unix_chkpwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unix_chkpwd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72151","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72151.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72151","rid":"SV-86775r5_rule","stig_id":"RHEL-07-030640","fix_id":"F-78503r8_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unix_chkpwd command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"gpasswd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/gpasswd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"gpasswd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72153","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72153.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72153","rid":"SV-86777r5_rule","stig_id":"RHEL-07-030650","fix_id":"F-78505r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe gpasswd command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chage\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/chage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chage\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72155","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72155.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72155","rid":"SV-86779r5_rule","stig_id":"RHEL-07-030660","fix_id":"F-78507r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chage command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"userhelper\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/userhelper /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"userhelper\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72157","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72157.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72157","rid":"SV-86781r5_rule","stig_id":"RHEL-07-030670","fix_id":"F-78509r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe userhelper command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"su\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/su /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"su\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72159","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72159.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72159","rid":"SV-86783r5_rule","stig_id":"RHEL-07-030680","fix_id":"F-78511r6_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe su command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"sudo\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/sudo /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"sudo\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72161","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72161.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72161","rid":"SV-86785r4_rule","stig_id":"RHEL-07-030690","fix_id":"F-78513r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudo command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to access the \"/etc/sudoers\" file and files\nin the \"/etc/sudoers.d/\" directory.\n\n Check for modification of the following files being audited by performing\nthe following commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -i \"/etc/sudoers\" /etc/audit/audit.rules\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n # grep -i \"/etc/sudoers.d/\" /etc/audit/audit.rules\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n If the commands do not return output that match the examples, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to access the \"/etc/sudoers\" file and files\nin the \"/etc/sudoers.d/\" directory.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72163","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72163.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72163","rid":"SV-86787r5_rule","stig_id":"RHEL-07-030700","fix_id":"F-78517r6_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudoers file and all files in the /etc/sudoers.d/ directory.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"newgrp\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -i /usr/bin/newgrp /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"newgrp\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72165","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72165.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72165","rid":"SV-86789r4_rule","stig_id":"RHEL-07-030710","fix_id":"F-78519r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe newgrp command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chsh\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -i /usr/bin/chsh /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chsh\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72167","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72167.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72167","rid":"SV-86791r4_rule","stig_id":"RHEL-07-030720","fix_id":"F-78521r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chsh command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"mount\" command and syscall occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -iw \"mount\" /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"mount\" syscall, this is a finding.\n\n If all uses of the \"mount\" command are not being audited, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"mount\" command and syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72171","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72171.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72171","rid":"SV-86795r7_rule","stig_id":"RHEL-07-030740","fix_id":"F-78525r9_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe mount command and syscall.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"umount\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -iw \"/usr/bin/umount\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"umount\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72173","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72173.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72173","rid":"SV-86797r5_rule","stig_id":"RHEL-07-030750","fix_id":"F-78527r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe umount command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"postdrop\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/sbin/postdrop /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"postdrop\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72175","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72175.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72175","rid":"SV-86799r4_rule","stig_id":"RHEL-07-030760","fix_id":"F-78529r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postdrop command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"postqueue\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/sbin/postqueue /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"postqueue\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72177","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72177.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72177","rid":"SV-86801r3_rule","stig_id":"RHEL-07-030770","fix_id":"F-78531r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postqueue command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"ssh-keysign\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/libexec/openssh/ssh-keysign /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"ssh-keysign\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72179","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72179.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72179","rid":"SV-86803r3_rule","stig_id":"RHEL-07-030780","fix_id":"F-78533r4_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ssh-keysign command.","waiver_data":{}},{"code":"","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"crontab\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/crontab /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"crontab\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72183","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72183.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72183","rid":"SV-86807r3_rule","stig_id":"RHEL-07-030800","fix_id":"F-78537r4_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe crontab command.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"pam_timestamp_check\" command\noccur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw \"/usr/sbin/pam_timestamp_check\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"pam_timestamp_check\" command\noccur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72185","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72185.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00215","gid":"V-72185","rid":"SV-86809r4_rule","stig_id":"RHEL-07-030810","fix_id":"F-78539r4_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe pam_timestamp_check command.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"init_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw init_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"init_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"init_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72187","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72187.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72187","rid":"SV-86811r5_rule","stig_id":"RHEL-07-030820","fix_id":"F-78541r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe init_module syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"delete_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw delete_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"delete_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"delete_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72189","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72189.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72189","rid":"SV-86813r5_rule","stig_id":"RHEL-07-030830","fix_id":"F-78543r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe delete_module syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"kmod\" command occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw kmod /etc/audit/audit.rules\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"kmod\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72191","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72191.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72191","rid":"SV-86815r5_rule","stig_id":"RHEL-07-030840","fix_id":"F-78545r10_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe kmod command.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/passwd\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/passwd /etc/audit/audit.rules\n\n -w /etc/passwd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/passwd\".\n\n Add or update the following rule \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/passwd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72197","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72197.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","satisfies":["SRG-OS-000004-GPOS-00004","SRG-OS-000239-GPOS-00089","SRG-OS-000240-GPOS-00090","SRG-OS-000241-GPOS-00091","SRG-OS-000303-GPOS-00120","SRG-OS-000476-GPOS-00221"],"gid":"V-72197","rid":"SV-86821r5_rule","stig_id":"RHEL-07-030870","fix_id":"F-78551r4_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/passwd.","waiver_data":{}},{"code":"","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"rename\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw rename /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"rename\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"rename\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72199","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72199.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72199","rid":"SV-86823r5_rule","stig_id":"RHEL-07-030880","fix_id":"F-78553r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rename syscall.","waiver_data":{}},{"code":"","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"renameat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw renameat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"renameat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"renameat\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72201","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72201.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72201","rid":"SV-86825r5_rule","stig_id":"RHEL-07-030890","fix_id":"F-78555r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe renameat syscall.","waiver_data":{}},{"code":"","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"rmdir\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw rmdir /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"rmdir\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"rmdir\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72203","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72203.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72203","rid":"SV-86827r5_rule","stig_id":"RHEL-07-030900","fix_id":"F-78557r9_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rmdir syscall.","waiver_data":{}},{"code":"","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unlink\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw unlink /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"unlink\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unlink\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72205","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72205.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72205","rid":"SV-86829r5_rule","stig_id":"RHEL-07-030910","fix_id":"F-78559r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlink syscall.","waiver_data":{}},{"code":"","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unlinkat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw unlinkat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"unlinkat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unlinkat\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72207","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72207.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72207","rid":"SV-86831r5_rule","stig_id":"RHEL-07-030920","fix_id":"F-78561r10_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlinkat syscall.","waiver_data":{}},{"code":"","desc":"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.","descriptions":[{"data":"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify \"rsyslog\" is configured to send all messages to a log aggregation\nserver.\n\n Check the configuration of \"rsyslog\" with the following command:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \"/etc/rsyslog.conf\".\n\n # grep @ /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n *.* @@logagg.site.mil\n\n If there are no lines in the \"/etc/rsyslog.conf\" or\n\"/etc/rsyslog.d/*.conf\" files that contain the \"@\" or \"@@\" symbol(s), and\nthe lines with the correct symbol(s) to send output to another system do not\ncover all \"rsyslog\" output, ask the System Administrator to indicate how the\naudit logs are off-loaded to a different system or media.\n\n If the lines are commented out or there is no evidence that the audit logs\nare being sent to another system, this is a finding.","label":"check"},{"data":"Modify the \"/etc/rsyslog.conf\" or an \"/etc/rsyslog.d/*.conf\" file to\ncontain a configuration line to send all \"rsyslog\" output to a log\naggregation system:\n *.* @@","label":"fix"}],"id":"V-72209","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72209.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72209","rid":"SV-86833r2_rule","stig_id":"RHEL-07-031000","fix_id":"F-78563r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must send rsyslog output\nto a log aggregation server.","waiver_data":{}},{"code":"","desc":"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.","descriptions":[{"data":"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the system is not accepting \"rsyslog\" messages from other\nsystems unless it is documented as a log aggregation server.\n\n Check the configuration of \"rsyslog\" with the following command:\n\n # grep imtcp /etc/rsyslog.conf\n $ModLoad imtcp\n # grep imudp /etc/rsyslog.conf\n $ModLoad imudp\n # grep imrelp /etc/rsyslog.conf\n $ModLoad imrelp\n\n If any of the above modules are being loaded in the \"/etc/rsyslog.conf\"\nfile, ask to see the documentation for the system being used for log\naggregation.\n\n If the documentation does not exist, or does not specify the server as a\nlog aggregation system, this is a finding.","label":"check"},{"data":"Modify the \"/etc/rsyslog.conf\" file to remove the \"ModLoad\nimtcp\", \"ModLoad imudp\", and \"ModLoad imrelp\" configuration lines, or\ndocument the system as being used for log aggregation.","label":"fix"}],"id":"V-72211","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72211.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72211","rid":"SV-86835r2_rule","stig_id":"RHEL-07-031010","fix_id":"F-78565r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the rsyslog daemon does not accept log messages from other servers unless\nthe server is being used for log aggregation.","waiver_data":{}},{"code":"","desc":"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.","descriptions":[{"data":"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify an anti-virus solution is installed on the system. The anti-virus\nsolution may be bundled with an approved host-based security solution.\n\n If there is no anti-virus solution installed on the system, this is a\nfinding.","label":"check"},{"data":"Install an antivirus solution on the system.","label":"fix"}],"id":"V-72213","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72213.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72213","rid":"SV-86837r3_rule","stig_id":"RHEL-07-032000","fix_id":"F-78567r2_fix","cci":["CCI-001668"],"nist":["SI-3 a"]},"title":"The Red Hat Enterprise Linux operating system must use a virus scan\nprogram.","waiver_data":{}},{"code":"","desc":"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.","descriptions":[{"data":"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system limits the number of concurrent sessions to\n\"10\" for all accounts and/or account types by issuing the following command:\n\n # grep \"maxlogins\" /etc/security/limits.conf /etc/security/limits.d/*.conf\n\n * hard maxlogins 10\n\n This can be set as a global domain (with the * wildcard) but may be set\ndifferently for multiple domains.\n\n If the \"maxlogins\" item is missing, commented out, or the value is not\nset to \"10\" or less for all domains that have the \"maxlogins\" item\nassigned, this is a finding.","label":"check"},{"data":"Configure the operating system to limit the number of concurrent sessions\nto \"10\" for all accounts and/or account types.\n\n Add the following line to the top of the /etc/security/limits.conf or in a\n\".conf\" file defined in /etc/security/limits.d/ :\n\n * hard maxlogins 10","label":"fix"}],"id":"V-72217","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72217.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000027-GPOS-00008","gid":"V-72217","rid":"SV-86841r3_rule","stig_id":"RHEL-07-040000","fix_id":"F-78571r2_fix","cci":["CCI-000054"],"nist":["AC-10"]},"title":"The Red Hat Enterprise Linux operating system must limit the number of\nconcurrent sessions to 10 for all accounts and/or account types.","waiver_data":{}},{"code":"","desc":"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.","descriptions":[{"data":"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.","label":"default"},{"data":"","label":"rationale"},{"data":"Inspect the firewall configuration and running services to verify that it\nis configured to prohibit or restrict the use of functions, ports, protocols,\nand/or services that are unnecessary or prohibited.\n\n Check which services are currently active with the following command:\n\n # firewall-cmd --list-all\n public (default, active)\n interfaces: enp0s3\n sources:\n services: dhcpv6-client dns http https ldaps rpc-bind ssh\n ports:\n masquerade: no\n forward-ports:\n icmp-blocks:\n rich rules:\n\n Ask the System Administrator for the site or program PPSM CLSA. Verify the\nservices allowed by the firewall match the PPSM CLSA.\n\n If there are additional ports, protocols, or services that are not in the\nPPSM CLSA, or there are ports, protocols, or services that are prohibited by\nthe PPSM Category Assurance List (CAL), this is a finding.","label":"check"},{"data":"Update the host's firewall settings and/or running services to\ncomply with the PPSM CLSA for the site or program and the PPSM CAL.","label":"fix"}],"id":"V-72219","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72219.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000096-GPOS-00050","satisfies":["SRG-OS-000096-GPOS-00050","SRG-OS-000297-GPOS-00115"],"gid":"V-72219","rid":"SV-86843r2_rule","stig_id":"RHEL-07-040100","fix_id":"F-78573r1_fix","cci":["CCI-000382","CCI-002314"],"nist":["CM-7 b","AC-17 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nprohibit or restrict the use of functions, ports, protocols, and/or services,\nas defined in the Ports, Protocols, and Services Management Component Local\nService Assessment (PPSM CLSA) and vulnerability assessments.","waiver_data":{}},{"code":"","desc":"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.","descriptions":[{"data":"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uses mechanisms meeting the requirements of\napplicable federal laws, Executive orders, directives, policies, regulations,\nstandards, and guidance for authentication to a cryptographic module.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n The location of the \"sshd_config\" file may vary if a different daemon is\nin use.\n\n Inspect the \"Ciphers\" configuration with the following command:\n\n # grep -i ciphers /etc/ssh/sshd_config\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n If any ciphers other than \"aes128-ctr\", \"aes192-ctr\", or \"aes256-ctr\"\nare listed, the \"Ciphers\" keyword is missing, or the returned line is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to use FIPS 140-2 approved cryptographic algorithms.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor).\n\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72221","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72221.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000033-GPOS-00014","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"],"gid":"V-72221","rid":"SV-86845r3_rule","stig_id":"RHEL-07-040110","fix_id":"F-78575r3_fix","cci":["CCI-000068","CCI-000366","CCI-000803"],"nist":["AC-17 (2)","CM-6 b","IA-7"]},"title":"The Red Hat Enterprise Linux operating system must use a FIPS 140-2\napproved cryptographic algorithm for SSH communications.","waiver_data":{}},{"code":"","desc":"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system terminates all network connections associated\nwith a communications session at the end of the session or based on inactivity.\n\n Check the value of the system inactivity timeout with the following command:\n\n # grep -i tmout /etc/profile.d/*\n\n etc/profile.d/tmout.sh:TMOUT=600\n\n /etc/profile.d/tmout.sh:readonly TMOUT\n\n /etc/profile.d/tmout.sh:export TMOUT\n\n If \"TMOUT\" is not set to \"600\" or less in a script located in the\n/etc/profile.d/ directory to enforce session termination after inactivity, this\nis a finding.","label":"check"},{"data":"Configure the operating system to terminate all network connections\nassociated with a communications session at the end of the session or after a\nperiod of inactivity.\n\n Create a script to enforce the inactivity timeout (for example\n/etc/profile.d/tmout.sh) such as:\n\n #!/bin/bash\n\n TMOUT=600\n readonly TMOUT\n export TMOUT","label":"fix"}],"id":"V-72223","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72223.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","gid":"V-72223","rid":"SV-86847r4_rule","stig_id":"RHEL-07-040160","fix_id":"F-78577r5_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with a communication session are\nterminated at the end of the session or after 10 minutes of inactivity from the\nuser at a command prompt, except to fulfill documented and validated mission\nrequirements.","waiver_data":{}},{"code":"","desc":"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify any publicly accessible connection to the operating system displays\nthe Standard Mandatory DoD Notice and Consent Banner before granting access to\nthe system.\n\n Check for the location of the banner file being used with the following\ncommand:\n\n # grep -i banner /etc/ssh/sshd_config\n\n banner /etc/issue\n\n This command will return the banner keyword and the name of the file that\ncontains the ssh banner (in this case \"/etc/issue\").\n\n If the line is commented out, this is a finding.\n\n View the file specified by the banner keyword to check that it matches the\ntext of the Standard Mandatory DoD Notice and Consent Banner:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n If the system does not display a graphical logon banner or the banner does\nnot match the Standard Mandatory DoD Notice and Consent Banner, this is a\nfinding.\n\n If the text in the file does not match the Standard Mandatory DoD Notice\nand Consent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the ssh.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment the banner keyword and\nconfigure it to point to a file that will contain the logon banner (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor). An example configuration line is:\n\n banner /etc/issue\n\n Either create the file containing the banner or replace the text in the\nfile with the Standard Mandatory DoD Notice and Consent Banner. The DoD\nrequired text is:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72225","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72225.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-72225","rid":"SV-86849r4_rule","stig_id":"RHEL-07-040170","fix_id":"F-78579r4_fix","cci":["CCI-000048","CCI-000050","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"],"nist":["AC-8 a","AC-8 b","AC-8 c 1","AC-8 c 2","AC-8 c 2","AC-8 c\n2","AC-8 c 3"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner immediately prior to, or as\npart of, remote access logon prompts.","waiver_data":{}},{"code":"","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP authentication sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Ensure that LDAP is configured to use TLS by using the following command:\n\n # grep -i \"start_tls\" /etc/sssd/sssd.conf\n ldap_id_use_start_tls = true\n\n If the \"ldap_id_use_start_tls\" option is not \"true\", this is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP authentication sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_id_use_start_tls = true","label":"fix"}],"id":"V-72227","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72227.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72227","rid":"SV-86851r4_rule","stig_id":"RHEL-07-040180","fix_id":"F-78581r2_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) authentication communications.","waiver_data":{}},{"code":"","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Verify the sssd service is configured to require the use of certificates:\n\n # grep -i tls_reqcert /etc/sssd/sssd.conf\n ldap_tls_reqcert = demand\n\n If the \"ldap_tls_reqcert\" setting is missing, commented out, or does not\nexist, this is a finding.\n\n If the \"ldap_tls_reqcert\" setting is not set to \"demand\" or \"hard\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_tls_reqcert = demand","label":"fix"}],"id":"V-72229","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72229.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72229","rid":"SV-86853r4_rule","stig_id":"RHEL-07-040190","fix_id":"F-78583r4_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.","waiver_data":{}},{"code":"","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" that the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Check the path to the X.509 certificate for peer authentication with the\nfollowing command:\n\n # grep -i tls_cacert /etc/sssd/sssd.conf\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt\n\n Verify the \"ldap_tls_cacert\" option points to a file that contains the\ntrusted CA certificate.\n\n If this file does not exist, or the option is commented out or missing,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt","label":"fix"}],"id":"V-72231","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72231.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72231","rid":"SV-86855r4_rule","stig_id":"RHEL-07-040200","fix_id":"F-78585r3_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.","waiver_data":{}},{"code":"","desc":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.","descriptions":[{"data":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if sshd is installed with the following command:\n\n# yum list installed \\*ssh\\*\nlibssh2.x86_64 1.4.3-8.el7 @anaconda/7.1\nopenssh.x86_64 6.6.1p1-11.el7 @anaconda/7.1\nopenssh-server.x86_64 6.6.1p1-11.el7 @anaconda/7.1\n\nIf the \"SSH server\" package is not installed, this is a finding.","label":"check"},{"data":"Install SSH packages onto the host with the following commands:\n\n# yum install openssh-server.x86_64","label":"fix"}],"id":"V-72233","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72233.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000423-GPOS-00187","satisfies":["SRG-OS-000423-GPOS-00187","SRG-OS-000424-GPOS-00188","SRG-OS-000425-GPOS-00189","SRG-OS-000426-GPOS-00190"],"gid":"V-72233","rid":"SV-86857r3_rule","stig_id":"RHEL-07-040300","fix_id":"F-78587r3_fix","cci":["CCI-002418","CCI-002420","CCI-002421","CCI-002422"],"nist":["SC-8","SC-8 (2)","SC-8 (1)","SC-8 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems have SSH installed.","waiver_data":{}},{"code":"","desc":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.","descriptions":[{"data":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify SSH is loaded and active with the following command:\n\n # systemctl status sshd\n sshd.service - OpenSSH server daemon\n Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)\n Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days\nago\n Main PID: 1348 (sshd)\n CGroup: /system.slice/sshd.service\n 1053 /usr/sbin/sshd -D\n\n If \"sshd\" does not show a status of \"active\" and \"running\", this is a\nfinding.","label":"check"},{"data":"Configure the SSH service to automatically start after reboot with the\nfollowing command:\n\n # systemctl enable sshd.service","label":"fix"}],"id":"V-72235","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72235.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000423-GPOS-00187","satisfies":["SRG-OS-000423-GPOS-00187","SRG-OS-000423-GPOS-00188","SRG-OS-000423-GPOS-00189","SRG-OS-000423-GPOS-00190"],"gid":"V-72235","rid":"SV-86859r3_rule","stig_id":"RHEL-07-040310","fix_id":"F-78589r2_fix","cci":["CCI-002418","CCI-002420","CCI-002421","CCI-002422"],"nist":["SC-8","SC-8 (2)","SC-8 (1)","SC-8 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems use SSH for confidentiality and integrity of\ntransmitted and received information as well as information during preparation\nfor transmission.","waiver_data":{}},{"code":"","desc":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \"ClientAliveInterval\" keyword with the\nfollowing command:\n\n # grep -iw clientaliveinterval /etc/ssh/sshd_config\n\n ClientAliveInterval 600\n\n If \"ClientAliveInterval\" is not configured, commented out, or has a value\nof \"0\", this is a finding.\n\n If \"ClientAliveInterval\" has a value that is greater than \"600\" and is\nnot documented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.","label":"check"},{"data":"Configure the operating system to automatically terminate a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveInterval 600\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72237","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72237.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","satisfies":["SRG-OS-000163-GPOS-00072","SRG-OS-000279-GPOS-00109"],"gid":"V-72237","rid":"SV-86861r4_rule","stig_id":"RHEL-07-040320","fix_id":"F-78591r2_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic are terminated at the\nend of the session or after 10 minutes of inactivity, except to fulfill\ndocumented and validated mission requirements.","waiver_data":{}},{"code":"","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon does not allow authentication using RSA rhosts\nauthentication.\n\n To determine how the SSH daemon's \"RhostsRSAAuthentication\" option is\nset, run the following command:\n\n # grep RhostsRSAAuthentication /etc/ssh/sshd_config\n RhostsRSAAuthentication no\n\n If the value is returned as \"yes\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using RSA rhosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"no\":\n\n RhostsRSAAuthentication no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72239","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72239.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72239","rid":"SV-86863r4_rule","stig_id":"RHEL-07-040330","fix_id":"F-78593r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using RSA rhosts\nauthentication.","waiver_data":{}},{"code":"","desc":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \"ClientAliveCountMax\" keyword with the\nfollowing command:\n\n # grep -i clientalivecount /etc/ssh/sshd_config\n ClientAliveCountMax 0\n\n If \"ClientAliveCountMax\" is not set to \"0\", this is a finding.","label":"check"},{"data":"Configure the operating system to terminate automatically a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveCountMax 0\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72241","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72241.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","satisfies":["SRG-OS-000163-GPOS-00072","SRG-OS-000279-GPOS-00109"],"gid":"V-72241","rid":"SV-86865r4_rule","stig_id":"RHEL-07-040340","fix_id":"F-78595r4_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic terminate after a\nperiod of inactivity.","waiver_data":{}},{"code":"","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \"IgnoreRhosts\" option is set, run the\nfollowing command:\n\n # grep -i IgnoreRhosts /etc/ssh/sshd_config\n\n IgnoreRhosts yes\n\n If the value is returned as \"no\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"yes\":\n\n IgnoreRhosts yes","label":"fix"}],"id":"V-72243","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72243.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72243","rid":"SV-86867r3_rule","stig_id":"RHEL-07-040350","fix_id":"F-78597r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using rhosts authentication.","waiver_data":{}},{"code":"","desc":"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.","descriptions":[{"data":"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify SSH provides users with feedback on when account accesses last\noccurred.\n\n Check that \"PrintLastLog\" keyword in the sshd daemon configuration file\nis used and set to \"yes\" with the following command:\n\n # grep -i printlastlog /etc/ssh/sshd_config\n PrintLastLog yes\n\n If the \"PrintLastLog\" keyword is set to \"no\", is missing, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to provide users with feedback on when account accesses last\noccurred by setting the required configuration options in \"/etc/pam.d/sshd\"\nor in the \"sshd_config\" file used by the system (\"/etc/ssh/sshd_config\"\nwill be used in the example) (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor).\n\n Modify the \"PrintLastLog\" line in \"/etc/ssh/sshd_config\" to match the\nfollowing:\n\n PrintLastLog yes\n\n The SSH service must be restarted for changes to \"sshd_config\" to take\neffect.","label":"fix"}],"id":"V-72245","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72245.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72245","rid":"SV-86869r3_rule","stig_id":"RHEL-07-040360","fix_id":"F-78599r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon an SSH logon.","waiver_data":{}},{"code":"","desc":"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.","descriptions":[{"data":"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify remote access using SSH prevents users from logging on directly as\nroot.\n\n Check that SSH prevents users from logging on directly as root with the\nfollowing command:\n\n # grep -i permitrootlogin /etc/ssh/sshd_config\n PermitRootLogin no\n\n If the \"PermitRootLogin\" keyword is set to \"yes\", is missing, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to stop users from logging on remotely as the root user.\n\n Edit the appropriate \"/etc/ssh/sshd_config\" file to uncomment or add the\nline for the \"PermitRootLogin\" keyword and set its value to \"no\" (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor):\n\n PermitRootLogin no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72247","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72247.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72247","rid":"SV-86871r3_rule","stig_id":"RHEL-07-040370","fix_id":"F-78601r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not permit direct\nlogons to the root account using remote access via SSH.","waiver_data":{}},{"code":"","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \"IgnoreUserKnownHosts\" option is set,\nrun the following command:\n\n # grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config\n\n IgnoreUserKnownHosts yes\n\n If the value is returned as \"no\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"yes\":\n\n IgnoreUserKnownHosts yes\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72249","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72249.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72249","rid":"SV-86873r3_rule","stig_id":"RHEL-07-040380","fix_id":"F-78603r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using known hosts\nauthentication.","waiver_data":{}},{"code":"","desc":"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.","descriptions":[{"data":"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon is configured to only use the SSHv2 protocol.\n\n Check that the SSH daemon is configured to only use the SSHv2 protocol with\nthe following command:\n\n # grep -i protocol /etc/ssh/sshd_config\n Protocol 2\n #Protocol 1,2\n\n If any protocol line other than \"Protocol 2\" is uncommented, this is a\nfinding.","label":"check"},{"data":"Remove all Protocol lines that reference version \"1\" in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor). The \"Protocol\" line must be as follows:\n\n Protocol 2\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72251","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72251.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000074-GPOS-00042","satisfies":["SRG-OS-000074-GPOS-00042","SRG-OS-000480-GPOS-00227"],"gid":"V-72251","rid":"SV-86875r4_rule","stig_id":"RHEL-07-040390","fix_id":"F-78605r2_fix","cci":["CCI-000197","CCI-000366"],"nist":["IA-5 (1) (c)","CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use the SSHv2 protocol.","waiver_data":{}},{"code":"","desc":"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.","descriptions":[{"data":"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n Check that the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers with the following command:\n\n # grep -i macs /etc/ssh/sshd_config\n MACs hmac-sha2-256,hmac-sha2-512\n\n If any ciphers other than \"hmac-sha2-256\" or \"hmac-sha2-512\" are listed\nor the returned line is commented out, this is a finding.","label":"check"},{"data":"Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the\n\"MACs\" keyword and set its value to \"hmac-sha2-256\" and/or\n\"hmac-sha2-512\" (this file may be named differently or be in a different\nlocation if using a version of SSH that is provided by a third-party vendor):\n\n MACs hmac-sha2-256,hmac-sha2-512\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72253","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72253.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72253","rid":"SV-86877r3_rule","stig_id":"RHEL-07-040400","fix_id":"F-78607r2_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use Message Authentication Codes\n(MACs) employing FIPS 140-2 approved cryptographic hash algorithms.","waiver_data":{}},{"code":"","desc":"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.","descriptions":[{"data":"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH public host key files have mode \"0644\" or less permissive.\n\n Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n The following command will find all SSH public key files on the system:\n\n # find /etc/ssh -name '*.pub' -exec ls -lL {} \\;\n\n -rw-r--r-- 1 root root 618 Nov 28 06:43 ssh_host_dsa_key.pub\n -rw-r--r-- 1 root root 347 Nov 28 06:43 ssh_host_key.pub\n -rw-r--r-- 1 root root 238 Nov 28 06:43 ssh_host_rsa_key.pub\n\n If any file has a mode more permissive than \"0644\", this is a finding.","label":"check"},{"data":"Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n Change the mode of public host key files under \"/etc/ssh\" to \"0644\"\nwith the following command:\n\n # chmod 0644 /etc/ssh/*.key.pub","label":"fix"}],"id":"V-72255","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72255.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72255","rid":"SV-86879r2_rule","stig_id":"RHEL-07-040410","fix_id":"F-78609r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH public host key files have mode 0644 or less permissive.","waiver_data":{}},{"code":"","desc":"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.","descriptions":[{"data":"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH private host key files have mode \"0640\" or less permissive.\n\n The following command will find all SSH private key files on the system and\nlist their modes:\n\n # find / -name '*ssh_host*key' | xargs ls -lL\n\n -rw-r----- 1 root ssh_keys 668 Nov 28 06:43 ssh_host_dsa_key\n -rw-r----- 1 root ssh_keys 582 Nov 28 06:43 ssh_host_key\n -rw-r----- 1 root ssh_keys 887 Nov 28 06:43 ssh_host_rsa_key\n\n If any file has a mode more permissive than \"0640\", this is a finding.","label":"check"},{"data":"Configure the mode of SSH private host key files under \"/etc/ssh\" to\n\"0640\" with the following command:\n\n # chmod 0640 /path/to/file/ssh_host*key","label":"fix"}],"id":"V-72257","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72257.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72257","rid":"SV-86881r3_rule","stig_id":"RHEL-07-040420","fix_id":"F-78611r5_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH private host key files have mode 0640 or less permissive.","waiver_data":{}},{"code":"","desc":"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.","descriptions":[{"data":"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not permit GSSAPI authentication unless approved.\n\n Check that the SSH daemon does not permit GSSAPI authentication with the\nfollowing command:\n\n # grep -i gssapiauth /etc/ssh/sshd_config\n GSSAPIAuthentication no\n\n If the \"GSSAPIAuthentication\" keyword is missing, is set to \"yes\" and\nis not documented with the Information System Security Officer (ISSO), or the\nreturned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"GSSAPIAuthentication\" keyword in \"/etc/ssh/sshd_config\"\n(this file may be named differently or be in a different location if using a\nversion of SSH that is provided by a third-party vendor) and set the value to\n\"no\":\n\n GSSAPIAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If GSSAPI authentication is required, it must be documented, to include the\nlocation of the configuration file, with the ISSO.","label":"fix"}],"id":"V-72259","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72259.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72259","rid":"SV-86883r3_rule","stig_id":"RHEL-07-040430","fix_id":"F-78613r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Generic Security Service Application\nProgram Interface (GSSAPI) authentication unless needed.","waiver_data":{}},{"code":"","desc":"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.","descriptions":[{"data":"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not permit Kerberos to authenticate passwords\nunless approved.\n\n Check that the SSH daemon does not permit Kerberos to authenticate\npasswords with the following command:\n\n # grep -i kerberosauth /etc/ssh/sshd_config\n KerberosAuthentication no\n\n If the \"KerberosAuthentication\" keyword is missing, or is set to \"yes\"\nand is not documented with the Information System Security Officer (ISSO), or\nthe returned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"KerberosAuthentication\" keyword in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \"no\":\n\n KerberosAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If Kerberos authentication is required, it must be documented, to include\nthe location of the configuration file, with the ISSO.","label":"fix"}],"id":"V-72261","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72261.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72261","rid":"SV-86885r3_rule","stig_id":"RHEL-07-040440","fix_id":"F-78615r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Kerberos authentication unless needed.","waiver_data":{}},{"code":"","desc":"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.","descriptions":[{"data":"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs strict mode checking of home directory\nconfiguration files.\n\n The location of the \"sshd_config\" file may vary if a different daemon is\nin use.\n\n Inspect the \"sshd_config\" file with the following command:\n\n # grep -i strictmodes /etc/ssh/sshd_config\n\n StrictModes yes\n\n If \"StrictModes\" is set to \"no\", is missing, or the returned line is\ncommented out, this is a finding.","label":"check"},{"data":"Uncomment the \"StrictModes\" keyword in \"/etc/ssh/sshd_config\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) and set the value to \"yes\":\n\n StrictModes yes\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72263","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72263.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72263","rid":"SV-86887r3_rule","stig_id":"RHEL-07-040450","fix_id":"F-78617r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon performs strict mode checking of home directory\nconfiguration files.","waiver_data":{}},{"code":"","desc":"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.","descriptions":[{"data":"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs privilege separation.\n\n Check that the SSH daemon performs privilege separation with the following\ncommand:\n\n # grep -i usepriv /etc/ssh/sshd_config\n\n UsePrivilegeSeparation sandbox\n\n If the \"UsePrivilegeSeparation\" keyword is set to \"no\", is missing, or\nthe returned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"UsePrivilegeSeparation\" keyword in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \"sandbox\" or \"yes\":\n\n UsePrivilegeSeparation sandbox\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72265","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72265.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72265","rid":"SV-86889r3_rule","stig_id":"RHEL-07-040460","fix_id":"F-78619r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon uses privilege separation.","waiver_data":{}},{"code":"","desc":"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.","descriptions":[{"data":"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs compression after a user successfully\nauthenticates.\n\n Check that the SSH daemon performs compression after a user successfully\nauthenticates with the following command:\n\n # grep -i compression /etc/ssh/sshd_config\n Compression delayed\n\n If the \"Compression\" keyword is set to \"yes\", is missing, or the\nreturned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"Compression\" keyword in \"/etc/ssh/sshd_config\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) on the system and set the\nvalue to \"delayed\" or \"no\":\n\n Compression no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72267","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72267.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72267","rid":"SV-86891r3_rule","stig_id":"RHEL-07-040470","fix_id":"F-78621r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow compression or only allows compression after\nsuccessful authentication.","waiver_data":{}},{"code":"","desc":"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).","descriptions":[{"data":"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if NTP is running in continuous mode:\n\n # ps -ef | grep ntp\n\n If NTP is not running, check to see if \"chronyd\" is running in continuous\nmode:\n\n # ps -ef | grep chronyd\n\n If NTP or \"chronyd\" is not running, this is a finding.\n\n If the NTP process is found, then check the \"ntp.conf\" file for the\n\"maxpoll\" option setting:\n\n # grep maxpoll /etc/ntp.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is set to \"17\" or is not set, this is a finding.\n\n If the file does not exist, check the \"/etc/cron.daily\" subdirectory for\na crontab file controlling the execution of the \"ntpd -q\" command.\n\n # grep -i \"ntpd -q\" /etc/cron.daily/*\n # ls -al /etc/cron.* | grep ntp\n\n ntp\n\n If a crontab file does not exist in the \"/etc/cron.daily\" that executes\nthe \"ntpd -q\" command, this is a finding.\n\n If the \"chronyd\" process is found, then check the \"chrony.conf\" file\nfor the \"maxpoll\" option setting:\n\n # grep maxpoll /etc/chrony.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is not set or the line is commented out, this is a finding.","label":"check"},{"data":"Edit the \"/etc/ntp.conf\" or \"/etc/chrony.conf\" file and add or update\nan entry to define \"maxpoll\" to \"10\" as follows:\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If NTP was running and \"maxpoll\" was updated, the NTP service must be\nrestarted:\n\n # systemctl restart ntpd\n\n If NTP was not running, it must be started:\n\n # systemctl start ntpd\n\n If \"chronyd\" was running and \"maxpoll\" was updated, the service must be\nrestarted:\n\n # systemctl restart chronyd.service\n\n If \"chronyd\" was not running, it must be started:\n\n # systemctl start chronyd.service","label":"fix"}],"id":"V-72269","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72269.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000355-GPOS-00143","satisfies":["SRG-OS-000355-GPOS-00143","SRG-OS-000356-GPOS-00144"],"gid":"V-72269","rid":"SV-86893r5_rule","stig_id":"RHEL-07-040500","fix_id":"F-78623r5_fix","cci":["CCI-001891","CCI-002046"],"nist":["AU-8 (1) (a)","AU-8 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must, for networked\nsystems, synchronize clocks with a server that is synchronized to one of the\nredundant United States Naval Observatory (USNO) time servers, a time server\ndesignated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global\nPositioning System (GPS).","waiver_data":{}},{"code":"","desc":"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.","descriptions":[{"data":"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enabled an application firewall.\n\n Check to see if \"firewalld\" is installed with the following command:\n\n # yum list installed firewalld\n firewalld-0.3.9-11.el7.noarch.rpm\n\n If the \"firewalld\" package is not installed, ask the System Administrator\nif another firewall application (such as iptables) is installed.\n\n If an application firewall is not installed, this is a finding.\n\n Check to see if the firewall is loaded and active with the following\ncommand:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago\n\n If \"firewalld\" does not show a status of \"loaded\" and \"active\", this\nis a finding.\n\n Check the state of the firewall:\n\n # firewall-cmd --state\n running\n\n If \"firewalld\" does not show a state of \"running\", this is a finding.","label":"check"},{"data":"Ensure the operating system's application firewall is enabled.\n\n Install the \"firewalld\" package, if it is not on the system, with the\nfollowing command:\n\n # yum install firewalld\n\n Start the firewall via \"systemctl\" with the following command:\n\n # systemctl start firewalld","label":"fix"}],"id":"V-72273","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72273.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","satisfies":["SRG-OS-000480-GPOS-00227","SRG-OS-000480-GPOS-00231","SRG-OS-000480-GPOS-00232"],"gid":"V-72273","rid":"SV-86897r2_rule","stig_id":"RHEL-07-040520","fix_id":"F-78627r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must enable an\napplication firewall, if available.","waiver_data":{}},{"code":"","desc":"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.","descriptions":[{"data":"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify users are provided with feedback on when account accesses last\noccurred.\n\n Check that \"pam_lastlog\" is used and not silent with the following\ncommand:\n\n # grep pam_lastlog /etc/pam.d/postlogin\n session required pam_lastlog.so showfailed\n\n If \"pam_lastlog\" is missing from \"/etc/pam.d/postlogin\" file, or the\nsilent option is present, this is a finding.","label":"check"},{"data":"Configure the operating system to provide users with feedback on when\naccount accesses last occurred by setting the required configuration options in\n\"/etc/pam.d/postlogin\".\n\n Add the following line to the top of \"/etc/pam.d/postlogin\":\n\n session required pam_lastlog.so showfailed","label":"fix"}],"id":"V-72275","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72275.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72275","rid":"SV-86899r4_rule","stig_id":"RHEL-07-040530","fix_id":"F-78629r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon logon.","waiver_data":{}},{"code":"","desc":"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.","descriptions":[{"data":"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify there are no \".shosts\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name '*.shosts'\n\n If any \".shosts\" files are found on the system, this is a finding.","label":"check"},{"data":"Remove any found \".shosts\" files from the system.\n\n# rm /[path]/[to]/[file]/.shosts","label":"fix"}],"id":"V-72277","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72277.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72277","rid":"SV-86901r2_rule","stig_id":"RHEL-07-040540","fix_id":"F-78631r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not contain .shosts\nfiles.","waiver_data":{}},{"code":"","desc":"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.","descriptions":[{"data":"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify there are no \"shosts.equiv\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name shosts.equiv\n\n If any \"shosts.equiv\" files are found on the system, this is a finding.","label":"check"},{"data":"Remove any found \"shosts.equiv\" files from the system.\n\n# rm /[path]/[to]/[file]/shosts.equiv","label":"fix"}],"id":"V-72279","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72279.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72279","rid":"SV-86903r2_rule","stig_id":"RHEL-07-040550","fix_id":"F-78633r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not contain\nshosts.equiv files.","waiver_data":{}},{"code":"","desc":"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.","descriptions":[{"data":"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.","label":"default"},{"data":"","label":"rationale"},{"data":"Determine whether the system is using local or DNS name resolution with the\nfollowing command:\n\n # grep hosts /etc/nsswitch.conf\n hosts: files dns\n\n If the DNS entry is missing from the host's line in the\n\"/etc/nsswitch.conf\" file, the \"/etc/resolv.conf\" file must be empty.\n\n Verify the \"/etc/resolv.conf\" file is empty with the following command:\n\n # ls -al /etc/resolv.conf\n -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf\n\n If local host authentication is being used and the \"/etc/resolv.conf\"\nfile is not empty, this is a finding.\n\n If the DNS entry is found on the host's line of the \"/etc/nsswitch.conf\"\nfile, verify the operating system is configured to use two or more name servers\nfor DNS resolution.\n\n Determine the name servers used by the system with the following command:\n\n # grep nameserver /etc/resolv.conf\n nameserver 192.168.1.2\n nameserver 192.168.1.3\n\n If less than two lines are returned that are not commented out, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to use two or more name servers for DNS\nresolution.\n\n Edit the \"/etc/resolv.conf\" file to uncomment or add the two or more\n\"nameserver\" option lines with the IP address of local authoritative name\nservers. If local host resolution is being performed, the \"/etc/resolv.conf\"\nfile must be empty. An empty \"/etc/resolv.conf\" file can be created as\nfollows:\n\n # echo -n > /etc/resolv.conf\n\n And then make the file immutable with the following command:\n\n # chattr +i /etc/resolv.conf\n\n If the \"/etc/resolv.conf\" file must be mutable, the required\nconfiguration must be documented with the Information System Security Officer\n(ISSO) and the file must be verified by the system file integrity tool.","label":"fix"}],"id":"V-72281","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72281.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72281","rid":"SV-86905r2_rule","stig_id":"RHEL-07-040600","fix_id":"F-78635r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"For Red Hat Enterprise Linux operating systems using DNS resolution,\nat least two name servers must be configured.","waiver_data":{}},{"code":"","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not accept IPv4 source-routed packets.\n\n # grep net.ipv4.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv4.conf.all.accept_source_route = 0\n\n If \" net.ipv4.conf.all.accept_source_route \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.accept_source_route\n net.ipv4.conf.all.accept_source_route = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl -system","label":"fix"}],"id":"V-72283","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72283.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72283","rid":"SV-86907r2_rule","stig_id":"RHEL-07-040610","fix_id":"F-78637r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets.","waiver_data":{}},{"code":"","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not accept IPv4 source-routed packets by default.\n\n # grep net.ipv4.conf.default.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n net.ipv4.conf.default.accept_source_route = 0\n\n If \" net.ipv4.conf.default.accept_source_route \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.accept_source_route\n net.ipv4.conf.default.accept_source_route = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72285","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72285.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72285","rid":"SV-86909r2_rule","stig_id":"RHEL-07-040620","fix_id":"F-78639r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets by default.","waiver_data":{}},{"code":"","desc":"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.","descriptions":[{"data":"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast\naddress.\n\n # grep net.ipv4.icmp_echo_ignore_broadcasts /etc/sysctl.conf /etc/sysctl.d/*\n\n If \" net.ipv4.icmp_echo_ignore_broadcasts\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the\n\"icmp_echo_ignore_broadcasts\" variable with the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.icmp_echo_ignore_broadcasts\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72287","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72287.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72287","rid":"SV-86911r2_rule","stig_id":"RHEL-07-040630","fix_id":"F-78641r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not respond to\nInternet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP)\nechoes sent to a broadcast address.","waiver_data":{}},{"code":"","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system will not accept IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.default.accept_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \" net.ipv4.conf.default.accept_redirects \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the value of the\n\"accept_redirects\" variables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.accept_redirects'\n net.ipv4.conf.default.accept_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to not accept IPv4 ICMP redirect messages by adding the\nfollowing line to \"/etc/sysctl.conf\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72289","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72289.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72289","rid":"SV-86913r3_rule","stig_id":"RHEL-07-040640","fix_id":"F-78643r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages from being accepted.","waiver_data":{}},{"code":"","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n # grep 'net.ipv4.conf.default.send_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \"net.ipv4.conf.default.send_redirects\" is not configured in the\n\"/etc/sysctl.conf\" file or in the /etc/sysctl.d/ directory, is commented out\nor does not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"default send_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.send_redirects'\n\n net.ipv4.conf.default.send_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Configure the system to not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72291","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72291.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72291","rid":"SV-86915r4_rule","stig_id":"RHEL-07-040650","fix_id":"F-78645r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow\ninterfaces to perform Internet Protocol version 4 (IPv4) Internet Control\nMessage Protocol (ICMP) redirects by default.","waiver_data":{}},{"code":"","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not send IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.send_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \"net.ipv4.conf.all.send_redirects\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"all send_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.send_redirects'\n\n net.ipv4.conf.all.send_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Configure the system to not allow interfaces to perform IPv4 ICMP\nredirects.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72293","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72293.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72293","rid":"SV-86917r3_rule","stig_id":"RHEL-07-040660","fix_id":"F-78647r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not send Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.","waiver_data":{}},{"code":"","desc":"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.","descriptions":[{"data":"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify network interfaces are not in promiscuous mode unless approved by\nthe ISSO and documented.\n\n Check for the status with the following command:\n\n # ip link | grep -i promisc\n\n If network interfaces are found on the system in promiscuous mode and their\nuse has not been approved by the ISSO and documented, this is a finding.","label":"check"},{"data":"Configure network interfaces to turn off promiscuous mode unless approved\nby the ISSO and documented.\n\n Set the promiscuous mode of an interface to off with the following command:\n\n #ip link set dev multicast off promisc off","label":"fix"}],"id":"V-72295","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72295.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72295","rid":"SV-86919r2_rule","stig_id":"RHEL-07-040670","fix_id":"F-78649r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"Network interfaces configured on the Red Hat Enterprise Linux\noperating system must not be in promiscuous mode.","waiver_data":{}},{"code":"","desc":"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.","descriptions":[{"data":"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is configured to prevent unrestricted mail relaying.\n\n Determine if \"postfix\" is installed with the following commands:\n\n # yum list installed postfix\n postfix-2.6.6-6.el7.x86_64.rpm\n\n If postfix is not installed, this is Not Applicable.\n\n If postfix is installed, determine if it is configured to reject\nconnections from unknown or untrusted networks with the following command:\n\n # postconf -n smtpd_client_restrictions\n smtpd_client_restrictions = permit_mynetworks, reject\n\n If the \"smtpd_client_restrictions\" parameter contains any entries other\nthan \"permit_mynetworks\" and \"reject\", this is a finding.","label":"check"},{"data":"If \"postfix\" is installed, modify the \"/etc/postfix/main.cf\" file to\nrestrict client connections to the local network with the following command:\n\n # postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'","label":"fix"}],"id":"V-72297","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72297.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72297","rid":"SV-86921r3_rule","stig_id":"RHEL-07-040680","fix_id":"F-78651r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nprevent unrestricted mail relaying.","waiver_data":{}},{"code":"","desc":"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.","descriptions":[{"data":"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify an FTP server has not been installed on the system.\n\n Check to see if an FTP server has been installed with the following\ncommands:\n\n # yum list installed vsftpd\n\n vsftpd-3.0.2.el7.x86_64.rpm\n\n If \"vsftpd\" is installed and is not documented with the Information\nSystem Security Officer (ISSO) as an operational requirement, this is a finding.","label":"check"},{"data":"Document the \"vsftpd\" package with the ISSO as an operational requirement\nor remove it from the system with the following command:\n\n # yum remove vsftpd","label":"fix"}],"id":"V-72299","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72299.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72299","rid":"SV-86923r3_rule","stig_id":"RHEL-07-040690","fix_id":"F-78653r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have a File\nTransfer Protocol (FTP) server package installed unless needed.","waiver_data":{}},{"code":"","desc":"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.","descriptions":[{"data":"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify a TFTP server has not been installed on the system.\n\n Check to see if a TFTP server has been installed with the following command:\n\n # yum list installed tftp-server\n tftp-server-0.49-9.el7.x86_64.rpm\n\n If TFTP is installed and the requirement for TFTP is not documented with\nthe ISSO, this is a finding.","label":"check"},{"data":"Remove the TFTP package from the system with the following command:\n\n# yum remove tftp-server","label":"fix"}],"id":"V-72301","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72301.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72301","rid":"SV-86925r2_rule","stig_id":"RHEL-07-040700","fix_id":"F-78655r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must not have the\nTrivial File Transfer Protocol (TFTP) server package installed if not required\nfor operational support.","waiver_data":{}},{"code":"","desc":"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.","descriptions":[{"data":"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify remote X connections for interactive users are encrypted.\n\n Check that remote X connections are encrypted with the following command:\n\n # grep -i x11forwarding /etc/ssh/sshd_config | grep -v \"^#\"\n\n X11Forwarding yes\n\n If the \"X11Forwarding\" keyword is set to \"no\" or is missing, this is a\nfinding.","label":"check"},{"data":"Configure SSH to encrypt connections for interactive users.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the\n\"X11Forwarding\" keyword and set its value to \"yes\" (this file may be named\ndifferently or be in a different location if using a version of SSH that is\nprovided by a third-party vendor):\n\n X11Forwarding yes\n\n The SSH service must be restarted for changes to take effect:\n\n # systemctl restart sshd","label":"fix"}],"id":"V-72303","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72303.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72303","rid":"SV-86927r4_rule","stig_id":"RHEL-07-040710","fix_id":"F-78657r6_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat remote X connections for interactive users are encrypted.","waiver_data":{}},{"code":"","desc":"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.","descriptions":[{"data":"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the TFTP daemon is configured to operate in secure mode.\n\n Check to see if a TFTP server has been installed with the following\ncommands:\n\n # yum list installed tftp-server\n tftp-server.x86_64 x.x-x.el7 rhel-7-server-rpms\n\n If a TFTP server is not installed, this is Not Applicable.\n\n If a TFTP server is installed, check for the server arguments with the\nfollowing command:\n\n # grep server_args /etc/xinetd.d/tftp\n server_args = -s /var/lib/tftpboot\n\n If the \"server_args\" line does not have a \"-s\" option and a\nsubdirectory is not assigned, this is a finding.","label":"check"},{"data":"Configure the TFTP daemon to operate in secure mode by adding the following\nline to \"/etc/xinetd.d/tftp\" (or modify the line to have the required value):\n\n server_args = -s /var/lib/tftpboot","label":"fix"}],"id":"V-72305","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72305.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72305","rid":"SV-86929r3_rule","stig_id":"RHEL-07-040720","fix_id":"F-78659r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP\ndaemon is configured to operate in secure mode.","waiver_data":{}},{"code":"","desc":"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.","descriptions":[{"data":"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that if the system has X Windows System installed, it is authorized.\n\n Check for the X11 package with the following command:\n\n # rpm -qa | grep xorg | grep server\n\n Ask the System Administrator if use of the X Windows System is an\noperational requirement.\n\n If the use of X Windows on the system is not documented with the\nInformation System Security Officer (ISSO), this is a finding.","label":"check"},{"data":"Document the requirement for an X Windows server with the ISSO or remove\nthe related packages with the following commands:\n\n # rpm -e xorg-x11-server-common","label":"fix"}],"id":"V-72307","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72307.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72307","rid":"SV-86931r4_rule","stig_id":"RHEL-07-040730","fix_id":"F-78661r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have an X\nWindows display manager installed unless approved.","waiver_data":{}},{"code":"","desc":"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.","descriptions":[{"data":"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is not performing packet forwarding, unless the system is\na router.\n\n # grep net.ipv4.ip_forward /etc/sysctl.conf /etc/sysctl.d/*\n\n net.ipv4.ip_forward = 0\n\n If \"net.ipv4.ip_forward\" is not configured in the /etc/sysctl.conf file\nor in the /etc/sysctl.d/ directory, is commented out, or does not have a value\nof \"0\", this is a finding.\n\n Check that the operating system does not implement IP forwarding using the\nfollowing command:\n\n # /sbin/sysctl -a | grep net.ipv4.ip_forward\n net.ipv4.ip_forward = 0\n\n If IP forwarding value is \"1\" and the system is hosting any application,\ndatabase, or web servers, this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.ip_forward = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72309","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72309.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72309","rid":"SV-86933r2_rule","stig_id":"RHEL-07-040740","fix_id":"F-78663r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not be performing\npacket forwarding unless the system is a router.","waiver_data":{}},{"code":"","desc":"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.","descriptions":[{"data":"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify \"AUTH_GSS\" is being used to authenticate NFS mounts.\n\n To check if the system is importing an NFS file system, look for any\nentries in the \"/etc/fstab\" file that have a file system type of \"nfs\" with\nthe following command:\n\n # cat /etc/fstab | grep nfs\n 192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=krb5:krb5i:krb5p\n\n If the system is mounting file systems via NFS and has the sec option\nwithout the \"krb5:krb5i:krb5p\" settings, the \"sec\" option has the \"sys\"\nsetting, or the \"sec\" option is missing, this is a finding.","label":"check"},{"data":"Update the \"/etc/fstab\" file so the option \"sec\" is defined for each\nNFS mounted file system and the \"sec\" option does not have the \"sys\"\nsetting.\n\n Ensure the \"sec\" option is defined as \"krb5:krb5i:krb5p\".","label":"fix"}],"id":"V-72311","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72311.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72311","rid":"SV-86935r4_rule","stig_id":"RHEL-07-040750","fix_id":"F-78665r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the Network File System (NFS) is configured to use RPCSEC_GSS.","waiver_data":{}},{"code":"","desc":"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.","descriptions":[{"data":"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a system using SNMP is not using default community strings.\n\n Check to see if the \"/etc/snmp/snmpd.conf\" file exists with the following\ncommand:\n\n # ls -al /etc/snmp/snmpd.conf\n -rw------- 1 root root 52640 Mar 12 11:08 snmpd.conf\n\n If the file does not exist, this is Not Applicable.\n\n If the file does exist, check for the default community strings with the\nfollowing commands:\n\n # grep public /etc/snmp/snmpd.conf\n # grep private /etc/snmp/snmpd.conf\n\n If either of these commands returns any output, this is a finding.","label":"check"},{"data":"If the \"/etc/snmp/snmpd.conf\" file exists, modify any lines\nthat contain a community string value of \"public\" or \"private\" to another\nstring value.","label":"fix"}],"id":"V-72313","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72313.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72313","rid":"SV-86937r2_rule","stig_id":"RHEL-07-040800","fix_id":"F-78667r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"SNMP community strings on the Red Hat Enterprise Linux operating\nsystem must be changed from the default.","waiver_data":{}},{"code":"","desc":"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.","descriptions":[{"data":"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.","label":"default"},{"data":"","label":"rationale"},{"data":"If the \"firewalld\" package is not installed, ask the System Administrator\n(SA) if another firewall application (such as iptables) is installed. If an\napplication firewall is not installed, this is a finding.\n\n Verify the system's access control program is configured to grant or deny\nsystem access to specific hosts.\n\n Check to see if \"firewalld\" is active with the following command:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago\n\n If \"firewalld\" is active, check to see if it is configured to grant or\ndeny access to specific hosts or services with the following commands:\n\n # firewall-cmd --get-default-zone\n public\n\n # firewall-cmd --list-all --zone=public\n public (active)\n target: default\n icmp-block-inversion: no\n interfaces: eth0\n sources:\n services: mdns ssh\n ports:\n protocols:\n masquerade: no\n forward-ports:\n icmp-blocks:\n\n If \"firewalld\" is not active, determine whether \"tcpwrappers\" is being\nused by checking whether the \"hosts.allow\" and \"hosts.deny\" files are empty\nwith the following commands:\n\n # ls -al /etc/hosts.allow\n rw-r----- 1 root root 9 Aug 2 23:13 /etc/hosts.allow\n\n # ls -al /etc/hosts.deny\n -rw-r----- 1 root root 9 Apr 9 2007 /etc/hosts.deny\n\n If \"firewalld\" and \"tcpwrappers\" are not installed, configured, and\nactive, ask the SA if another access control program (such as iptables) is\ninstalled and active. Ask the SA to show that the running configuration grants\nor denies access to specific hosts or services.\n\n If \"firewalld\" is active and is not configured to grant access to\nspecific hosts or \"tcpwrappers\" is not configured to grant or deny access to\nspecific hosts, this is a finding.","label":"check"},{"data":"If \"firewalld\" is installed and active on the system, configure rules for\nallowing specific services and hosts.\n\n If \"firewalld\" is not \"active\", enable \"tcpwrappers\" by configuring\n\"/etc/hosts.allow\" and \"/etc/hosts.deny\" to allow or deny access to\nspecific hosts.","label":"fix"}],"id":"V-72315","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72315.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72315","rid":"SV-86939r3_rule","stig_id":"RHEL-07-040810","fix_id":"F-78669r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system access control program\nmust be configured to grant or deny system access to specific hosts and\nservices.","waiver_data":{}},{"code":"","desc":"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).","descriptions":[{"data":"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not have unauthorized IP tunnels configured.\n\n Check to see if \"libreswan\" is installed with the following command:\n\n # yum list installed libreswan\n libreswan.x86-64 3.20-5.el7_4\n\n If \"libreswan\" is installed, check to see if the \"IPsec\" service is\nactive with the following command:\n\n # systemctl status ipsec\n ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec\n Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)\n Active: inactive (dead)\n\n If the \"IPsec\" service is active, check to see if any tunnels are\nconfigured in \"/etc/ipsec.conf\" and \"/etc/ipsec.d/\" with the following\ncommands:\n\n # grep -iw conn /etc/ipsec.conf /etc/ipsec.d/*.conf\n\n If there are indications that a \"conn\" parameter is configured for a\ntunnel, ask the System Administrator if the tunnel is documented with the ISSO.\n\n If \"libreswan\" is installed, \"IPsec\" is active, and an undocumented\ntunnel is active, this is a finding.","label":"check"},{"data":"Remove all unapproved tunnels from the system, or document them\nwith the ISSO.","label":"fix"}],"id":"V-72317","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72317.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72317","rid":"SV-86941r2_rule","stig_id":"RHEL-07-040820","fix_id":"F-78671r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have\nunauthorized IP tunnels configured.","waiver_data":{}},{"code":"","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"If IPv6 is not enabled, the key will not exist, and this is Not Applicable.\n\n Verify the system does not accept IPv6 source-routed packets.\n\n # grep net.ipv6.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv6.conf.all.accept_source_route = 0\n\n If \"net.ipv6.conf.all.accept_source_route\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv6.conf.all.accept_source_route\n net.ipv6.conf.all.accept_source_route = 0\n\n If the returned lines do not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter, if IPv6 is enabled, by\nadding the following line to \"/etc/sysctl.conf\" or a configuration file in\nthe /etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv6.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72319","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72319.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72319","rid":"SV-86943r2_rule","stig_id":"RHEL-07-040830","fix_id":"F-78673r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward IPv6\nsource-routed packets.","waiver_data":{}},{"code":"","desc":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","label":"default"},{"data":"Verify the operating system has the packages required for multifactor\nauthentication installed.\n\nCheck for the presence of the packages required to support multifactor\nauthentication with the following commands:\n\n# yum list installed esc\nesc-1.1.0-26.el7.noarch.rpm\n\n# yum list installed pam_pkcs11\npam_pkcs11-0.6.2-14.el7.noarch.rpm\n\nIf the \"esc\" and \"pam_pkcs11\" packages are not installed, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to implement multifactor authentication by\ninstalling the required packages.\n\nInstall the \"esc\" and \"pam_pkcs11\" packages on the system with the\nfollowing command:\n\n# yum install esc pam_pkcs11","label":"fix"}],"id":"V-72417","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72417.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72417","rid":"SV-87041r4_rule","stig_id":"RHEL-07-041001","fix_id":"F-78769r4_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must have the required\n packages for multifactor authentication installed.","waiver_data":{}},{"code":"","desc":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements multifactor authentication for\nremote access to privileged accounts via pluggable authentication modules (PAM).\n\n Check the \"/etc/sssd/sssd.conf\" file for the authentication services that\nare being used with the following command:\n\n # grep services /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf\n\n services = nss, pam\n\n If the \"pam\" service is not present on all \"services\" lines, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to implement multifactor authentication for\nremote access to privileged accounts via pluggable authentication modules (PAM).\n\n Modify all of the services lines in \"/etc/sssd/sssd.conf\" or in\nconfiguration files found under \"/etc/sssd/conf.d\" to include pam.","label":"fix"}],"id":"V-72427","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72427.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72427","rid":"SV-87051r4_rule","stig_id":"RHEL-07-041002","fix_id":"F-78779r3_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must implement\n multifactor authentication for access to privileged accounts via pluggable\n authentication modules (PAM).","waiver_data":{}},{"code":"","desc":"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements certificate status checking for PKI\nauthentication.\n\n Check to see if Online Certificate Status Protocol (OCSP) is enabled on the\nsystem with the following command:\n\n # grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -v \"^#\"\n\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n\n There should be at least three lines returned.\n\n If \"ocsp_on\" is not present in all uncommented \"cert_policy\" lines in\n\"/etc/pam_pkcs11/pam_pkcs11.conf\", this is a finding.","label":"check"},{"data":"Configure the operating system to do certificate status checking for PKI\nauthentication.\n\n Modify all of the \"cert_policy\" lines in\n\"/etc/pam_pkcs11/pam_pkcs11.conf\" to include \"ocsp_on\".","label":"fix"}],"id":"V-72433","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72433.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72433","rid":"SV-87057r5_rule","stig_id":"RHEL-07-041003","fix_id":"F-78785r3_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncertificate status checking for PKI authentication.","waiver_data":{}},{"code":"","desc":"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding a screensaver\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock delay setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i lock-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-delay\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock delay:\n\n /org/gnome/desktop/screensaver/lock-delay","label":"fix"}],"id":"V-73155","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73155.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-73155","rid":"SV-87807r4_rule","stig_id":"RHEL-07-010081","fix_id":"F-79601r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\n overriding the screensaver lock-delay setting for the graphical user interface.","waiver_data":{}},{"code":"","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding session idle\ndelay after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the session idle delay setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i idle-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/session/idle-delay\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a session\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in /etc/dconf/profile/user, the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the session idle delay:\n\n /org/gnome/desktop/session/idle-delay","label":"fix"}],"id":"V-73157","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73157.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-73157","rid":"SV-87809r4_rule","stig_id":"RHEL-07-010082","fix_id":"F-79603r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the session idle-delay setting for the graphical user interface.","waiver_data":{}},{"code":"","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \"pwquality\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \"pwquality\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uses \"pwquality\" to enforce the password\ncomplexity rules.\n\n Check for the use of \"pwquality\" with the following command:\n\n # cat /etc/pam.d/system-auth | grep pam_pwquality\n\n password required pam_pwquality.so retry=3\n\n If the command does not return an uncommented line containing the value\n\"pam_pwquality.so\", this is a finding.\n\n If the value of \"retry\" is set to \"0\" or greater than \"3\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to use \"pwquality\" to enforce password\ncomplexity rules.\n\n Add the following line to \"/etc/pam.d/system-auth\" (or modify the line to\nhave the required value):\n\n password required pam_pwquality.so retry=3\n\n Note: The value of \"retry\" should be between \"1\" and \"3\".","label":"fix"}],"id":"V-73159","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73159.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-73159","rid":"SV-87811r4_rule","stig_id":"RHEL-07-010119","fix_id":"F-79605r5_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, pwquality\nmust be used.","waiver_data":{}},{"code":"","desc":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","descriptions":[{"data":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are being NFS imported are configured with the\n\"noexec\" option.\n\n Find the file system(s) that contain the directories being imported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,noexec 0 0\n\n If a file system found in \"/etc/fstab\" refers to NFS and it does not have\nthe \"noexec\" option set, and use of NFS imported binaries is not documented\nwith the Information System Security Officer (ISSO) as an operational\nrequirement, this is a finding.\n\n Verify the NFS is mounted with the \"noexec\"option:\n\n # mount | grep nfs | grep noexec\n If no results are returned and use of NFS imported binaries is not\ndocumented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"noexec\" option on\nfile systems that are being imported via NFS.","label":"fix"}],"id":"V-73161","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73161.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-73161","rid":"SV-87813r2_rule","stig_id":"RHEL-07-021021","fix_id":"F-79607r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent binary\nfiles from being executed on file systems that are being imported via Network\nFile System (NFS).","waiver_data":{}},{"code":"","desc":"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.","descriptions":[{"data":"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the action the operating system takes if there is an error sending\naudit records to a remote system.\n\n Check the action that takes place if there is an error sending audit\nrecords to a remote system with the following command:\n\n # grep -i network_failure_action /etc/audisp/audisp-remote.conf\n network_failure_action = syslog\n\n If the value of the \"network_failure_action\" option is not \"syslog\",\n\"single\", or \"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the action the operating system takes if there is an error\nsending audit records to a remote system.\n\n Uncomment the \"network_failure_action\" option in\n\"/etc/audisp/audisp-remote.conf\" and set it to \"syslog\", \"single\", or\n\"halt\".\n\n network_failure_action = syslog","label":"fix"}],"id":"V-73163","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73163.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","gid":"V-73163","rid":"SV-87815r3_rule","stig_id":"RHEL-07-030321","fix_id":"F-79609r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when there is an error sending\naudit records to a remote system.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/group\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/group /etc/audit/audit.rules\n\n -w /etc/group -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/group\".\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/group -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73165","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73165.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73165","rid":"SV-87817r3_rule","stig_id":"RHEL-07-030871","fix_id":"F-79611r3_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/group.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/gshadow\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/gshadow /etc/audit/audit.rules\n\n -w /etc/gshadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/gshadow\".\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/gshadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73167","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73167.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73167","rid":"SV-87819r4_rule","stig_id":"RHEL-07-030872","fix_id":"F-79613r3_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/gshadow.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/shadow /etc/audit/audit.rules\n\n -w /etc/shadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Add or update the following file system rule in\n\"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/shadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73171","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73171.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73171","rid":"SV-87823r4_rule","stig_id":"RHEL-07-030873","fix_id":"F-79617r4_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/shadow.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/security/opasswd /etc/audit/audit.rules\n\n -w /etc/security/opasswd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Add or update the following file system rule in\n\"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/security/opasswd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect:\n # systemctl restart auditd","label":"fix"}],"id":"V-73173","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73173.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73173","rid":"SV-87825r5_rule","stig_id":"RHEL-07-030874","fix_id":"F-79619r6_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/opasswd.","waiver_data":{}},{"code":"","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system ignores IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.accept_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \" net.ipv4.conf.all.accept_redirects \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"accept_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.accept_redirects'\n\n net.ipv4.conf.all.accept_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to ignore IPv4 ICMP redirect messages by adding the\nfollowing line to \"/etc/sysctl.conf\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-73175","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73175.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-73175","rid":"SV-87827r4_rule","stig_id":"RHEL-07-040641","fix_id":"F-79621r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must ignore Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages.","waiver_data":{}},{"code":"","desc":"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.","descriptions":[{"data":"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that there are no wireless interfaces configured on the system.\n\n This is N/A for systems that do not have wireless network adapters.\n\n Check for the presence of active wireless interfaces with the following\ncommand:\n\n # nmcli device\n DEVICE TYPE STATE\n eth0 ethernet connected\n wlp3s0 wifi disconnected\n lo loopback unmanaged\n\n If a wireless interface is configured and its use on the system is not\ndocumented with the Information System Security Officer (ISSO), this is a\nfinding.","label":"check"},{"data":"Configure the system to disable all wireless network interfaces with the\nfollowing command:\n\n #nmcli radio wifi off","label":"fix"}],"id":"V-73177","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73177.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000424-GPOS-00188","gid":"V-73177","rid":"SV-87829r2_rule","stig_id":"RHEL-07-041010","fix_id":"F-79623r1_fix","cci":["CCI-001443","CCI-001444","CCI-002418"],"nist":["AC-18 (1)","AC-18 (1)","SC-8"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all wireless network adapters are disabled.","waiver_data":{}},{"code":"","desc":"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.","descriptions":[{"data":"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uniquely identifies and authenticates users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Determine which profile the system database is using with the following\ncommand:\n\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Note: The example is using the database local for the system, so the path\nis \"/etc/dconf/db/local.d\". This path must be modified if a database other\nthan local is being used.\n\n # grep enable-smartcard-authentication /etc/dconf/db/local.d/*\n\n enable-smartcard-authentication=true\n\n If \"enable-smartcard-authentication\" is set to \"false\" or the keyword\nis missing, this is a finding.","label":"check"},{"data":"Configure the operating system to uniquely identify and authenticate users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example is using the database local for the system, so if the\nsystem is using another database in \"/etc/dconf/profile/user\", the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/00-defaults\n\n Edit \"[org/gnome/login-screen]\" and add or update the following line:\n enable-smartcard-authentication=true\n\n Update the system databases:\n # dconf update","label":"fix"}],"id":"V-77819","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77819.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-77819","rid":"SV-92515r2_rule","stig_id":"RHEL-07-010061","fix_id":"F-84519r4_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate users using multifactor authentication via a graphical\nuser logon.","waiver_data":{}},{"code":"","desc":"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.","descriptions":[{"data":"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system disables the ability to load the DCCP kernel\nmodule.\n\n # grep -r dccp /etc/modprobe.d/* | grep -i \"/bin/true\" | grep -v \"^#\"\n\n install dccp /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of DCCP is not documented with the Information System Security Officer\n(ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use the DCCP kernel\nmodule.\n\n Check to see if the DCCP kernel module is disabled with the following\ncommand:\n\n # grep -i dccp /etc/modprobe.d/* | grep -i \"blacklist\" | grep -v \"^#\"\n\n blacklist dccp\n\n If the command does not return any output or the output is not \"blacklist\ndccp\", and use of the dccp kernel module is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to use the DCCP\nkernel module.\n\n Create a file under \"/etc/modprobe.d\" with the following command:\n\n # touch /etc/modprobe.d/dccp.conf\n\n Add the following line to the created file:\n\n install dccp /bin/true\n\n Ensure that the DCCP module is blacklisted:\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist dccp","label":"fix"}],"id":"V-77821","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77821.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000378-GPOS-00163","gid":"V-77821","rid":"SV-92517r3_rule","stig_id":"RHEL-07-020101","fix_id":"F-84521r3_fix","cci":["CCI-001958"],"nist":["IA-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the Datagram Congestion Control Protocol (DCCP) kernel module is disabled\nunless required.","waiver_data":{}},{"code":"","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must require authentication upon booting into\nsingle-user and maintenance modes.\n\n Check that the operating system requires authentication upon booting into\nsingle-user mode with the following command:\n\n # grep -i execstart /usr/lib/systemd/system/rescue.service | grep -i sulogin\n\n ExecStart=-/bin/sh -c \"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\"\n\n If \"ExecStart\" does not have \"/usr/sbin/sulogin\" as an option, this is\na finding.","label":"check"},{"data":"Configure the operating system to require authentication upon booting into\nsingle-user and maintenance modes.\n\n Add or modify the \"ExecStart\" line in\n\"/usr/lib/systemd/system/rescue.service\" to include \"/usr/sbin/sulogin\":\n\n ExecStart=-/bin/sh -c \"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\"","label":"fix"}],"id":"V-77823","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77823.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-77823","rid":"SV-92519r2_rule","stig_id":"RHEL-07-010481","fix_id":"F-84523r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"The Red Hat Enterprise Linux operating system must require\nauthentication upon booting into single-user and maintenance modes.","waiver_data":{}},{"code":"","desc":"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.","descriptions":[{"data":"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements virtual address space randomization.\n\n # grep kernel.randomize_va_space /etc/sysctl.conf /etc/sysctl.d/*\n\n kernel.randomize_va_space = 2\n\n If \"kernel.randomize_va_space\" is not configured in the /etc/sysctl.conf\nfile or in the /etc/sysctl.d/ directory, is commented out or does not have a\nvalue of \"2\", this is a finding.\n\n Check that the operating system implements virtual address space\nrandomization with the following command:\n\n # /sbin/sysctl -a | grep kernel.randomize_va_space\n\n kernel.randomize_va_space = 2\n\n If \"kernel.randomize_va_space\" does not have a value of \"2\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system implement virtual address space\nrandomization.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a config file in the /etc/sysctl.d/ directory\n(or modify the line to have the required value):\n\n kernel.randomize_va_space = 2\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-77825","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77825.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-77825","rid":"SV-92521r2_rule","stig_id":"RHEL-07-040201","fix_id":"F-84531r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must implement virtual\naddress space randomization.","waiver_data":{}},{"code":"","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding the screensaver\nlock-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock-enabled setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i lock-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-enabled\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock-enabled setting:\n\n /org/gnome/desktop/screensaver/lock-enabled","label":"fix"}],"id":"V-78995","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78995.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-78995","rid":"SV-93701r3_rule","stig_id":"RHEL-07-010062","fix_id":"F-85745r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver lock-enabled setting for the graphical user\ninterface.","waiver_data":{}},{"code":"","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding the screensaver\nidle-activation-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the idle-activation-enabled setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/idle-activation-enabled\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver idle-activation-enabled setting:\n\n /org/gnome/desktop/screensaver/idle-activation-enabled","label":"fix"}],"id":"V-78997","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78997.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-78997","rid":"SV-93703r2_rule","stig_id":"RHEL-07-010101","fix_id":"F-85747r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver idle-activation-enabled setting for the graphical\nuser interface.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"create_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw create_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"create_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"create_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-78999","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78999.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-78999","rid":"SV-93705r3_rule","stig_id":"RHEL-07-030819","fix_id":"F-85749r4_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe create_module syscall.","waiver_data":{}},{"code":"","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"finit_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw finit_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"finit_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"finit_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-79001","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-79001.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-79001","rid":"SV-93707r3_rule","stig_id":"RHEL-07-030821","fix_id":"F-85751r3_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe finit_module syscall.","waiver_data":{}},{"code":"","desc":"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.","descriptions":[{"data":"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that /etc/pam.d/passwd is configured to use /etc/pam.d/system-auth\nwhen changing passwords:\n\n # cat /etc/pam.d/passwd | grep -i substack | grep -i system-auth\n password substack system-auth\n\n If no results are returned, the line is commented out, this is a finding.","label":"check"},{"data":"Configure PAM to utilize /etc/pam.d/system-auth when changing passwords.\n\n Add the following line to \"/etc/pam.d/passwd\" (or modify the line to have\nthe required value):\n\n password substack system-auth","label":"fix"}],"id":"V-81003","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81003.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-81003","rid":"SV-95715r1_rule","stig_id":"RHEL-07-010118","fix_id":"F-87837r1_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing\npasswords.","waiver_data":{}},{"code":"","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use UEFI, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -iw grub2_password /boot/grub2/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \"grub.pbkdf2.sha512\", this is a\nfinding.\n\n Verify that the \"root\" account is set as the \"superusers\":\n\n # grep -iw \"superusers\" /boot/grub2/grub.cfg\n set superusers=\"root\"\n export superusers\n\n If \"superusers\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/grub2/grub.cfg file and add or modify the following lines in\nthe \"### BEGIN /etc/grub.d/01_users ###\" section:\n\n set superusers=\"root\"\n export superusers","label":"fix"}],"id":"V-81005","impact":0.7,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81005.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-81005","rid":"SV-95717r1_rule","stig_id":"RHEL-07-010482","fix_id":"F-87839r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems version 7.2 or newer with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.","waiver_data":{}},{"code":"","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use BIOS, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \"grub.pbkdf2.sha512\", this is a\nfinding.\n\n Verify that the \"root\" account is set as the \"superusers\":\n\n # grep -iw \"superusers\" /boot/efi/EFI/redhat/grub.cfg\n set superusers=\"root\"\n export superusers\n\n If \"superusers\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/efi/EFI/redhat/grub.cfg file and add or modify the following\nlines in the \"### BEGIN /etc/grub.d/01_users ###\" section:\n\n set superusers=\"root\"\n export superusers","label":"fix"}],"id":"V-81007","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81007.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-81007","rid":"SV-95719r1_rule","stig_id":"RHEL-07-010491","fix_id":"F-87841r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems version 7.2 or newer using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.","waiver_data":{}},{"code":"","desc":"The \"nodev\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","descriptions":[{"data":"The \"nodev\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"nodev\" option is configured for /dev/shm:\n\n\n # cat /etc/fstab | grep /dev/shm\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"nodev\" option is not listed, this is\na finding.\n\n Verify \"/dev/shm\" is mounted with the \"nodev\" option:\n\n # mount | grep \"/dev/shm\" | grep nodev\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"nodev\" option.","label":"fix"}],"id":"V-81009","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81009.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81009","rid":"SV-95721r2_rule","stig_id":"RHEL-07-021022","fix_id":"F-87843r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nodev option.","waiver_data":{}},{"code":"","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"nosuid\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"nosuid\" option is not listed, this\nis a finding.\n\n Verify \"/dev/shm\" is mounted with the \"nosuid\" option:\n\n # mount | grep \"/dev/shm\" | grep nosuid\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"nosuid\" option.","label":"fix"}],"id":"V-81011","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81011.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81011","rid":"SV-95723r2_rule","stig_id":"RHEL-07-021023","fix_id":"F-87845r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nosuid option.","waiver_data":{}},{"code":"","desc":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","descriptions":[{"data":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"noexec\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"noexec\" option is not listed, this\nis a finding.\n\n Verify \"/dev/shm\" is mounted with the \"noexec\" option:\n\n # mount | grep \"/dev/shm\" | grep noexec\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"noexec\" option.","label":"fix"}],"id":"V-81013","impact":0.3,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81013.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81013","rid":"SV-95725r2_rule","stig_id":"RHEL-07-021024","fix_id":"F-87847r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe noexec option.","waiver_data":{}},{"code":"","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the \"au-remote\" plugin is active on the system:\n\n # grep \"active\" /etc/audisp/plugins.d/au-remote.conf\n\n active = yes\n\n If the \"active\" setting is not set to \"yes\", or the line is commented\nout, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/plugins.d/au-remote.conf file and change the value of\n\"active\" to \"yes\".\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81015","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81015.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81015","rid":"SV-95727r1_rule","stig_id":"RHEL-07-030200","fix_id":"F-87849r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nuse the au-remote plugin.","waiver_data":{}},{"code":"","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the \"au-remote\" plugin is configured to always off-load audit logs\nusing the audisp-remote daemon:\n\n # cat /etc/audisp/plugins.d/au-remote.conf | grep -v \"^#\"\n\n active = yes\n direction = out\n path = /sbin/audisp-remote\n type = always\n format = string\n\n If the \"direction\" setting is not set to \"out\", or the line is\ncommented out, this is a finding.\n\n If the \"path\" setting is not set to \"/sbin/audisp-remote\", or the line\nis commented out, this is a finding.\n\n If the \"type\" setting is not set to \"always\", or the line is commented\nout, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/plugins.d/au-remote.conf file and add or update the\nfollowing values:\n\n direction = out\n path = /sbin/audisp-remote\n type = always\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81017","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81017.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81017","rid":"SV-95729r1_rule","stig_id":"RHEL-07-030201","fix_id":"F-87851r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must configure the\nau-remote plugin to off-load audit logs using the audisp-remote daemon.","waiver_data":{}},{"code":"","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the audisp daemon is configured to take an appropriate action when\nthe internal queue is full:\n\n # grep \"overflow_action\" /etc/audisp/audispd.conf\n\n overflow_action = syslog\n\n If the \"overflow_action\" option is not \"syslog\", \"single\", or\n\"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/audispd.conf file and add or update the\n\"overflow_action\" option:\n\n overflow_action = syslog\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81019","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81019.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81019","rid":"SV-95731r1_rule","stig_id":"RHEL-07-030210","fix_id":"F-87853r3_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must take appropriate\naction when the audisp-remote buffer is full.","waiver_data":{}},{"code":"","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the audisp daemon is configured to label all off-loaded audit logs:\n\n # grep \"name_format\" /etc/audisp/audispd.conf\n\n name_format = hostname\n\n If the \"name_format\" option is not \"hostname\", \"fqd\", or \"numeric\",\nor the line is commented out, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/audispd.conf file and add or update the\n\"name_format\" option:\n\n name_format = hostname\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81021","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81021.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81021","rid":"SV-95733r1_rule","stig_id":"RHEL-07-030211","fix_id":"F-87855r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must label all\noff-loaded audit logs before sending them to the central log server.","waiver_data":{}},{"code":"","desc":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","descriptions":[{"data":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.all.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.all.rp_filter = 1\n\n If \"net.ipv4.conf.all.rp_filter\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.rp_filter\n net.ipv4.conf.all.rp_filter = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-92251","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92251.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-92251","rid":"SV-102353r1_rule","stig_id":"RHEL-07-040611","fix_id":"F-98473r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible on all interfaces.","waiver_data":{}},{"code":"","desc":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","descriptions":[{"data":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.default.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.default.rp_filter = 1\n\n If \"net.ipv4.conf.default.rp_filter\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.rp_filter\n net.ipv4.conf.default.rp_filter = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-92253","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92253.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-92253","rid":"SV-102355r1_rule","stig_id":"RHEL-07-040612","fix_id":"F-98475r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible by default.","waiver_data":{}},{"code":"","desc":"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.","descriptions":[{"data":"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.","label":"default"},{"data":"","label":"rationale"},{"data":"Ask the SA or ISSO if a host-based intrusion detection application is\nloaded on the system. Per OPORD 16-0080, the preferred intrusion detection\nsystem is McAfee HBSS available through the U.S. Cyber Command (USCYBERCOM).\n\n If another host-based intrusion detection application is in use, such as\nSELinux, this must be documented and approved by the local Authorizing Official.\n\n Procedure:\n Examine the system to determine if the Host Intrusion Prevention System\n(HIPS) is installed:\n\n # rpm -qa | grep MFEhiplsm\n\n Verify that the McAfee HIPS module is active on the system:\n\n # ps -ef | grep -i “hipclient”\n\n If the MFEhiplsm package is not installed, check for another intrusion\ndetection system:\n\n # find / -name \n\n Where is the name of the primary application daemon to\ndetermine if the application is loaded on the system.\n\n Determine if the application is active on the system:\n\n # ps -ef | grep -i \n\n If the MFEhiplsm package is not installed and an alternate host-based\nintrusion detection application has not been documented for use, this is a\nfinding.\n\n If no host-based intrusion detection system is installed and running on the\nsystem, this is a finding.","label":"check"},{"data":"Install and enable the latest McAfee HIPS package, available from\nUSCYBERCOM.\n\n Note: If the system does not support the McAfee HIPS package, install and\nenable a supported intrusion detection system application and document its use\nwith the Authorizing Official.","label":"fix"}],"id":"V-92255","impact":0.5,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92255.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000196","gid":"V-92255","rid":"SV-102357r1_rule","stig_id":"RHEL-07-020019","fix_id":"F-98477r1_fix","cci":["CCI-001263"],"nist":["SI-4 (5)"]},"title":"The Red Hat Enterprise Linux operating system must have a host-based\nintrusion detection tool installed.","waiver_data":{}},{"code":"","desc":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","descriptions":[{"data":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active in the GUI with\nthe following command:\n\n # grep logout /etc/dconf/local.d/*\n\n logout=''\n\n If \"logout\" is not set to use two single quotations, or is missing, this\nis a finding.","label":"check"},{"data":"Configure the system to disable the Ctrl-Alt-Delete sequence for the GUI\nwith the following command:\n\n # touch /etc/dconf/db/local.d/00-disable-CAD\n\n Add the setting to disable the Ctrl-Alt-Delete sequence for GNOME:\n\n [org/gnome/settings-daemon/plugins/media-keys]\n logout=''","label":"fix"}],"id":"V-94843","impact":0,"refs":[],"results":[],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-94843.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-94843","rid":"SV-104673r1_rule","stig_id":"RHEL-07-020231","fix_id":"F-100967r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled in the GUI.","waiver_data":{}}],"copyright_email":".","depends":[{"name":"redhat-enterprise-linux-7-stig-baseline","status":"loaded","url":"https://github.com/mitre/redhat-enterprise-linux-7-stig-baseline/archive/master.tar.gz"}],"groups":[{"controls":["V-71849"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71849.rb"},{"controls":["V-71855"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71855.rb"},{"controls":["V-71859"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71859.rb"},{"controls":["V-71861"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71861.rb"},{"controls":["V-71863"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71863.rb"},{"controls":["V-71891"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71891.rb"},{"controls":["V-71893"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71893.rb"},{"controls":["V-71897"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71897.rb"},{"controls":["V-71899"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71899.rb"},{"controls":["V-71901"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71901.rb"},{"controls":["V-71903"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71903.rb"},{"controls":["V-71905"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71905.rb"},{"controls":["V-71907"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71907.rb"},{"controls":["V-71909"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71909.rb"},{"controls":["V-71911"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71911.rb"},{"controls":["V-71913"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71913.rb"},{"controls":["V-71915"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71915.rb"},{"controls":["V-71917"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71917.rb"},{"controls":["V-71919"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71919.rb"},{"controls":["V-71921"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71921.rb"},{"controls":["V-71923"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71923.rb"},{"controls":["V-71925"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71925.rb"},{"controls":["V-71927"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71927.rb"},{"controls":["V-71929"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71929.rb"},{"controls":["V-71931"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71931.rb"},{"controls":["V-71933"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71933.rb"},{"controls":["V-71935"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71935.rb"},{"controls":["V-71937"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71937.rb"},{"controls":["V-71939"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71939.rb"},{"controls":["V-71941"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71941.rb"},{"controls":["V-71943"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71943.rb"},{"controls":["V-71945"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71945.rb"},{"controls":["V-71947"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71947.rb"},{"controls":["V-71949"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71949.rb"},{"controls":["V-71951"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71951.rb"},{"controls":["V-71953"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71953.rb"},{"controls":["V-71955"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71955.rb"},{"controls":["V-71957"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71957.rb"},{"controls":["V-71959"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71959.rb"},{"controls":["V-71961"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71961.rb"},{"controls":["V-71963"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71963.rb"},{"controls":["V-71965"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71965.rb"},{"controls":["V-71967"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71967.rb"},{"controls":["V-71969"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71969.rb"},{"controls":["V-71971"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71971.rb"},{"controls":["V-71973"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71973.rb"},{"controls":["V-71975"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71975.rb"},{"controls":["V-71977"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71977.rb"},{"controls":["V-71979"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71979.rb"},{"controls":["V-71983"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71983.rb"},{"controls":["V-71985"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71985.rb"},{"controls":["V-71987"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71987.rb"},{"controls":["V-71989"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71989.rb"},{"controls":["V-71991"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71991.rb"},{"controls":["V-71993"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71993.rb"},{"controls":["V-71995"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71995.rb"},{"controls":["V-71997"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71997.rb"},{"controls":["V-71999"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71999.rb"},{"controls":["V-72001"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72001.rb"},{"controls":["V-72003"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72003.rb"},{"controls":["V-72005"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72005.rb"},{"controls":["V-72007"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72007.rb"},{"controls":["V-72009"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72009.rb"},{"controls":["V-72011"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72011.rb"},{"controls":["V-72013"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72013.rb"},{"controls":["V-72015"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72015.rb"},{"controls":["V-72017"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72017.rb"},{"controls":["V-72019"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72019.rb"},{"controls":["V-72021"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72021.rb"},{"controls":["V-72023"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72023.rb"},{"controls":["V-72025"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72025.rb"},{"controls":["V-72027"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72027.rb"},{"controls":["V-72029"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72029.rb"},{"controls":["V-72031"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72031.rb"},{"controls":["V-72033"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72033.rb"},{"controls":["V-72035"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72035.rb"},{"controls":["V-72037"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72037.rb"},{"controls":["V-72039"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72039.rb"},{"controls":["V-72041"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72041.rb"},{"controls":["V-72043"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72043.rb"},{"controls":["V-72045"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72045.rb"},{"controls":["V-72047"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72047.rb"},{"controls":["V-72049"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72049.rb"},{"controls":["V-72051"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72051.rb"},{"controls":["V-72053"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72053.rb"},{"controls":["V-72055"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72055.rb"},{"controls":["V-72057"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72057.rb"},{"controls":["V-72059"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72059.rb"},{"controls":["V-72061"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72061.rb"},{"controls":["V-72063"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72063.rb"},{"controls":["V-72065"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72065.rb"},{"controls":["V-72067"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72067.rb"},{"controls":["V-72069"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72069.rb"},{"controls":["V-72071"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72071.rb"},{"controls":["V-72073"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72073.rb"},{"controls":["V-72075"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72075.rb"},{"controls":["V-72077"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72077.rb"},{"controls":["V-72079"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72079.rb"},{"controls":["V-72081"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72081.rb"},{"controls":["V-72083"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72083.rb"},{"controls":["V-72085"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72085.rb"},{"controls":["V-72087"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72087.rb"},{"controls":["V-72089"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72089.rb"},{"controls":["V-72091"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72091.rb"},{"controls":["V-72093"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72093.rb"},{"controls":["V-72095"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72095.rb"},{"controls":["V-72097"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72097.rb"},{"controls":["V-72099"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72099.rb"},{"controls":["V-72101"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72101.rb"},{"controls":["V-72103"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72103.rb"},{"controls":["V-72105"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72105.rb"},{"controls":["V-72107"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72107.rb"},{"controls":["V-72109"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72109.rb"},{"controls":["V-72111"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72111.rb"},{"controls":["V-72113"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72113.rb"},{"controls":["V-72115"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72115.rb"},{"controls":["V-72117"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72117.rb"},{"controls":["V-72119"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72119.rb"},{"controls":["V-72121"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72121.rb"},{"controls":["V-72123"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72123.rb"},{"controls":["V-72125"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72125.rb"},{"controls":["V-72127"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72127.rb"},{"controls":["V-72129"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72129.rb"},{"controls":["V-72131"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72131.rb"},{"controls":["V-72133"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72133.rb"},{"controls":["V-72135"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72135.rb"},{"controls":["V-72137"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72137.rb"},{"controls":["V-72139"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72139.rb"},{"controls":["V-72141"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72141.rb"},{"controls":["V-72145"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72145.rb"},{"controls":["V-72147"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72147.rb"},{"controls":["V-72149"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72149.rb"},{"controls":["V-72151"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72151.rb"},{"controls":["V-72153"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72153.rb"},{"controls":["V-72155"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72155.rb"},{"controls":["V-72157"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72157.rb"},{"controls":["V-72159"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72159.rb"},{"controls":["V-72161"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72161.rb"},{"controls":["V-72163"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72163.rb"},{"controls":["V-72165"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72165.rb"},{"controls":["V-72167"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72167.rb"},{"controls":["V-72171"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72171.rb"},{"controls":["V-72173"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72173.rb"},{"controls":["V-72175"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72175.rb"},{"controls":["V-72177"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72177.rb"},{"controls":["V-72179"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72179.rb"},{"controls":["V-72183"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72183.rb"},{"controls":["V-72185"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72185.rb"},{"controls":["V-72187"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72187.rb"},{"controls":["V-72189"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72189.rb"},{"controls":["V-72191"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72191.rb"},{"controls":["V-72197"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72197.rb"},{"controls":["V-72199"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72199.rb"},{"controls":["V-72201"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72201.rb"},{"controls":["V-72203"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72203.rb"},{"controls":["V-72205"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72205.rb"},{"controls":["V-72207"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72207.rb"},{"controls":["V-72209"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72209.rb"},{"controls":["V-72211"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72211.rb"},{"controls":["V-72213"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72213.rb"},{"controls":["V-72217"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72217.rb"},{"controls":["V-72219"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72219.rb"},{"controls":["V-72221"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72221.rb"},{"controls":["V-72223"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72223.rb"},{"controls":["V-72225"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72225.rb"},{"controls":["V-72227"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72227.rb"},{"controls":["V-72229"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72229.rb"},{"controls":["V-72231"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72231.rb"},{"controls":["V-72233"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72233.rb"},{"controls":["V-72235"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72235.rb"},{"controls":["V-72237"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72237.rb"},{"controls":["V-72239"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72239.rb"},{"controls":["V-72241"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72241.rb"},{"controls":["V-72243"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72243.rb"},{"controls":["V-72245"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72245.rb"},{"controls":["V-72247"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72247.rb"},{"controls":["V-72249"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72249.rb"},{"controls":["V-72251"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72251.rb"},{"controls":["V-72253"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72253.rb"},{"controls":["V-72255"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72255.rb"},{"controls":["V-72257"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72257.rb"},{"controls":["V-72259"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72259.rb"},{"controls":["V-72261"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72261.rb"},{"controls":["V-72263"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72263.rb"},{"controls":["V-72265"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72265.rb"},{"controls":["V-72267"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72267.rb"},{"controls":["V-72269"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72269.rb"},{"controls":["V-72273"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72273.rb"},{"controls":["V-72275"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72275.rb"},{"controls":["V-72277"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72277.rb"},{"controls":["V-72279"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72279.rb"},{"controls":["V-72281"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72281.rb"},{"controls":["V-72283"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72283.rb"},{"controls":["V-72285"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72285.rb"},{"controls":["V-72287"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72287.rb"},{"controls":["V-72289"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72289.rb"},{"controls":["V-72291"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72291.rb"},{"controls":["V-72293"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72293.rb"},{"controls":["V-72295"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72295.rb"},{"controls":["V-72297"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72297.rb"},{"controls":["V-72299"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72299.rb"},{"controls":["V-72301"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72301.rb"},{"controls":["V-72303"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72303.rb"},{"controls":["V-72305"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72305.rb"},{"controls":["V-72307"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72307.rb"},{"controls":["V-72309"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72309.rb"},{"controls":["V-72311"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72311.rb"},{"controls":["V-72313"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72313.rb"},{"controls":["V-72315"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72315.rb"},{"controls":["V-72317"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72317.rb"},{"controls":["V-72319"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72319.rb"},{"controls":["V-72417"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72417.rb"},{"controls":["V-72427"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72427.rb"},{"controls":["V-72433"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72433.rb"},{"controls":["V-73155"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73155.rb"},{"controls":["V-73157"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73157.rb"},{"controls":["V-73159"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73159.rb"},{"controls":["V-73161"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73161.rb"},{"controls":["V-73163"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73163.rb"},{"controls":["V-73165"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73165.rb"},{"controls":["V-73167"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73167.rb"},{"controls":["V-73171"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73171.rb"},{"controls":["V-73173"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73173.rb"},{"controls":["V-73175"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73175.rb"},{"controls":["V-73177"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73177.rb"},{"controls":["V-77819"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77819.rb"},{"controls":["V-77821"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77821.rb"},{"controls":["V-77823"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77823.rb"},{"controls":["V-77825"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77825.rb"},{"controls":["V-78995"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78995.rb"},{"controls":["V-78997"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78997.rb"},{"controls":["V-78999"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78999.rb"},{"controls":["V-79001"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-79001.rb"},{"controls":["V-81003"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81003.rb"},{"controls":["V-81005"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81005.rb"},{"controls":["V-81007"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81007.rb"},{"controls":["V-81009"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81009.rb"},{"controls":["V-81011"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81011.rb"},{"controls":["V-81013"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81013.rb"},{"controls":["V-81015"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81015.rb"},{"controls":["V-81017"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81017.rb"},{"controls":["V-81019"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81019.rb"},{"controls":["V-81021"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81021.rb"},{"controls":["V-92251"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92251.rb"},{"controls":["V-92253"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92253.rb"},{"controls":["V-92255"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92255.rb"},{"controls":["V-94843"],"id":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-94843.rb"}],"license":"Apache-2.0","maintainer":"Example project","name":"example-inspec-overlay-profile-against-rhel7-stig-baseline-profile","parent_profile":"second-layer-example-inspec-overlay-profile-against-1st-layer-example-inspec-overlay-profile","sha256":"07b31921789ce8bc0c83c6e35f00f32ce6807b9196d74331644537b69681b4f8","status":"loaded","status_message":"","summary":"Example InSpec profile using dependency feature, aka 'overlay'","supports":[],"title":"example-inspec-overlay-profile-against-rhel7-stig-baseline-profile","version":"2.6.0"},{"attributes":[{"name":"min_len","options":{"type":"Numeric","value":24}},{"name":"unsuccessful_attempts","options":{"type":"Numeric","value":20}},{"name":"disable_slow_controls","options":{"type":"Boolean","value":true}},{"name":"monitor_kernel_log","options":{"type":"Boolean","value":true}},{"name":"rpm_verify_perms_except","options":{"type":"Array","value":[]}},{"name":"rpm_verify_integrity_except","options":{"type":"Array","value":[]}},{"name":"banner_message_enabled","options":{"type":"Boolean","value":true}},{"name":"log_aggregation_server","options":{"type":"Boolean","value":false}},{"name":"application_groups","options":{"type":"Array","value":[]}},{"name":"x11_enabled","options":{"type":"Boolean","value":false}},{"name":"user_accounts","options":{"type":"Array","value":[]}},{"name":"known_system_accounts","options":{"type":"Array","value":["root","bin","daemon","adm","lp","sync","shutdown","halt","mail","operator","nobody","systemd-bus-proxy","dbus","polkitd","postfix","sssd","chrony","systemd-network","sshd","ntp"]}},{"name":"dconf_user","options":{"type":"String","value":""}},{"name":"banner_message_text_gui","options":{"type":"String","value":"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."}},{"name":"banner_message_text_gui_limited","options":{"type":"String","value":"I've read & consent to terms in IS user agreem't."}},{"name":"banner_message_text_cli","options":{"type":"String","value":"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."}},{"name":"banner_message_text_cli_limited","options":{"type":"String","value":"I've read & consent to terms in IS user agreem't."}},{"name":"banner_message_text_ral","options":{"type":"String","value":"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."}},{"name":"banner_message_text_ral_limited","options":{"type":"String","value":"I've read & consent to terms in IS user agreem't."}},{"name":"lock_delay","options":{"type":"Numeric","value":5}},{"name":"difok","options":{"type":"Numeric","value":8}},{"name":"min_reuse_generations","options":{"type":"Numeric","value":5}},{"name":"days_of_inactivity","options":{"type":"Numeric","value":0}},{"name":"fail_interval","options":{"type":"Numeric","value":900}},{"name":"lockout_time","options":{"value":604800}},{"name":"file_integrity_tool","options":{"type":"String","value":"aide"}},{"name":"file_integrity_interval","options":{"type":"String","value":"weekly"}},{"name":"system_activity_timeout","options":{"type":"Numeric","value":600}},{"name":"client_alive_interval","options":{"type":"Numeric","value":600}},{"name":"smart_card_status","options":{"type":"String","value":"enabled"}},{"name":"log_pkg_path","options":{"type":"String","value":"/etc/rsyslog.conf"}},{"name":"exempt_home_users","options":{"type":"Array","value":[]}},{"name":"grub_main_cfg","options":{"type":"String","value":"/boot/grub2/grub.cfg"}},{"name":"grub_uefi_main_cfg","options":{"type":"String","value":"/boot/efi/EFI/redhat/grub.cfg"}},{"name":"grub_superuser","options":{"type":"String","value":"root"}},{"name":"grub_user_boot_files","options":{"type":"Array","value":["/boot/grub2/user.cfg"]}},{"name":"grub_uefi_user_boot_files","options":{"type":"Array","value":["/boot/efi/EFI/redhat/user.cfg"]}},{"name":"efi_superusers","options":{"type":"Array","value":"***","sensitive":true}},{"name":"admin_logins","options":{"type":"Array","value":"***","sensitive":true}},{"name":"max_rety","options":{"type":"Numeric","value":3}},{"name":"mfa_pkg_list","options":{"type":"Array","value":["nss-tools","nss-pam-ldapd","esc","pam_pkcs11","pam_krb5","opensc","pcsc-lite-ccid","gdm","authconfig","authconfig-gtk","krb5-libs","krb5-workstation","krb5-pkinit","pcsc-lite","pcsc-lite-libs"]}},{"name":"multifactor_enabled","options":{"type":"Boolean","value":true}},{"name":"non_interactive_shells","options":{"type":"Array","value":["/sbin/nologin","/sbin/halt","/sbin/shutdown","/bin/false","/bin/sync","/bin/true"]}},{"name":"randomize_va_space","options":{"type":"Numeric","value":2}},{"name":"non_removable_media_fs","options":{"type":"Array","value":["xfs","ext4","swap","tmpfs"]}},{"name":"approved_tunnels","options":{"type":"Array","value":[]}},{"name":"virtual_machine","options":{"type":"Boolean","value":false}},{"name":"max_retry","options":{"type":"Numeric","value":3}},{"name":"firewalld_services","options":{"type":"Array","value":[]}},{"name":"firewalld_hosts_allow","options":{"type":"Array","value":[]}},{"name":"firewalld_hosts_deny","options":{"type":"Array","value":[]}},{"name":"firewalld_ports_allow","options":{"type":"Array","value":[]}},{"name":"firewalld_ports_deny","options":{"type":"Hash","value":{}}},{"name":"tcpwrappers_allow","options":{"type":"Hash","value":{}}},{"name":"tcpwrappers_deny","options":{"type":"Hash","value":{}}},{"name":"iptables_rules","options":{"type":"Array","value":[]}},{"name":"firewalld_services_deny","options":{"type":"Hash","value":{}}},{"name":"firewalld_zones","options":{"type":"Array","value":[]}},{"name":"maxlogins_limit","options":{"type":"Numeric","value":10}},{"name":"custom_antivirus","options":{"type":"Boolean","value":false}},{"name":"custom_antivirus_description","options":{"type":"String","value":"None"}},{"name":"custom_hips","options":{"type":"Boolean","value":false}},{"name":"custom_hips_description","options":{"type":"String","value":"An6yTr21kC"}},{"name":"max_daemon_processes","options":{"type":"Numeric","value":1}},{"name":"aide_exclude_patterns","options":{"type":"Array","value":[]}},{"name":"terminal_mux_pkgs","options":{"type":"Array","value":["tmux","screen"]}},{"name":"required_rules","options":{"type":"Array","value":["auth required pam_faillock.so unlock_time=.*","auth sufficient pam_unix.so try_first_pass","auth [default=die] pam_faillock.so unlock_time=.*"]}},{"name":"alternate_rules","options":{"type":"Array","value":["auth required pam_faillock.so unlock_time=.*","auth sufficient pam_sss.so forward_pass","auth sufficient pam_unix.so try_first_pass","auth [default=die] pam_faillock.so unlock_time=.*"]}},{"name":"data_loss_prevention_installed","options":{"type":"Boolean","value":true}},{"name":"alternate_logs","options":{"type":"Boolean","value":false}},{"name":"gssapi_approved","options":{"type":"Boolean","value":true}},{"name":"disconnected_system","options":{"type":"Boolean","value":false}}],"controls":[{"code":"control \"V-71849\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the file permissions, ownership, and group membership of system files and\ncommands match the vendor values.\"\n desc \"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file permissions, ownership, and group membership of system\nfiles and commands match the vendor values.\n\n Check the default file permissions, ownership, and group membership of\nsystem files and commands with the following command:\n\n # for i in `rpm -Va | egrep -i '^\\\\.[M|U|G|.]{8}' | cut -d \\\" \\\" -f4,5`;do\nfor j in `rpm -qf $i`;do rpm -ql $j --dump | cut -d \\\" \\\" -f1,5,6,7 | grep\n$i;done;done\n\n /var/log/gdm 040755 root root\n /etc/audisp/audisp-remote.conf 0100640 root root\n /usr/bin/passwd 0104755 root root\n\n For each file returned, verify the current permissions, ownership, and\ngroup membership:\n # ls -la \n\n -rw-------. 1 root root 133 Jan 11 13:25 /etc/audisp/audisp-remote.conf\n\n If the file is more permissive than the default permissions, this is a\nfinding.\n\n If the file is not owned by the default owner and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.\n\n If the file is not a member of the default group and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.\n \"\n desc \"fix\", \"\n Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n Reset the user and group ownership of files within a package with the\nfollowing command:\n\n #rpm --setugids \n\n\n Reset the permissions of files within a package with the following command:\n\n #rpm --setperms \n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000257-GPOS-00098\"\n tag satisfies: [\"SRG-OS-000257-GPOS-00098\", \"SRG-OS-000278-GPOS-00108\"]\n tag gid: \"V-71849\"\n tag rid: \"SV-86473r4_rule\"\n tag stig_id: \"RHEL-07-010010\"\n tag fix_id: \"F-78201r4_fix\"\n tag cci: [\"CCI-001494\", \"CCI-001496\", \"CCI-002165\", \"CCI-002235\"]\n tag nist: [\"AU-9\", \"AU-9 (3)\", \"AC-3 (4)\", \"AC-6 (10)\"]\n\n rpm_verify_perms_except = input('rpm_verify_perms_except')\n\n if input('disable_slow_controls')\n describe \"This control consistently takes a long time to run and has been disabled\n using the disable_slow_controls attribute.\" do\n skip \"This control consistently takes a long time to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.\"\n end\n else\n describe command(\"rpm -Va | grep '^.M' | awk 'NF>1{print $NF}'\").stdout.strip.split(\"\\n\") do\n it { should all(be_in rpm_verify_perms_except) }\n end\n end\nend\n","desc":"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.","descriptions":[{"data":"Discretionary access control is weakened if a user or group has access\npermissions to system files and directories greater than the default.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file permissions, ownership, and group membership of system\nfiles and commands match the vendor values.\n\n Check the default file permissions, ownership, and group membership of\nsystem files and commands with the following command:\n\n # for i in `rpm -Va | egrep -i '^\\.[M|U|G|.]{8}' | cut -d \" \" -f4,5`;do\nfor j in `rpm -qf $i`;do rpm -ql $j --dump | cut -d \" \" -f1,5,6,7 | grep\n$i;done;done\n\n /var/log/gdm 040755 root root\n /etc/audisp/audisp-remote.conf 0100640 root root\n /usr/bin/passwd 0104755 root root\n\n For each file returned, verify the current permissions, ownership, and\ngroup membership:\n # ls -la \n\n -rw-------. 1 root root 133 Jan 11 13:25 /etc/audisp/audisp-remote.conf\n\n If the file is more permissive than the default permissions, this is a\nfinding.\n\n If the file is not owned by the default owner and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.\n\n If the file is not a member of the default group and is not documented with\nthe Information System Security Officer (ISSO), this is a finding.","label":"check"},{"data":"Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n Reset the user and group ownership of files within a package with the\nfollowing command:\n\n #rpm --setugids \n\n\n Reset the permissions of files within a package with the following command:\n\n #rpm --setperms ","label":"fix"}],"id":"V-71849","impact":0.7,"refs":[],"results":[{"code_desc":"This control consistently takes a long time to run and has been disabled\n using the disable_slow_controls attribute.","resource":"","run_time":0.000014285,"skip_message":"This control consistently takes a long time to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71849.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000257-GPOS-00098","satisfies":["SRG-OS-000257-GPOS-00098","SRG-OS-000278-GPOS-00108"],"gid":"V-71849","rid":"SV-86473r4_rule","stig_id":"RHEL-07-010010","fix_id":"F-78201r4_fix","cci":["CCI-001494","CCI-001496","CCI-002165","CCI-002235"],"nist":["AU-9","AU-9 (3)","AC-3 (4)","AC-6 (10)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file permissions, ownership, and group membership of system files and\ncommands match the vendor values.","waiver_data":{}},{"code":"control \"V-71855\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the cryptographic hash of system files and commands matches vendor values.\"\n desc \"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the cryptographic hash of system files and commands match the vendor\nvalues.\n\n Check the cryptographic hash of system files and commands with the\nfollowing command:\n\n Note: System configuration files (indicated by a \\\"c\\\" in the second\ncolumn) are expected to change over time. Unusual modifications should be\ninvestigated through the system audit log.\n\n # rpm -Va --noconfig | grep '^..5'\n\n If there is any output from the command for system files or binaries, this\nis a finding.\n \"\n desc \"fix\", \"\n Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh \n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71855\"\n tag rid: \"SV-86479r4_rule\"\n tag stig_id: \"RHEL-07-010020\"\n tag fix_id: \"F-78207r1_fix\"\n tag cci: [\"CCI-001749\"]\n tag nist: [\"CM-5 (3)\"]\n\nrpm_verify_integrity_except = input('rpm_verify_integrity_except')\n\nif input('disable_slow_controls')\n describe \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.\" do\n skip \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.\"\n end\n else\n # grep excludes files that are marked with 'c' attribute (config files)\n describe command(\"rpm -Va | grep '^..5' | grep -E -v '[a-z]*c[a-z]*\\\\s+\\\\S+$' | awk 'NF>1{print $NF}'\").\n stdout.strip.split(\"\\n\") do\n it { should all(be_in rpm_verify_integrity_except) }\n end\n end\nend\n","desc":"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, system command and files\ncan be altered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the cryptographic hash of system files and commands match the vendor\nvalues.\n\n Check the cryptographic hash of system files and commands with the\nfollowing command:\n\n Note: System configuration files (indicated by a \"c\" in the second\ncolumn) are expected to change over time. Unusual modifications should be\ninvestigated through the system audit log.\n\n # rpm -Va --noconfig | grep '^..5'\n\n If there is any output from the command for system files or binaries, this\nis a finding.","label":"check"},{"data":"Run the following command to determine which package owns the file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh ","label":"fix"}],"id":"V-71855","impact":0.7,"refs":[],"results":[{"code_desc":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","resource":"","run_time":0.000008675,"skip_message":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71855.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71855","rid":"SV-86479r4_rule","stig_id":"RHEL-07-010020","fix_id":"F-78207r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cryptographic hash of system files and commands matches vendor values.","waiver_data":{}},{"code":"control \"V-71859\" do\n title \"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a graphical user logon.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a graphical\nuser logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the operating system displays a banner at the logon screen\nwith the following command:\n\n # grep banner-message-enable /etc/dconf/db/local.d/*\n banner-message-enable=true\n\n If \\\"banner-message-enable\\\" is set to \\\"false\\\" or is missing, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/01-banner-message\n\n Add the following line to the [org/gnome/login-screen] section of the\n\\\"/etc/dconf/db/local.d/01-banner-message\\\":\n\n [org/gnome/login-screen]\n banner-message-enable=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\",\n\"SRG-OS-000228-GPOS-00088\"]\n tag gid: \"V-71859\"\n tag rid: \"SV-86483r4_rule\"\n tag stig_id: \"RHEL-07-010030\"\n tag fix_id: \"F-78211r4_fix\"\n tag cci: [\"CCI-000048\"]\n tag nist: [\"AC-8 a\"]\n\n if package('gnome-desktop3').installed?\n if !input('dconf_user').nil? and command('whoami').stdout.strip == 'root'\n describe command(\"sudo -u input('dconf_user') dconf read /org/gnome/login-screen/banner-message-enable\") do\n its('stdout.strip') { should cmp input('banner_message_enabled').to_s }\n end\n else\n describe command(\"dconf read /org/gnome/login-screen/banner-message-enable\") do\n its('stdout.strip') { should cmp input('banner_message_enabled').to_s }\n end\n end\n else\n impact 0.0\n describe \"The GNOME desktop is not installed\" do \n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n end\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a graphical\nuser logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the operating system displays a banner at the logon screen\nwith the following command:\n\n # grep banner-message-enable /etc/dconf/db/local.d/*\n banner-message-enable=true\n\n If \"banner-message-enable\" is set to \"false\" or is missing, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/01-banner-message\n\n Add the following line to the [org/gnome/login-screen] section of the\n\"/etc/dconf/db/local.d/01-banner-message\":\n\n [org/gnome/login-screen]\n banner-message-enable=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71859","impact":0,"refs":[],"results":[{"code_desc":"The GNOME desktop is not installed","resource":"","run_time":0.000007091,"skip_message":"The GNOME desktop is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71859.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-71859","rid":"SV-86483r4_rule","stig_id":"RHEL-07-010030","fix_id":"F-78211r4_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a graphical user logon.","waiver_data":{}},{"code":"control \"V-71861\" do\n title \"The Red Hat Enterprise Linux operating system must display the\napproved Standard Mandatory DoD Notice and Consent Banner before granting local\nor remote access to the system via a graphical user logon.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system displays the approved Standard Mandatory DoD\nNotice and Consent Banner before granting access to the operating system via a\ngraphical user logon.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Check that the operating system displays the exact approved Standard\nMandatory DoD Notice and Consent Banner text with the command:\n # grep banner-message-text /etc/dconf/db/local.d/*\n banner-message-text=\n 'You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\\\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\\\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\\\n -At any time, the USG may inspect and seize data stored on this IS.\\\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\\\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\\\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \\\"\\\n \\\" characters are for formatting only. They will not be displayed on the\nGUI.\n If the banner does not match the approved Standard Mandatory DoD Notice and\nConsent Banner, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the approved Standard Mandatory\nDoD Notice and Consent Banner before granting access to the system.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n # touch /etc/dconf/db/local.d/01-banner-message\n Add the following line to the [org/gnome/login-screen] section of the\n\\\"/etc/dconf/db/local.d/01-banner-message\\\":\n [org/gnome/login-screen]\n banner-message-enable=true\n banner-message-text='You are accessing a U.S. Government (USG) Information\nSystem (IS) that is provided for USG-authorized use only.\\\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\\\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\\\n -At any time, the USG may inspect and seize data stored on this IS.\\\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\\\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\\\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \\\"\\\n \\\" characters are for formatting only. They will not be displayed on the\nGUI.\n Run the following command to update the database:\n # dconf update\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\",\n\"SRG-OS-000228-GPOS-00088\"]\n tag gid: \"V-71861\"\n tag rid: \"SV-86485r4_rule\"\n tag stig_id: \"RHEL-07-010040\"\n tag fix_id: \"F-78213r5_fix\"\n tag cci: [\"CCI-000048\"]\n tag nist: [\"AC-8 a\"]\n if package('gnome-desktop3').installed?\n #Get all files that have the banner-message-text specified.\n banner_files =\n command(\"grep -l banner-message-text /etc/dconf/db/local.d/*\").stdout.split(\"\\n\")\n #If there are no banner files then this is a finding.\n banner_missing = banner_files.empty?\n describe \"If no files specify the banner text then this is a finding\" do\n subject { banner_missing }\n it{should be false}\n end if banner_missing\n #If there are banner files then check them to make sure they have the correct text.\n banner_files.each do |banner_file|\n banner_message =\n parse_config_file(banner_file).params(\"org/gnome/login-screen\",\"banner-message-text\").gsub(%r{[\\r\\n\\s]}, '')\n #dconf expects the banner-message-text to be quoted so remove leading and trailing quote.\n #See https://developer.gnome.org/dconf/unstable/dconf-tool.html which states:\n # VALUE arguments must be in GVariant format, so e.g. a string must include\n # explicit quotes: \"'foo'\". This format is also used when printing out values.\n if banner_message.start_with?('\"') || banner_message.start_with?('\\'')\n banner_message = banner_message[1,banner_message.length]\n end\n if banner_message.end_with?('\"') || banner_message.end_with?('\\'')\n banner_message = banner_message.chop\n end\n banner_message.gsub!('\\\\n', '')\n foo = input('banner_message_text_gui');\n foo2 = input('banner_message_text_gui_limited');\n describe.one do\n describe banner_message do\n it{should cmp foo.gsub(%r{[\\r\\n\\s]}, '')}\n end\n describe banner_message do\n it{should cmp foo2.gsub(%r{[\\r\\n\\s]}, '')}\n end\n end\n end\n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n -At any time, the USG may inspect and seize data stored on this IS.\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the approved Standard Mandatory DoD\nNotice and Consent Banner before granting access to the operating system via a\ngraphical user logon.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Check that the operating system displays the exact approved Standard\nMandatory DoD Notice and Consent Banner text with the command:\n # grep banner-message-text /etc/dconf/db/local.d/*\n banner-message-text=\n 'You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(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\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \" \" characters are for formatting only. They will not be displayed on the\nGUI.\n If the banner does not match the approved Standard Mandatory DoD Notice and\nConsent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the approved Standard Mandatory\nDoD Notice and Consent Banner before granting access to the system.\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n Create a database to contain the system-wide graphical user logon settings\n(if it does not already exist) with the following command:\n # touch /etc/dconf/db/local.d/01-banner-message\n Add the following line to the [org/gnome/login-screen] section of the\n\"/etc/dconf/db/local.d/01-banner-message\":\n [org/gnome/login-screen]\n banner-message-enable=true\n banner-message-text='You are accessing a U.S. Government (USG) Information\nSystem (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(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\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details. '\n Note: The \" \" characters are for formatting only. They will not be displayed on the\nGUI.\n Run the following command to update the database:\n # dconf update","label":"fix"}],"id":"V-71861","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GNOME installed","resource":"","run_time":0.000005985,"skip_message":"The system does not have GNOME installed, this requirement is Not\n Applicable.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71861.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-71861","rid":"SV-86485r4_rule","stig_id":"RHEL-07-010040","fix_id":"F-78213r5_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\napproved Standard Mandatory DoD Notice and Consent Banner before granting local\nor remote access to the system via a graphical user logon.","waiver_data":{}},{"code":"control \"V-71863\" do\n title \"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a command line user logon.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a command\nline user logon.\n\n Check to see if the operating system displays a banner at the command line\nlogon screen with the following command:\n\n # more /etc/issue\n\n The command should return the following text:\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n If the operating system does not display a graphical logon banner or the\nbanner does not match the Standard Mandatory DoD Notice and Consent Banner,\nthis is a finding.\n\n If the text in the \\\"/etc/issue\\\" file does not match the Standard\nMandatory DoD Notice and Consent Banner, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the command line by\nediting the \\\"/etc/issue\\\" file.\n\n Replace the default text with the Standard Mandatory DoD Notice and Consent\nBanner. The DoD required text is:\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\"]\n tag gid: \"V-71863\"\n tag rid: \"SV-86487r3_rule\"\n tag stig_id: \"RHEL-07-010050\"\n tag fix_id: \"F-78217r2_fix\"\n tag cci: [\"CCI-000048\"]\n tag nist: [\"AC-8 a\"]\n\n banner_message_text_cli = input('banner_message_text_cli')\n banner_message_text_cli_limited = input('banner_message_text_cli_limited')\n\n clean_banner = banner_message_text_cli.gsub(%r{[\\r\\n\\s]}, '')\n clean_banner_limited = banner_message_text_cli_limited.gsub(%r{[\\r\\n\\s]}, '')\n banner_file = file(\"/etc/issue\")\n banner_missing = !banner_file.exist?\n\n describe \"The banner text is not set because /etc/issue does not exist\" do\n subject { banner_missing }\n it { should be false }\n end if banner_missing\n\n banner_message = banner_file.content.gsub(%r{[\\r\\n\\s]}, '')\n describe.one do\n describe \"The banner text should match the standard banner\" do\n subject { banner_message }\n it { should cmp clean_banner }\n end\n describe \"The banner text should match the limited banner\" do\n subject { banner_message }\n it{should cmp clean_banner_limited }\n end\n end if !banner_missing\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the operating system ensures privacy and security\nnotification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system displays the Standard Mandatory DoD Notice and\nConsent Banner before granting access to the operating system via a command\nline user logon.\n\n Check to see if the operating system displays a banner at the command line\nlogon screen with the following command:\n\n # more /etc/issue\n\n The command should return the following text:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n If the operating system does not display a graphical logon banner or the\nbanner does not match the Standard Mandatory DoD Notice and Consent Banner,\nthis is a finding.\n\n If the text in the \"/etc/issue\" file does not match the Standard\nMandatory DoD Notice and Consent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the command line by\nediting the \"/etc/issue\" file.\n\n Replace the default text with the Standard Mandatory DoD Notice and Consent\nBanner. The DoD required text is:\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"fix"}],"id":"V-71863","impact":0.5,"refs":[],"results":[{"code_desc":"The banner text should match the standard banner is expected to cmp == \"YouareaccessingaU.S.Government(USG)InformationSystem(IS)thatisprovidedforUSG-authorizeduseonly.ByusingthisIS(whichincludesanydeviceattachedtothisIS),youconsenttothefollowingconditions:-TheUSGroutinelyinterceptsandmonitorscommunicationsonthisISforpurposesincluding,butnotlimitedto,penetrationtesting,COMSECmonitoring,networkoperationsanddefense,personnelmisconduct(PM),lawenforcement(LE),andcounterintelligence(CI)investigations.-Atanytime,theUSGmayinspectandseizedatastoredonthisIS.-Communicationsusing,ordatastoredon,thisISarenotprivate,aresubjecttoroutinemonitoring,interception,andsearch,andmaybedisclosedorusedforanyUSG-authorizedpurpose.-ThisISincludessecuritymeasures(e.g.,authenticationandaccesscontrols)toprotectUSGinterests--notforyourpersonalbenefitorprivacy.-Notwithstandingtheabove,usingthisISdoesnotconstituteconsenttoPM,LEorCIinvestigativesearchingormonitoringofthecontentofprivilegedcommunications,orworkproduct,relatedtopersonalrepresentationorservicesbyattorneys,psychotherapists,orclergy,andtheirassistants.Suchcommunicationsandworkproductareprivateandconfidential.SeeUserAgreementfordetails.\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: YouareaccessingaU.S.Government(USG)InformationSystem(IS)thatisprovidedforUSG-authorizeduseonly.ByusingthisIS(whichincludesanydeviceattachedtothisIS),youconsenttothefollowingconditions:-TheUSGroutinelyinterceptsandmonitorscommunicationsonthisISforpurposesincluding,butnotlimitedto,penetrationtesting,COMSECmonitoring,networkoperationsanddefense,personnelmisconduct(PM),lawenforcement(LE),andcounterintelligence(CI)investigations.-Atanytime,theUSGmayinspectandseizedatastoredonthisIS.-Communicationsusing,ordatastoredon,thisISarenotprivate,aresubjecttoroutinemonitoring,interception,andsearch,andmaybedisclosedorusedforanyUSG-authorizedpurpose.-ThisISincludessecuritymeasures(e.g.,authenticationandaccesscontrols)toprotectUSGinterests--notforyourpersonalbenefitorprivacy.-Notwithstandingtheabove,usingthisISdoesnotconstituteconsenttoPM,LEorCIinvestigativesearchingormonitoringofthecontentofprivilegedcommunications,orworkproduct,relatedtopersonalrepresentationorservicesbyattorneys,psychotherapists,orclergy,andtheirassistants.Suchcommunicationsandworkproductareprivateandconfidential.SeeUserAgreementfordetails.\n got: \\SKernel\\ronan\\m\n\n(compared using `cmp` matcher)\n","run_time":0.000311318,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The banner text should match the limited banner is expected to cmp == \"I'veread&consenttotermsinISuseragreem't.\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: I'veread&consenttotermsinISuseragreem't.\n got: \\SKernel\\ronan\\m\n\n(compared using `cmp` matcher)\n","run_time":0.000264551,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71863.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007"],"gid":"V-71863","rid":"SV-86487r3_rule","stig_id":"RHEL-07-010050","fix_id":"F-78217r2_fix","cci":["CCI-000048"],"nist":["AC-8 a"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner before granting local or\nremote access to the system via a command line user logon.","waiver_data":{}},{"code":"control \"V-71891\" do\n title \"The Red Hat Enterprise Linux operating system must enable a user\nsession lock until that user re-establishes access using established\nidentification and authentication procedures.\"\n desc \"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enables a user's session lock until that user\nre-establishes access using established identification and authentication\nprocedures. The screen program must be installed to lock sessions on the\nconsole.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the screen lock is enabled with the following command:\n\n # grep -i lock-enabled /etc/dconf/db/local.d/*\n lock-enabled=true\n\n If the \\\"lock-enabled\\\" setting is missing or is not set to \\\"true\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enable a user's session lock until that\nuser re-establishes access using established identification and authentication\nprocedures.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following example:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit the \\\"[org/gnome/desktop/screensaver]\\\" section of the database file\nand add or update the following lines:\n\n # Set this to true to lock the screen when the screensaver activates\n lock-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000028-GPOS-00009\"\n tag satisfies: [\"SRG-OS-000028-GPOS-00009\", \"SRG-OS-000030-GPOS-00011\"]\n tag gid: \"V-71891\"\n tag rid: \"SV-86515r6_rule\"\n tag stig_id: \"RHEL-07-010060\"\n tag fix_id: \"F-78243r9_fix\"\n tag cci: [\"CCI-000056\"]\n tag nist: [\"AC-11 b\"]\n\n if package('gnome-desktop3').installed?\n describe command('gsettings get org.gnome.desktop.screensaver lock-enabled') do\n its('stdout.strip') { should cmp 'true' }\n end\n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n Regardless of where the session lock is determined and implemented, once\ninvoked, the session lock must remain in place until the user reauthenticates.\nNo other activity aside from reauthentication must unlock the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enables a user's session lock until that user\nre-establishes access using established identification and authentication\nprocedures. The screen program must be installed to lock sessions on the\nconsole.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if the screen lock is enabled with the following command:\n\n # grep -i lock-enabled /etc/dconf/db/local.d/*\n lock-enabled=true\n\n If the \"lock-enabled\" setting is missing or is not set to \"true\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to enable a user's session lock until that\nuser re-establishes access using established identification and authentication\nprocedures.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following example:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit the \"[org/gnome/desktop/screensaver]\" section of the database file\nand add or update the following lines:\n\n # Set this to true to lock the screen when the screensaver activates\n lock-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71891","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GNOME installed","resource":"","run_time":0.000006798,"skip_message":"The system does not have GNOME installed, this requirement is Not\n Applicable.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71891.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000028-GPOS-00009","satisfies":["SRG-OS-000028-GPOS-00009","SRG-OS-000030-GPOS-00011"],"gid":"V-71891","rid":"SV-86515r6_rule","stig_id":"RHEL-07-010060","fix_id":"F-78243r9_fix","cci":["CCI-000056"],"nist":["AC-11 b"]},"title":"The Red Hat Enterprise Linux operating system must enable a user\nsession lock until that user re-establishes access using established\nidentification and authentication procedures.","waiver_data":{}},{"code":"control \"V-71893\" do\n title \"The Red Hat Enterprise Linux operating system must initiate a\nscreensaver after a 15-minute period of inactivity for graphical user\ninterfaces.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if GNOME is configured to display a screensaver after a 15\nminute delay with the following command:\n\n # grep -i idle-delay /etc/dconf/db/local.d/*\n idle-delay=uint32 900\n\n If the \\\"idle-delay\\\" setting is missing or is not set to \\\"900\\\" or less,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit /etc/dconf/db/local.d/00-screensaver and add or update the following\nlines:\n\n [org/gnome/desktop/session]\n # Set the lock time out to 900 seconds before the session is considered idle\n idle-delay=uint32 900\n\n You must include the \\\"uint32\\\" along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71893\"\n tag rid: \"SV-86517r5_rule\"\n tag stig_id: \"RHEL-07-010070\"\n tag fix_id: \"F-78245r5_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n unless package('gnome-desktop3').installed?\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n else \n describe command(\"gsettings get org.gnome.desktop.session idle-delay | cut -d ' ' -f2\") do\n its('stdout.strip') { should cmp <= 900 }\n end \n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check to see if GNOME is configured to display a screensaver after a 15\nminute delay with the following command:\n\n # grep -i idle-delay /etc/dconf/db/local.d/*\n idle-delay=uint32 900\n\n If the \"idle-delay\" setting is missing or is not set to \"900\" or less,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to initiate a screensaver after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Edit /etc/dconf/db/local.d/00-screensaver and add or update the following\nlines:\n\n [org/gnome/desktop/session]\n # Set the lock time out to 900 seconds before the session is considered idle\n idle-delay=uint32 900\n\n You must include the \"uint32\" along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71893","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GNOME installed","resource":"","run_time":0.000004607,"skip_message":"The system does not have GNOME installed, this requirement is Not\n Applicable.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71893.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71893","rid":"SV-86517r5_rule","stig_id":"RHEL-07-010070","fix_id":"F-78245r5_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a\nscreensaver after a 15-minute period of inactivity for graphical user\ninterfaces.","waiver_data":{}},{"code":"control \"V-71897\" do\n title \"The Red Hat Enterprise Linux operating system must have the screen\npackage installed.\"\n desc \": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system has the screen package installed.\n\n Check to see if the screen package is installed with the following command:\n\n # yum list installed screen\n screen-4.3.1-3-x86_64.rpm\n\n If the screen package is not installed, check to see if the tmux package is\ninstalled with the following command:\n\n #yum list installed tmux\n tmux-1.8-4.el7.x86_64.rpm\n\n If either the screen package or the tmux package is not installed, this is\na finding.\n \"\n desc \"fix\", \"\n Install the screen package to allow the initiation of a session lock after\na 15-minute period of inactivity.\n\n Install the screen program (if it is not on the system) with the following\ncommand:\n\n # yum install screen\n\n OR\n\n Install the tmux program (if it is not on the system) with the following\ncommand:\n\n #yum install tmux\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71897\"\n tag rid: \"SV-86521r3_rule\"\n tag stig_id: \"RHEL-07-010090\"\n tag fix_id: \"F-78249r3_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n multiplexer_packages = input('terminal_mux_pkgs')\n\n describe.one do\n multiplexer_packages.each do |pkg| \n describe package(pkg) do\n it { should be_installed }\n end\n end\n end\nend\n","desc":": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.","descriptions":[{"data":": A session time-out lock is a temporary action taken when a user\nstops work and moves away from the immediate physical vicinity of the\ninformation system but does not log out because of the temporary nature of the\nabsence. Rather than relying on the user to manually lock their operating\nsystem session prior to vacating the vicinity, operating systems need to be\nable to identify when a user's session has idled and take action to initiate\nthe session lock.\n\n The screen and tmux packages allow for a session lock to be implemented and\nconfigured.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system has the screen package installed.\n\n Check to see if the screen package is installed with the following command:\n\n # yum list installed screen\n screen-4.3.1-3-x86_64.rpm\n\n If the screen package is not installed, check to see if the tmux package is\ninstalled with the following command:\n\n #yum list installed tmux\n tmux-1.8-4.el7.x86_64.rpm\n\n If either the screen package or the tmux package is not installed, this is\na finding.","label":"check"},{"data":"Install the screen package to allow the initiation of a session lock after\na 15-minute period of inactivity.\n\n Install the screen program (if it is not on the system) with the following\ncommand:\n\n # yum install screen\n\n OR\n\n Install the tmux program (if it is not on the system) with the following\ncommand:\n\n #yum install tmux","label":"fix"}],"id":"V-71897","impact":0.5,"refs":[],"results":[{"code_desc":"System Package tmux is expected to be installed","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `System Package tmux` is installed","run_time":0.000352551,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"package","resource_params":"[\"tmux\"]"},{"code_desc":"System Package screen is expected to be installed","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `System Package screen` is installed","run_time":0.000195058,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"package","resource_params":"[\"screen\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71897.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71897","rid":"SV-86521r3_rule","stig_id":"RHEL-07-010090","fix_id":"F-78249r3_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must have the screen\npackage installed.","waiver_data":{}},{"code":"control \"V-71899\" do\n title \"The Red Hat Enterprise Linux operating system must initiate a session\nlock for the screensaver after a period of inactivity for graphical user\ninterfaces.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have a Graphical User Interface installed,\nthis requirement is Not Applicable.\n\n Check for the session lock settings with the following commands:\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/*\n\n idle-activation-enabled=true\n\n If \\\"idle-activation-enabled\\\" is not set to \\\"true\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable screensaver locking after 15 minutes of\ninactivity:\n\n [org/gnome/desktop/screensaver]\n\n idle-activation-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71899\"\n tag rid: \"SV-86523r5_rule\"\n tag stig_id: \"RHEL-07-010100\"\n tag fix_id: \"F-78251r2_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n describe command('gsettings get org.gnome.desktop.screensaver idle-activation-enabled') do\n its('stdout.strip') { should cmp 'true' }\n end \n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces. The screen program must be\ninstalled to lock sessions on the console.\n\n Note: If the system does not have a Graphical User Interface installed,\nthis requirement is Not Applicable.\n\n Check for the session lock settings with the following commands:\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/*\n\n idle-activation-enabled=true\n\n If \"idle-activation-enabled\" is not set to \"true\", this is a finding.","label":"check"},{"data":"Configure the operating system to initiate a session lock after a 15-minute\nperiod of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable screensaver locking after 15 minutes of\ninactivity:\n\n [org/gnome/desktop/screensaver]\n\n idle-activation-enabled=true\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71899","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GNOME installed","resource":"","run_time":0.000008448,"skip_message":"The system does not have GNOME installed, this requirement is Not\n Applicable.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71899.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71899","rid":"SV-86523r5_rule","stig_id":"RHEL-07-010100","fix_id":"F-78251r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a session\nlock for the screensaver after a period of inactivity for graphical user\ninterfaces.","waiver_data":{}},{"code":"control \"V-71901\" do\n title \"The Red Hat Enterprise Linux operating system must initiate a session\nlock for graphical user interfaces when the screensaver is activated.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates a session lock a for graphical user\ninterfaces when the screensaver is activated.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n If GNOME is installed, check to see a session lock occurs when the\nscreensaver is activated with the following command:\n\n # grep -i lock-delay /etc/dconf/db/local.d/*\n lock-delay=uint32 5\n\n If the \\\"lock-delay\\\" setting is missing, or is not set to \\\"5\\\" or less,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate a session lock for graphical\nuser interfaces when a screensaver is activated.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable session locking when a screensaver is activated:\n\n [org/gnome/desktop/screensaver]\n lock-delay=uint32 5\n\n The \\\"uint32\\\" must be included along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-71901\"\n tag rid: \"SV-86525r3_rule\"\n tag stig_id: \"RHEL-07-010110\"\n tag fix_id: \"F-78253r2_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n describe command(\"gsettings get org.gnome.desktop.screensaver lock-delay | cut -d ' ' -f2\") do\n its('stdout.strip') { should cmp <= input('lock_delay') }\n end\n else\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates a session lock a for graphical user\ninterfaces when the screensaver is activated.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n If GNOME is installed, check to see a session lock occurs when the\nscreensaver is activated with the following command:\n\n # grep -i lock-delay /etc/dconf/db/local.d/*\n lock-delay=uint32 5\n\n If the \"lock-delay\" setting is missing, or is not set to \"5\" or less,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to initiate a session lock for graphical\nuser interfaces when a screensaver is activated.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n # touch /etc/dconf/db/local.d/00-screensaver\n\n Add the setting to enable session locking when a screensaver is activated:\n\n [org/gnome/desktop/screensaver]\n lock-delay=uint32 5\n\n The \"uint32\" must be included along with the integer key values as shown.\n\n Update the system databases:\n\n # dconf update\n\n Users must log out and back in again before the system-wide settings take\neffect.","label":"fix"}],"id":"V-71901","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GNOME installed","resource":"","run_time":0.000007923,"skip_message":"The system does not have GNOME installed, this requirement is Not\n Applicable.","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71901.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-71901","rid":"SV-86525r3_rule","stig_id":"RHEL-07-010110","fix_id":"F-78253r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must initiate a session\nlock for graphical user interfaces when the screensaver is activated.","waiver_data":{}},{"code":"control \"V-71903\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one upper-case character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Note: The value to require a number of upper-case characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"ucredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep ucredit /etc/security/pwquality.conf\n ucredit = -1\n\n If the value of \\\"ucredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce password complexity by requiring\nthat at least one upper-case character be used by setting the \\\"ucredit\\\"\noption.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\nline to have the required value):\n\n ucredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000069-GPOS-00037\"\n tag gid: \"V-71903\"\n tag rid: \"SV-86527r3_rule\"\n tag stig_id: \"RHEL-07-010120\"\n tag fix_id: \"F-78255r1_fix\"\n tag cci: [\"CCI-000192\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('ucredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of upper-case characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"ucredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep ucredit /etc/security/pwquality.conf\n ucredit = -1\n\n If the value of \"ucredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one upper-case character be used by setting the \"ucredit\"\noption.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n ucredit = -1","label":"fix"}],"id":"V-71903","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf ucredit.to_i is expected to cmp < 0","message":"\nexpected it to be < 0\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000279502,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71903.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-71903","rid":"SV-86527r3_rule","stig_id":"RHEL-07-010120","fix_id":"F-78255r1_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one upper-case character.","waiver_data":{}},{"code":"control \"V-71905\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one lower-case character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Note: The value to require a number of lower-case characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"lcredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep lcredit /etc/security/pwquality.conf\n lcredit = -1\n\n If the value of \\\"lcredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the system to require at least one lower-case character when\ncreating or changing a password.\n\n Add or modify the following line\n in \\\"/etc/security/pwquality.conf\\\":\n\n lcredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000070-GPOS-00038\"\n tag gid: \"V-71905\"\n tag rid: \"SV-86529r5_rule\"\n tag stig_id: \"RHEL-07-010130\"\n tag fix_id: \"F-78257r6_fix\"\n tag cci: [\"CCI-000193\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('lcredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of lower-case characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"lcredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep lcredit /etc/security/pwquality.conf\n lcredit = -1\n\n If the value of \"lcredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the system to require at least one lower-case character when\ncreating or changing a password.\n\n Add or modify the following line\n in \"/etc/security/pwquality.conf\":\n\n lcredit = -1","label":"fix"}],"id":"V-71905","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf lcredit.to_i is expected to cmp < 0","message":"\nexpected it to be < 0\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000200022,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71905.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000070-GPOS-00038","gid":"V-71905","rid":"SV-86529r5_rule","stig_id":"RHEL-07-010130","fix_id":"F-78257r6_fix","cci":["CCI-000193"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one lower-case character.","waiver_data":{}},{"code":"control \"V-71907\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are assigned, the new password\nmust contain at least one numeric character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Note: The value to require a number of numeric characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"dcredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep dcredit /etc/security/pwquality.conf\n dcredit = -1\n\n If the value of \\\"dcredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce password complexity by requiring\nthat at least one numeric character be used by setting the \\\"dcredit\\\" option.\n\n Add the following line to /etc/security/pwquality.conf (or modify the line\nto have the required value):\n\n dcredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000071-GPOS-00039\"\n tag gid: \"V-71907\"\n tag rid: \"SV-86531r3_rule\"\n tag stig_id: \"RHEL-07-010140\"\n tag fix_id: \"F-78259r1_fix\"\n tag cci: [\"CCI-000194\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('dcredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Note: The value to require a number of numeric characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"dcredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep dcredit /etc/security/pwquality.conf\n dcredit = -1\n\n If the value of \"dcredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one numeric character be used by setting the \"dcredit\" option.\n\n Add the following line to /etc/security/pwquality.conf (or modify the line\nto have the required value):\n\n dcredit = -1","label":"fix"}],"id":"V-71907","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf dcredit.to_i is expected to cmp < 0","message":"\nexpected it to be < 0\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000246768,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71907.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000071-GPOS-00039","gid":"V-71907","rid":"SV-86531r3_rule","stig_id":"RHEL-07-010140","fix_id":"F-78259r1_fix","cci":["CCI-000194"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are assigned, the new password\nmust contain at least one numeric character.","waiver_data":{}},{"code":"control \"V-71909\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one special character.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enforces password complexity by requiring that\nat least one special character be used.\n\n Note: The value to require a number of special characters to be set is\nexpressed as a negative number in \\\"/etc/security/pwquality.conf\\\".\n\n Check the value for \\\"ocredit\\\" in \\\"/etc/security/pwquality.conf\\\" with\nthe following command:\n\n # grep ocredit /etc/security/pwquality.conf\n ocredit=-1\n\n If the value of \\\"ocredit\\\" is not set to a negative value, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce password complexity by requiring\nthat at least one special character be used by setting the \\\"ocredit\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\nline to have the required value):\n\n ocredit = -1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000266-GPOS-00101\"\n tag gid: \"V-71909\"\n tag rid: \"SV-86533r2_rule\"\n tag stig_id: \"RHEL-07-010150\"\n tag fix_id: \"F-78261r2_fix\"\n tag cci: [\"CCI-001619\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('ocredit.to_i') { should cmp < 0 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces password complexity by requiring that\nat least one special character be used.\n\n Note: The value to require a number of special characters to be set is\nexpressed as a negative number in \"/etc/security/pwquality.conf\".\n\n Check the value for \"ocredit\" in \"/etc/security/pwquality.conf\" with\nthe following command:\n\n # grep ocredit /etc/security/pwquality.conf\n ocredit=-1\n\n If the value of \"ocredit\" is not set to a negative value, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to enforce password complexity by requiring\nthat at least one special character be used by setting the \"ocredit\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n ocredit = -1","label":"fix"}],"id":"V-71909","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf ocredit.to_i is expected to cmp < 0","message":"\nexpected it to be < 0\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000195452,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71909.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000266-GPOS-00101","gid":"V-71909","rid":"SV-86533r2_rule","stig_id":"RHEL-07-010150","fix_id":"F-78261r2_fix","cci":["CCI-001619"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, the new\npassword must contain at least one special character.","waiver_data":{}},{"code":"control \"V-71911\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of eight of the total number of\ncharacters must be changed.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"difok\\\" option sets the number of characters in a password that must\nnot be present in the old password.\n\n Check for the value of the \\\"difok\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep difok /etc/security/pwquality.conf\n difok = 8\n\n If the value of \\\"difok\\\" is set to less than \\\"8\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of at least eight of\nthe total number of characters when passwords are changed by setting the\n\\\"difok\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\nline to have the required value):\n\n difok = 8\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71911\"\n tag rid: \"SV-86535r2_rule\"\n tag stig_id: \"RHEL-07-010160\"\n tag fix_id: \"F-78263r1_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n difok = input('difok')\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('difok.to_i') { should cmp >= difok }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"difok\" option sets the number of characters in a password that must\nnot be present in the old password.\n\n Check for the value of the \"difok\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep difok /etc/security/pwquality.conf\n difok = 8\n\n If the value of \"difok\" is set to less than \"8\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of at least eight of\nthe total number of characters when passwords are changed by setting the\n\"difok\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\n difok = 8","label":"fix"}],"id":"V-71911","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf difok.to_i is expected to cmp >= 8","message":"\nexpected it to be >= 8\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000196585,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71911.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71911","rid":"SV-86535r2_rule","stig_id":"RHEL-07-010160","fix_id":"F-78263r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of eight of the total number of\ncharacters must be changed.","waiver_data":{}},{"code":"control \"V-71913\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of four character classes must be\nchanged.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"minclass\\\" option sets the minimum number of required classes of\ncharacters for the new password (digits, upper-case, lower-case, others).\n\n Check for the value of the \\\"minclass\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep minclass /etc/security/pwquality.conf\n minclass = 4\n\n If the value of \\\"minclass\\\" is set to less than \\\"4\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of at least four\ncharacter classes when passwords are changed by setting the \\\"minclass\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf conf\\\" (or modify\nthe line to have the required value):\n\n minclass = 4\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71913\"\n tag rid: \"SV-86537r2_rule\"\n tag stig_id: \"RHEL-07-010170\"\n tag fix_id: \"F-78265r1_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('minclass.to_i') { should cmp >= 4 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"minclass\" option sets the minimum number of required classes of\ncharacters for the new password (digits, upper-case, lower-case, others).\n\n Check for the value of the \"minclass\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep minclass /etc/security/pwquality.conf\n minclass = 4\n\n If the value of \"minclass\" is set to less than \"4\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of at least four\ncharacter classes when passwords are changed by setting the \"minclass\" option.\n\n Add the following line to \"/etc/security/pwquality.conf conf\" (or modify\nthe line to have the required value):\n\n minclass = 4","label":"fix"}],"id":"V-71913","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf minclass.to_i is expected to cmp >= 4","message":"\nexpected it to be >= 4\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.0003651,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71913.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71913","rid":"SV-86537r2_rule","stig_id":"RHEL-07-010170","fix_id":"F-78265r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed a minimum of four character classes must be\nchanged.","waiver_data":{}},{"code":"control \"V-71915\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating consecutive characters\nmust not be more than three characters.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"maxrepeat\\\" option sets the maximum number of allowed same\nconsecutive characters in a new password.\n\n Check for the value of the \\\"maxrepeat\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep maxrepeat /etc/security/pwquality.conf\n maxrepeat = 3\n\n If the value of \\\"maxrepeat\\\" is set to more than \\\"3\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of the number of\nrepeating consecutive characters when passwords are changed by setting the\n\\\"maxrepeat\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf conf\\\" (or modify\nthe line to have the required value):\n\n maxrepeat = 3\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71915\"\n tag rid: \"SV-86539r3_rule\"\n tag stig_id: \"RHEL-07-010180\"\n tag fix_id: \"F-78267r2_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('maxrepeat.to_i') { should cmp <= 3 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"maxrepeat\" option sets the maximum number of allowed same\nconsecutive characters in a new password.\n\n Check for the value of the \"maxrepeat\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep maxrepeat /etc/security/pwquality.conf\n maxrepeat = 3\n\n If the value of \"maxrepeat\" is set to more than \"3\", this is a finding.","label":"check"},{"data":"Configure the operating system to require the change of the number of\nrepeating consecutive characters when passwords are changed by setting the\n\"maxrepeat\" option.\n\n Add the following line to \"/etc/security/pwquality.conf conf\" (or modify\nthe line to have the required value):\n\n maxrepeat = 3","label":"fix"}],"id":"V-71915","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf maxrepeat.to_i is expected to cmp <= 3","run_time":0.000179274,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71915.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71915","rid":"SV-86539r3_rule","stig_id":"RHEL-07-010180","fix_id":"F-78267r2_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating consecutive characters\nmust not be more than three characters.","waiver_data":{}},{"code":"control \"V-71917\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating characters of the same\ncharacter class must not be more than four characters.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The \\\"maxclassrepeat\\\" option sets the maximum number of allowed same\nconsecutive characters in the same class in the new password.\n\n Check for the value of the \\\"maxclassrepeat\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep maxclassrepeat /etc/security/pwquality.conf\n maxclassrepeat = 4\n\n If the value of \\\"maxclassrepeat\\\" is set to more than \\\"4\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to require the change of the number of\nrepeating characters of the same character class when passwords are changed by\nsetting the \\\"maxclassrepeat\\\" option.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" conf (or modify\nthe line to have the required value):\n\n maxclassrepeat = 4\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000072-GPOS-00040\"\n tag gid: \"V-71917\"\n tag rid: \"SV-86541r2_rule\"\n tag stig_id: \"RHEL-07-010190\"\n tag fix_id: \"F-78269r1_fix\"\n tag cci: [\"CCI-000195\"]\n tag nist: [\"IA-5 (1) (b)\"]\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('maxclassrepeat.to_i') { should cmp <= 4 }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks.\n\n Password complexity is one factor of several that determines how long it\ntakes to crack a password. The more complex the password, the greater the\nnumber of possible combinations that need to be tested before the password is\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"The \"maxclassrepeat\" option sets the maximum number of allowed same\nconsecutive characters in the same class in the new password.\n\n Check for the value of the \"maxclassrepeat\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\n # grep maxclassrepeat /etc/security/pwquality.conf\n maxclassrepeat = 4\n\n If the value of \"maxclassrepeat\" is set to more than \"4\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to require the change of the number of\nrepeating characters of the same character class when passwords are changed by\nsetting the \"maxclassrepeat\" option.\n\n Add the following line to \"/etc/security/pwquality.conf\" conf (or modify\nthe line to have the required value):\n\n maxclassrepeat = 4","label":"fix"}],"id":"V-71917","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf maxclassrepeat.to_i is expected to cmp <= 4","run_time":0.000263295,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71917.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000072-GPOS-00040","gid":"V-71917","rid":"SV-86541r2_rule","stig_id":"RHEL-07-010190","fix_id":"F-78269r1_fix","cci":["CCI-000195"],"nist":["IA-5 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed the number of repeating characters of the same\ncharacter class must not be more than four characters.","waiver_data":{}},{"code":"control \"V-71919\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the PAM system service is configured to store only encrypted\nrepresentations of passwords.\"\n desc \"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the PAM system service is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep password /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n Outcome should look like following:\n /etc/pam.d/system-auth-ac:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n /etc/pam.d/password-auth:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n\n If the \\\"/etc/pam.d/system-auth\\\" and \\\"/etc/pam.d/password-auth\\\"\nconfiguration files allow for password hashes other than SHA512 to be used,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add the following line in \\\"/etc/pam.d/system-auth\\\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Add the following line in \\\"/etc/pam.d/password-auth\\\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000073-GPOS-00041\"\n tag gid: \"V-71919\"\n tag rid: \"SV-86543r3_rule\"\n tag stig_id: \"RHEL-07-010200\"\n tag fix_id: \"F-78271r4_fix\"\n tag cci: [\"CCI-000196\"]\n tag nist: [\"IA-5 (1) (c)\"]\n\n describe pam(\"/etc/pam.d/system-auth\") do\n its('lines') { should match_pam_rule('password sufficient pam_unix.so sha512') }\n its('lines') { should match_pam_rule('password .* pam_unix.so').all_without_args('^(md5|bigcrypt|sha256|blowfish)$') }\n end\nend\n","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the PAM system service is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep password /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n Outcome should look like following:\n /etc/pam.d/system-auth-ac:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n /etc/pam.d/password-auth:password sufficient pam_unix.so sha512\nshadow try_first_pass use_authtok\n\n If the \"/etc/pam.d/system-auth\" and \"/etc/pam.d/password-auth\"\nconfiguration files allow for password hashes other than SHA512 to be used,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add the following line in \"/etc/pam.d/system-auth\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Add the following line in \"/etc/pam.d/password-auth\":\n pam_unix.so sha512 shadow try_first_pass use_authtok\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71919","impact":0.5,"refs":[],"results":[{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include password sufficient pam_unix.so sha512","message":"expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...ss=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\\nsession required pam_unix.so\" to include password sufficient pam_unix.so sha512\nDiff:\n@@ -1,2 +1,18 @@\n-password sufficient pam_unix.so sha512\n+account required pam_unix.so\n+account sufficient pam_localuser.so\n+account sufficient pam_succeed_if.so uid < 1000 quiet\n+account required pam_permit.so\n+auth required pam_env.so\n+auth required pam_faildelay.so delay=2000000\n+auth sufficient pam_unix.so nullok try_first_pass\n+auth requisite pam_succeed_if.so uid >= 1000 quiet_success\n+auth required pam_deny.so\n+password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+password required pam_deny.so\n+session optional pam_keyinit.so revoke\n+session required pam_limits.so\n+-session optional pam_systemd.so\n+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\n+session required pam_unix.so\n","run_time":0.001169953,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include password .* pam_unix.so, all without args ^(md5|bigcrypt|sha256|blowfish)$","run_time":0.000622588,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71919.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71919","rid":"SV-86543r3_rule","stig_id":"RHEL-07-010200","fix_id":"F-78271r4_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the PAM system service is configured to store only encrypted\nrepresentations of passwords.","waiver_data":{}},{"code":"control \"V-71921\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nuse the shadow file to store only encrypted representations of passwords.\"\n desc \"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system's shadow file is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep -i encrypt /etc/login.defs\n ENCRYPT_METHOD SHA512\n\n If the \\\"/etc/login.defs\\\" configuration file does not exist or allows for\npassword hashes other than SHA512 to be used, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \\\"/etc/login.defs\\\":\n\n ENCRYPT_METHOD SHA512\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000073-GPOS-00041\"\n tag gid: \"V-71921\"\n tag rid: \"SV-86545r2_rule\"\n tag stig_id: \"RHEL-07-010210\"\n tag fix_id: \"F-78273r1_fix\"\n tag cci: [\"CCI-000196\"]\n tag nist: [\"IA-5 (1) (c)\"]\n\n describe login_defs do\n its('ENCRYPT_METHOD') { should cmp \"SHA512\" }\n end\nend\n","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system's shadow file is configured to store only encrypted\nrepresentations of passwords. The strength of encryption that must be used to\nhash passwords for all accounts is SHA512.\n\n Check that the system is configured to create SHA512 hashed passwords with\nthe following command:\n\n # grep -i encrypt /etc/login.defs\n ENCRYPT_METHOD SHA512\n\n If the \"/etc/login.defs\" configuration file does not exist or allows for\npassword hashes other than SHA512 to be used, this is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \"/etc/login.defs\":\n\n ENCRYPT_METHOD SHA512","label":"fix"}],"id":"V-71921","impact":0.5,"refs":[],"results":[{"code_desc":"login.defs ENCRYPT_METHOD is expected to cmp == \"SHA512\"","message":"\nexpected: SHA512\n got: MD5\n\n(compared using `cmp` matcher)\n","run_time":0.000711354,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"login_defs","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71921.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71921","rid":"SV-86545r2_rule","stig_id":"RHEL-07-010210","fix_id":"F-78273r1_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nuse the shadow file to store only encrypted representations of passwords.","waiver_data":{}},{"code":"control \"V-71923\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat user and group account administration utilities are configured to store\nonly encrypted representations of passwords.\"\n desc \"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the user and group account administration utilities are configured\nto store only encrypted representations of passwords. The strength of\nencryption that must be used to hash passwords for all accounts is \\\"SHA512\\\".\n\n Check that the system is configured to create \\\"SHA512\\\" hashed passwords\nwith the following command:\n\n # grep -i sha512 /etc/libuser.conf\n\n crypt_style = sha512\n\n If the \\\"crypt_style\\\" variable is not set to \\\"sha512\\\", is not in the\ndefaults section, is commented out, or does not exist, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \\\"/etc/libuser.conf\\\" in the [defaults]\nsection:\n\n crypt_style = sha512\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000073-GPOS-00041\"\n tag gid: \"V-71923\"\n tag rid: \"SV-86547r3_rule\"\n tag stig_id: \"RHEL-07-010220\"\n tag fix_id: \"F-78275r1_fix\"\n tag cci: [\"CCI-000196\"]\n tag nist: [\"IA-5 (1) (c)\"]\n\n describe command(\"cat /etc/libuser.conf | grep -i sha512\") do\n its('stdout.strip') { should match %r(^crypt_style = sha512$) }\n end\nend\n","desc":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","descriptions":[{"data":"Passwords need to be protected at all times, and encryption is the\nstandard method for protecting passwords. If passwords are not encrypted, they\ncan be plainly read (i.e., clear text) and easily compromised. Passwords\nencrypted with a weak algorithm are no more protected than if they are kept in\nplain text.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the user and group account administration utilities are configured\nto store only encrypted representations of passwords. The strength of\nencryption that must be used to hash passwords for all accounts is \"SHA512\".\n\n Check that the system is configured to create \"SHA512\" hashed passwords\nwith the following command:\n\n # grep -i sha512 /etc/libuser.conf\n\n crypt_style = sha512\n\n If the \"crypt_style\" variable is not set to \"sha512\", is not in the\ndefaults section, is commented out, or does not exist, this is a finding.","label":"check"},{"data":"Configure the operating system to store only SHA512 encrypted\nrepresentations of passwords.\n\n Add or update the following line in \"/etc/libuser.conf\" in the [defaults]\nsection:\n\n crypt_style = sha512","label":"fix"}],"id":"V-71923","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `cat /etc/libuser.conf | grep -i sha512` stdout.strip is expected to match /^crypt_style = sha512$/","message":"expected \"\" to match /^crypt_style = sha512$/\nDiff:\n@@ -1,2 +1,2 @@\n-/^crypt_style = sha512$/\n+\"\"\n","run_time":0.026374921,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"command","resource_params":"[\"cat /etc/libuser.conf | grep -i sha512\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71923.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000073-GPOS-00041","gid":"V-71923","rid":"SV-86547r3_rule","stig_id":"RHEL-07-010220","fix_id":"F-78275r1_fix","cci":["CCI-000196"],"nist":["IA-5 (1) (c)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat user and group account administration utilities are configured to store\nonly encrypted representations of passwords.","waiver_data":{}},{"code":"control \"V-71925\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 24 hours/1 day minimum\nlifetime.\"\n desc \"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enforces 24 hours/1 day as the minimum password\nlifetime for new user accounts.\n\n Check for the value of \\\"PASS_MIN_DAYS\\\" in \\\"/etc/login.defs\\\" with the\nfollowing command:\n\n # grep -i pass_min_days /etc/login.defs\n PASS_MIN_DAYS 1\n\n If the \\\"PASS_MIN_DAYS\\\" parameter value is not \\\"1\\\" or greater, or is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce 24 hours/1 day as the minimum\npassword lifetime.\n\n Add the following line in \\\"/etc/login.defs\\\" (or modify the line to have\nthe required value):\n\n PASS_MIN_DAYS 1\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000075-GPOS-00043\"\n tag gid: \"V-71925\"\n tag rid: \"SV-86549r2_rule\"\n tag stig_id: \"RHEL-07-010230\"\n tag fix_id: \"F-78277r1_fix\"\n tag cci: [\"CCI-000198\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n describe login_defs do\n its('PASS_MIN_DAYS.to_i') { should cmp >= 1 }\n end\nend\n","desc":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","descriptions":[{"data":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces 24 hours/1 day as the minimum password\nlifetime for new user accounts.\n\n Check for the value of \"PASS_MIN_DAYS\" in \"/etc/login.defs\" with the\nfollowing command:\n\n # grep -i pass_min_days /etc/login.defs\n PASS_MIN_DAYS 1\n\n If the \"PASS_MIN_DAYS\" parameter value is not \"1\" or greater, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce 24 hours/1 day as the minimum\npassword lifetime.\n\n Add the following line in \"/etc/login.defs\" (or modify the line to have\nthe required value):\n\n PASS_MIN_DAYS 1","label":"fix"}],"id":"V-71925","impact":0.5,"refs":[],"results":[{"code_desc":"login.defs PASS_MIN_DAYS.to_i is expected to cmp >= 1","message":"\nexpected it to be >= 1\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000798993,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"login_defs","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71925.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000075-GPOS-00043","gid":"V-71925","rid":"SV-86549r2_rule","stig_id":"RHEL-07-010230","fix_id":"F-78277r1_fix","cci":["CCI-000198"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 24 hours/1 day minimum\nlifetime.","waiver_data":{}},{"code":"control \"V-71927\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are restricted to a 24 hours/1 day minimum lifetime.\"\n desc \"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check whether the minimum time period between password changes for each\nuser account is one day or greater.\n\n # awk -F: '$4 < 1 {print $1 \\\" \\\" $4}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure non-compliant accounts to enforce a 24 hours/1 day minimum\npassword lifetime:\n\n # chage -m 1 [user]\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000075-GPOS-00043\"\n tag gid: \"V-71927\"\n tag rid: \"SV-86551r2_rule\"\n tag stig_id: \"RHEL-07-010240\"\n tag fix_id: \"F-78279r1_fix\"\n tag cci: [\"CCI-000198\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n shadow.users.each do |user|\n # filtering on non-system accounts (uid >= 1000)\n next unless user(user).uid >= 1000\n describe shadow.users(user) do\n its('min_days.first.to_i') { should cmp >= 1 }\n end\n end\nend\n","desc":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","descriptions":[{"data":"Enforcing a minimum password lifetime helps to prevent repeated\npassword changes to defeat the password reuse or history enforcement\nrequirement. If users are allowed to immediately and continually change their\npassword, the password could be repeatedly changed in a short period of time to\ndefeat the organization's policy regarding password reuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Check whether the minimum time period between password changes for each\nuser account is one day or greater.\n\n # awk -F: '$4 < 1 {print $1 \" \" $4}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.","label":"check"},{"data":"Configure non-compliant accounts to enforce a 24 hours/1 day minimum\npassword lifetime:\n\n # chage -m 1 [user]","label":"fix"}],"id":"V-71927","impact":0.5,"refs":[],"results":[{"code_desc":"/etc/shadow with user == \"nfsnobody\" min_days.first.to_i is expected to cmp >= 1","message":"\nexpected it to be >= 1\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000225666,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"/etc/shadow with user == \"vagrant\" min_days.first.to_i is expected to cmp >= 1","message":"\nexpected it to be >= 1\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000253172,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71927.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000075-GPOS-00043","gid":"V-71927","rid":"SV-86551r2_rule","stig_id":"RHEL-07-010240","fix_id":"F-78279r1_fix","cci":["CCI-000198"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are restricted to a 24 hours/1 day minimum lifetime.","waiver_data":{}},{"code":"control \"V-71929\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 60-day maximum lifetime.\"\n desc \"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system enforces a 60-day maximum password lifetime\nrestriction for new user accounts.\n\n Check for the value of \\\"PASS_MAX_DAYS\\\" in \\\"/etc/login.defs\\\" with the\nfollowing command:\n\n # grep -i pass_max_days /etc/login.defs\n PASS_MAX_DAYS 60\n\n If the \\\"PASS_MAX_DAYS\\\" parameter value is not 60 or less, or is commented\nout, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce a 60-day maximum password\nlifetime restriction.\n\n Add the following line in \\\"/etc/login.defs\\\" (or modify the line to have\nthe required value):\n\n PASS_MAX_DAYS 60\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000076-GPOS-00044\"\n tag gid: \"V-71929\"\n tag rid: \"SV-86553r2_rule\"\n tag stig_id: \"RHEL-07-010250\"\n tag fix_id: \"F-78281r1_fix\"\n tag cci: [\"CCI-000199\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n unless command(\"grep 'pam_unix.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'optional'\").stdout.empty? && command(\"grep 'pam_permit.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'required'\").stdout.empty?\n impact 0.0\n describe \"The system is not using password for authentication\" do\n skip \"The system is not using password for authentication, this control is Not Applicable.\"\n end\n else\n describe login_defs do\n its('PASS_MAX_DAYS.to_i') { should cmp <= 60 }\n end\n end\nend\n","desc":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","descriptions":[{"data":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system enforces a 60-day maximum password lifetime\nrestriction for new user accounts.\n\n Check for the value of \"PASS_MAX_DAYS\" in \"/etc/login.defs\" with the\nfollowing command:\n\n # grep -i pass_max_days /etc/login.defs\n PASS_MAX_DAYS 60\n\n If the \"PASS_MAX_DAYS\" parameter value is not 60 or less, or is commented\nout, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce a 60-day maximum password\nlifetime restriction.\n\n Add the following line in \"/etc/login.defs\" (or modify the line to have\nthe required value):\n\n PASS_MAX_DAYS 60","label":"fix"}],"id":"V-71929","impact":0.5,"refs":[],"results":[{"code_desc":"login.defs PASS_MAX_DAYS.to_i is expected to cmp <= 60","message":"\nexpected it to be <= 60\n got: 99999\n\n(compared using `cmp` matcher)\n","run_time":0.00061629,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"login_defs","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71929.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000076-GPOS-00044","gid":"V-71929","rid":"SV-86553r2_rule","stig_id":"RHEL-07-010250","fix_id":"F-78281r1_fix","cci":["CCI-000199"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords for new users are restricted to a 60-day maximum lifetime.","waiver_data":{}},{"code":"control \"V-71931\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat existing passwords are restricted to a 60-day maximum lifetime.\"\n desc \"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check whether the maximum time period for existing passwords is restricted\nto 60 days.\n\n # awk -F: '$5 > 60 {print $1 \\\" \\\" $5}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.\n\n \"\n desc \"fix\", \"\n Configure non-compliant accounts to enforce a 60-day maximum password\nlifetime restriction.\n\n # chage -M 60 [user]\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000076-GPOS-00044\"\n tag gid: \"V-71931\"\n tag rid: \"SV-86555r3_rule\"\n tag stig_id: \"RHEL-07-010260\"\n tag fix_id: \"F-78283r1_fix\"\n tag cci: [\"CCI-000199\"]\n tag nist: [\"IA-5 (1) (d)\"]\n\n shadow.users.each do |user|\n # filtering on non-system accounts (uid >= 1000)\n next unless user(user).uid >= 1000\n describe shadow.users(user) do\n its('max_days.first.to_i') { should cmp <= 60 }\n end\n end\nend\n","desc":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","descriptions":[{"data":"Any password, no matter how complex, can eventually be cracked.\nTherefore, passwords need to be changed periodically. If the operating system\ndoes not limit the lifetime of passwords and force users to change their\npasswords, there is the risk that the operating system passwords could be\ncompromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Check whether the maximum time period for existing passwords is restricted\nto 60 days.\n\n # awk -F: '$5 > 60 {print $1 \" \" $5}' /etc/shadow\n\n If any results are returned that are not associated with a system account,\nthis is a finding.","label":"check"},{"data":"Configure non-compliant accounts to enforce a 60-day maximum password\nlifetime restriction.\n\n # chage -M 60 [user]","label":"fix"}],"id":"V-71931","impact":0.5,"refs":[],"results":[{"code_desc":"/etc/shadow with user == \"nfsnobody\" max_days.first.to_i is expected to cmp <= 60","run_time":0.000184604,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"/etc/shadow with user == \"vagrant\" max_days.first.to_i is expected to cmp <= 60","message":"\nexpected it to be <= 60\n got: 99999\n\n(compared using `cmp` matcher)\n","run_time":0.000228775,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71931.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000076-GPOS-00044","gid":"V-71931","rid":"SV-86555r3_rule","stig_id":"RHEL-07-010260","fix_id":"F-78283r1_fix","cci":["CCI-000199"],"nist":["IA-5 (1) (d)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat existing passwords are restricted to a 60-day maximum lifetime.","waiver_data":{}},{"code":"control \"V-71933\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are prohibited from reuse for a minimum of five generations.\"\n desc \"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prohibits password reuse for a minimum of five\ngenerations.\n\n Check for the value of the \\\"remember\\\" argument in\n\\\"/etc/pam.d/system-auth\\\" and \\\"/etc/pam.d/password-auth\\\" with the following\ncommand:\n\n # grep -i remember /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n If the line containing the \\\"pam_pwhistory.so\\\" line does not have the\n\\\"remember\\\" module argument set, is commented out, or the value of the\n\\\"remember\\\" module argument is set to less than \\\"5\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prohibit password reuse for a minimum of\nfive generations.\n\n Add the following line in \\\"/etc/pam.d/system-auth\\\" and\n\\\"/etc/pam.d/password-auth\\\" (or modify the line to have the required value):\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000077-GPOS-00045\"\n tag gid: \"V-71933\"\n tag rid: \"SV-86557r3_rule\"\n tag stig_id: \"RHEL-07-010270\"\n tag fix_id: \"F-78285r3_fix\"\n tag cci: [\"CCI-000200\"]\n tag nist: [\"IA-5 (1) (e)\"]\n\n min_reuse_generations = input('min_reuse_generations')\n\n describe pam(\"/etc/pam.d/system-auth\") do\n its('lines') { should match_pam_rule('password (required|requisite|sufficient) pam_(unix|pwhistory).so').any_with_integer_arg('remember', '>=', min_reuse_generations) }\n end\nend\n","desc":"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.","descriptions":[{"data":"Password complexity, or strength, is a measure of the effectiveness of\na password in resisting attempts at guessing and brute-force attacks. If the\ninformation system or application allows the user to consecutively reuse their\npassword when that password has exceeded its defined lifetime, the end result\nis a password that is not changed per policy requirements.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prohibits password reuse for a minimum of five\ngenerations.\n\n Check for the value of the \"remember\" argument in\n\"/etc/pam.d/system-auth\" and \"/etc/pam.d/password-auth\" with the following\ncommand:\n\n # grep -i remember /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n If the line containing the \"pam_pwhistory.so\" line does not have the\n\"remember\" module argument set, is commented out, or the value of the\n\"remember\" module argument is set to less than \"5\", this is a finding.","label":"check"},{"data":"Configure the operating system to prohibit password reuse for a minimum of\nfive generations.\n\n Add the following line in \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" (or modify the line to have the required value):\n\n password requisite pam_pwhistory.so use_authtok remember=5 retry=3\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"},{"data":"This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords","label":"caveat"}],"id":"V-71933","impact":0,"refs":[{"ref":[]}],"results":[{"code_desc":"This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords","resource":"","run_time":0.000010459,"skip_message":"This is Not Applicable for the project since we have an approved risk-based decision on 10/1/2021 allowing reuse of old passwords","start_time":"2022-03-06T22:05:48+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71933.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000077-GPOS-00045","gid":"V-71933","rid":"SV-86557r3_rule","stig_id":"RHEL-07-010270","fix_id":"F-78285r3_fix","cci":["CCI-000200"],"nist":["IA-5 (1) (e)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are prohibited from reuse for a minimum of five generations.","waiver_data":{}},{"code":"control \"V-71935\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat passwords are a minimum of 15 characters in length.\"\n desc \"The shorter the password, the lower the number of possible\ncombinations that need to be tested before the password is compromised.\n\n Password complexity, or strength, is a measure of the effectiveness of a\npassword in resisting attempts at guessing and brute-force attacks. Password\nlength is one factor of several that helps to determine strength and how long\nit takes to crack a password. Use of more characters in a password helps to\nexponentially increase the time and/or resources required to compromise the\npassword.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enforces a minimum 15-character password\nlength. The \\\"minlen\\\" option sets the minimum number of characters in a new\npassword.\n\n Check for the value of the \\\"minlen\\\" option in\n\\\"/etc/security/pwquality.conf\\\" with the following command:\n\n # grep minlen /etc/security/pwquality.conf\n minlen = 15\n\n If the command does not return a \\\"minlen\\\" value of 15 or greater, this is\na finding.\n \"\n desc \"fix\", \"\n Configure operating system to enforce a minimum 15-character password\nlength.\n\n Add the following line to \\\"/etc/security/pwquality.conf\\\" (or modify the\nline to have the required value):\n\n minlen = 15\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000078-GPOS-00046\"\n tag gid: \"V-71935\"\n tag rid: \"SV-86559r2_rule\"\n tag stig_id: \"RHEL-07-010280\"\n tag fix_id: \"F-78287r1_fix\"\n tag cci: [\"CCI-000205\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n min_len = input('min_len')\n\n describe parse_config_file(\"/etc/security/pwquality.conf\") do\n its('minlen.to_i') { should cmp >= min_len }\n end\nend\n","desc":"The shorter the password, the lower the number of possible\ncombinations that need to be tested before the password is compromised.\n\n Password complexity, or strength, is a measure of the effectiveness of a\npassword in resisting attempts at guessing and brute-force attacks. Password\nlength is one factor of several that helps to determine strength and how long\nit takes to crack a password. Use of more characters in a password helps to\nexponentially increase the time and/or resources required to compromise the\npassword.","descriptions":[{"data":"The shorter the password, the lower the number of possible\ncombinations that need to be tested before the password is compromised.\n\n Password complexity, or strength, is a measure of the effectiveness of a\npassword in resisting attempts at guessing and brute-force attacks. Password\nlength is one factor of several that helps to determine strength and how long\nit takes to crack a password. Use of more characters in a password helps to\nexponentially increase the time and/or resources required to compromise the\npassword.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces a minimum 24-character password\nlength. The \"minlen\" option sets the minimum number of characters in a new\npassword.\n\t\tCheck for the value of the \"minlen\" option in\n\"/etc/security/pwquality.conf\" with the following command:\n\t\t# grep minlen /etc/security/pwquality.conf\n\t\tminlen = 24\n\t\tIf the command does not return a \"minlen\" value of 24 or greater, this is\na finding.","label":"check"},{"data":"Configure operating system to enforce a minimum 24-character password\nlength.\n\t\tAdd the following line to \"/etc/security/pwquality.conf\" (or modify the\nline to have the required value):\n\t\tminlen = 24","label":"fix"},{"data":"The project2 requires more secure password length of 24 characters as approved on 1/12/2022","label":"caveat"}],"id":"V-71935","impact":0.5,"refs":[{"ref":[]}],"results":[{"code_desc":"Parse Config File /etc/security/pwquality.conf minlen.to_i is expected to cmp >= 24","message":"\nexpected it to be >= 24\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000300726,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/security/pwquality.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71935.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000078-GPOS-00046","gid":"V-71935","rid":"SV-86559r2_rule","stig_id":"RHEL-07-010280","fix_id":"F-78287r1_fix","cci":["CCI-000205"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\n\tthat passwords are a minimum of 24 characters in length.","waiver_data":{}},{"code":"control \"V-71937\" do\n title \"The Red Hat Enterprise Linux operating system must not have accounts\nconfigured with blank or null passwords.\"\n desc \"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n To verify that null passwords cannot be used, run the following command:\n\n # grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n If this produces any output, it may be possible to log on with accounts\nwith empty passwords.\n\n If null passwords can be used, this is a finding.\n \"\n desc \"fix\", \"\n If an account is configured for password authentication but does not have\nan assigned password, it may be possible to log on to the account without\nauthenticating.\n\n Remove any instances of the \\\"nullok\\\" option in \\\"/etc/pam.d/system-auth\\\"\nand \\\"/etc/pam.d/password-auth\\\" to prevent logons with empty passwords.\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71937\"\n tag rid: \"SV-86561r3_rule\"\n tag stig_id: \"RHEL-07-010290\"\n tag fix_id: \"F-78289r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n # Fetch all files under /etc/pam.d excluding '*-ac' files\n # but including symlinks\n pam_file_list = command('find /etc/pam.d ! -name \\'*-ac\\' -a \\( -type f -o -type l \\)').stdout.strip.split\n\n pam_file_list.each do |pam_file|\n describe pam(pam_file) do\n its('lines') { should match_pam_rule('.* .* pam_unix.so').all_without_args('nullok') }\n end\n end\nend\n","desc":"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.","descriptions":[{"data":"If an account has an empty password, anyone could log on and run\ncommands with the privileges of that account. Accounts with empty passwords\nshould never be used in operational environments.","label":"default"},{"data":"","label":"rationale"},{"data":"To verify that null passwords cannot be used, run the following command:\n\n # grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth\n\n If this produces any output, it may be possible to log on with accounts\nwith empty passwords.\n\n If null passwords can be used, this is a finding.","label":"check"},{"data":"If an account is configured for password authentication but does not have\nan assigned password, it may be possible to log on to the account without\nauthenticating.\n\n Remove any instances of the \"nullok\" option in \"/etc/pam.d/system-auth\"\nand \"/etc/pam.d/password-auth\" to prevent logons with empty passwords.\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71937","impact":0.7,"refs":[],"results":[{"code_desc":"PAM Config[/etc/pam.d/config-util] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,5 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.001169477,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/config-util\"]"},{"code_desc":"PAM Config[/etc/pam.d/other] lines is expected to include .* .* pam_unix.so, all without args nullok","run_time":0.000361165,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/other\"]"},{"code_desc":"PAM Config[/etc/pam.d/chfn] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.003459847,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/chfn\"]"},{"code_desc":"PAM Config[/etc/pam.d/chsh] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.003662348,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/chsh\"]"},{"code_desc":"PAM Config[/etc/pam.d/login] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.00299316,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/login\"]"},{"code_desc":"PAM Config[/etc/pam.d/remote] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.002644012,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/remote\"]"},{"code_desc":"PAM Config[/etc/pam.d/runuser] lines is expected to include .* .* pam_unix.so, all without args nullok","run_time":0.000360632,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/runuser\"]"},{"code_desc":"PAM Config[/etc/pam.d/runuser-l] lines is expected to include .* .* pam_unix.so, all without args nullok","run_time":0.000549119,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/runuser-l\"]"},{"code_desc":"PAM Config[/etc/pam.d/su] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.002793623,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/su\"]"},{"code_desc":"PAM Config[/etc/pam.d/su-l] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,65 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.009660297,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/su-l\"]"},{"code_desc":"PAM Config[/etc/pam.d/systemd-user] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,9 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.001565479,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/systemd-user\"]"},{"code_desc":"PAM Config[/etc/pam.d/polkit-1] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.002458838,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/polkit-1\"]"},{"code_desc":"PAM Config[/etc/pam.d/crond] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,13 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.00185928,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/crond\"]"},{"code_desc":"PAM Config[/etc/pam.d/vlock] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,5 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.00125249,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/vlock\"]"},{"code_desc":"PAM Config[/etc/pam.d/vmtoolsd] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,9 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.00178686,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/vmtoolsd\"]"},{"code_desc":"PAM Config[/etc/pam.d/sshd] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.002748146,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/sshd\"]"},{"code_desc":"PAM Config[/etc/pam.d/smtp.postfix] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,9 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.001649189,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/smtp.postfix\"]"},{"code_desc":"PAM Config[/etc/pam.d/sudo] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,17 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.002609295,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/sudo\"]"},{"code_desc":"PAM Config[/etc/pam.d/sudo-i] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,65 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.009561671,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/sudo-i\"]"},{"code_desc":"PAM Config[/etc/pam.d/passwd] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,13 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.002301997,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/passwd\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,5 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.001028714,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/postlogin] lines is expected to include .* .* pam_unix.so, all without args nullok","run_time":0.000371944,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/postlogin\"]"},{"code_desc":"PAM Config[/etc/pam.d/password-auth] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,5 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.000956859,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/password-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/fingerprint-auth] lines is expected to include .* .* pam_unix.so, all without args nullok","run_time":0.000651745,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/fingerprint-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/smartcard-auth] lines is expected to include .* .* pam_unix.so, all without args nullok","run_time":0.000610917,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/smartcard-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/subscription-manager] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,13 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.002608839,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/subscription-manager\"]"},{"code_desc":"PAM Config[/etc/pam.d/smtp] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,9 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.001632307,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/smtp\"]"},{"code_desc":"PAM Config[/etc/pam.d/postgresql] lines is expected to include .* .* pam_unix.so, all without args nullok","message":"expected \"auth sufficient pam_unix.so nullok try_first_pass\\naccount required pam_unix.so\\npassword sufficient...d sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\\nsession required pam_unix.so\" to include .* .* pam_unix.so, all without args nullok\nDiff:\n@@ -1,2 +1,9 @@\n-.* .* pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n+auth sufficient pam_unix.so nullok try_first_pass\n+account required pam_unix.so\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+session required pam_unix.so\n","run_time":0.003130073,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/postgresql\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71937.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71937","rid":"SV-86561r3_rule","stig_id":"RHEL-07-010290","fix_id":"F-78289r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have accounts\nconfigured with blank or null passwords.","waiver_data":{}},{"code":"control \"V-71939\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using an empty password.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n To determine how the SSH daemon's \\\"PermitEmptyPasswords\\\" option is set,\nrun the following command:\n\n # grep -i PermitEmptyPasswords /etc/ssh/sshd_config\n PermitEmptyPasswords no\n\n If no line, a commented line, or a line indicating the value \\\"no\\\" is\nreturned, the required value is set.\n\n If the required value is not set, this is a finding.\n \"\n desc \"fix\", \"\n To explicitly disallow remote logon from accounts with empty passwords, add\nor correct the following line in \\\"/etc/ssh/sshd_config\\\":\n\n PermitEmptyPasswords no\n\n The SSH service must be restarted for changes to take effect. Any accounts\nwith empty passwords should be disabled immediately, and PAM configuration\nshould prevent users from being able to assign themselves empty passwords.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000106-GPOS-00053\"\n tag gid: \"V-71939\"\n tag rid: \"SV-86563r3_rule\"\n tag stig_id: \"RHEL-07-010300\"\n tag fix_id: \"F-78291r2_fix\"\n tag cci: [\"CCI-000766\"]\n tag nist: [\"IA-2 (2)\"]\n\n describe sshd_config do\n its('PermitEmptyPasswords') { should eq 'no' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"To determine how the SSH daemon's \"PermitEmptyPasswords\" option is set,\nrun the following command:\n\n # grep -i PermitEmptyPasswords /etc/ssh/sshd_config\n PermitEmptyPasswords no\n\n If no line, a commented line, or a line indicating the value \"no\" is\nreturned, the required value is set.\n\n If the required value is not set, this is a finding.","label":"check"},{"data":"To explicitly disallow remote logon from accounts with empty passwords, add\nor correct the following line in \"/etc/ssh/sshd_config\":\n\n PermitEmptyPasswords no\n\n The SSH service must be restarted for changes to take effect. Any accounts\nwith empty passwords should be disabled immediately, and PAM configuration\nshould prevent users from being able to assign themselves empty passwords.","label":"fix"}],"id":"V-71939","impact":0.7,"refs":[],"results":[{"code_desc":"SSHD Configuration PermitEmptyPasswords is expected to eq \"no\"","message":"\nexpected: \"no\"\n got: nil\n\n(compared using ==)\n","run_time":0.001481741,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71939.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000106-GPOS-00053","gid":"V-71939","rid":"SV-86563r3_rule","stig_id":"RHEL-07-010300","fix_id":"F-78291r2_fix","cci":["CCI-000766"],"nist":["IA-2 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using an empty password.","waiver_data":{}},{"code":"control \"V-71941\" do\n title \"The Red Hat Enterprise Linux operating system must disable account\nidentifiers (individuals, groups, roles, and devices) if the password expires.\"\n desc \"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system disables account identifiers (individuals,\ngroups, roles, and devices) after the password expires with the following\ncommand:\n\n # grep -i inactive /etc/default/useradd\n INACTIVE=0\n\n If the value is not set to \\\"0\\\", is commented out, or is not defined, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable account identifiers (individuals,\ngroups, roles, and devices) after the password expires.\n\n Add the following line to \\\"/etc/default/useradd\\\" (or modify the line to\nhave the required value):\n\n INACTIVE=0\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000118-GPOS-00060\"\n tag gid: \"V-71941\"\n tag rid: \"SV-86565r2_rule\"\n tag stig_id: \"RHEL-07-010310\"\n tag fix_id: \"F-78293r1_fix\"\n tag cci: [\"CCI-000795\"]\n tag nist: [\"IA-4 e\"]\n\n days_of_inactivity = input('days_of_inactivity')\n\n unless command(\"grep 'pam_unix.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'optional'\").stdout.empty? && command(\"grep 'pam_permit.so' /etc/pam.d/system-auth | grep 'auth ' | grep 'required'\").stdout.empty?\n impact 0.0\n describe \"The system is not using password for authentication\" do\n skip \"The system is not using password for authentication, this control is Not Applicable.\"\n end\n else\n describe parse_config_file(\"/etc/default/useradd\") do\n its('INACTIVE') { should cmp >= 0 }\n its('INACTIVE') { should cmp <= days_of_inactivity }\n end\n end\n\nend\n","desc":"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.","descriptions":[{"data":"Inactive identifiers pose a risk to systems and applications because\nattackers may exploit an inactive identifier and potentially obtain undetected\naccess to the system. Owners of inactive accounts will not notice if\nunauthorized access to their user account has been obtained.\n\n Operating systems need to track periods of inactivity and disable\napplication identifiers after zero days of inactivity.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system disables account identifiers (individuals,\ngroups, roles, and devices) after the password expires with the following\ncommand:\n\n # grep -i inactive /etc/default/useradd\n INACTIVE=0\n\n If the value is not set to \"0\", is commented out, or is not defined, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable account identifiers (individuals,\ngroups, roles, and devices) after the password expires.\n\n Add the following line to \"/etc/default/useradd\" (or modify the line to\nhave the required value):\n\n INACTIVE=0","label":"fix"}],"id":"V-71941","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/default/useradd INACTIVE is expected to cmp >= 0","message":"\nexpected it to be >= 0\n got: -1\n\n(compared using `cmp` matcher)\n","run_time":0.000303204,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/default/useradd\"]"},{"code_desc":"Parse Config File /etc/default/useradd INACTIVE is expected to cmp <= 0","run_time":0.000221805,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"parse_config_file","resource_params":"[\"/etc/default/useradd\"]"}],"source_location":{"line":1,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71941.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000118-GPOS-00060","gid":"V-71941","rid":"SV-86565r2_rule","stig_id":"RHEL-07-010310","fix_id":"F-78293r1_fix","cci":["CCI-000795"],"nist":["IA-4 e"]},"title":"The Red Hat Enterprise Linux operating system must disable account\nidentifiers (individuals, groups, roles, and devices) if the password expires.","waiver_data":{}},{"code":"control \"V-71943\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nlock accounts for a minimum of 15 minutes after three unsuccessful logon\nattempts within a 15-minute timeframe.\"\n desc \"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as\nbrute-forcing, is reduced. Limits are imposed by locking the account.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check that the system locks an account for a minimum of 15 minutes after\nthree unsuccessful logon attempts within a period of 15 minutes with the\nfollowing command:\n\n # grep pam_faillock.so /etc/pam.d/password-auth\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \\\"deny\\\" parameter is set to \\\"0\\\" or a value less than \\\"3\\\" on\nboth \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module, or is missing from\nthese lines, this is a finding.\n\n If the \\\"even_deny_root\\\" parameter is not set on both \\\"auth\\\" lines with\nthe \\\"pam_faillock.so\\\" module, or is missing from these lines, this is a\nfinding.\n\n If the \\\"fail_interval\\\" parameter is set to \\\"0\\\" or is set to a value\nless than \\\"900\\\" on both \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module,\nor is missing from these lines, this is a finding.\n\n If the \\\"unlock_time\\\" parameter is not set to \\\"0\\\", \\\"never\\\", or is set\nto a value less than \\\"900\\\" on both \\\"auth\\\" lines with the\n\\\"pam_faillock.so\\\" module, or is missing from these lines, this is a finding.\n\n Note: The maximum configurable value for \\\"unlock_time\\\" is \\\"604800\\\".\n\n If any line referencing the \\\"pam_faillock.so\\\" module is commented out,\nthis is a finding.\n\n # grep pam_faillock.so /etc/pam.d/system-auth\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \\\"deny\\\" parameter is set to \\\"0\\\" or a value less than \\\"3\\\" on\nboth \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module, or is missing from\nthese lines, this is a finding.\n\n If the \\\"even_deny_root\\\" parameter is not set on both \\\"auth\\\" lines with\nthe \\\"pam_faillock.so\\\" module, or is missing from these lines, this is a\nfinding.\n\n If the \\\"fail_interval\\\" parameter is set to \\\"0\\\" or is set to a value\nless than \\\"900\\\" on both \\\"auth\\\" lines with the \\\"pam_faillock.so\\\" module,\nor is missing from these lines, this is a finding.\n\n If the \\\"unlock_time\\\" parameter is not set to \\\"0\\\", \\\"never\\\", or is set\nto a value less than \\\"900\\\" on both \\\"auth\\\" lines with the\n\\\"pam_faillock.so\\\" module or is missing from these lines, this is a finding.\n\n Note: The maximum configurable value for \\\"unlock_time\\\" is \\\"604800\\\".\n If any line referencing the \\\"pam_faillock.so\\\" module is commented out,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to lock an account for the maximum period\nwhen three unsuccessful logon attempts in 15 minutes are made.\n\n Modify the first three lines of the auth section and the first line of the\naccount section of the \\\"/etc/pam.d/system-auth\\\" and\n\\\"/etc/pam.d/password-auth\\\" files to match the following lines:\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth sufficient pam_unix.so try_first_pass\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000329-GPOS-00128\"\n tag satisfies: [\"SRG-OS-000329-GPOS-00128\", \"SRG-OS-000021-GPOS-00005\"]\n tag gid: \"V-71943\"\n tag rid: \"SV-86567r5_rule\"\n tag stig_id: \"RHEL-07-010320\"\n tag fix_id: \"F-78295r5_fix\"\n tag cci: [\"CCI-000044\", \"CCI-002236\", \"CCI-002237\", \"CCI-002238\"]\n tag nist: [\"AC-7 a\", \"AC-7 b\", \"AC-7 b\", \"AC-7 b\"]\n\n describe pam('/etc/pam.d/password-auth') do\n its('lines') {\n should match_pam_rules(input('required_rules')).exactly.or \\\n match_pam_rules(input('alternate_rules')).exactly\n }\n its('lines') { should match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('deny', '<=', input('unsuccessful_attempts')) }\n its('lines') { should match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('fail_interval', '<=', input('fail_interval')) }\n its('lines') {\n should match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_args('unlock_time=(0|never)').or \\\n (match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('unlock_time', '<=', 604800).and \\\n match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('unlock_time', '>=', input('lockout_time')))\n }\n end\n\n describe pam('/etc/pam.d/system-auth') do\n its('lines') {\n should match_pam_rules(input('required_rules')).exactly.or \\\n match_pam_rules(input('alternate_rules')).exactly\n }\n its('lines') { should match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('deny', '<=', input('unsuccessful_attempts')) }\n its('lines') { should match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('fail_interval', '<=', input('fail_interval')) }\n its('lines') {\n should match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_args('unlock_time=(0|never)').or \\\n (match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('unlock_time', '<=', 604800).and \\\n match_pam_rule('auth [default=die]|required pam_faillock.so').all_with_integer_arg('unlock_time', '>=', input('lockout_time')))\n }\n end\nend\n","desc":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as\nbrute-forcing, is reduced. Limits are imposed by locking the account.","descriptions":[{"data":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as\nbrute-forcing, is reduced. Limits are imposed by locking the account.","label":"default"},{"data":"","label":"rationale"},{"data":"Check that the system locks an account for a minimum of 60 minutes after\n20 unsuccessful logon attempts within a period of 120 minutes with the\nfollowing command:\n\t\t# grep pam_faillock.so /etc/pam.d/password-auth\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tIf the \"deny\" parameter is set to \"0\" or a value less than \"20\" on\nboth \"auth\" lines with the \"pam_faillock.so\" module, or is missing from\nthese lines, this is a finding.\n\t\tIf the \"even_deny_root\" parameter is not set on both \"auth\" lines with\nthe \"pam_faillock.so\" module, or is missing from these lines, this is a\nfinding.\n\t\tIf the \"fail_interval\" parameter is set to \"0\" or is set to a value\nless than \"7200\" on both \"auth\" lines with the \"pam_faillock.so\" module,\nor is missing from these lines, this is a finding.\n\t\tIf the \"unlock_time\" parameter is not set to \"0\", \"never\", or is set\nto a value less than \"3600\" on both \"auth\" lines with the\n\"pam_faillock.so\" module, or is missing from these lines, this is a finding.\n\t\tNote: The maximum configurable value for \"unlock_time\" is \"604800\".\n\t\tIf any line referencing the \"pam_faillock.so\" module is commented out,\nthis is a finding.\n\t\t# grep pam_faillock.so /etc/pam.d/system-auth\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tIf the \"deny\" parameter is set to \"0\" or a value less than \"20\" on\nboth \"auth\" lines with the \"pam_faillock.so\" module, or is missing from\nthese lines, this is a finding.\n\t\tIf the \"even_deny_root\" parameter is not set on both \"auth\" lines with\nthe \"pam_faillock.so\" module, or is missing from these lines, this is a\nfinding.\n\t\tIf the \"fail_interval\" parameter is set to \"0\" or is set to a value\nless than \"7200\" on both \"auth\" lines with the \"pam_faillock.so\" module,\nor is missing from these lines, this is a finding.\n\t\tIf the \"unlock_time\" parameter is not set to \"0\", \"never\", or is set\nto a value less than \"3600\" on both \"auth\" lines with the\n\"pam_faillock.so\" module or is missing from these lines, this is a finding.\n\t\tNote: The maximum configurable value for \"unlock_time\" is \"604800\".\n\t\tIf any line referencing the \"pam_faillock.so\" module is commented out,\nthis is a finding.","label":"check"},{"data":"Configure the ACME operating system to lock an account for 60 minutes\nwhen 20 unsuccessful logon attempts in 120 minutes are made.\n\t\tModify the first three lines of the auth section and the first line of the\naccount section of the \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" files to match the following lines:\n\t\tauth required pam_faillock.so preauth silent audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\tauth sufficient pam_unix.so try_first_pass\n\t\tauth [default=die] pam_faillock.so authfail audit deny=20 even_deny_root\nfail_interval=7200 unlock_time=3600\n\t\taccount required pam_faillock.so\n\t\tNote: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"},{"data":"The project2 needs to set this to 20 since we have an approved risk-based decision on 2/1/2022 allowing it","label":"caveat"}],"id":"V-71943","impact":0.5,"refs":[{"ref":[]},{"ref":[]}],"results":[{"code_desc":"PAM Config[/etc/pam.d/password-auth] lines is expected to include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly or include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_sss.so forward_pass\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly","message":" expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...ss=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\\nsession required pam_unix.so\" to include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly\n\n...or:\n\n expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...ss=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\\nsession required pam_unix.so\" to include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_sss.so forward_pass\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly\nDiff for (include [\"auth required pam_faillock.so unlock_time=.*\", \"auth...):\n@@ -1,4 +1,18 @@\n-[\"auth required pam_faillock.so unlock_time=.*\",\n- \"auth sufficient pam_unix.so try_first_pass\",\n- \"auth [default=die] pam_faillock.so unlock_time=.*\"]\n+[#<#::Pam::Rule:0x000000000877ae40 @to_s=\"auth required pam_env.so\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_env.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000877aa08 @to_s=\"auth required pam_faildelay.so delay=2000000\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_faildelay.so\", @module_arguments=[\"delay=2000000\"]>,\n+ #<#::Pam::Rule:0x000000000877a580 @to_s=\"auth sufficient pam_unix.so nullok try_first_pass\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"nullok\", \"try_first_pass\"]>,\n+ #<#::Pam::Rule:0x000000000877a030 @to_s=\"auth requisite pam_succeed_if.so uid >= 1000 quiet_success\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"requisite\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \">=\", \"1000\", \"quiet_success\"]>,\n+ #<#::Pam::Rule:0x0000000008779a40 @to_s=\"auth required pam_deny.so\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008779658 @to_s=\"account required pam_unix.so\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008779270 @to_s=\"account sufficient pam_localuser.so\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_localuser.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008778e38 @to_s=\"account sufficient pam_succeed_if.so uid < 1000 quiet\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \"<\", \"1000\", \"quiet\"]>,\n+ #<#::Pam::Rule:0x00000000087788c0 @to_s=\"account required pam_permit.so\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_permit.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x00000000087784d8 @to_s=\"password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\", @service=\"password-auth\", @silent=false, @type=\"password\", @control=\"requisite\", @module_path=\"pam_pwquality.so\", @module_arguments=[\"try_first_pass\", \"local_users_only\", \"retry=3\", \"authtok_type=\"]>,\n+ #<#::Pam::Rule:0x000000000876be68 @to_s=\"password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\", @service=\"password-auth\", @silent=false, @type=\"password\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"md5\", \"shadow\", \"nullok\", \"try_first_pass\", \"use_authtok\"]>,\n+ #<#::Pam::Rule:0x000000000876b850 @to_s=\"password required pam_deny.so\", @service=\"password-auth\", @silent=false, @type=\"password\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000876b490 @to_s=\"session optional pam_keyinit.so revoke\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"optional\", @module_path=\"pam_keyinit.so\", @module_arguments=[\"revoke\"]>,\n+ #<#::Pam::Rule:0x000000000876afe0 @to_s=\"session required pam_limits.so\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_limits.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000876abf8 @to_s=\"-session optional pam_systemd.so\", @service=\"password-auth\", @silent=true, @type=\"session\", @control=\"optional\", @module_path=\"pam_systemd.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000876a798 @to_s=\"session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"[success=1 default=ignore]\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"service\", \"in\", \"crond\", \"quiet\", \"use_uid\"]>,\n+ #<#::Pam::Rule:0x000000000876a1d0 @to_s=\"session required pam_unix.so\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>]\n\nDiff for (include [\"auth required pam_faillock.so unlock_time=.*\", \"auth...):\n@@ -1,5 +1,18 @@\n-[\"auth required pam_faillock.so unlock_time=.*\",\n- \"auth sufficient pam_sss.so forward_pass\",\n- \"auth sufficient pam_unix.so try_first_pass\",\n- \"auth [default=die] pam_faillock.so unlock_time=.*\"]\n+[#<#::Pam::Rule:0x000000000877ae40 @to_s=\"auth required pam_env.so\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_env.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000877aa08 @to_s=\"auth required pam_faildelay.so delay=2000000\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_faildelay.so\", @module_arguments=[\"delay=2000000\"]>,\n+ #<#::Pam::Rule:0x000000000877a580 @to_s=\"auth sufficient pam_unix.so nullok try_first_pass\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"nullok\", \"try_first_pass\"]>,\n+ #<#::Pam::Rule:0x000000000877a030 @to_s=\"auth requisite pam_succeed_if.so uid >= 1000 quiet_success\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"requisite\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \">=\", \"1000\", \"quiet_success\"]>,\n+ #<#::Pam::Rule:0x0000000008779a40 @to_s=\"auth required pam_deny.so\", @service=\"password-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008779658 @to_s=\"account required pam_unix.so\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008779270 @to_s=\"account sufficient pam_localuser.so\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_localuser.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008778e38 @to_s=\"account sufficient pam_succeed_if.so uid < 1000 quiet\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \"<\", \"1000\", \"quiet\"]>,\n+ #<#::Pam::Rule:0x00000000087788c0 @to_s=\"account required pam_permit.so\", @service=\"password-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_permit.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x00000000087784d8 @to_s=\"password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\", @service=\"password-auth\", @silent=false, @type=\"password\", @control=\"requisite\", @module_path=\"pam_pwquality.so\", @module_arguments=[\"try_first_pass\", \"local_users_only\", \"retry=3\", \"authtok_type=\"]>,\n+ #<#::Pam::Rule:0x000000000876be68 @to_s=\"password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\", @service=\"password-auth\", @silent=false, @type=\"password\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"md5\", \"shadow\", \"nullok\", \"try_first_pass\", \"use_authtok\"]>,\n+ #<#::Pam::Rule:0x000000000876b850 @to_s=\"password required pam_deny.so\", @service=\"password-auth\", @silent=false, @type=\"password\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000876b490 @to_s=\"session optional pam_keyinit.so revoke\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"optional\", @module_path=\"pam_keyinit.so\", @module_arguments=[\"revoke\"]>,\n+ #<#::Pam::Rule:0x000000000876afe0 @to_s=\"session required pam_limits.so\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_limits.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000876abf8 @to_s=\"-session optional pam_systemd.so\", @service=\"password-auth\", @silent=true, @type=\"session\", @control=\"optional\", @module_path=\"pam_systemd.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000876a798 @to_s=\"session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"[success=1 default=ignore]\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"service\", \"in\", \"crond\", \"quiet\", \"use_uid\"]>,\n+ #<#::Pam::Rule:0x000000000876a1d0 @to_s=\"session required pam_unix.so\", @service=\"password-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>]\n","run_time":0.019496799,"start_time":"2022-03-06T22:05:48+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/password-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/password-auth] lines is expected to include auth [default=die]|required pam_faillock.so, all with arg deny <= 20","run_time":0.003031359,"start_time":"2022-03-06T22:05:48+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/password-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/password-auth] lines is expected to include auth [default=die]|required pam_faillock.so, all with arg fail_interval <= 900","run_time":0.00119378,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/password-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/password-auth] lines is expected to include auth [default=die]|required pam_faillock.so, all with args unlock_time=(0|never) or include auth [default=die]|required pam_faillock.so, all with arg unlock_time <= 604800 and include auth [default=die]|required pam_faillock.so, all with arg unlock_time >= 604800","run_time":0.001523815,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/password-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly or include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_sss.so forward_pass\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly","message":" expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...ss=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\\nsession required pam_unix.so\" to include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly\n\n...or:\n\n expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...ss=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\\nsession required pam_unix.so\" to include [\"auth required pam_faillock.so unlock_time=.*\", \"auth sufficient pam_sss.so forward_pass\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so unlock_time=.*\"] exactly\nDiff for (include [\"auth required pam_faillock.so unlock_time=.*\", \"auth...):\n@@ -1,4 +1,18 @@\n-[\"auth required pam_faillock.so unlock_time=.*\",\n- \"auth sufficient pam_unix.so try_first_pass\",\n- \"auth [default=die] pam_faillock.so unlock_time=.*\"]\n+[#<#::Pam::Rule:0x0000000008768240 @to_s=\"auth required pam_env.so\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_env.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008763dd0 @to_s=\"auth required pam_faildelay.so delay=2000000\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_faildelay.so\", @module_arguments=[\"delay=2000000\"]>,\n+ #<#::Pam::Rule:0x0000000008763948 @to_s=\"auth sufficient pam_unix.so nullok try_first_pass\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"nullok\", \"try_first_pass\"]>,\n+ #<#::Pam::Rule:0x0000000008763448 @to_s=\"auth requisite pam_succeed_if.so uid >= 1000 quiet_success\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"requisite\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \">=\", \"1000\", \"quiet_success\"]>,\n+ #<#::Pam::Rule:0x0000000008762e08 @to_s=\"auth required pam_deny.so\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008762a20 @to_s=\"account required pam_unix.so\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008762638 @to_s=\"account sufficient pam_localuser.so\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_localuser.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008762250 @to_s=\"account sufficient pam_succeed_if.so uid < 1000 quiet\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \"<\", \"1000\", \"quiet\"]>,\n+ #<#::Pam::Rule:0x0000000008761cd8 @to_s=\"account required pam_permit.so\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_permit.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x00000000087618a0 @to_s=\"password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\", @service=\"system-auth\", @silent=false, @type=\"password\", @control=\"requisite\", @module_path=\"pam_pwquality.so\", @module_arguments=[\"try_first_pass\", \"local_users_only\", \"retry=3\", \"authtok_type=\"]>,\n+ #<#::Pam::Rule:0x00000000087612d8 @to_s=\"password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\", @service=\"system-auth\", @silent=false, @type=\"password\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"md5\", \"shadow\", \"nullok\", \"try_first_pass\", \"use_authtok\"]>,\n+ #<#::Pam::Rule:0x0000000008760d10 @to_s=\"password required pam_deny.so\", @service=\"system-auth\", @silent=false, @type=\"password\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008760950 @to_s=\"session optional pam_keyinit.so revoke\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"optional\", @module_path=\"pam_keyinit.so\", @module_arguments=[\"revoke\"]>,\n+ #<#::Pam::Rule:0x0000000008760400 @to_s=\"session required pam_limits.so\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_limits.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008760018 @to_s=\"-session optional pam_systemd.so\", @service=\"system-auth\", @silent=true, @type=\"session\", @control=\"optional\", @module_path=\"pam_systemd.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000875bba8 @to_s=\"session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"[success=1 default=ignore]\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"service\", \"in\", \"crond\", \"quiet\", \"use_uid\"]>,\n+ #<#::Pam::Rule:0x000000000875b590 @to_s=\"session required pam_unix.so\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>]\n\nDiff for (include [\"auth required pam_faillock.so unlock_time=.*\", \"auth...):\n@@ -1,5 +1,18 @@\n-[\"auth required pam_faillock.so unlock_time=.*\",\n- \"auth sufficient pam_sss.so forward_pass\",\n- \"auth sufficient pam_unix.so try_first_pass\",\n- \"auth [default=die] pam_faillock.so unlock_time=.*\"]\n+[#<#::Pam::Rule:0x0000000008768240 @to_s=\"auth required pam_env.so\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_env.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008763dd0 @to_s=\"auth required pam_faildelay.so delay=2000000\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_faildelay.so\", @module_arguments=[\"delay=2000000\"]>,\n+ #<#::Pam::Rule:0x0000000008763948 @to_s=\"auth sufficient pam_unix.so nullok try_first_pass\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"nullok\", \"try_first_pass\"]>,\n+ #<#::Pam::Rule:0x0000000008763448 @to_s=\"auth requisite pam_succeed_if.so uid >= 1000 quiet_success\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"requisite\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \">=\", \"1000\", \"quiet_success\"]>,\n+ #<#::Pam::Rule:0x0000000008762e08 @to_s=\"auth required pam_deny.so\", @service=\"system-auth\", @silent=false, @type=\"auth\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008762a20 @to_s=\"account required pam_unix.so\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008762638 @to_s=\"account sufficient pam_localuser.so\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_localuser.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008762250 @to_s=\"account sufficient pam_succeed_if.so uid < 1000 quiet\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"sufficient\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"uid\", \"<\", \"1000\", \"quiet\"]>,\n+ #<#::Pam::Rule:0x0000000008761cd8 @to_s=\"account required pam_permit.so\", @service=\"system-auth\", @silent=false, @type=\"account\", @control=\"required\", @module_path=\"pam_permit.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x00000000087618a0 @to_s=\"password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\", @service=\"system-auth\", @silent=false, @type=\"password\", @control=\"requisite\", @module_path=\"pam_pwquality.so\", @module_arguments=[\"try_first_pass\", \"local_users_only\", \"retry=3\", \"authtok_type=\"]>,\n+ #<#::Pam::Rule:0x00000000087612d8 @to_s=\"password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\", @service=\"system-auth\", @silent=false, @type=\"password\", @control=\"sufficient\", @module_path=\"pam_unix.so\", @module_arguments=[\"md5\", \"shadow\", \"nullok\", \"try_first_pass\", \"use_authtok\"]>,\n+ #<#::Pam::Rule:0x0000000008760d10 @to_s=\"password required pam_deny.so\", @service=\"system-auth\", @silent=false, @type=\"password\", @control=\"required\", @module_path=\"pam_deny.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008760950 @to_s=\"session optional pam_keyinit.so revoke\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"optional\", @module_path=\"pam_keyinit.so\", @module_arguments=[\"revoke\"]>,\n+ #<#::Pam::Rule:0x0000000008760400 @to_s=\"session required pam_limits.so\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_limits.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x0000000008760018 @to_s=\"-session optional pam_systemd.so\", @service=\"system-auth\", @silent=true, @type=\"session\", @control=\"optional\", @module_path=\"pam_systemd.so\", @module_arguments=[]>,\n+ #<#::Pam::Rule:0x000000000875bba8 @to_s=\"session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"[success=1 default=ignore]\", @module_path=\"pam_succeed_if.so\", @module_arguments=[\"service\", \"in\", \"crond\", \"quiet\", \"use_uid\"]>,\n+ #<#::Pam::Rule:0x000000000875b590 @to_s=\"session required pam_unix.so\", @service=\"system-auth\", @silent=false, @type=\"session\", @control=\"required\", @module_path=\"pam_unix.so\", @module_arguments=[]>]\n","run_time":0.013561729,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include auth [default=die]|required pam_faillock.so, all with arg deny <= 20","run_time":0.001117503,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include auth [default=die]|required pam_faillock.so, all with arg fail_interval <= 900","run_time":0.000968592,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include auth [default=die]|required pam_faillock.so, all with args unlock_time=(0|never) or include auth [default=die]|required pam_faillock.so, all with arg unlock_time <= 604800 and include auth [default=die]|required pam_faillock.so, all with arg unlock_time >= 604800","run_time":0.002110677,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71943.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000329-GPOS-00128","satisfies":["SRG-OS-000329-GPOS-00128","SRG-OS-000021-GPOS-00005"],"gid":"V-71943","rid":"SV-86567r5_rule","stig_id":"RHEL-07-010320","fix_id":"F-78295r5_fix","cci":["CCI-000044","CCI-002236","CCI-002237","CCI-002238"],"nist":["AC-7 a","AC-7 b","AC-7 b","AC-7 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 60 minutes after 20 unsuccessful logon attempts within a 120-minute timeframe.","waiver_data":{}},{"code":"control \"V-71945\" do\n title \"The Red Hat Enterprise Linux operating system must lock the associated\naccount after three unsuccessful root logon attempts are made within a\n15-minute period.\"\n desc \"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system automatically locks the root account until it\nis released by an administrator when three unsuccessful logon attempts in 15\nminutes are made.\n\n # grep pam_faillock.so /etc/pam.d/password-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \\\"even_deny_root\\\" setting is not defined on both lines with the\n\\\"pam_faillock.so\\\" module, is commented out, or is missing from a line, this\nis a finding.\n\n # grep pam_faillock.so /etc/pam.d/system-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \\\"even_deny_root\\\" setting is not defined on both lines with the\n\\\"pam_faillock.so\\\" module, is commented out, or is missing from a line, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to lock automatically the root account until\nthe locked account is released by an administrator when three unsuccessful\nlogon attempts in 15 minutes are made.\n\n Modify the first three lines of the auth section and the first line of the\naccount section of the \\\"/etc/pam.d/system-auth\\\" and\n\\\"/etc/pam.d/password-auth\\\" files to match the following lines:\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth sufficient pam_unix.so try_first_pass\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n Note: Manual changes to the listed files may be overwritten by the\n\\\"authconfig\\\" program. The \\\"authconfig\\\" program should not be used to update\nthe configurations listed in this requirement.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000329-GPOS-00128\"\n tag satisfies: [\"SRG-OS-000329-GPOS-00128\", \"SRG-OS-000021-GPOS-00005\"]\n tag gid: \"V-71945\"\n tag rid: \"SV-86569r4_rule\"\n tag stig_id: \"RHEL-07-010330\"\n tag fix_id: \"F-78297r3_fix\"\n tag cci: [\"CCI-002238\"]\n tag nist: [\"AC-7 b\"]\n\n required_lines = [\n 'auth required pam_faillock.so even_deny_root',\n 'auth sufficient pam_unix.so try_first_pass',\n 'auth [default=die] pam_faillock.so even_deny_root'\n ]\n\n describe pam('/etc/pam.d/password-auth') do\n its('lines') { should match_pam_rules(required_lines) }\n its('lines') { should match_pam_rule('auth .* pam_faillock.so (preauth|authfail)').all_with_args('even_deny_root') }\n end\n\n describe pam('/etc/pam.d/system-auth') do\n its('lines') { should match_pam_rules(required_lines) }\n its('lines') { should match_pam_rule('auth .* pam_faillock.so (preauth|authfail)').all_with_args('even_deny_root') }\n end\nend\n","desc":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.","descriptions":[{"data":"By limiting the number of failed logon attempts, the risk of\nunauthorized system access via user password guessing, otherwise known as brute\nforcing, is reduced. Limits are imposed by locking the account.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically locks the root account until it\nis released by an administrator when three unsuccessful logon attempts in 15\nminutes are made.\n\n # grep pam_faillock.so /etc/pam.d/password-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \"even_deny_root\" setting is not defined on both lines with the\n\"pam_faillock.so\" module, is commented out, or is missing from a line, this\nis a finding.\n\n # grep pam_faillock.so /etc/pam.d/system-auth\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n If the \"even_deny_root\" setting is not defined on both lines with the\n\"pam_faillock.so\" module, is commented out, or is missing from a line, this\nis a finding.","label":"check"},{"data":"Configure the operating system to lock automatically the root account until\nthe locked account is released by an administrator when three unsuccessful\nlogon attempts in 15 minutes are made.\n\n Modify the first three lines of the auth section and the first line of the\naccount section of the \"/etc/pam.d/system-auth\" and\n\"/etc/pam.d/password-auth\" files to match the following lines:\n\n auth required pam_faillock.so preauth silent audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n auth sufficient pam_unix.so try_first_pass\n auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root\nfail_interval=900 unlock_time=900\n account required pam_faillock.so\n\n Note: Manual changes to the listed files may be overwritten by the\n\"authconfig\" program. The \"authconfig\" program should not be used to update\nthe configurations listed in this requirement.","label":"fix"}],"id":"V-71945","impact":0.5,"refs":[],"results":[{"code_desc":"PAM Config[/etc/pam.d/password-auth] lines is expected to include [\"auth required pam_faillock.so even_deny_root\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so even_deny_root\"]","message":"expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...ss=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\\nsession required pam_unix.so\" to include [\"auth required pam_faillock.so even_deny_root\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so even_deny_root\"]\nDiff:\n@@ -1,4 +1,18 @@\n-auth required pam_faillock.so even_deny_root\n-auth sufficient pam_unix.so try_first_pass\n-auth [default=die] pam_faillock.so even_deny_root\n+account required pam_unix.so\n+account sufficient pam_localuser.so\n+account sufficient pam_succeed_if.so uid < 1000 quiet\n+account required pam_permit.so\n+auth required pam_env.so\n+auth required pam_faildelay.so delay=2000000\n+auth sufficient pam_unix.so nullok try_first_pass\n+auth requisite pam_succeed_if.so uid >= 1000 quiet_success\n+auth required pam_deny.so\n+password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+password required pam_deny.so\n+session optional pam_keyinit.so revoke\n+session required pam_limits.so\n+-session optional pam_systemd.so\n+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\n+session required pam_unix.so\n","run_time":0.026210061,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/password-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/password-auth] lines is expected to include auth .* pam_faillock.so (preauth|authfail), all with args even_deny_root","run_time":0.000833779,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/password-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include [\"auth required pam_faillock.so even_deny_root\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so even_deny_root\"]","message":"expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...ss=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\\nsession required pam_unix.so\" to include [\"auth required pam_faillock.so even_deny_root\", \"auth sufficient pam_unix.so try_first_pass\", \"auth [default=die] pam_faillock.so even_deny_root\"]\nDiff:\n@@ -1,4 +1,18 @@\n-auth required pam_faillock.so even_deny_root\n-auth sufficient pam_unix.so try_first_pass\n-auth [default=die] pam_faillock.so even_deny_root\n+account required pam_unix.so\n+account sufficient pam_localuser.so\n+account sufficient pam_succeed_if.so uid < 1000 quiet\n+account required pam_permit.so\n+auth required pam_env.so\n+auth required pam_faildelay.so delay=2000000\n+auth sufficient pam_unix.so nullok try_first_pass\n+auth requisite pam_succeed_if.so uid >= 1000 quiet_success\n+auth required pam_deny.so\n+password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+password required pam_deny.so\n+session optional pam_keyinit.so revoke\n+session required pam_limits.so\n+-session optional pam_systemd.so\n+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\n+session required pam_unix.so\n","run_time":0.002067939,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"},{"code_desc":"PAM Config[/etc/pam.d/system-auth] lines is expected to include auth .* pam_faillock.so (preauth|authfail), all with args even_deny_root","run_time":0.00132759,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/system-auth\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71945.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000329-GPOS-00128","satisfies":["SRG-OS-000329-GPOS-00128","SRG-OS-000021-GPOS-00005"],"gid":"V-71945","rid":"SV-86569r4_rule","stig_id":"RHEL-07-010330","fix_id":"F-78297r3_fix","cci":["CCI-002238"],"nist":["AC-7 b"]},"title":"The Red Hat Enterprise Linux operating system must lock the associated\naccount after three unsuccessful root logon attempts are made within a\n15-minute period.","waiver_data":{}},{"code":"control \"V-71947\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat users must provide a password for privilege escalation.\"\n desc \"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system requires users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" and \\\"/etc/sudoers.d/*\\\"\nfiles with the following command:\n\n # grep -i nopasswd /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \\\"NOPASSWD\\\" tag, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" file with the following\ncommand:\n # visudo\n\n Remove any occurrences of \\\"NOPASSWD\\\" tags in the file.\n\n Check the configuration of the /etc/sudoers.d/* files with the following\ncommand:\n # grep -i nopasswd /etc/sudoers.d/*\n\n Remove any occurrences of \\\"NOPASSWD\\\" tags in the file.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000373-GPOS-00156\"\n tag satisfies: [\"SRG-OS-000373-GPOS-00156\", \"SRG-OS-000373-GPOS-00157\",\n\"SRG-OS-000373-GPOS-00158\"]\n tag gid: \"V-71947\"\n tag rid: \"SV-86571r3_rule\"\n tag stig_id: \"RHEL-07-010340\"\n tag fix_id: \"F-78299r2_fix\"\n tag cci: [\"CCI-002038\"]\n tag nist: [\"IA-11\"]\n\n processed = []\n to_process = ['/etc/sudoers', '/etc/sudoers.d']\n\n while !to_process.empty?\n in_process = to_process.pop\n next if processed.include? in_process\n processed.push in_process\n\n if file(in_process).directory?\n to_process.concat(\n command(\"find #{in_process} -maxdepth 1 -mindepth 1\").\n stdout.strip.split(\"\\n\").\n select { |f| file(f).file? }\n )\n elsif file(in_process).file?\n to_process.concat(\n command(\"grep -E '#include\\\\s+' #{in_process} | sed 's/.*#include[[:space:]]*//g'\").\n stdout.strip.split(\"\\n\").\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n select { |f| file(f).exist? }\n )\n to_process.concat(\n command(\"grep -E '#includedir\\\\s+' #{in_process} | sed 's/.*#includedir[[:space:]]*//g'\").\n stdout.strip.split(\"\\n\").\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n select { |f| file(f).exist? }\n )\n end\n end\n\n sudoers = processed.select { |f| file(f).file? }\n\n sudoers.each do |sudoer|\n sudo_content = file(sudoer).content.strip.split(\"\\n\")\n nopasswd_lines = sudo_content.select { |l| l.match?(/^[^#].*NOPASSWD/) }\n describe \"#{sudoer} rules containing NOPASSWD\" do\n subject { nopasswd_lines }\n it { should be_empty }\n end\n end\nend\n","desc":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.","descriptions":[{"data":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user re-authenticate.","label":"default"},{"data":"","label":"rationale"},{"data":"If passwords are not being used for authentication, this is Not Applicable.\n\n Verify the operating system requires users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" and \"/etc/sudoers.d/*\"\nfiles with the following command:\n\n # grep -i nopasswd /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \"NOPASSWD\" tag, this is a finding.","label":"check"},{"data":"Configure the operating system to require users to supply a password for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" file with the following\ncommand:\n # visudo\n\n Remove any occurrences of \"NOPASSWD\" tags in the file.\n\n Check the configuration of the /etc/sudoers.d/* files with the following\ncommand:\n # grep -i nopasswd /etc/sudoers.d/*\n\n Remove any occurrences of \"NOPASSWD\" tags in the file.","label":"fix"}],"id":"V-71947","impact":0.5,"refs":[],"results":[{"code_desc":"/etc/sudoers.d/proxy rules containing NOPASSWD is expected to be empty","run_time":0.03596127,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"/etc/sudoers.d/vagrant rules containing NOPASSWD is expected to be empty","message":"expected `[\"%vagrant ALL=(ALL) NOPASSWD: ALL\"].empty?` to be truthy, got false","run_time":0.009196975,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"/etc/sudoers rules containing NOPASSWD is expected to be empty","run_time":0.009149513,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71947.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000373-GPOS-00156","satisfies":["SRG-OS-000373-GPOS-00156","SRG-OS-000373-GPOS-00157","SRG-OS-000373-GPOS-00158"],"gid":"V-71947","rid":"SV-86571r3_rule","stig_id":"RHEL-07-010340","fix_id":"F-78299r2_fix","cci":["CCI-002038"],"nist":["IA-11"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat users must provide a password for privilege escalation.","waiver_data":{}},{"code":"control \"V-71949\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat users must re-authenticate for privilege escalation.\"\n desc \"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system requires users to reauthenticate for privilege\nescalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" and \\\"/etc/sudoers.d/*\\\"\nfiles with the following command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \\\"!authenticate\\\" tag, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to require users to reauthenticate for\nprivilege escalation.\n\n Check the configuration of the \\\"/etc/sudoers\\\" file with the following\ncommand:\n\n # visudo\n Remove any occurrences of \\\"!authenticate\\\" tags in the file.\n\n Check the configuration of the \\\"/etc/sudoers.d/*\\\" files with the\nfollowing command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n Remove any occurrences of \\\"!authenticate\\\" tags in the file(s).\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000373-GPOS-00156\"\n tag satisfies: [\"SRG-OS-000373-GPOS-00156\", \"SRG-OS-000373-GPOS-00157\",\n\"SRG-OS-000373-GPOS-00158\"]\n tag gid: \"V-71949\"\n tag rid: \"SV-86573r3_rule\"\n tag stig_id: \"RHEL-07-010350\"\n tag fix_id: \"F-78301r3_fix\"\n tag cci: [\"CCI-002038\"]\n tag nist: [\"IA-11\"]\n\n describe command(\"grep -ir authenticate /etc/sudoers /etc/sudoers.d/*\") do\n its('stdout') { should_not match %r{!authenticate} }\n end\nend\n","desc":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.","descriptions":[{"data":"Without re-authentication, users may access resources or perform tasks\nfor which they do not have authorization.\n\n When operating systems provide the capability to escalate a functional\ncapability, it is critical the user reauthenticate.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system requires users to reauthenticate for privilege\nescalation.\n\n Check the configuration of the \"/etc/sudoers\" and \"/etc/sudoers.d/*\"\nfiles with the following command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n\n If any uncommented line is found with a \"!authenticate\" tag, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to require users to reauthenticate for\nprivilege escalation.\n\n Check the configuration of the \"/etc/sudoers\" file with the following\ncommand:\n\n # visudo\n Remove any occurrences of \"!authenticate\" tags in the file.\n\n Check the configuration of the \"/etc/sudoers.d/*\" files with the\nfollowing command:\n\n # grep -i authenticate /etc/sudoers /etc/sudoers.d/*\n Remove any occurrences of \"!authenticate\" tags in the file(s).","label":"fix"}],"id":"V-71949","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `grep -ir authenticate /etc/sudoers /etc/sudoers.d/*` stdout is expected not to match /!authenticate/","run_time":0.018636813,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"command","resource_params":"[\"grep -ir authenticate /etc/sudoers /etc/sudoers.d/*\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71949.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000373-GPOS-00156","satisfies":["SRG-OS-000373-GPOS-00156","SRG-OS-000373-GPOS-00157","SRG-OS-000373-GPOS-00158"],"gid":"V-71949","rid":"SV-86573r3_rule","stig_id":"RHEL-07-010350","fix_id":"F-78301r3_fix","cci":["CCI-002038"],"nist":["IA-11"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat users must re-authenticate for privilege escalation.","waiver_data":{}},{"code":"control \"V-71951\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the delay between logon prompts following a failed console logon attempt\nis at least four seconds.\"\n desc \"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enforces a delay of at least four seconds\nbetween console logon prompts following a failed logon attempt.\n\n Check the value of the \\\"fail_delay\\\" parameter in the \\\"/etc/login.defs\\\"\nfile with the following command:\n\n # grep -i fail_delay /etc/login.defs\n FAIL_DELAY 4\n\n If the value of \\\"FAIL_DELAY\\\" is not set to \\\"4\\\" or greater, or the line\nis commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to enforce a delay of at least four seconds\nbetween logon prompts following a failed console logon attempt.\n\n Modify the \\\"/etc/login.defs\\\" file to set the \\\"FAIL_DELAY\\\" parameter to\n\\\"4\\\" or greater:\n\n FAIL_DELAY 4\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00226\"\n tag gid: \"V-71951\"\n tag rid: \"SV-86575r2_rule\"\n tag stig_id: \"RHEL-07-010430\"\n tag fix_id: \"F-78303r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe login_defs do\n its('FAIL_DELAY.to_i') { should cmp >= 4 }\n end\nend\n","desc":"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.","descriptions":[{"data":"Configuring the operating system to implement organization-wide\nsecurity implementation guides and security checklists verifies compliance with\nfederal standards and establishes a common security baseline across DoD that\nreflects the most restrictive security posture consistent with operational\nrequirements.\n\n Configuration settings are the set of parameters that can be changed in\nhardware, software, or firmware components of the system that affect the\nsecurity posture and/or functionality of the system. Security-related\nparameters are those parameters impacting the security state of the system,\nincluding the parameters required to satisfy other security control\nrequirements. Security-related parameters include, for example, registry\nsettings; account, file, and directory permission settings; and settings for\nfunctions, ports, protocols, services, and remote connections.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enforces a delay of at least four seconds\nbetween console logon prompts following a failed logon attempt.\n\n Check the value of the \"fail_delay\" parameter in the \"/etc/login.defs\"\nfile with the following command:\n\n # grep -i fail_delay /etc/login.defs\n FAIL_DELAY 4\n\n If the value of \"FAIL_DELAY\" is not set to \"4\" or greater, or the line\nis commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to enforce a delay of at least four seconds\nbetween logon prompts following a failed console logon attempt.\n\n Modify the \"/etc/login.defs\" file to set the \"FAIL_DELAY\" parameter to\n\"4\" or greater:\n\n FAIL_DELAY 4","label":"fix"}],"id":"V-71951","impact":0.5,"refs":[],"results":[{"code_desc":"login.defs FAIL_DELAY.to_i is expected to cmp >= 4","message":"\nexpected it to be >= 4\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000704013,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"login_defs","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71951.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00226","gid":"V-71951","rid":"SV-86575r2_rule","stig_id":"RHEL-07-010430","fix_id":"F-78303r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the delay between logon prompts following a failed console logon attempt\nis at least four seconds.","waiver_data":{}},{"code":"control \"V-71953\" do\n title \"The Red Hat Enterprise Linux operating system must not allow an\nunattended or automatic logon to the system via a graphical user interface.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow an unattended or automatic logon\nto the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \\\"AutomaticLoginEnable\\\" in the\n\\\"/etc/gdm/custom.conf\\\" file with the following command:\n\n # grep -i automaticloginenable /etc/gdm/custom.conf\n AutomaticLoginEnable=false\n\n If the value of \\\"AutomaticLoginEnable\\\" is not set to \\\"false\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow an unattended or automatic\nlogon to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \\\"AutomaticLoginEnable\\\" parameter in the\n[daemon] section of the \\\"/etc/gdm/custom.conf\\\" file to \\\"false\\\":\n\n [daemon]\n AutomaticLoginEnable=false\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71953\"\n tag rid: \"SV-86577r2_rule\"\n tag stig_id: \"RHEL-07-010440\"\n tag fix_id: \"F-78305r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n custom_conf = '/etc/gdm/custom.conf'\n\n if package('gdm').installed?\n if ((f = file(custom_conf)).exist?)\n describe ini(custom_conf) do\n its('daemon.AutomaticLoginEnable') { cmp false }\n end\n else\n describe f do\n it { should exist }\n end\n end\n else\n impact 0.0\n describe \"The system does not have GDM installed\" do\n skip \"The system does not have GDM installed, this requirement is Not Applicable.\"\n end\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow an unattended or automatic logon\nto the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \"AutomaticLoginEnable\" in the\n\"/etc/gdm/custom.conf\" file with the following command:\n\n # grep -i automaticloginenable /etc/gdm/custom.conf\n AutomaticLoginEnable=false\n\n If the value of \"AutomaticLoginEnable\" is not set to \"false\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to not allow an unattended or automatic\nlogon to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \"AutomaticLoginEnable\" parameter in the\n[daemon] section of the \"/etc/gdm/custom.conf\" file to \"false\":\n\n [daemon]\n AutomaticLoginEnable=false","label":"fix"}],"id":"V-71953","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GDM installed","resource":"","run_time":0.000012677,"skip_message":"The system does not have GDM installed, this requirement is Not Applicable.","start_time":"2022-03-06T22:05:49+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71953.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71953","rid":"SV-86577r2_rule","stig_id":"RHEL-07-010440","fix_id":"F-78305r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow an\nunattended or automatic logon to the system via a graphical user interface.","waiver_data":{}},{"code":"control \"V-71955\" do\n title \"The Red Hat Enterprise Linux operating system must not allow an\nunrestricted logon to the system.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow an unrestricted logon to the\nsystem via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \\\"TimedLoginEnable\\\" parameter in\n\\\"/etc/gdm/custom.conf\\\" file with the following command:\n\n # grep -i timedloginenable /etc/gdm/custom.conf\n TimedLoginEnable=false\n\n If the value of \\\"TimedLoginEnable\\\" is not set to \\\"false\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow an unrestricted account to log\non to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \\\"TimedLoginEnable\\\" parameter in the [daemon]\nsection of the \\\"/etc/gdm/custom.conf\\\" file to \\\"false\\\":\n\n [daemon]\n TimedLoginEnable=false\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71955\"\n tag rid: \"SV-86579r3_rule\"\n tag stig_id: \"RHEL-07-010450\"\n tag fix_id: \"F-78307r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n custom_conf = '/etc/gdm/custom.conf'\n\n if package('gdm').installed?\n impact 0.7\n if ((f = file(custom_conf)).exist?)\n describe ini(custom_conf) do\n its('daemon.TimedLoginEnable') { cmp false }\n end\n else\n describe f do\n it { should exist }\n end\n end\n else\n impact 0.0\n describe \"The system does not have GDM installed\" do\n skip \"The system does not have GDM installed, this requirement is Not Applicable.\"\n end\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow an unrestricted logon to the\nsystem via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Check for the value of the \"TimedLoginEnable\" parameter in\n\"/etc/gdm/custom.conf\" file with the following command:\n\n # grep -i timedloginenable /etc/gdm/custom.conf\n TimedLoginEnable=false\n\n If the value of \"TimedLoginEnable\" is not set to \"false\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to not allow an unrestricted account to log\non to the system via a graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Add or edit the line for the \"TimedLoginEnable\" parameter in the [daemon]\nsection of the \"/etc/gdm/custom.conf\" file to \"false\":\n\n [daemon]\n TimedLoginEnable=false","label":"fix"}],"id":"V-71955","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GDM installed","resource":"","run_time":0.000007698,"skip_message":"The system does not have GDM installed, this requirement is Not Applicable.","start_time":"2022-03-06T22:05:49+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71955.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71955","rid":"SV-86579r3_rule","stig_id":"RHEL-07-010450","fix_id":"F-78307r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow an\nunrestricted logon to the system.","waiver_data":{}},{"code":"control \"V-71957\" do\n title \"The Red Hat Enterprise Linux operating system must not allow users to\noverride SSH environment variables.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow users to override environment\nvariables to the SSH daemon.\n\n Check for the value of the \\\"PermitUserEnvironment\\\" keyword with the\nfollowing command:\n\n # grep -i permituserenvironment /etc/ssh/sshd_config\n PermitUserEnvironment no\n\n If the \\\"PermitUserEnvironment\\\" keyword is not set to \\\"no\\\", is missing,\nor is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow users to override environment\nvariables to the SSH daemon.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for\n\\\"PermitUserEnvironment\\\" keyword and set the value to \\\"no\\\":\n\n PermitUserEnvironment no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71957\"\n tag rid: \"SV-86581r3_rule\"\n tag stig_id: \"RHEL-07-010460\"\n tag fix_id: \"F-78309r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('PermitUserEnvironment') { should eq 'no' }\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow users to override environment\nvariables to the SSH daemon.\n\n Check for the value of the \"PermitUserEnvironment\" keyword with the\nfollowing command:\n\n # grep -i permituserenvironment /etc/ssh/sshd_config\n PermitUserEnvironment no\n\n If the \"PermitUserEnvironment\" keyword is not set to \"no\", is missing,\nor is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to not allow users to override environment\nvariables to the SSH daemon.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for\n\"PermitUserEnvironment\" keyword and set the value to \"no\":\n\n PermitUserEnvironment no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-71957","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration PermitUserEnvironment is expected to eq \"no\"","message":"\nexpected: \"no\"\n got: nil\n\n(compared using ==)\n","run_time":0.001215896,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71957.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71957","rid":"SV-86581r3_rule","stig_id":"RHEL-07-010460","fix_id":"F-78309r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow users to\noverride SSH environment variables.","waiver_data":{}},{"code":"control \"V-71959\" do\n title \"The Red Hat Enterprise Linux operating system must not allow a\nnon-certificate trusted host SSH logon to the system.\"\n desc \"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system does not allow a non-certificate trusted host\nSSH logon to the system.\n\n Check for the value of the \\\"HostbasedAuthentication\\\" keyword with the\nfollowing command:\n\n # grep -i hostbasedauthentication /etc/ssh/sshd_config\n HostbasedAuthentication no\n\n If the \\\"HostbasedAuthentication\\\" keyword is not set to \\\"no\\\", is\nmissing, or is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to not allow a non-certificate trusted host\nSSH logon to the system.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for\n\\\"HostbasedAuthentication\\\" keyword and set the value to \\\"no\\\":\n\n HostbasedAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00229\"\n tag gid: \"V-71959\"\n tag rid: \"SV-86583r3_rule\"\n tag stig_id: \"RHEL-07-010470\"\n tag fix_id: \"F-78311r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('HostbasedAuthentication') { should eq 'no' }\n end\nend\n","desc":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","descriptions":[{"data":"Failure to restrict system access to authenticated users negatively\nimpacts operating system security.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system does not allow a non-certificate trusted host\nSSH logon to the system.\n\n Check for the value of the \"HostbasedAuthentication\" keyword with the\nfollowing command:\n\n # grep -i hostbasedauthentication /etc/ssh/sshd_config\n HostbasedAuthentication no\n\n If the \"HostbasedAuthentication\" keyword is not set to \"no\", is\nmissing, or is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to not allow a non-certificate trusted host\nSSH logon to the system.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for\n\"HostbasedAuthentication\" keyword and set the value to \"no\":\n\n HostbasedAuthentication no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-71959","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration HostbasedAuthentication is expected to eq \"no\"","message":"\nexpected: \"no\"\n got: nil\n\n(compared using ==)\n","run_time":0.001086089,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71959.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00229","gid":"V-71959","rid":"SV-86583r3_rule","stig_id":"RHEL-07-010470","fix_id":"F-78311r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow a\nnon-certificate trusted host SSH logon to the system.","waiver_data":{}},{"code":"control \"V-71961\" do\n title \"Red Hat Enterprise Linux operating systems prior to version 7.2 with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use UEFI, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -i password_pbkdf2 /boot/grub2/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \\\"password_pbkdf2\\\", this is\na finding.\n\n If the \\\"superusers-account\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \\\"/etc/grub.d/40_custom\\\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\\\"root\\\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \\\"grub.conf\\\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/grub2/grub.cfg\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-71961\"\n tag rid: \"SV-86585r6_rule\"\n tag stig_id: \"RHEL-07-010480\"\n tag fix_id: \"F-78313r3_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n grub_superuser = input('grub_superuser')\n grub_user_boot_files = input('grub_user_boot_files')\n grub_main_cfg = input('grub_main_cfg')\n\n grub_main_content = file(grub_main_cfg).content\n\n if file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running UEFI\" do\n skip \"The System is running UEFI, this control is Not Applicable.\"\n end\n else\n if os[:release] >= \"7.2\"\n impact 0.0\n describe \"System running version of RHEL that is equal to or newer than 7.2\" do\n skip \"The System is running version #{os[:release]} of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n # Check if any additional superusers are set\n pattern = %r{\\s*set superusers=\\\"(\\w+)\\\"}i\n matches = grub_main_content.match(pattern)\n superusers = matches.nil? ? [] : matches.captures\n describe \"There must be only one grub2 superuser, and it must have the value #{grub_superuser}\" do\n subject { superusers }\n its('length') { should cmp 1 }\n its('first') { should cmp grub_superuser }\n end\n\n # Need each password entry that has the superuser\n pattern = %r{(.*)\\s#{grub_superuser}\\s}i\n matches = grub_main_content.match(pattern)\n password_entries = matches.nil? ? [] : matches.captures\n # Each of the entries should start with password_pbkdf2\n describe 'The grub2 superuser password entry must begin with \\'password_pbkdf2\\'' do\n subject { password_entries }\n its('length') { is_expected.to be >= 1}\n password_entries.each do |entry|\n subject { entry }\n it { should include 'password_pbkdf2'}\n end\n end\n\n # Get lines such as 'password_pbkdf2 root ${ENV}'\n pattern = %r{password_pbkdf2\\s#{grub_superuser}\\s(\\${\\w+})}i\n matches = grub_main_content.match(pattern)\n env_vars = matches.nil? ? [] : matches.captures\n if env_vars.length > 0\n # If there is an environment variable in the configuration file check that it is set with correct values by looking\n # in user.cfg files.\n env_vars = env_vars.map { |env_var| env_var.gsub(/[${}]/, '') }\n present_user_boot_files = grub_user_boot_files.select { |user_boot_file| file(user_boot_file).exist? }\n describe 'grub2 user configuration files for the superuser should be present if they set an environment variable' do\n subject { present_user_boot_files }\n its('length') { is_expected.to be >= 1 }\n present_user_boot_files.each do |user_boot_file|\n env_vars.each do |env_var|\n describe \"#{user_boot_file} should set #{env_var} to a pbkdf2 value\" do\n subject { file(user_boot_file) }\n its('content') { should match %r{^#{env_var}=grub.pbkdf2}i }\n end\n end\n end\n end\n else\n # If there are no environment variable set, look for pbkdf2 after the superuser name\n pattern = %r{password_pbkdf2\\s#{grub_superuser}\\sgrub\\.pbkdf2}i\n describe 'The grub2 superuser account password should be encrypted with pbkdf2.' do\n subject { grub_main_content }\n it { should match pattern }\n end\n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use UEFI, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -i password_pbkdf2 /boot/grub2/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \"password_pbkdf2\", this is\na finding.\n\n If the \"superusers-account\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \"/etc/grub.d/40_custom\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\"root\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \"grub.conf\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/grub2/grub.cfg","label":"fix"}],"id":"V-71961","impact":0,"refs":[],"results":[{"code_desc":"System running version of RHEL that is equal to or newer than 7.2","resource":"","run_time":0.000008234,"skip_message":"The System is running version 7.9.2009 of RHEL, this control is Not Applicable.","start_time":"2022-03-06T22:05:49+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71961.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-71961","rid":"SV-86585r6_rule","stig_id":"RHEL-07-010480","fix_id":"F-78313r3_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems prior to version 7.2 with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-71963\" do\n title \"Red Hat Enterprise Linux operating systems prior to version 7.2 using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use BIOS, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -i password /boot/efi/EFI/redhat/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \\\"password_pbkdf2\\\", this is\na finding.\n\n If the \\\"superusers-account\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \\\"/etc/grub.d/40_custom\\\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\\\"root\\\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \\\"grub.conf\\\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-71963\"\n tag rid: \"SV-86587r4_rule\"\n tag stig_id: \"RHEL-07-010490\"\n tag fix_id: \"F-78315r3_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n os_minor_version = os().release.split('.')[1].to_i\n\n efi_superusers = os_minor_version < 2 ? input('efi_superusers') : ['root']\n efi_superusers.push('root') if !efi_superusers.include?('root')\n efi_main_cfg = \"/boot/efi/EFI/#{os().name}/grub.cfg\"\n\n unless file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running BIOS\" do\n skip \"The System is running BIOS, this control is Not Applicable.\"\n end\n else\n if os[:release] < \"7.2\"\n impact 0.0\n describe \"System running version of RHEL prior to 7.2\" do\n skip \"The System is running an outdated version of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n efi_superusers.each do |user|\n describe file(efi_main_cfg) do\n its('content') { should match %r{^\\s*password_pbkdf2\\s+#{user} } }\n end\n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use BIOS, this is Not Applicable.\n For systems that are running RHEL 7.2 or newer, this is Not Applicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -i password /boot/efi/EFI/redhat/grub.cfg\n\n password_pbkdf2 [superusers-account] [password-hash]\n\n If the root password entry does not begin with \"password_pbkdf2\", this is\na finding.\n\n If the \"superusers-account\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-mkpasswd-pbkdf2\n\n Enter Password:\n Reenter Password:\n PBKDF2 hash of your password is\ngrub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45\n\n Edit \"/etc/grub.d/40_custom\" and add the following lines below the\ncomments:\n\n # vi /etc/grub.d/40_custom\n\n set superusers=\"root\"\n\n password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}\n\n Generate a new \"grub.conf\" file with the new password with the following\ncommands:\n\n # grub2-mkconfig --output=/tmp/grub2.cfg\n # mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg","label":"fix"}],"id":"V-71963","impact":0,"refs":[],"results":[{"code_desc":"System running BIOS","resource":"","run_time":0.000007806,"skip_message":"The System is running BIOS, this control is Not Applicable.","start_time":"2022-03-06T22:05:49+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71963.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-71963","rid":"SV-86587r4_rule","stig_id":"RHEL-07-010490","fix_id":"F-78315r3_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems prior to version 7.2 using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-71965\" do\n title \"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate organizational users (or processes acting on behalf of\norganizational users) using multifactor authentication.\"\n desc \"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system requires multifactor authentication to uniquely\nidentify organizational users using multifactor authentication.\n\n Check to see if smartcard authentication is enforced on the system:\n\n # authconfig --test | grep \\\"pam_pkcs11 is enabled\\\"\n\n If no results are returned, this is a finding.\n\n # authconfig --test | grep \\\"smartcard removal action\\\"\n\n If \\\"smartcard removal action\\\" is blank, this is a finding.\n\n # authconfig --test | grep \\\"smartcard module\\\"\n\n If \\\"smartcard module\\\" is blank, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require individuals to be authenticated\nwith a multifactor authenticator.\n\n Enable smartcard logons with the following commands:\n\n # authconfig --enablesmartcard --smartcardaction=0 --update\n # authconfig --enablerequiresmartcard -update\n\n Modify the \\\"/etc/pam_pkcs11/pkcs11_eventmgr.conf\\\" file to uncomment the\nfollowing line:\n\n #/usr/X11R6/bin/xscreensaver-command -lock\n\n Modify the \\\"/etc/pam_pkcs11/pam_pkcs11.conf\\\" file to use the cackey\nmodule if required.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000104-GPOS-00051\"\n tag satisfies: [\"SRG-OS-000104-GPOS-00051\", \"SRG-OS-000106-GPOS-00053\",\n\"SRG-OS-000107-GPOS-00054\", \"SRG-OS-000109-GPOS-00056\",\n\"SRG-OS-000108-GPOS-00055\", \"SRG-OS-000108-GPOS-00057\",\n\"SRG-OS-000108-GPOS-00058\"]\n tag gid: \"V-71965\"\n tag rid: \"SV-86589r2_rule\"\n tag stig_id: \"RHEL-07-010500\"\n tag fix_id: \"F-78317r3_fix\"\n tag cci: [\"CCI-000766\"]\n tag nist: [\"IA-2 (2)\"]\n\n smart_card_status = input('smart_card_status')\n if smart_card_status.eql?('enabled')\n impact 0.5\n describe command(\"authconfig --test | grep -i smartcard\") do\n its('stdout') { should match %r{use\\sonly\\ssmartcard\\sfor\\slogin\\sis\\s#{smart_card_status}} }\n its('stdout') { should match %r{smartcard\\smodule\\s=\\s\".+\"} }\n its('stdout') { should match %r{smartcard\\sremoval\\saction\\s=\\s\".+\"} }\n end\n else\n impact 0.0\n describe \"The system is not smartcard enabled\" do\n skip \"The system is not using Smartcards / PIVs to fulfil the MFA requirement, this control is Not Applicable.\"\n end\n end\nend\n","desc":"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.","descriptions":[{"data":"To assure accountability and prevent unauthenticated access,\norganizational users must be identified and authenticated to prevent potential\nmisuse and compromise of the system.\n\n Organizational users include organizational employees or individuals the\norganization deems to have equivalent status of employees (e.g., contractors).\nOrganizational users (and processes acting on behalf of users) must be uniquely\nidentified and authenticated to all accesses, except for the following:\n\n 1) Accesses explicitly identified and documented by the organization.\nOrganizations document specific user actions that can be performed on the\ninformation system without identification or authentication;\n\n and\n\n 2) Accesses that occur through authorized use of group authenticators\nwithout individual authentication. Organizations may require unique\nidentification of individuals in group accounts (e.g., shared privilege\naccounts) or for detailed accountability of individual activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system requires multifactor authentication to uniquely\nidentify organizational users using multifactor authentication.\n\n Check to see if smartcard authentication is enforced on the system:\n\n # authconfig --test | grep \"pam_pkcs11 is enabled\"\n\n If no results are returned, this is a finding.\n\n # authconfig --test | grep \"smartcard removal action\"\n\n If \"smartcard removal action\" is blank, this is a finding.\n\n # authconfig --test | grep \"smartcard module\"\n\n If \"smartcard module\" is blank, this is a finding.","label":"check"},{"data":"Configure the operating system to require individuals to be authenticated\nwith a multifactor authenticator.\n\n Enable smartcard logons with the following commands:\n\n # authconfig --enablesmartcard --smartcardaction=0 --update\n # authconfig --enablerequiresmartcard -update\n\n Modify the \"/etc/pam_pkcs11/pkcs11_eventmgr.conf\" file to uncomment the\nfollowing line:\n\n #/usr/X11R6/bin/xscreensaver-command -lock\n\n Modify the \"/etc/pam_pkcs11/pam_pkcs11.conf\" file to use the cackey\nmodule if required.","label":"fix"}],"id":"V-71965","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `authconfig --test | grep -i smartcard` stdout is expected to match /use\\sonly\\ssmartcard\\sfor\\slogin\\sis\\senabled/","message":"expected \"SSSD smartcard support is disabled\\n use only smartcard for login is disabled\\n smartcard module = \\\"\\\"\\n smartcard removal action = \\\"\\\"\\n\" to match /use\\sonly\\ssmartcard\\sfor\\slogin\\sis\\senabled/\nDiff:\n@@ -1,2 +1,5 @@\n-/use\\sonly\\ssmartcard\\sfor\\slogin\\sis\\senabled/\n+SSSD smartcard support is disabled\n+ use only smartcard for login is disabled\n+ smartcard module = \"\"\n+ smartcard removal action = \"\"\n","run_time":0.116022194,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"command","resource_params":"[\"authconfig --test | grep -i smartcard\"]"},{"code_desc":"Command: `authconfig --test | grep -i smartcard` stdout is expected to match /smartcard\\smodule\\s=\\s\".+\"/","message":"expected \"SSSD smartcard support is disabled\\n use only smartcard for login is disabled\\n smartcard module = \\\"\\\"\\n smartcard removal action = \\\"\\\"\\n\" to match /smartcard\\smodule\\s=\\s\".+\"/\nDiff:\n@@ -1,2 +1,5 @@\n-/smartcard\\smodule\\s=\\s\".+\"/\n+SSSD smartcard support is disabled\n+ use only smartcard for login is disabled\n+ smartcard module = \"\"\n+ smartcard removal action = \"\"\n","run_time":0.000406691,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"command","resource_params":"[\"authconfig --test | grep -i smartcard\"]"},{"code_desc":"Command: `authconfig --test | grep -i smartcard` stdout is expected to match /smartcard\\sremoval\\saction\\s=\\s\".+\"/","message":"expected \"SSSD smartcard support is disabled\\n use only smartcard for login is disabled\\n smartcard module = \\\"\\\"\\n smartcard removal action = \\\"\\\"\\n\" to match /smartcard\\sremoval\\saction\\s=\\s\".+\"/\nDiff:\n@@ -1,2 +1,5 @@\n-/smartcard\\sremoval\\saction\\s=\\s\".+\"/\n+SSSD smartcard support is disabled\n+ use only smartcard for login is disabled\n+ smartcard module = \"\"\n+ smartcard removal action = \"\"\n","run_time":0.000426029,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"command","resource_params":"[\"authconfig --test | grep -i smartcard\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71965.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000104-GPOS-00051","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"],"gid":"V-71965","rid":"SV-86589r2_rule","stig_id":"RHEL-07-010500","fix_id":"F-78317r3_fix","cci":["CCI-000766"],"nist":["IA-2 (2)"]},"title":"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate organizational users (or processes acting on behalf of\norganizational users) using multifactor authentication.","waiver_data":{}},{"code":"control \"V-71967\" do\n title \"The Red Hat Enterprise Linux operating system must not have the\nrsh-server package installed.\"\n desc \"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check to see if the rsh-server package is installed with the following\ncommand:\n\n # yum list installed rsh-server\n\n If the rsh-server package is installed, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable non-essential capabilities by\nremoving the rsh-server package from the system with the following command:\n\n # yum remove rsh-server\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000095-GPOS-00049\"\n tag gid: \"V-71967\"\n tag rid: \"SV-86591r2_rule\"\n tag stig_id: \"RHEL-07-020000\"\n tag fix_id: \"F-78319r1_fix\"\n tag cci: [\"CCI-000381\"]\n tag nist: [\"CM-7 a\"]\n\n describe package(\"rsh-server\") do\n it { should_not be_installed }\n end\nend\n","desc":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.","descriptions":[{"data":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n The rsh-server service provides an unencrypted remote access service that\ndoes not provide for the confidentiality and integrity of user passwords or the\nremote session and has very weak authentication.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if the rsh-server package is installed with the following\ncommand:\n\n # yum list installed rsh-server\n\n If the rsh-server package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the rsh-server package from the system with the following command:\n\n # yum remove rsh-server","label":"fix"}],"id":"V-71967","impact":0.7,"refs":[],"results":[{"code_desc":"System Package rsh-server is expected not to be installed","run_time":0.231608036,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"package","resource_params":"[\"rsh-server\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71967.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-71967","rid":"SV-86591r2_rule","stig_id":"RHEL-07-020000","fix_id":"F-78319r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the\nrsh-server package installed.","waiver_data":{}},{"code":"control \"V-71969\" do\n title \"The Red Hat Enterprise Linux operating system must not have the ypserv\npackage installed.\"\n desc \"Removing the \\\"ypserv\\\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n The NIS service provides an unencrypted authentication service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n Check to see if the \\\"ypserve\\\" package is installed with the following\ncommand:\n\n # yum list installed ypserv\n\n If the \\\"ypserv\\\" package is installed, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable non-essential capabilities by\nremoving the \\\"ypserv\\\" package from the system with the following command:\n\n # yum remove ypserv\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000095-GPOS-00049\"\n tag gid: \"V-71969\"\n tag rid: \"SV-86593r2_rule\"\n tag stig_id: \"RHEL-07-020010\"\n tag fix_id: \"F-78321r1_fix\"\n tag cci: [\"CCI-000381\"]\n tag nist: [\"CM-7 a\"]\n\n describe package(\"ypserv\") do\n it { should_not be_installed }\n end\nend\n","desc":"Removing the \"ypserv\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.","descriptions":[{"data":"Removing the \"ypserv\" package decreases the risk of the accidental\n(or intentional) activation of NIS or NIS+ services.","label":"default"},{"data":"","label":"rationale"},{"data":"The NIS service provides an unencrypted authentication service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n Check to see if the \"ypserve\" package is installed with the following\ncommand:\n\n # yum list installed ypserv\n\n If the \"ypserv\" package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the \"ypserv\" package from the system with the following command:\n\n # yum remove ypserv","label":"fix"}],"id":"V-71969","impact":0.7,"refs":[],"results":[{"code_desc":"System Package ypserv is expected not to be installed","run_time":0.045347315,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"package","resource_params":"[\"ypserv\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71969.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-71969","rid":"SV-86593r2_rule","stig_id":"RHEL-07-020010","fix_id":"F-78321r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the ypserv\npackage installed.","waiver_data":{}},{"code":"control \"V-71971\" do\n title \"The Red Hat Enterprise Linux operating system must prevent\nnon-privileged users from executing privileged functions to include disabling,\ncircumventing, or altering implemented security safeguards/countermeasures.\"\n desc \"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system prevents non-privileged users from executing\nprivileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Get a list of authorized users (other than System Administrator and guest\naccounts) for the system.\n\n Check the list against the system by using the following command:\n\n # semanage login -l | more\n Login Name SELinux User MLS/MCS Range Service\n __default__ user_u s0-s0:c0.c1023 *\n root unconfined_u s0-s0:c0.c1023 *\n system_u system_u s0-s0:c0.c1023 *\n joe staff_u s0-s0:c0.c1023 *\n\n All administrators must be mapped to the \\\"sysadm_u\\\" or \\\"staff_u\\\" users\nrole.\n\n All authorized non-administrative users must be mapped to the \\\"user_u\\\"\nrole.\n\n If they are not mapped in this way, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent non-privileged users from\nexecuting privileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Use the following command to map a new user to the \\\"sysdam_u\\\" role:\n\n #semanage login -a -s sysadm_u \n\n Use the following command to map an existing user to the \\\"sysdam_u\\\" role:\n\n #semanage login -m -s sysadm_u \n\n Use the following command to map a new user to the \\\"staff_u\\\" role:\n\n #semanage login -a -s staff_u \n\n Use the following command to map an existing user to the \\\"staff_u\\\" role:\n\n #semanage login -m -s staff_u \n\n Use the following command to map a new user to the \\\"user_u\\\" role:\n\n # semanage login -a -s user_u \n\n Use the following command to map an existing user to the \\\"user_u\\\" role:\n\n # semanage login -m -s user_u \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000324-GPOS-00125\"\n tag gid: \"V-71971\"\n tag rid: \"SV-86595r2_rule\"\n tag stig_id: \"RHEL-07-020020\"\n tag fix_id: \"F-78323r1_fix\"\n tag cci: [\"CCI-002165\", \"CCI-002235\"]\n tag nist: [\"AC-3 (4)\", \"AC-6 (10)\"]\n\n admin_logins = input('admin_logins')\n\n if package('MFEhiplsm').installed? && processes(/hipclient/).exist?\n impact 0.0\n describe \"HIPS is active on the system\" do\n skip \"A HIPS process is active on the system, this control is Not Applicable.\"\n end\n elsif service('cma').installed? && service('cma').enabled?\n impact 0.0\n describe \"HBSS is active on the system\" do\n skip \"A HBSS service is active on the system, this control is Not Applicable.\"\n end\n else\n impact 0.5\n describe command('selinuxenabled') do\n its('exist?') { should be true }\n its('exit_status') { should eq 0 }\n end\n\n selinux_mode = file('/etc/selinux/config').content.lines.\n grep(/\\A\\s*SELINUXTYPE=/).last.split('=').last.strip\n\n seusers = file(\"/etc/selinux/#{selinux_mode}/seusers\").content.lines.\n grep_v(/(#|\\A\\s+\\Z)/).map(&:strip)\n\n seusers = seusers.map{|x| x.split(':')[0..1]}\n\n describe 'seusers' do\n it { expect(seusers).to_not be_empty }\n end\n\n users_to_ignore = [\n 'root',\n 'system_u'\n ]\n\n seusers.each do |user, context|\n next if users_to_ignore.include?(user)\n\n describe \"SELinux login #{user}\" do\n if user == '__default__'\n let(:valid_users){[ 'user_u' ]}\n elsif admin_logins.include?(user)\n let(:valid_users){[\n 'sysadm_u',\n 'staff_u'\n ]}\n else\n let(:valid_users){[\n 'user_u',\n 'guest_u',\n 'xguest_u'\n ]}\n end\n\n it { expect(context).to be_in(valid_users) }\n end\n end\n end\nend\n","desc":"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.","descriptions":[{"data":"Preventing non-privileged users from executing privileged functions\nmitigates the risk that unauthorized individuals or processes may gain\nunnecessary access to information or privileges.\n\n Privileged functions include, for example, establishing accounts,\nperforming system integrity checks, or administering cryptographic key\nmanagement activities. Non-privileged users are individuals who do not possess\nappropriate authorizations. Circumventing intrusion detection and prevention\nmechanisms or malicious code protection mechanisms are examples of privileged\nfunctions that require protection from non-privileged users.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system prevents non-privileged users from executing\nprivileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Get a list of authorized users (other than System Administrator and guest\naccounts) for the system.\n\n Check the list against the system by using the following command:\n\n # semanage login -l | more\n Login Name SELinux User MLS/MCS Range Service\n __default__ user_u s0-s0:c0.c1023 *\n root unconfined_u s0-s0:c0.c1023 *\n system_u system_u s0-s0:c0.c1023 *\n joe staff_u s0-s0:c0.c1023 *\n\n All administrators must be mapped to the \"sysadm_u\" or \"staff_u\" users\nrole.\n\n All authorized non-administrative users must be mapped to the \"user_u\"\nrole.\n\n If they are not mapped in this way, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent non-privileged users from\nexecuting privileged functions to include disabling, circumventing, or altering\nimplemented security safeguards/countermeasures.\n\n Use the following command to map a new user to the \"sysdam_u\" role:\n\n #semanage login -a -s sysadm_u \n\n Use the following command to map an existing user to the \"sysdam_u\" role:\n\n #semanage login -m -s sysadm_u \n\n Use the following command to map a new user to the \"staff_u\" role:\n\n #semanage login -a -s staff_u \n\n Use the following command to map an existing user to the \"staff_u\" role:\n\n #semanage login -m -s staff_u \n\n Use the following command to map a new user to the \"user_u\" role:\n\n # semanage login -a -s user_u \n\n Use the following command to map an existing user to the \"user_u\" role:\n\n # semanage login -m -s user_u ","label":"fix"}],"id":"V-71971","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `selinuxenabled` exist? is expected to equal true","run_time":0.010903528,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"command","resource_params":"[\"selinuxenabled\"]"},{"code_desc":"Command: `selinuxenabled` exit_status is expected to eq 0","run_time":0.017534771,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"command","resource_params":"[\"selinuxenabled\"]"},{"code_desc":"seusers is expected not to be empty","run_time":0.011377382,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"SELinux login __default__ is expected to be in \"user_u\"","message":"expected `unconfined_u` to be in the list: `[\"user_u\"]`","run_time":0.002216481,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71971.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000324-GPOS-00125","gid":"V-71971","rid":"SV-86595r2_rule","stig_id":"RHEL-07-020020","fix_id":"F-78323r1_fix","cci":["CCI-002165","CCI-002235"],"nist":["AC-3 (4)","AC-6 (10)"]},"title":"The Red Hat Enterprise Linux operating system must prevent\nnon-privileged users from executing privileged functions to include disabling,\ncircumventing, or altering implemented security safeguards/countermeasures.","waiver_data":{}},{"code":"control \"V-71973\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat a file integrity tool verifies the baseline operating system configuration\nat least weekly.\"\n desc \"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system routinely checks the baseline configuration for\nunauthorized changes.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed at least once per\nweek.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running daily or weekly on the system\nthat executes AIDE daily to scan for changes to the system baseline. The\ncommand used in the example will use a daily occurrence.\n\n Check the cron directories for a script file controlling the execution of\nthe file integrity application. For example, if AIDE is installed on the\nsystem, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 29 Nov 22 2015 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n If the file integrity application does not exist, or a script file\ncontrolling the execution of the file integrity application does not exist,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to run automatically on the system at\nleast weekly. The following example output is generic. It will set cron to run\nAIDE daily, but other file integrity tools may be used:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \\\"$HOSTNAME - Daily aide integrity\ncheck run\\\" root@sysname.mil\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000363-GPOS-00150\"\n tag gid: \"V-71973\"\n tag rid: \"SV-86597r2_rule\"\n tag stig_id: \"RHEL-07-020030\"\n tag fix_id: \"F-78325r2_fix\"\n tag cci: [\"CCI-001744\"]\n tag nist: [\"CM-3 (5)\"]\n\n file_integrity_tool = input('file_integrity_tool')\n file_integrity_interval = input('file_integrity_interval')\n\n describe package(file_integrity_tool) do\n it { should be_installed }\n end\n\n if file_integrity_interval == 'monthly'\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n it { should exist }\n end\n describe file(\"/etc/cron.weekly/#{file_integrity_tool}\") do\n it { should exist }\n end\n describe file(\"/etc/cron.monthly/#{file_integrity_tool}\") do\n it { should exist }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n elsif file_integrity_interval == 'weekly'\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n it { should exist }\n end\n describe file(\"/etc/cron.weekly/#{file_integrity_tool}\") do\n it { should exist }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n end\n end\n elsif file_integrity_interval == 'daily'\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n it { should exist }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('days') { should cmp '*' }\n its('months') { should cmp '*' }\n its('weekdays') { should cmp '*' }\n end\n end\n end\nend\n","desc":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","descriptions":[{"data":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system routinely checks the baseline configuration for\nunauthorized changes.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed at least once per\nweek.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running daily or weekly on the system\nthat executes AIDE daily to scan for changes to the system baseline. The\ncommand used in the example will use a daily occurrence.\n\n Check the cron directories for a script file controlling the execution of\nthe file integrity application. For example, if AIDE is installed on the\nsystem, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 29 Nov 22 2015 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n If the file integrity application does not exist, or a script file\ncontrolling the execution of the file integrity application does not exist,\nthis is a finding.","label":"check"},{"data":"Configure the file integrity tool to run automatically on the system at\nleast weekly. The following example output is generic. It will set cron to run\nAIDE daily, but other file integrity tools may be used:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil","label":"fix"}],"id":"V-71973","impact":0.5,"refs":[],"results":[{"code_desc":"System Package aide is expected to be installed","run_time":0.002029644,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"package","resource_params":"[\"aide\"]"},{"code_desc":"File /etc/cron.daily/aide is expected to exist","exception":"RSpec::Core::MultipleExceptionError","message":"expected File /etc/cron.daily/aide to exist","run_time":0.000270489,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"file","resource_params":"[\"/etc/cron.daily/aide\"]"},{"code_desc":"File /etc/cron.weekly/aide is expected to exist","exception":"RSpec::Core::MultipleExceptionError","message":"expected File /etc/cron.weekly/aide to exist","run_time":0.000224962,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"file","resource_params":"[\"/etc/cron.weekly/aide\"]"},{"code_desc":"crontab for user root with command =~ /aide/ days is expected to cmp == \"*\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: *\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.000444558,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"crontab for user root with command =~ /aide/ months is expected to cmp == \"*\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: *\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.00058343,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71973.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000363-GPOS-00150","gid":"V-71973","rid":"SV-86597r2_rule","stig_id":"RHEL-07-020030","fix_id":"F-78325r2_fix","cci":["CCI-001744"],"nist":["CM-3 (5)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat a file integrity tool verifies the baseline operating system configuration\nat least weekly.","waiver_data":{}},{"code":"control \"V-71975\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat designated personnel are notified if baseline configurations are changed\nin an unauthorized manner.\"\n desc \"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system notifies designated personnel if baseline\nconfigurations are changed in an unauthorized manner.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed and notify\nspecified individuals via email or an alert.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running routinely on the system that\nexecutes AIDE to scan for changes to the system baseline. The commands used in\nthe example will use a daily occurrence.\n\n Check the cron directories for a \\\"crontab\\\" script file controlling the\nexecution of the file integrity application. For example, if AIDE is installed\non the system, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 32 Jul 1 2011 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n AIDE does not have a configuration that will send a notification, so the\ncron job uses the mail application on the system to email the results of the\nfile integrity run as in the following example:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \\\"$HOSTNAME - Daily aide integrity\ncheck run\\\" root@sysname.mil\n\n If the file integrity application does not notify designated personnel of\nchanges, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to notify designated personnel if baseline\nconfigurations are changed in an unauthorized manner. The AIDE tool can be\nconfigured to email designated personnel with the use of the cron system.\n\n The following example output is generic. It will set cron to run AIDE daily\nand to send email at the completion of the analysis.\n\n # more /etc/cron.daily/aide\n\n /usr/sbin/aide --check | /bin/mail -s \\\"$HOSTNAME - Daily aide integrity\ncheck run\\\" root@sysname.mil\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000363-GPOS-00150\"\n tag gid: \"V-71975\"\n tag rid: \"SV-86599r2_rule\"\n tag stig_id: \"RHEL-07-020040\"\n tag fix_id: \"F-78327r3_fix\"\n tag cci: [\"CCI-001744\"]\n tag nist: [\"CM-3 (5)\"]\n\n file_integrity_tool = input('file_integrity_tool')\n\n describe package(file_integrity_tool) do\n it { should be_installed }\n end\n describe.one do\n describe file(\"/etc/cron.daily/#{file_integrity_tool}\") do\n its('content') { should match %r{/bin/mail} }\n end\n describe file(\"/etc/cron.weekly/#{file_integrity_tool}\") do\n its('content') { should match %r{/bin/mail} }\n end\n describe crontab('root').where { command =~ %r{#{file_integrity_tool}} } do\n its('commands.flatten') { should include(match %r{/bin/mail}) }\n end\n if file(\"/etc/cron.d/#{file_integrity_tool}\").exist?\n describe crontab(path: \"/etc/cron.d/#{file_integrity_tool}\") do\n its('commands') { should include(match %r{/bin/mail}) }\n end\n end\n end\nend\n","desc":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","descriptions":[{"data":"Unauthorized changes to the baseline configuration could make the\nsystem vulnerable to various attacks or allow unauthorized access to the\noperating system. Changes to operating system configurations can have\nunintended side effects, some of which may be relevant to security.\n\n Detecting such changes and providing an automated response can help avoid\nunintended, negative consequences that could ultimately affect the security\nstate of the operating system. The operating system's Information Management\nOfficer (IMO)/Information System Security Officer (ISSO) and System\nAdministrators (SAs) must be notified via email and/or monitoring system trap\nwhen there is an unauthorized modification of a configuration item.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system notifies designated personnel if baseline\nconfigurations are changed in an unauthorized manner.\n\n Note: A file integrity tool other than Advanced Intrusion Detection\nEnvironment (AIDE) may be used, but the tool must be executed and notify\nspecified individuals via email or an alert.\n\n Check to see if AIDE is installed on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the SA how file integrity checks are\nperformed on the system.\n\n Check for the presence of a cron job running routinely on the system that\nexecutes AIDE to scan for changes to the system baseline. The commands used in\nthe example will use a daily occurrence.\n\n Check the cron directories for a \"crontab\" script file controlling the\nexecution of the file integrity application. For example, if AIDE is installed\non the system, use the following command:\n\n # ls -al /etc/cron.* | grep aide\n -rwxr-xr-x 1 root root 32 Jul 1 2011 aide\n\n # grep aide /etc/crontab /var/spool/cron/root\n /etc/crontab: 30 04 * * * /root/aide\n /var/spool/cron/root: 30 04 * * * /root/aide\n\n AIDE does not have a configuration that will send a notification, so the\ncron job uses the mail application on the system to email the results of the\nfile integrity run as in the following example:\n\n # more /etc/cron.daily/aide\n #!/bin/bash\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil\n\n If the file integrity application does not notify designated personnel of\nchanges, this is a finding.","label":"check"},{"data":"Configure the operating system to notify designated personnel if baseline\nconfigurations are changed in an unauthorized manner. The AIDE tool can be\nconfigured to email designated personnel with the use of the cron system.\n\n The following example output is generic. It will set cron to run AIDE daily\nand to send email at the completion of the analysis.\n\n # more /etc/cron.daily/aide\n\n /usr/sbin/aide --check | /bin/mail -s \"$HOSTNAME - Daily aide integrity\ncheck run\" root@sysname.mil","label":"fix"}],"id":"V-71975","impact":0.5,"refs":[],"results":[{"code_desc":"System Package aide is expected to be installed","run_time":0.00080451,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"package","resource_params":"[\"aide\"]"},{"code_desc":"File /etc/cron.daily/aide content is expected to match /\\/bin\\/mail/","exception":"RSpec::Core::MultipleExceptionError","message":"expected nil to match /\\/bin\\/mail/","run_time":0.000346319,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"file","resource_params":"[\"/etc/cron.daily/aide\"]"},{"code_desc":"File /etc/cron.weekly/aide content is expected to match /\\/bin\\/mail/","exception":"RSpec::Core::MultipleExceptionError","message":"expected nil to match /\\/bin\\/mail/","run_time":0.000311006,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"file","resource_params":"[\"/etc/cron.weekly/aide\"]"},{"code_desc":"crontab for user root with command =~ /aide/ commands.flatten is expected to include (match /\\/bin\\/mail/)","exception":"RSpec::Core::MultipleExceptionError","message":"expected [] to include (match /\\/bin\\/mail/)\nDiff:\n@@ -1,2 +1,2 @@\n-[(match /\\/bin\\/mail/)]\n+[]\n","run_time":0.000716091,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71975.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000363-GPOS-00150","gid":"V-71975","rid":"SV-86599r2_rule","stig_id":"RHEL-07-020040","fix_id":"F-78327r3_fix","cci":["CCI-001744"],"nist":["CM-3 (5)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat designated personnel are notified if baseline configurations are changed\nin an unauthorized manner.","waiver_data":{}},{"code":"control \"V-71977\" do\n title \"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components from a repository without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.\"\n desc \"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components from a repository without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of packages from a repository prior\nto install with the following command:\n\n # grep gpgcheck /etc/yum.conf\n gpgcheck=1\n\n If \\\"gpgcheck\\\" is not set to \\\"1\\\", or if options are missing or commented\nout, ask the System Administrator how the certificates for patches and other\noperating system components are verified.\n\n If there is no process to validate certificates that is approved by the\norganization, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify the signature of packages from a\nrepository prior to install by setting the following option in the\n\\\"/etc/yum.conf\\\" file:\n\n gpgcheck=1\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000366-GPOS-00153\"\n tag gid: \"V-71977\"\n tag rid: \"SV-86601r2_rule\"\n tag stig_id: \"RHEL-07-020050\"\n tag fix_id: \"F-78329r1_fix\"\n tag cci: [\"CCI-001749\"]\n tag nist: [\"CM-5 (3)\"]\n\n yum_conf = '/etc/yum.conf'\n\n if ((f = file(yum_conf)).exist?)\n describe ini(yum_conf) do\n its('main.gpgcheck') { should cmp 1 }\n end\n else\n describe f do\n it { should exist }\n end\n end\nend\n","desc":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","descriptions":[{"data":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components from a repository without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of packages from a repository prior\nto install with the following command:\n\n # grep gpgcheck /etc/yum.conf\n gpgcheck=1\n\n If \"gpgcheck\" is not set to \"1\", or if options are missing or commented\nout, ask the System Administrator how the certificates for patches and other\noperating system components are verified.\n\n If there is no process to validate certificates that is approved by the\norganization, this is a finding.","label":"check"},{"data":"Configure the operating system to verify the signature of packages from a\nrepository prior to install by setting the following option in the\n\"/etc/yum.conf\" file:\n\n gpgcheck=1","label":"fix"}],"id":"V-71977","impact":0.7,"refs":[],"results":[{"code_desc":"INI /etc/yum.conf main.gpgcheck is expected to cmp == 1","run_time":0.000330704,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"ini","resource_params":"[\"/etc/yum.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71977.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000366-GPOS-00153","gid":"V-71977","rid":"SV-86601r2_rule","stig_id":"RHEL-07-020050","fix_id":"F-78329r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components from a repository without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.","waiver_data":{}},{"code":"control \"V-71979\" do\n title \"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components of local packages without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.\"\n desc \"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components of local packages without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of local packages prior to install\nwith the following command:\n\n # grep localpkg_gpgcheck /etc/yum.conf\n localpkg_gpgcheck=1\n\n If \\\"localpkg_gpgcheck\\\" is not set to \\\"1\\\", or if options are missing or\ncommented out, ask the System Administrator how the signatures of local\npackages and other operating system components are verified.\n\n If there is no process to validate the signatures of local packages that is\napproved by the organization, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify the signature of local packages\nprior to install by setting the following option in the \\\"/etc/yum.conf\\\" file:\n\n localpkg_gpgcheck=1\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000366-GPOS-00153\"\n tag gid: \"V-71979\"\n tag rid: \"SV-86603r2_rule\"\n tag stig_id: \"RHEL-07-020060\"\n tag fix_id: \"F-78331r1_fix\"\n tag cci: [\"CCI-001749\"]\n tag nist: [\"CM-5 (3)\"]\n\n yum_conf = '/etc/yum.conf'\n\n if ((f = file(yum_conf)).exist?)\n describe ini(yum_conf) do\n its('main.localpkg_gpgcheck') { cmp 1 }\n end\n else\n describe f do\n it { should exist }\n end\n end\nend\n","desc":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","descriptions":[{"data":"Changes to any software components can have significant effects on the\noverall security of the operating system. This requirement ensures the software\nhas not been tampered with and that it has been provided by a trusted vendor.\n\n Accordingly, patches, service packs, device drivers, or operating system\ncomponents must be signed with a certificate recognized and approved by the\norganization.\n\n Verifying the authenticity of the software prior to installation validates\nthe integrity of the patch or upgrade received from a vendor. This verifies the\nsoftware has not been tampered with and that it has been provided by a trusted\nvendor. Self-signed certificates are disallowed by this requirement. The\noperating system should not have to verify the software again. This requirement\ndoes not mandate DoD certificates for this purpose; however, the certificate\nused to verify the software must be from an approved CA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents the installation of patches, service\npacks, device drivers, or operating system components of local packages without\nverification that they have been digitally signed using a certificate that is\nrecognized and approved by the organization.\n\n Check that yum verifies the signature of local packages prior to install\nwith the following command:\n\n # grep localpkg_gpgcheck /etc/yum.conf\n localpkg_gpgcheck=1\n\n If \"localpkg_gpgcheck\" is not set to \"1\", or if options are missing or\ncommented out, ask the System Administrator how the signatures of local\npackages and other operating system components are verified.\n\n If there is no process to validate the signatures of local packages that is\napproved by the organization, this is a finding.","label":"check"},{"data":"Configure the operating system to verify the signature of local packages\nprior to install by setting the following option in the \"/etc/yum.conf\" file:\n\n localpkg_gpgcheck=1","label":"fix"}],"id":"V-71979","impact":0.7,"refs":[],"results":[{"code_desc":"INI /etc/yum.conf main.localpkg_gpgcheck ","run_time":0.000282308,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"ini","resource_params":"[\"/etc/yum.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71979.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000366-GPOS-00153","gid":"V-71979","rid":"SV-86603r2_rule","stig_id":"RHEL-07-020060","fix_id":"F-78331r1_fix","cci":["CCI-001749"],"nist":["CM-5 (3)"]},"title":"The Red Hat Enterprise Linux operating system must prevent the\ninstallation of software, patches, service packs, device drivers, or operating\nsystem components of local packages without verification they have been\ndigitally signed using a certificate that is issued by a Certificate Authority\n(CA) that is recognized and approved by the organization.","waiver_data":{}},{"code":"control \"V-71983\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\ndisable USB mass storage.\"\n desc \"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If there is an HBSS with a Device Control Module and a Data Loss Prevention\nmechanism, this requirement is not applicable.\n\n Verify the operating system disables the ability to load the USB Storage\nkernel module.\n\n # grep -r usb-storage /etc/modprobe.d/* | grep -i \\\"/bin/true\\\" | grep -v\n\\\"^#\\\"\n\n install usb-storage /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of USB Storage is not documented with the Information System Security\nOfficer (ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use USB mass storage\ndevices.\n\n Check to see if USB mass storage is disabled with the following command:\n\n # grep usb-storage /etc/modprobe.d/* | grep -i \\\"blacklist\\\" | grep -v\n\\\"^#\\\"\n blacklist usb-storage\n\n If the command does not return any output or the output is not \\\"blacklist\nusb-storage\\\", and use of USB storage devices is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable the ability to use the USB\nStorage kernel module.\n\n Create a file under \\\"/etc/modprobe.d\\\" with the following command:\n\n # touch /etc/modprobe.d/usb-storage.conf\n\n Add the following line to the created file:\n\n install usb-storage /bin/true\n\n Configure the operating system to disable the ability to use USB mass\nstorage devices.\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist usb-storage\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000114-GPOS-00059\"\n tag satisfies: [\"SRG-OS-000114-GPOS-00059\", \"SRG-OS-000378-GPOS-00163\",\n\"SRG-OS-000480-GPOS-00227\"]\n tag gid: \"V-71983\"\n tag rid: \"SV-86607r4_rule\"\n tag stig_id: \"RHEL-07-020100\"\n tag fix_id: \"F-78335r4_fix\"\n tag cci: [\"CCI-000366\", \"CCI-000778\", \"CCI-001958\"]\n tag nist: [\"CM-6 b\", \"IA-3\", \"IA-3\"]\n\n unless input('data_loss_prevention_installed')\n impact 0.0\n describe \"The system is not using an HBSS with a Device Control Module and a Data Loss Prevention mechanism\" do\n skip \"The system is not using an HBSS with a Device Control Module and a Data Loss Prevention mechanism, this control is Not Applicable.\"\n end\n else\n describe kernel_module('usb_storage') do\n it { should_not be_loaded }\n it { should be_blacklisted }\n end\n end\nend\n","desc":"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.","descriptions":[{"data":"USB mass storage permits easy introduction of unknown devices, thereby\nfacilitating malicious activity.","label":"default"},{"data":"","label":"rationale"},{"data":"If there is an HBSS with a Device Control Module and a Data Loss Prevention\nmechanism, this requirement is not applicable.\n\n Verify the operating system disables the ability to load the USB Storage\nkernel module.\n\n # grep -r usb-storage /etc/modprobe.d/* | grep -i \"/bin/true\" | grep -v\n\"^#\"\n\n install usb-storage /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of USB Storage is not documented with the Information System Security\nOfficer (ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use USB mass storage\ndevices.\n\n Check to see if USB mass storage is disabled with the following command:\n\n # grep usb-storage /etc/modprobe.d/* | grep -i \"blacklist\" | grep -v\n\"^#\"\n blacklist usb-storage\n\n If the command does not return any output or the output is not \"blacklist\nusb-storage\", and use of USB storage devices is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to use the USB\nStorage kernel module.\n\n Create a file under \"/etc/modprobe.d\" with the following command:\n\n # touch /etc/modprobe.d/usb-storage.conf\n\n Add the following line to the created file:\n\n install usb-storage /bin/true\n\n Configure the operating system to disable the ability to use USB mass\nstorage devices.\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist usb-storage","label":"fix"}],"id":"V-71983","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Module usb_storage is expected not to be loaded","run_time":0.057767097,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"kernel_module","resource_params":"[\"usb_storage\"]"},{"code_desc":"Kernel Module usb_storage is expected to be blacklisted","message":"expected `Kernel Module usb_storage.blacklisted?` to be truthy, got false","run_time":0.207785532,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"kernel_module","resource_params":"[\"usb_storage\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71983.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000114-GPOS-00059","satisfies":["SRG-OS-000114-GPOS-00059","SRG-OS-000378-GPOS-00163","SRG-OS-000480-GPOS-00227"],"gid":"V-71983","rid":"SV-86607r4_rule","stig_id":"RHEL-07-020100","fix_id":"F-78335r4_fix","cci":["CCI-000366","CCI-000778","CCI-001958"],"nist":["CM-6 b","IA-3","IA-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\ndisable USB mass storage.","waiver_data":{}},{"code":"control \"V-71985\" do\n title \"The Red Hat Enterprise Linux operating system must disable the file\nsystem automounter unless required.\"\n desc \"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system disables the ability to automount devices.\n\n Check to see if automounter service is active with the following command:\n\n # systemctl status autofs\n autofs.service - Automounts filesystems on demand\n Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)\n Active: inactive (dead)\n\n If the \\\"autofs\\\" status is set to \\\"active\\\" and is not documented with\nthe Information System Security Officer (ISSO) as an operational requirement,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable the ability to automount devices.\n\n Turn off the automount service with the following commands:\n\n # systemctl stop autofs\n # systemctl disable autofs\n\n If \\\"autofs\\\" is required for Network File System (NFS), it must be\ndocumented with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000114-GPOS-00059\"\n tag satisfies: [\"SRG-OS-000114-GPOS-00059\", \"SRG-OS-000378-GPOS-00163\",\n\"SRG-OS-000480-GPOS-00227\"]\n tag gid: \"V-71985\"\n tag rid: \"SV-86609r2_rule\"\n tag stig_id: \"RHEL-07-020110\"\n tag fix_id: \"F-78337r2_fix\"\n tag cci: [\"CCI-000366\", \"CCI-000778\", \"CCI-001958\"]\n tag nist: [\"CM-6 b\", \"IA-3\", \"IA-3\"]\n\n describe systemd_service('autofs.service') do\n it { should_not be_running }\n it { should_not be_enabled }\n it { should_not be_installed }\n end\nend\n","desc":"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.","descriptions":[{"data":"Automatically mounting file systems permits easy introduction of\nunknown devices, thereby facilitating malicious activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system disables the ability to automount devices.\n\n Check to see if automounter service is active with the following command:\n\n # systemctl status autofs\n autofs.service - Automounts filesystems on demand\n Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)\n Active: inactive (dead)\n\n If the \"autofs\" status is set to \"active\" and is not documented with\nthe Information System Security Officer (ISSO) as an operational requirement,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to automount devices.\n\n Turn off the automount service with the following commands:\n\n # systemctl stop autofs\n # systemctl disable autofs\n\n If \"autofs\" is required for Network File System (NFS), it must be\ndocumented with the ISSO.","label":"fix"}],"id":"V-71985","impact":0.5,"refs":[],"results":[{"code_desc":"Service autofs.service is expected not to be running","run_time":0.103984815,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"systemd_service","resource_params":"[\"autofs.service\"]"},{"code_desc":"Service autofs.service is expected not to be enabled","run_time":0.000204906,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"systemd_service","resource_params":"[\"autofs.service\"]"},{"code_desc":"Service autofs.service is expected not to be installed","run_time":0.000135709,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"systemd_service","resource_params":"[\"autofs.service\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71985.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000114-GPOS-00059","satisfies":["SRG-OS-000114-GPOS-00059","SRG-OS-000378-GPOS-00163","SRG-OS-000480-GPOS-00227"],"gid":"V-71985","rid":"SV-86609r2_rule","stig_id":"RHEL-07-020110","fix_id":"F-78337r2_fix","cci":["CCI-000366","CCI-000778","CCI-001958"],"nist":["CM-6 b","IA-3","IA-3"]},"title":"The Red Hat Enterprise Linux operating system must disable the file\nsystem automounter unless required.","waiver_data":{}},{"code":"control \"V-71987\" do\n title \"The Red Hat Enterprise Linux operating system must remove all software\ncomponents after updated versions have been installed.\"\n desc \"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system removes all software components after updated\nversions have been installed.\n\n Check if yum is configured to remove unneeded packages with the following\ncommand:\n\n # grep -i clean_requirements_on_remove /etc/yum.conf\n clean_requirements_on_remove=1\n\n If \\\"clean_requirements_on_remove\\\" is not set to \\\"1\\\", \\\"True\\\", or\n\\\"yes\\\", or is not set in \\\"/etc/yum.conf\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to remove all software components after\nupdated versions have been installed.\n\n Set the \\\"clean_requirements_on_remove\\\" option to \\\"1\\\" in the\n\\\"/etc/yum.conf\\\" file:\n\n clean_requirements_on_remove=1\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000437-GPOS-00194\"\n tag gid: \"V-71987\"\n tag rid: \"SV-86611r2_rule\"\n tag stig_id: \"RHEL-07-020200\"\n tag fix_id: \"F-78339r1_fix\"\n tag cci: [\"CCI-002617\"]\n tag nist: [\"SI-2 (6)\"]\n\n describe parse_config_file(\"/etc/yum.conf\") do\n its('main.clean_requirements_on_remove') { should match %r{1|True|yes}i }\n end\nend\n","desc":"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.","descriptions":[{"data":"Previous versions of software components that are not removed from the\ninformation system after updates have been installed may be exploited by\nadversaries. Some information technology products may remove older versions of\nsoftware automatically from the information system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system removes all software components after updated\nversions have been installed.\n\n Check if yum is configured to remove unneeded packages with the following\ncommand:\n\n # grep -i clean_requirements_on_remove /etc/yum.conf\n clean_requirements_on_remove=1\n\n If \"clean_requirements_on_remove\" is not set to \"1\", \"True\", or\n\"yes\", or is not set in \"/etc/yum.conf\", this is a finding.","label":"check"},{"data":"Configure the operating system to remove all software components after\nupdated versions have been installed.\n\n Set the \"clean_requirements_on_remove\" option to \"1\" in the\n\"/etc/yum.conf\" file:\n\n clean_requirements_on_remove=1","label":"fix"}],"id":"V-71987","impact":0.3,"refs":[],"results":[{"code_desc":"Parse Config File /etc/yum.conf main.clean_requirements_on_remove is expected to match /1|True|yes/i","message":"expected nil to match /1|True|yes/i","run_time":0.000351809,"start_time":"2022-03-06T22:05:49+00:00","status":"failed","resource_class":"parse_config_file","resource_params":"[\"/etc/yum.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71987.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000437-GPOS-00194","gid":"V-71987","rid":"SV-86611r2_rule","stig_id":"RHEL-07-020200","fix_id":"F-78339r1_fix","cci":["CCI-002617"],"nist":["SI-2 (6)"]},"title":"The Red Hat Enterprise Linux operating system must remove all software\ncomponents after updated versions have been installed.","waiver_data":{}},{"code":"control \"V-71989\" do\n title \"The Red Hat Enterprise Linux operating system must enable SELinux.\"\n desc \"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \\\"SELinux\\\" is active and in \\\"Enforcing\\\" mode with the following\ncommand:\n\n # getenforce\n Enforcing\n\n If \\\"SELinux\\\" is not active and not in \\\"Enforcing\\\" mode, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \\\"SELinux\\\" status and the \\\"Enforcing\\\" mode by modifying the\n\\\"/etc/selinux/config\\\" file to have the following line:\n\n SELINUX=enforcing\n\n A reboot is required for the changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000445-GPOS-00199\"\n tag gid: \"V-71989\"\n tag rid: \"SV-86613r3_rule\"\n tag stig_id: \"RHEL-07-020210\"\n tag fix_id: \"F-78341r2_fix\"\n tag cci: [\"CCI-002165\", \"CCI-002696\"]\n tag nist: [\"AC-3 (4)\", \"SI-6 a\"]\n\n\n if package('MFEhiplsm').installed? && processes(/hipclient/).exist?\n impact 0.0\n describe \"HIPS is active on the system\" do\n skip \"A HIPS process is active on the system, this control is Not Applicable.\"\n end\n elsif service('cma').installed? && service('cma').enabled?\n impact 0.0\n describe \"HBSS is active on the system\" do\n skip \"A HBSS service is active on the system, this control is Not Applicable.\"\n end\n else\n impact 0.7\n describe command('getenforce') do\n its('stdout.strip') { should eq 'Enforcing' }\n end\n end\nend\n","desc":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","descriptions":[{"data":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \"SELinux\" is active and in \"Enforcing\" mode with the following\ncommand:\n\n # getenforce\n Enforcing\n\n If \"SELinux\" is not active and not in \"Enforcing\" mode, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \"SELinux\" status and the \"Enforcing\" mode by modifying the\n\"/etc/selinux/config\" file to have the following line:\n\n SELINUX=enforcing\n\n A reboot is required for the changes to take effect.","label":"fix"}],"id":"V-71989","impact":0.7,"refs":[],"results":[{"code_desc":"Command: `getenforce` stdout.strip is expected to eq \"Enforcing\"","run_time":0.083677819,"start_time":"2022-03-06T22:05:49+00:00","status":"passed","resource_class":"command","resource_params":"[\"getenforce\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71989.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000445-GPOS-00199","gid":"V-71989","rid":"SV-86613r3_rule","stig_id":"RHEL-07-020210","fix_id":"F-78341r2_fix","cci":["CCI-002165","CCI-002696"],"nist":["AC-3 (4)","SI-6 a"]},"title":"The Red Hat Enterprise Linux operating system must enable SELinux.","waiver_data":{}},{"code":"control \"V-71991\" do\n title \"The Red Hat Enterprise Linux operating system must enable the SELinux\ntargeted policy.\"\n desc \"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \\\"SELinux\\\" is active and is enforcing the targeted policy with\nthe following command:\n\n # sestatus\n\n SELinux status: enabled\n\n SELinuxfs mount: /selinux\n\n SELinux root directory: /etc/selinux\n\n Loaded policy name: targeted\n\n Current mode: enforcing\n\n Mode from config file: enforcing\n\n Policy MLS status: enabled\n\n Policy deny_unknown status: allowed\n\n Max kernel policy version: 28\n\n If the \\\"Loaded policy name\\\" is not set to \\\"targeted\\\", this is a finding.\n\n Verify that the /etc/selinux/config file is configured to the\n\\\"SELINUXTYPE\\\" to \\\"targeted\\\":\n\n # grep -i \\\"selinuxtype\\\" /etc/selinux/config | grep -v '^#'\n\n SELINUXTYPE = targeted\n\n If no results are returned or \\\"SELINUXTYPE\\\" is not set to \\\"targeted\\\",\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \\\"SELinuxtype\\\" to the \\\"targeted\\\" policy by modifying the\n\\\"/etc/selinux/config\\\" file to have the following line:\n\n SELINUXTYPE=targeted\n\n A reboot is required for the changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000445-GPOS-00199\"\n tag gid: \"V-71991\"\n tag rid: \"SV-86615r5_rule\"\n tag stig_id: \"RHEL-07-020220\"\n tag fix_id: \"F-78343r2_fix\"\n tag cci: [\"CCI-002165\", \"CCI-002696\"]\n tag nist: [\"AC-3 (4)\", \"SI-6 a\"]\n\n describe.one do\n describe command('sestatus') do\n its('stdout') { should match %r{^Policy\\sfrom\\sconfigs\\sfile:\\s+targeted\\n?$} }\n end\n describe command('sestatus') do\n its('stdout') { should match %r{^Loaded\\spolicy\\sname:\\s+targeted\\n?$} }\n end\n end\nend\n","desc":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","descriptions":[{"data":"Without verification of the security functions, security functions may\nnot operate correctly and the failure may go unnoticed. Security function is\ndefined as the hardware, software, and/or firmware of the information system\nresponsible for enforcing the system security policy and supporting the\nisolation of code and data on which the protection is based. Security\nfunctionality includes, but is not limited to, establishing system accounts,\nconfiguring access authorizations (i.e., permissions, privileges), setting\nevents to be audited, and setting intrusion detection parameters.\n\n This requirement applies to operating systems performing security function\nverification/testing and/or systems and environments that require this\nfunctionality.","label":"default"},{"data":"","label":"rationale"},{"data":"If an HBSS or HIPS is active on the system, this is Not Applicable.\n\n Verify the operating system verifies correct operation of all security\nfunctions.\n\n Check if \"SELinux\" is active and is enforcing the targeted policy with\nthe following command:\n\n # sestatus\n\n SELinux status: enabled\n\n SELinuxfs mount: /selinux\n\n SELinux root directory: /etc/selinux\n\n Loaded policy name: targeted\n\n Current mode: enforcing\n\n Mode from config file: enforcing\n\n Policy MLS status: enabled\n\n Policy deny_unknown status: allowed\n\n Max kernel policy version: 28\n\n If the \"Loaded policy name\" is not set to \"targeted\", this is a finding.\n\n Verify that the /etc/selinux/config file is configured to the\n\"SELINUXTYPE\" to \"targeted\":\n\n # grep -i \"selinuxtype\" /etc/selinux/config | grep -v '^#'\n\n SELINUXTYPE = targeted\n\n If no results are returned or \"SELINUXTYPE\" is not set to \"targeted\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to verify correct operation of all security\nfunctions.\n\n Set the \"SELinuxtype\" to the \"targeted\" policy by modifying the\n\"/etc/selinux/config\" file to have the following line:\n\n SELINUXTYPE=targeted\n\n A reboot is required for the changes to take effect.","label":"fix"}],"id":"V-71991","impact":0.7,"refs":[],"results":[{"code_desc":"Command: `sestatus` stdout is expected to match /^Loaded\\spolicy\\sname:\\s+targeted\\n?$/","run_time":0.000263898,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"command","resource_params":"[\"sestatus\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71991.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000445-GPOS-00199","gid":"V-71991","rid":"SV-86615r5_rule","stig_id":"RHEL-07-020220","fix_id":"F-78343r2_fix","cci":["CCI-002165","CCI-002696"],"nist":["AC-3 (4)","SI-6 a"]},"title":"The Red Hat Enterprise Linux operating system must enable the SELinux\ntargeted policy.","waiver_data":{}},{"code":"control \"V-71993\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled on the command line.\"\n desc \"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active with the\nfollowing command:\n\n # systemctl status ctrl-alt-del.target\n\n ctrl-alt-del.target\n Loaded: masked (/dev/null; bad)\n Active: inactive (dead)\n\n If the ctrl-alt-del.target is not masked, this is a finding.\n\n If the ctrl-alt-del.target is active, this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to disable the Ctrl-Alt-Delete sequence for the\ncommand line with the following command:\n\n # systemctl mask ctrl-alt-del.target\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71993\"\n tag rid: \"SV-86617r5_rule\"\n tag stig_id: \"RHEL-07-020230\"\n tag fix_id: \"F-78345r6_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe systemd_service('ctrl-alt-del.target') do\n it { should_not be_running }\n it { should_not be_enabled }\n end\nend\n","desc":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","descriptions":[{"data":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active with the\nfollowing command:\n\n # systemctl status ctrl-alt-del.target\n\n ctrl-alt-del.target\n Loaded: masked (/dev/null; bad)\n Active: inactive (dead)\n\n If the ctrl-alt-del.target is not masked, this is a finding.\n\n If the ctrl-alt-del.target is active, this is a finding.","label":"check"},{"data":"Configure the system to disable the Ctrl-Alt-Delete sequence for the\ncommand line with the following command:\n\n # systemctl mask ctrl-alt-del.target","label":"fix"}],"id":"V-71993","impact":0.7,"refs":[],"results":[{"code_desc":"Service ctrl-alt-del.target is expected not to be running","run_time":0.462182335,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"systemd_service","resource_params":"[\"ctrl-alt-del.target\"]"},{"code_desc":"Service ctrl-alt-del.target is expected not to be enabled","run_time":0.000218747,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"systemd_service","resource_params":"[\"ctrl-alt-del.target\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71993.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71993","rid":"SV-86617r5_rule","stig_id":"RHEL-07-020230","fix_id":"F-78345r6_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled on the command line.","waiver_data":{}},{"code":"control \"V-71995\" do\n title \"The Red Hat Enterprise Linux operating system must define default\npermissions for all authenticated users in such a way that the user can only\nread and modify their own files.\"\n desc \"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system defines default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Check for the value of the \\\"UMASK\\\" parameter in \\\"/etc/login.defs\\\" file\nwith the following command:\n\n Note: If the value of the \\\"UMASK\\\" parameter is set to \\\"000\\\" in\n\\\"/etc/login.defs\\\" file, the Severity is raised to a CAT I.\n\n # grep -i umask /etc/login.defs\n UMASK 077\n\n If the value for the \\\"UMASK\\\" parameter is not \\\"077\\\", or the \\\"UMASK\\\"\nparameter is missing or is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to define default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Add or edit the line for the \\\"UMASK\\\" parameter in \\\"/etc/login.defs\\\"\nfile to \\\"077\\\":\n\n UMASK 077\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00228\"\n tag gid: \"V-71995\"\n tag rid: \"SV-86619r2_rule\"\n tag stig_id: \"RHEL-07-020240\"\n tag fix_id: \"F-78347r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n\n if login_defs.read_params[\"UMASK\"].eql?('000')\n impact 0.7\n else\n impact 0.5\n end\n describe login_defs do\n its('UMASK') { should eq '077' }\n end\nend\n","desc":"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.","descriptions":[{"data":"Setting the most restrictive default permissions ensures that when new\naccounts are created, they do not have unnecessary access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system defines default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Check for the value of the \"UMASK\" parameter in \"/etc/login.defs\" file\nwith the following command:\n\n Note: If the value of the \"UMASK\" parameter is set to \"000\" in\n\"/etc/login.defs\" file, the Severity is raised to a CAT I.\n\n # grep -i umask /etc/login.defs\n UMASK 077\n\n If the value for the \"UMASK\" parameter is not \"077\", or the \"UMASK\"\nparameter is missing or is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to define default permissions for all\nauthenticated users in such a way that the user can only read and modify their\nown files.\n\n Add or edit the line for the \"UMASK\" parameter in \"/etc/login.defs\"\nfile to \"077\":\n\n UMASK 077","label":"fix"}],"id":"V-71995","impact":0.5,"refs":[],"results":[{"code_desc":"login.defs UMASK is expected to eq \"077\"","run_time":0.001082511,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"login_defs","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71995.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00228","gid":"V-71995","rid":"SV-86619r2_rule","stig_id":"RHEL-07-020240","fix_id":"F-78347r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must define default\npermissions for all authenticated users in such a way that the user can only\nread and modify their own files.","waiver_data":{}},{"code":"control \"V-71997\" do\n title \"The Red Hat Enterprise Linux operating system must be a vendor\nsupported release.\"\n desc \"An operating system release is considered \\\"supported\\\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the version of the operating system is vendor supported.\n\n Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n Red Hat Enterprise Linux Server release 7.4 (Maipo)\n\n Current End of Life for RHEL 7.1 is 31 March 2017.\n\n Current End of Life for RHEL 7.2 is 30 November 2017.\n\n Current End of Life for RHEL 7.3 is 30 November 2018.\n\n Current End of Life for RHEL 7.4 is 31 August 2019.\n\n Current End of Life for RHEL 7.5 is 30 April 2020.\n\n Current End of Life for RHEL 7.6 is 31 October 2020.\n\n Current End of Life for RHEL 7.7 is 30 August 2021.\n\n If the release is not supported by the vendor, this is a finding.\n \"\n desc \"fix\", \"Upgrade to a supported version of the operating system.\"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71997\"\n tag rid: \"SV-86621r5_rule\"\n tag stig_id: \"RHEL-07-020250\"\n tag fix_id: \"F-78349r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe file('/etc/redhat-release') do\n its('content') { should match %r{Release (6.7*|7.[2-9].*)}i }\n end\nend\n","desc":"An operating system release is considered \"supported\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.","descriptions":[{"data":"An operating system release is considered \"supported\" if the vendor\ncontinues to provide security patches for the product. With an unsupported\nrelease, it will not be possible to resolve security issues discovered in the\nsystem software.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the version of the operating system is vendor supported.\n\nCheck the version of the operating system with the following command:\n\n# cat /etc/redhat-release\n\nRed Hat Enterprise Linux Server release 7.4 (Maipo)\n\nCurrent End of Life for RHEL 7.1 is 31 March 2017.\n\nCurrent End of Life for RHEL 7.2 is 30 November 2017.\n\nCurrent End of Life for RHEL 7.3 is 30 November 2018.\n\nCurrent End of Life for RHEL 7.4 is 31 August 2019.\n\nCurrent End of Life for RHEL 7.5 is 30 April 2020.\n\nCurrent End of Life for RHEL 7.6 is 31 October 2020.\n\nCurrent End of Life for RHEL 7.7 is 30 August 2021.\n\nIf the release is not supported by the vendor, this is a finding.","label":"check"},{"data":"Upgrade to a supported version of the operating system.","label":"fix"}],"id":"V-71997","impact":0.7,"refs":[],"results":[{"code_desc":"File /etc/redhat-release content is expected to match /Release (6.7*|7.[2-9].*)/i","run_time":0.000323242,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/redhat-release\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71997.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71997","rid":"SV-86621r5_rule","stig_id":"RHEL-07-020250","fix_id":"F-78349r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be a vendor\nsupported release.","waiver_data":{}},{"code":"control \"V-71999\" do\n title \"The Red Hat Enterprise Linux operating system security patches and\n updates must be installed and up to date.\"\n desc \"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.\"\n\n desc \"check\", \"Verify the operating system security patches and updates are installed and\n up to date. Updates are required to be applied with a frequency determined by\n the site or Program Management Office (PMO).\n\n Obtain the list of available package security updates from Red Hat. The URL\n for updates is https://rhn.redhat.com/errata/. It is important to note that\n updates provided by Red Hat may not be present on the system if the underlying\n packages are not installed.\n\n Check that the available package security updates have been installed on\n the system with the following command:\n\n # yum history list | more\n Loaded plugins: langpacks, product-id, subscription-manager\n ID | Command line | Date and time | Action(s) |\n Altered\n\n -------------------------------------------------------------------------------\n 70 | install aide | 2016-05-05 10:58 | Install |\n 1\n 69 | update -y | 2016-05-04 14:34 | Update | 18 EE\n 68 | install vlc | 2016-04-21 17:12 | Install |\n 21\n 67 | update -y | 2016-04-21 17:04 | Update | 7 EE\n 66 | update -y | 2016-04-15 16:47 | E, I, U |\n 84 EE\n\n If package updates have not been performed on the system within the\n timeframe that the site/program documentation requires, this is a finding.\n\n If the operating system is in non-compliance with the Information Assurance\nVulnerability Management (IAVM) process, this is a finding.\n \"\n desc \"fix\", \"Install the operating system patches or updated packages\navailable from Red Hat within 30 days or sooner as local policy dictates.\"\n impact 0.5\n tag severity: 'medium'\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-71999\"\n tag rid: \"SV-86623r4_rule\"\n tag stig_id: \"RHEL-07-020260\"\n tag fix_id: \"F-78351r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if input('disconnected_system')\n describe \"The system is set to a `disconnected` state and you must validate \n the state of the system packages manually\" do \n skip \"The system is set to a `disconnected` state and you must validate \n the state of the system packages manually, or through another process, if you \n have an established update and patch process, please set this control as \n `Not Applicable` with a `caevat` via an overlay.\"\n end\n else\n updates = linux_update.updates\n package_names = updates.map { |h| h[\"name\"] }\n\n describe.one do\n describe \"List of out-of-date packages\" do\n subject { package_names }\n it { should be_empty }\n end\n\n updates.each do |update|\n describe package(update[\"name\"]) do\n its(\"version\") { should eq update[\"version\"] }\n end\n end\n end\n end\n end\n","desc":"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.","descriptions":[{"data":"Timely patching is critical for maintaining the operational\n availability, confidentiality, and integrity of information technology (IT)\n systems. However, failure to keep operating system and application software\n patched is a common mistake made by IT professionals. New patches are released\n daily, and it is often difficult for even experienced System Administrators to\n keep abreast of all the new patches. When new weaknesses in an operating system\n exist, patches are usually made available by the vendor to resolve the\n problems. If the most recent security patches and updates are not installed,\n unauthorized users may take advantage of weaknesses in the unpatched software.\n The lack of prompt attention to patching could result in a system compromise.","label":"default"},{"data":"Verify the operating system security patches and updates are installed and\n up to date. Updates are required to be applied with a frequency determined by\n the site or Program Management Office (PMO).\n\n Obtain the list of available package security updates from Red Hat. The URL\n for updates is https://rhn.redhat.com/errata/. It is important to note that\n updates provided by Red Hat may not be present on the system if the underlying\n packages are not installed.\n\n Check that the available package security updates have been installed on\n the system with the following command:\n\n # yum history list | more\n Loaded plugins: langpacks, product-id, subscription-manager\n ID | Command line | Date and time | Action(s) |\n Altered\n\n -------------------------------------------------------------------------------\n 70 | install aide | 2016-05-05 10:58 | Install |\n 1\n 69 | update -y | 2016-05-04 14:34 | Update | 18 EE\n 68 | install vlc | 2016-04-21 17:12 | Install |\n 21\n 67 | update -y | 2016-04-21 17:04 | Update | 7 EE\n 66 | update -y | 2016-04-15 16:47 | E, I, U |\n 84 EE\n\n If package updates have not been performed on the system within the\n timeframe that the site/program documentation requires, this is a finding.\n\n If the operating system is in non-compliance with the Information Assurance\nVulnerability Management (IAVM) process, this is a finding.","label":"check"},{"data":"Install the operating system patches or updated packages\navailable from Red Hat within 30 days or sooner as local policy dictates.","label":"fix"}],"id":"V-71999","impact":0.5,"refs":[],"results":[{"code_desc":"List of out-of-date packages is expected to be empty","exception":"RSpec::Core::MultipleExceptionError","message":"expected `[\"postgresql12-devel\", \"postgresql12-server\", \"postgresql12-docs\", \"bind-export-libs\", \"kernel-header..., \"bind-libs-lite\", \"cyrus-sasl\", \"cyrus-sasl-lib\", \"oniguruma\", \"nodejs-libs\", \"samba-common-libs\"].empty?` to be truthy, got false","run_time":0.001319238,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"System Package postgresql12-devel version is expected to eq \"12.10-1PGDG.rhel7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"12.10-1PGDG.rhel7\"\n got: \"12.9-1PGDG.rhel7\"\n\n(compared using ==)\n","run_time":0.000895898,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"postgresql12-devel\"]"},{"code_desc":"System Package postgresql12-server version is expected to eq \"12.10-1PGDG.rhel7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"12.10-1PGDG.rhel7\"\n got: \"12.9-1PGDG.rhel7\"\n\n(compared using ==)\n","run_time":0.000681408,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"postgresql12-server\"]"},{"code_desc":"System Package postgresql12-docs version is expected to eq \"12.10-1PGDG.rhel7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"12.10-1PGDG.rhel7\"\n got: \"12.9-1PGDG.rhel7\"\n\n(compared using ==)\n","run_time":0.000888235,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"postgresql12-docs\"]"},{"code_desc":"System Package bind-export-libs version is expected to eq \"9.11.4-26.P2.el7_9.9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"9.11.4-26.P2.el7_9.9\"\n got: \"9.11.4-26.P2.el7_9.8\"\n\n(compared using ==)\n","run_time":0.000768399,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"bind-export-libs\"]"},{"code_desc":"System Package kernel-headers version is expected to eq \"3.10.0-1160.59.1.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"3.10.0-1160.59.1.el7\"\n got: \"3.10.0-1160.53.1.el7\"\n\n(compared using ==)\n","run_time":0.000633197,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"kernel-headers\"]"},{"code_desc":"System Package openldap-devel version is expected to eq \"2.4.44-25.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"2.4.44-25.el7_9\"\n got: \"2.4.44-24.el7_9\"\n\n(compared using ==)\n","run_time":0.000632105,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"openldap-devel\"]"},{"code_desc":"System Package mssql-tools version is expected to eq \"17.9.1.1-1\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"17.9.1.1-1\"\n got: \"17.8.1.2-1\"\n\n(compared using ==)\n","run_time":0.000439643,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"mssql-tools\"]"},{"code_desc":"System Package epel-release version is expected to eq \"7-14\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"7-14\"\n got: \"7-11\"\n\n(compared using ==)\n","run_time":0.00064153,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"epel-release\"]"},{"code_desc":"System Package nodejs-docs version is expected to eq \"16.14.0-2.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"16.14.0-2.el7\"\n got: \"16.13.2-3.el7\"\n\n(compared using ==)\n","run_time":0.001147053,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"nodejs-docs\"]"},{"code_desc":"System Package bind-license version is expected to eq \"9.11.4-26.P2.el7_9.9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"9.11.4-26.P2.el7_9.9\"\n got: \"9.11.4-26.P2.el7_9.8\"\n\n(compared using ==)\n","run_time":0.001235699,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"bind-license\"]"},{"code_desc":"System Package openldap version is expected to eq \"2.4.44-25.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"2.4.44-25.el7_9\"\n got: \"2.4.44-24.el7_9\"\n\n(compared using ==)\n","run_time":0.002047235,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"openldap\"]"},{"code_desc":"System Package npm version is expected to eq \"8.3.1-1.16.14.0.2.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"8.3.1-1.16.14.0.2.el7\"\n got: \"8.1.2-1.16.13.2.3.el7\"\n\n(compared using ==)\n","run_time":0.001392324,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"npm\"]"},{"code_desc":"System Package cyrus-sasl-devel version is expected to eq \"2.1.26-24.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"2.1.26-24.el7_9\"\n got: \"2.1.26-23.el7\"\n\n(compared using ==)\n","run_time":0.001814768,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"cyrus-sasl-devel\"]"},{"code_desc":"System Package postgresql12-contrib version is expected to eq \"12.10-1PGDG.rhel7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"12.10-1PGDG.rhel7\"\n got: \"12.9-1PGDG.rhel7\"\n\n(compared using ==)\n","run_time":0.001735839,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"postgresql12-contrib\"]"},{"code_desc":"System Package nodejs version is expected to eq \"16.14.0-2.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"16.14.0-2.el7\"\n got: \"16.13.2-3.el7\"\n\n(compared using ==)\n","run_time":0.00065521,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"nodejs\"]"},{"code_desc":"System Package kernel version is expected to eq \"3.10.0-1160.59.1.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"3.10.0-1160.59.1.el7\"\n got: \"3.10.0-1160.53.1.el7\"\n\n(compared using ==)\n","run_time":0.001223106,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"kernel\"]"},{"code_desc":"System Package kernel-tools-libs version is expected to eq \"3.10.0-1160.59.1.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"3.10.0-1160.59.1.el7\"\n got: \"3.10.0-1160.53.1.el7\"\n\n(compared using ==)\n","run_time":0.00055483,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"kernel-tools-libs\"]"},{"code_desc":"System Package samba-client-libs version is expected to eq \"4.10.16-18.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"4.10.16-18.el7_9\"\n got: \"4.10.16-17.el7_9\"\n\n(compared using ==)\n","run_time":0.00049744,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"samba-client-libs\"]"},{"code_desc":"System Package kernel-tools version is expected to eq \"3.10.0-1160.59.1.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"3.10.0-1160.59.1.el7\"\n got: \"3.10.0-1160.53.1.el7\"\n\n(compared using ==)\n","run_time":0.000488482,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"kernel-tools\"]"},{"code_desc":"System Package postgresql12-libs version is expected to eq \"12.10-1PGDG.rhel7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"12.10-1PGDG.rhel7\"\n got: \"12.9-1PGDG.rhel7\"\n\n(compared using ==)\n","run_time":0.000654141,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"postgresql12-libs\"]"},{"code_desc":"System Package postgresql12 version is expected to eq \"12.10-1PGDG.rhel7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"12.10-1PGDG.rhel7\"\n got: \"12.9-1PGDG.rhel7\"\n\n(compared using ==)\n","run_time":0.000661786,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"postgresql12\"]"},{"code_desc":"System Package nodejs-full-i18n version is expected to eq \"16.14.0-2.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"16.14.0-2.el7\"\n got: \"16.13.2-3.el7\"\n\n(compared using ==)\n","run_time":0.000596313,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"nodejs-full-i18n\"]"},{"code_desc":"System Package msodbcsql17 version is expected to eq \"17.9.1.1-1\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"17.9.1.1-1\"\n got: \"17.8.1.2-1\"\n\n(compared using ==)\n","run_time":0.000685478,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"msodbcsql17\"]"},{"code_desc":"System Package docker-common version is expected to eq \"1.13.1-209.git7d71120.el7.centos\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"1.13.1-209.git7d71120.el7.centos\"\n got: \"1.13.1-208.git7d71120.el7_9\"\n\n(compared using ==)\n","run_time":0.000586024,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"docker-common\"]"},{"code_desc":"System Package docker version is expected to eq \"1.13.1-209.git7d71120.el7.centos\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"1.13.1-209.git7d71120.el7.centos\"\n got: \"1.13.1-208.git7d71120.el7_9\"\n\n(compared using ==)\n","run_time":0.000608955,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"docker\"]"},{"code_desc":"System Package libwbclient version is expected to eq \"4.10.16-18.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"4.10.16-18.el7_9\"\n got: \"4.10.16-17.el7_9\"\n\n(compared using ==)\n","run_time":0.000495388,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"libwbclient\"]"},{"code_desc":"System Package jq version is expected to eq \"1.6-2.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"1.6-2.el7\"\n got: \"1.5-1.0.1.el7\"\n\n(compared using ==)\n","run_time":0.001556774,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"jq\"]"},{"code_desc":"System Package python-perf version is expected to eq \"3.10.0-1160.59.1.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"3.10.0-1160.59.1.el7\"\n got: \"3.10.0-1160.53.1.el7\"\n\n(compared using ==)\n","run_time":0.000890851,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"python-perf\"]"},{"code_desc":"System Package aide version is expected to eq \"0.15.1-13.el7_9.1\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"0.15.1-13.el7_9.1\"\n got: \"0.15.1-13.el7\"\n\n(compared using ==)\n","run_time":0.000873699,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"aide\"]"},{"code_desc":"System Package docker-client version is expected to eq \"1.13.1-209.git7d71120.el7.centos\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"1.13.1-209.git7d71120.el7.centos\"\n got: \"1.13.1-208.git7d71120.el7_9\"\n\n(compared using ==)\n","run_time":0.000550517,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"docker-client\"]"},{"code_desc":"System Package samba-common version is expected to eq \"4.10.16-18.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"4.10.16-18.el7_9\"\n got: \"4.10.16-17.el7_9\"\n\n(compared using ==)\n","run_time":0.000515097,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"samba-common\"]"},{"code_desc":"System Package bind-libs-lite version is expected to eq \"9.11.4-26.P2.el7_9.9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"9.11.4-26.P2.el7_9.9\"\n got: \"9.11.4-26.P2.el7_9.8\"\n\n(compared using ==)\n","run_time":0.000484928,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"bind-libs-lite\"]"},{"code_desc":"System Package cyrus-sasl version is expected to eq \"2.1.26-24.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"2.1.26-24.el7_9\"\n got: \"2.1.26-23.el7\"\n\n(compared using ==)\n","run_time":0.00050099,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"cyrus-sasl\"]"},{"code_desc":"System Package cyrus-sasl-lib version is expected to eq \"2.1.26-24.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"2.1.26-24.el7_9\"\n got: \"2.1.26-23.el7\"\n\n(compared using ==)\n","run_time":0.000512084,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"cyrus-sasl-lib\"]"},{"code_desc":"System Package oniguruma version is expected to eq \"6.8.2-1.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"6.8.2-1.el7\"\n got: \"5.9.5-3.el7\"\n\n(compared using ==)\n","run_time":0.000523107,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"oniguruma\"]"},{"code_desc":"System Package nodejs-libs version is expected to eq \"16.14.0-2.el7\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"16.14.0-2.el7\"\n got: \"16.13.2-3.el7\"\n\n(compared using ==)\n","run_time":0.000494033,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"nodejs-libs\"]"},{"code_desc":"System Package samba-common-libs version is expected to eq \"4.10.16-18.el7_9\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: \"4.10.16-18.el7_9\"\n got: \"4.10.16-17.el7_9\"\n\n(compared using ==)\n","run_time":0.000502462,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"package","resource_params":"[\"samba-common-libs\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-71999.rb"},"tags":{"severity":"medium","gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-71999","rid":"SV-86623r4_rule","stig_id":"RHEL-07-020260","fix_id":"F-78351r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system security patches and\n updates must be installed and up to date.","waiver_data":{}},{"code":"control \"V-72001\" do\n title \"The Red Hat Enterprise Linux operating system must not have\nunnecessary accounts.\"\n desc \"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all accounts on the system are assigned to an active system,\napplication, or user account.\n\n Obtain the list of authorized system accounts from the Information System\nSecurity Officer (ISSO).\n\n Check the system accounts on the system with the following command:\n\n # more /etc/passwd\n root:x:0:0:root:/root:/bin/bash\n bin:x:1:1:bin:/bin:/sbin/nologin\n daemon:x:2:2:daemon:/sbin:/sbin/nologin\n sync:x:5:0:sync:/sbin:/bin/sync\n shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown\n halt:x:7:0:halt:/sbin:/sbin/halt\n games:x:12:100:games:/usr/games:/sbin/nologin\n gopher:x:13:30:gopher:/var/gopher:/sbin/nologin\n\n Accounts such as \\\"games\\\" and \\\"gopher\\\" are not authorized accounts as\nthey do not support authorized system functions.\n\n If the accounts on the system do not match the provided documentation, or\naccounts that do not support an authorized system function are present, this is\na finding.\n \"\n desc \"fix\", \"\n Configure the system so all accounts on the system are assigned to an\nactive system, application, or user account.\n\n Remove accounts that do not support approved system activities or that\nallow for a normal user to perform administrative-level actions.\n\n Document all authorized accounts on the system.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72001\"\n tag rid: \"SV-86625r2_rule\"\n tag stig_id: \"RHEL-07-020270\"\n tag fix_id: \"F-78353r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n known_system_accounts = input('known_system_accounts')\n user_accounts = input('user_accounts')\n\n allowed_accounts = (known_system_accounts + user_accounts).uniq\n passwd.users.each do |user|\n describe user do\n it \"is listed in allowed users.\" do\n expect(subject).to(be_in allowed_accounts)\n end\n end\n end\nend\n","desc":"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.","descriptions":[{"data":"Accounts providing no operational purpose provide additional\nopportunities for system compromise. Unnecessary accounts include user accounts\nfor individuals not requiring access to the system and application accounts for\napplications not installed on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all accounts on the system are assigned to an active system,\napplication, or user account.\n\n Obtain the list of authorized system accounts from the Information System\nSecurity Officer (ISSO).\n\n Check the system accounts on the system with the following command:\n\n # more /etc/passwd\n root:x:0:0:root:/root:/bin/bash\n bin:x:1:1:bin:/bin:/sbin/nologin\n daemon:x:2:2:daemon:/sbin:/sbin/nologin\n sync:x:5:0:sync:/sbin:/bin/sync\n shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown\n halt:x:7:0:halt:/sbin:/sbin/halt\n games:x:12:100:games:/usr/games:/sbin/nologin\n gopher:x:13:30:gopher:/var/gopher:/sbin/nologin\n\n Accounts such as \"games\" and \"gopher\" are not authorized accounts as\nthey do not support authorized system functions.\n\n If the accounts on the system do not match the provided documentation, or\naccounts that do not support an authorized system function are present, this is\na finding.","label":"check"},{"data":"Configure the system so all accounts on the system are assigned to an\nactive system, application, or user account.\n\n Remove accounts that do not support approved system activities or that\nallow for a normal user to perform administrative-level actions.\n\n Document all authorized accounts on the system.","label":"fix"}],"id":"V-72001","impact":0.5,"refs":[],"results":[{"code_desc":"root is listed in allowed users.","run_time":0.000471524,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"bin is listed in allowed users.","run_time":0.000148694,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"daemon is listed in allowed users.","run_time":0.000167644,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"adm is listed in allowed users.","run_time":0.000141687,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"lp is listed in allowed users.","run_time":0.000124653,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"sync is listed in allowed users.","run_time":0.000140141,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"shutdown is listed in allowed users.","run_time":0.000134696,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"halt is listed in allowed users.","run_time":0.000123351,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"mail is listed in allowed users.","run_time":0.000122111,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"operator is listed in allowed users.","run_time":0.000117801,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"games is listed in allowed users.","message":"expected `games` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000194427,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"ftp is listed in allowed users.","message":"expected `ftp` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000187924,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"nobody is listed in allowed users.","run_time":0.000167944,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"systemd-network is listed in allowed users.","run_time":0.000127769,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"dbus is listed in allowed users.","run_time":0.000125785,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"polkitd is listed in allowed users.","run_time":0.000128084,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"rpc is listed in allowed users.","message":"expected `rpc` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.00019956,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"rpcuser is listed in allowed users.","message":"expected `rpcuser` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000186334,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"nfsnobody is listed in allowed users.","message":"expected `nfsnobody` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000202157,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"sshd is listed in allowed users.","run_time":0.00013411,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"postfix is listed in allowed users.","run_time":0.000652663,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"chrony is listed in allowed users.","run_time":0.000341163,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"vagrant is listed in allowed users.","message":"expected `vagrant` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000407584,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"vboxadd is listed in allowed users.","message":"expected `vboxadd` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000227944,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"dockerroot is listed in allowed users.","message":"expected `dockerroot` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000277681,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"tss is listed in allowed users.","message":"expected `tss` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000211472,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"saslauth is listed in allowed users.","message":"expected `saslauth` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.00034335,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"postgres is listed in allowed users.","message":"expected `postgres` to be in the list: `[\"root\", \"bin\", \"daemon\", \"adm\", \"lp\", \"sync\", \"shutdown\", \"halt\", \"mail\", \"operator\", \"nobody\", \"systemd-bus-proxy\", \"dbus\", \"polkitd\", \"postfix\", \"sssd\", \"chrony\", \"systemd-network\", \"sshd\", \"ntp\"]`","run_time":0.000192348,"start_time":"2022-03-06T22:05:50+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72001.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72001","rid":"SV-86625r2_rule","stig_id":"RHEL-07-020270","fix_id":"F-78353r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have\nunnecessary accounts.","waiver_data":{}},{"code":"control \"V-72003\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all Group Identifiers (GIDs) referenced in the /etc/passwd file are\ndefined in the /etc/group file.\"\n desc \"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all GIDs referenced in the \\\"/etc/passwd\\\" file are defined in the\n\\\"/etc/group\\\" file.\n\n Check that all referenced GIDs exist with the following command:\n\n # pwck -r\n\n If GIDs referenced in \\\"/etc/passwd\\\" file are returned as not defined in\n\\\"/etc/group\\\" file, this is a finding.\n \"\n desc \"fix\", \"Configure the system to define all GIDs found in the\n\\\"/etc/passwd\\\" file by modifying the \\\"/etc/group\\\" file to add any\nnon-existent group referenced in the \\\"/etc/passwd\\\" file, or change the GIDs\nreferenced in the \\\"/etc/passwd\\\" file to a group that exists in\n\\\"/etc/group\\\".\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000104-GPOS-00051\"\n tag gid: \"V-72003\"\n tag rid: \"SV-86627r2_rule\"\n tag stig_id: \"RHEL-07-020300\"\n tag fix_id: \"F-78355r1_fix\"\n tag cci: [\"CCI-000764\"]\n tag nist: [\"IA-2\"]\n\n passwd.gids.each do |gid|\n describe etc_group do\n its('gids') { should include gid.to_i }\n end\n end\nend\n","desc":"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.","descriptions":[{"data":"If a user is assigned the GID of a group not existing on the system,\nand a group with the GID is subsequently created, the user may have unintended\nrights to any files associated with the group.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all GIDs referenced in the \"/etc/passwd\" file are defined in the\n\"/etc/group\" file.\n\n Check that all referenced GIDs exist with the following command:\n\n # pwck -r\n\n If GIDs referenced in \"/etc/passwd\" file are returned as not defined in\n\"/etc/group\" file, this is a finding.","label":"check"},{"data":"Configure the system to define all GIDs found in the\n\"/etc/passwd\" file by modifying the \"/etc/group\" file to add any\nnon-existent group referenced in the \"/etc/passwd\" file, or change the GIDs\nreferenced in the \"/etc/passwd\" file to a group that exists in\n\"/etc/group\".","label":"fix"}],"id":"V-72003","impact":0.3,"refs":[],"results":[{"code_desc":"/etc/group gids is expected to include 0","run_time":0.000201263,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 1","run_time":0.000158286,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 2","run_time":0.000133427,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 4","run_time":0.00020973,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 7","run_time":0.000132581,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 0","run_time":0.000139122,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 0","run_time":0.000301141,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 0","run_time":0.000235526,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 12","run_time":0.00013583,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 0","run_time":0.00013549,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 100","run_time":0.000216651,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 50","run_time":0.000173744,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 99","run_time":0.000144919,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 192","run_time":0.000193705,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 81","run_time":0.000174711,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 998","run_time":0.000415804,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 32","run_time":0.000239316,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 29","run_time":0.000190883,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 65534","run_time":0.000150091,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 74","run_time":0.000147809,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 89","run_time":0.000138769,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 995","run_time":0.000143219,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 1000","run_time":0.000266571,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 1","run_time":0.000276408,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 992","run_time":0.000160443,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 59","run_time":0.000141615,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 76","run_time":0.000161012,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"},{"code_desc":"/etc/group gids is expected to include 26","run_time":0.000153171,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"etc_group","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72003.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000104-GPOS-00051","gid":"V-72003","rid":"SV-86627r2_rule","stig_id":"RHEL-07-020300","fix_id":"F-78355r1_fix","cci":["CCI-000764"],"nist":["IA-2"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all Group Identifiers (GIDs) referenced in the /etc/passwd file are\ndefined in the /etc/group file.","waiver_data":{}},{"code":"control \"V-72005\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the root account must be the only account having unrestricted access to\nthe system.\"\n desc \"If an account other than root also has a User Identifier (UID) of\n\\\"0\\\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \\\"0\\\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check the system for duplicate UID \\\"0\\\" assignments with the following\ncommand:\n\n # awk -F: '$3 == 0 {print $1}' /etc/passwd\n\n If any accounts other than root have a UID of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Change the UID of any account on the system, other than root, that has a\nUID of \\\"0\\\".\n\n If the account is associated with system commands or applications, the UID\nshould be changed to one greater than \\\"0\\\" but less than \\\"1000\\\". Otherwise,\nassign a UID of greater than \\\"1000\\\" that has not already been assigned.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72005\"\n tag rid: \"SV-86629r2_rule\"\n tag stig_id: \"RHEL-07-020310\"\n tag fix_id: \"F-78357r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe passwd.uids(0) do\n its('users') { should cmp 'root' }\n its('entries.length') { should eq 1 }\n end\nend\n","desc":"If an account other than root also has a User Identifier (UID) of\n\"0\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \"0\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.","descriptions":[{"data":"If an account other than root also has a User Identifier (UID) of\n\"0\", it has root authority, giving that account unrestricted access to the\nentire operating system. Multiple accounts with a UID of \"0\" afford an\nopportunity for potential intruders to guess a password for a privileged\naccount.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the system for duplicate UID \"0\" assignments with the following\ncommand:\n\n # awk -F: '$3 == 0 {print $1}' /etc/passwd\n\n If any accounts other than root have a UID of \"0\", this is a finding.","label":"check"},{"data":"Change the UID of any account on the system, other than root, that has a\nUID of \"0\".\n\n If the account is associated with system commands or applications, the UID\nshould be changed to one greater than \"0\" but less than \"1000\". Otherwise,\nassign a UID of greater than \"1000\" that has not already been assigned.","label":"fix"}],"id":"V-72005","impact":0.7,"refs":[],"results":[{"code_desc":"/etc/passwd with uid == 0 users is expected to cmp == \"root\"","run_time":0.000306829,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"/etc/passwd with uid == 0 entries.length is expected to eq 1","run_time":0.000525955,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72005.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72005","rid":"SV-86629r2_rule","stig_id":"RHEL-07-020310","fix_id":"F-78357r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the root account must be the only account having unrestricted access to\nthe system.","waiver_data":{}},{"code":"control \"V-72007\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid owner.\"\n desc \"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \\\"UID\\\" as the UID of the un-owned\nfiles.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories on the system have a valid owner.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nouser\n\n If any files on the system do not have an assigned owner, this is a finding.\n \"\n desc \"fix\", \"\n Either remove all files and directories from the system that do not have a\nvalid user, or assign a valid user to all unowned files and directories on the\nsystem with the \\\"chown\\\" command:\n\n # chown \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72007\"\n tag rid: \"SV-86631r3_rule\"\n tag stig_id: \"RHEL-07-020320\"\n tag fix_id: \"F-78359r1_fix\"\n tag cci: [\"CCI-002165\"]\n tag nist: [\"AC-3 (4)\"]\n\n command('grep -v \"nodev\" /proc/filesystems | awk \\'NF{ print $NF }\\'').\n stdout.strip.split(\"\\n\").each do |fs|\n describe command(\"find / -xdev -xautofs -fstype #{fs} -nouser\") do\n its('stdout.strip') { should be_empty }\n end\n end\nend\n","desc":"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \"UID\" as the UID of the un-owned\nfiles.","descriptions":[{"data":"Unowned files and directories may be unintentionally inherited if a\nuser is assigned the same User Identifier \"UID\" as the UID of the un-owned\nfiles.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories on the system have a valid owner.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nouser\n\n If any files on the system do not have an assigned owner, this is a finding.","label":"check"},{"data":"Either remove all files and directories from the system that do not have a\nvalid user, or assign a valid user to all unowned files and directories on the\nsystem with the \"chown\" command:\n\n # chown ","label":"fix"}],"id":"V-72007","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `find / -xdev -xautofs -fstype fuseblk -nouser` stdout.strip is expected to be empty","run_time":0.773697783,"start_time":"2022-03-06T22:05:50+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -fstype fuseblk -nouser\"]"},{"code_desc":"Command: `find / -xdev -xautofs -fstype xfs -nouser` stdout.strip is expected to be empty","run_time":4.961099448,"start_time":"2022-03-06T22:05:51+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -fstype xfs -nouser\"]"},{"code_desc":"Command: `find / -xdev -xautofs -fstype iso9660 -nouser` stdout.strip is expected to be empty","run_time":0.860699607,"start_time":"2022-03-06T22:05:56+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -fstype iso9660 -nouser\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72007.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72007","rid":"SV-86631r3_rule","stig_id":"RHEL-07-020320","fix_id":"F-78359r1_fix","cci":["CCI-002165"],"nist":["AC-3 (4)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid owner.","waiver_data":{}},{"code":"control \"V-72009\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid group owner.\"\n desc \"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories on the system have a valid group.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nogroup\n\n If any files on the system do not have an assigned group, this is a finding.\n \"\n desc \"fix\", \"\n Either remove all files and directories from the system that do not have a\nvalid group, or assign a valid group to all files and directories on the system\nwith the \\\"chgrp\\\" command:\n\n # chgrp \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72009\"\n tag rid: \"SV-86633r3_rule\"\n tag stig_id: \"RHEL-07-020330\"\n tag fix_id: \"F-78361r1_fix\"\n tag cci: [\"CCI-002165\"]\n tag nist: [\"AC-3 (4)\"]\n\n command('grep -v \"nodev\" /proc/filesystems | awk \\'NF{ print $NF }\\'').\n stdout.strip.split(\"\\n\").each do |fs|\n describe command(\"find / -xdev -xautofs -fstype #{fs} -nogroup\") do\n its('stdout.strip') { should be_empty }\n end\n end\nend\n","desc":"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.","descriptions":[{"data":"Files without a valid group owner may be unintentionally inherited if\na group is assigned the same Group Identifier (GID) as the GID of the files\nwithout a valid group owner.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories on the system have a valid group.\n\n Check the owner of all files and directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -fstype xfs -nogroup\n\n If any files on the system do not have an assigned group, this is a finding.","label":"check"},{"data":"Either remove all files and directories from the system that do not have a\nvalid group, or assign a valid group to all files and directories on the system\nwith the \"chgrp\" command:\n\n # chgrp ","label":"fix"}],"id":"V-72009","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `find / -xdev -xautofs -fstype fuseblk -nogroup` stdout.strip is expected to be empty","run_time":0.768371216,"start_time":"2022-03-06T22:05:57+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -fstype fuseblk -nogroup\"]"},{"code_desc":"Command: `find / -xdev -xautofs -fstype xfs -nogroup` stdout.strip is expected to be empty","run_time":4.607123456,"start_time":"2022-03-06T22:05:57+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -fstype xfs -nogroup\"]"},{"code_desc":"Command: `find / -xdev -xautofs -fstype iso9660 -nogroup` stdout.strip is expected to be empty","run_time":0.800019094,"start_time":"2022-03-06T22:06:02+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -fstype iso9660 -nogroup\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72009.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72009","rid":"SV-86633r3_rule","stig_id":"RHEL-07-020330","fix_id":"F-78361r1_fix","cci":["CCI-002165"],"nist":["AC-3 (4)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories have a valid group owner.","waiver_data":{}},{"code":"control \"V-72011\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive users have a home directory assigned in the\n/etc/passwd file.\"\n desc \"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify local interactive users on the system have a home directory assigned.\n\n Check for missing local interactive user home directories with the\nfollowing command:\n\n # pwck -r\n user 'lp': directory '/var/spool/lpd' does not exist\n user 'news': directory '/var/spool/news' does not exist\n user 'uucp': directory '/var/spool/uucp' does not exist\n user 'smithj': directory '/home/smithj' does not exist\n\n Ask the System Administrator (SA) if any users found without home\ndirectories are local interactive users. If the SA is unable to provide a\nresponse, check for users with a User Identifier (UID) of 1000 or greater with\nthe following command:\n\n # cut -d: -f 1,3 /etc/passwd | egrep \\\":[1-4][0-9]{2}$|:[0-9]{1,2}$\\\"\n\n If any interactive users do not have a home directory assigned, this is a\nfinding.\n \"\n desc \"fix\", \"Assign home directories to all local interactive users that\ncurrently do not have a home directory assigned.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72011\"\n tag rid: \"SV-86635r2_rule\"\n tag stig_id: \"RHEL-07-020600\"\n tag fix_id: \"F-78363r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n describe directory(user_info.home) do\n it { should exist }\n end\n end\nend\n","desc":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","descriptions":[{"data":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify local interactive users on the system have a home directory assigned.\n\n Check for missing local interactive user home directories with the\nfollowing command:\n\n # pwck -r\n user 'lp': directory '/var/spool/lpd' does not exist\n user 'news': directory '/var/spool/news' does not exist\n user 'uucp': directory '/var/spool/uucp' does not exist\n user 'smithj': directory '/home/smithj' does not exist\n\n Ask the System Administrator (SA) if any users found without home\ndirectories are local interactive users. If the SA is unable to provide a\nresponse, check for users with a User Identifier (UID) of 1000 or greater with\nthe following command:\n\n # cut -d: -f 1,3 /etc/passwd | egrep \":[1-4][0-9]{2}$|:[0-9]{1,2}$\"\n\n If any interactive users do not have a home directory assigned, this is a\nfinding.","label":"check"},{"data":"Assign home directories to all local interactive users that\ncurrently do not have a home directory assigned.","label":"fix"}],"id":"V-72011","impact":0.5,"refs":[],"results":[{"code_desc":"Directory /root is expected to exist","run_time":0.000298665,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/root\"]"},{"code_desc":"Directory /home/vagrant is expected to exist","run_time":0.000258807,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/home/vagrant\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72011.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72011","rid":"SV-86635r2_rule","stig_id":"RHEL-07-020600","fix_id":"F-78363r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive users have a home directory assigned in the\n/etc/passwd file.","waiver_data":{}},{"code":"control \"V-72013\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user accounts, upon creation, are assigned a home\ndirectory.\"\n desc \"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all local interactive users on the system are assigned a home\ndirectory upon creation.\n\n Check to see if the system is configured to create home directories for\nlocal interactive users with the following command:\n\n # grep -i create_home /etc/login.defs\n CREATE_HOME yes\n\n If the value for \\\"CREATE_HOME\\\" parameter is not set to \\\"yes\\\", the line\nis missing, or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to assign home directories to all new local\ninteractive users by setting the \\\"CREATE_HOME\\\" parameter in\n\\\"/etc/login.defs\\\" to \\\"yes\\\" as follows.\n\n CREATE_HOME yes\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72013\"\n tag rid: \"SV-86637r2_rule\"\n tag stig_id: \"RHEL-07-020610\"\n tag fix_id: \"F-78365r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe login_defs do\n its('CREATE_HOME') { should eq 'yes' }\n end\nend\n","desc":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","descriptions":[{"data":"If local interactive users are not assigned a valid home directory,\nthere is no place for the storage and control of files they should own.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all local interactive users on the system are assigned a home\ndirectory upon creation.\n\n Check to see if the system is configured to create home directories for\nlocal interactive users with the following command:\n\n # grep -i create_home /etc/login.defs\n CREATE_HOME yes\n\n If the value for \"CREATE_HOME\" parameter is not set to \"yes\", the line\nis missing, or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the operating system to assign home directories to all new local\ninteractive users by setting the \"CREATE_HOME\" parameter in\n\"/etc/login.defs\" to \"yes\" as follows.\n\n CREATE_HOME yes","label":"fix"}],"id":"V-72013","impact":0.5,"refs":[],"results":[{"code_desc":"login.defs CREATE_HOME is expected to eq \"yes\"","run_time":0.002098134,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"login_defs","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72013.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72013","rid":"SV-86637r2_rule","stig_id":"RHEL-07-020610","fix_id":"F-78365r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user accounts, upon creation, are assigned a home\ndirectory.","waiver_data":{}},{"code":"control \"V-72015\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are defined in the /etc/passwd\nfile.\"\n desc \"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive\nnon-privileged users on the system with the following command:\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n\n smithj:1001:/home/smithj\n\n Note: This may miss interactive users that have been assigned a privileged\nUID. Evidence of interactive use may be obtained from a number of log files\ncontaining system logon information.\n\n Check that all referenced home directories exist with the following command:\n\n # pwck -r\n user 'smithj': directory '/home/smithj' does not exist\n\n If any home directories referenced in \\\"/etc/passwd\\\" are returned as not\ndefined, this is a finding.\n \"\n desc \"fix\", \"\n Create home directories to all local interactive users that currently do\nnot have a home directory assigned. Use the following commands to create the\nuser home directory assigned in \\\"/etc/ passwd\\\":\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\", a UID of \\\"smithj\\\", and a Group Identifier (GID) of\n\\\"users\\\" assigned in \\\"/etc/passwd\\\".\n\n # mkdir /home/smithj\n # chown smithj /home/smithj\n # chgrp users /home/smithj\n # chmod 0750 /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72015\"\n tag rid: \"SV-86639r2_rule\"\n tag stig_id: \"RHEL-07-020620\"\n tag fix_id: \"F-78367r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n describe directory(user_info.home) do\n it { should exist }\n end\n end\nend\n","desc":"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.","descriptions":[{"data":"If a local interactive user has a home directory defined that does not\nexist, the user may be given access to the / directory as the current working\ndirectory upon logon. This could create a Denial of Service because the user\nwould not be able to access their logon configuration files, and it may give\nthem visibility to system files they normally would not be able to access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive\nnon-privileged users on the system with the following command:\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n\n smithj:1001:/home/smithj\n\n Note: This may miss interactive users that have been assigned a privileged\nUID. Evidence of interactive use may be obtained from a number of log files\ncontaining system logon information.\n\n Check that all referenced home directories exist with the following command:\n\n # pwck -r\n user 'smithj': directory '/home/smithj' does not exist\n\n If any home directories referenced in \"/etc/passwd\" are returned as not\ndefined, this is a finding.","label":"check"},{"data":"Create home directories to all local interactive users that currently do\nnot have a home directory assigned. Use the following commands to create the\nuser home directory assigned in \"/etc/ passwd\":\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\", a UID of \"smithj\", and a Group Identifier (GID) of\n\"users\" assigned in \"/etc/passwd\".\n\n # mkdir /home/smithj\n # chown smithj /home/smithj\n # chgrp users /home/smithj\n # chmod 0750 /home/smithj","label":"fix"}],"id":"V-72015","impact":0.5,"refs":[],"results":[{"code_desc":"Directory /root is expected to exist","run_time":0.000184728,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/root\"]"},{"code_desc":"Directory /home/vagrant is expected to exist","run_time":0.000190608,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/home/vagrant\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72015.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72015","rid":"SV-86639r2_rule","stig_id":"RHEL-07-020620","fix_id":"F-78367r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are defined in the /etc/passwd\nfile.","waiver_data":{}},{"code":"control \"V-72017\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories have mode 0750 or less\npermissive.\"\n desc \"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users has a\nmode of \\\"0750\\\" or less permissive.\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If home directories referenced in \\\"/etc/passwd\\\" do not have a mode of\n\\\"0750\\\" or less permissive, this is a finding.\n \"\n desc \"fix\", \"\n Change the mode of interactive user's home directories to \\\"0750\\\". To\nchange the mode of a local interactive user's home directory, use the following\ncommand:\n\n Note: The example will be for the user \\\"smithj\\\".\n\n # chmod 0750 /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72017\"\n tag rid: \"SV-86641r3_rule\"\n tag stig_id: \"RHEL-07-020630\"\n tag fix_id: \"F-78369r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -maxdepth 0 -perm /027\").stdout.split(\"\\n\")\n end\n describe \"Home directories with excessive permissions\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.","descriptions":[{"data":"Excessive permissions on local interactive user home directories may\nallow unauthorized access to user files by other users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users has a\nmode of \"0750\" or less permissive.\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If home directories referenced in \"/etc/passwd\" do not have a mode of\n\"0750\" or less permissive, this is a finding.","label":"check"},{"data":"Change the mode of interactive user's home directories to \"0750\". To\nchange the mode of a local interactive user's home directory, use the following\ncommand:\n\n Note: The example will be for the user \"smithj\".\n\n # chmod 0750 /home/smithj","label":"fix"}],"id":"V-72017","impact":0.5,"refs":[],"results":[{"code_desc":"Home directories with excessive permissions is expected to be empty","run_time":0.011949493,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72017.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72017","rid":"SV-86641r3_rule","stig_id":"RHEL-07-020630","fix_id":"F-78369r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories have mode 0750 or less\npermissive.","waiver_data":{}},{"code":"control \"V-72019\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are owned by their respective\nusers.\"\n desc \"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If any home directories referenced in \\\"/etc/passwd\\\" are not owned by the\ninteractive user, this is a finding.\n \"\n desc \"fix\", \"\n Change the owner of a local interactive user's home directories to that\nowner. To change the owner of a local interactive user's home directory, use\nthe following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\".\n\n # chown smithj /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72019\"\n tag rid: \"SV-86643r5_rule\"\n tag stig_id: \"RHEL-07-020640\"\n tag fix_id: \"F-78371r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n describe directory(user_info.home) do\n it { should exist }\n its('owner') { should eq user_info.username }\n end\n end\nend\n","desc":"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.","descriptions":[{"data":"If a local interactive user does not own their home directory,\nunauthorized users could access or modify the user's files, and the users may\nnot be able to access their own files.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users on the\nsystem exists.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n If any home directories referenced in \"/etc/passwd\" are not owned by the\ninteractive user, this is a finding.","label":"check"},{"data":"Change the owner of a local interactive user's home directories to that\nowner. To change the owner of a local interactive user's home directory, use\nthe following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj","label":"fix"}],"id":"V-72019","impact":0.5,"refs":[],"results":[{"code_desc":"Directory /root is expected to exist","run_time":0.000167492,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/root\"]"},{"code_desc":"Directory /root owner is expected to eq \"root\"","run_time":0.024685546,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/root\"]"},{"code_desc":"Directory /home/vagrant is expected to exist","run_time":0.000312945,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/home/vagrant\"]"},{"code_desc":"Directory /home/vagrant owner is expected to eq \"vagrant\"","run_time":0.045955919,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"directory","resource_params":"[\"/home/vagrant\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72019.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72019","rid":"SV-86643r5_rule","stig_id":"RHEL-07-020640","fix_id":"F-78371r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are owned by their respective\nusers.","waiver_data":{}},{"code":"control \"V-72021\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are group-owned by the home\ndirectory owners primary group.\"\n desc \"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the assigned home directory of all local interactive users is\ngroup-owned by that user's primary GID.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n Check the user's primary group with the following command:\n\n # grep users /etc/group\n\n users:x:250:smithj,jonesj,jacksons\n\n If the user home directory referenced in \\\"/etc/passwd\\\" is not group-owned\nby that user's primary GID, this is a finding.\n \"\n desc \"fix\", \"\n Change the group owner of a local interactive user's home directory to the\ngroup found in \\\"/etc/passwd\\\". To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\", and has a primary group of users.\n\n # chgrp users /home/smithj\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72021\"\n tag rid: \"SV-86645r5_rule\"\n tag stig_id: \"RHEL-07-020650\"\n tag fix_id: \"F-78373r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -maxdepth 0 -not -gid #{user_info.gid}\").stdout.split(\"\\n\")\n end\n describe \"Home directories that are not group-owned by the user's primary GID\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.","descriptions":[{"data":"If the Group Identifier (GID) of a local interactive user's home\ndirectory is not the same as the primary GID of the user, this would allow\nunauthorized access to the user's files, and users that share the same group\nmay not be able to access files that they legitimately should.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the assigned home directory of all local interactive users is\ngroup-owned by that user's primary GID.\n\n Check the home directory assignment for all local interactive users on the\nsystem with the following command:\n\n # ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)\n\n -rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj\n\n Check the user's primary group with the following command:\n\n # grep users /etc/group\n\n users:x:250:smithj,jonesj,jacksons\n\n If the user home directory referenced in \"/etc/passwd\" is not group-owned\nby that user's primary GID, this is a finding.","label":"check"},{"data":"Change the group owner of a local interactive user's home directory to the\ngroup found in \"/etc/passwd\". To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\", and has a primary group of users.\n\n # chgrp users /home/smithj","label":"fix"}],"id":"V-72021","impact":0.5,"refs":[],"results":[{"code_desc":"Home directories that are not group-owned by the user's primary GID is expected to be empty","run_time":0.012100539,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72021.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72021","rid":"SV-86645r5_rule","stig_id":"RHEL-07-020650","fix_id":"F-78373r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user home directories are group-owned by the home\ndirectory owners primary group.","waiver_data":{}},{"code":"control \"V-72023\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are owned by the owner of the home directory.\"\n desc \"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories in a local interactive user's home\ndirectory are owned by the user.\n\n Check the owner of all files and directories in a local interactive user's\nhome directory with the following command:\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -lLR /home/smithj\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the home directory\nuser, this is a finding.\n \"\n desc \"fix\", \"\n Change the owner of a local interactive user's files and directories to\nthat owner. To change the owner of a local interactive user's files and\ndirectories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\".\n\n # chown smithj /home/smithj/\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72023\"\n tag rid: \"SV-86647r2_rule\"\n tag stig_id: \"RHEL-07-020660\"\n tag fix_id: \"F-78375r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -xdev -xautofs -not -user #{user_info.username}\").stdout.split(\"\\n\")\n end\n describe \"Files and directories that are not owned by the user\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.","descriptions":[{"data":"If local interactive users do not own the files in their directories,\nunauthorized users may be able to access them. Additionally, if files are not\nowned by the user, this could be an indication of system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories in a local interactive user's home\ndirectory are owned by the user.\n\n Check the owner of all files and directories in a local interactive user's\nhome directory with the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR /home/smithj\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the home directory\nuser, this is a finding.","label":"check"},{"data":"Change the owner of a local interactive user's files and directories to\nthat owner. To change the owner of a local interactive user's files and\ndirectories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj/","label":"fix"}],"id":"V-72023","impact":0.5,"refs":[],"results":[{"code_desc":"Files and directories that are not owned by the user is expected to be empty","message":"expected `[\"/home/vagrant/git3/inspec-profile-disa_stig-el7/inspec.lock\", \"/home/vagrant/git3/inspec-profile-di...ome/vagrant/test26url/profiles/testurl_sudo_archive.json\", \"/home/vagrant/test26url/testaide1.json\"].empty?` to be truthy, got false","run_time":0.013279351,"start_time":"2022-03-06T22:06:03+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72023.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72023","rid":"SV-86647r2_rule","stig_id":"RHEL-07-020660","fix_id":"F-78375r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are owned by the owner of the home directory.","waiver_data":{}},{"code":"control \"V-72025\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are group-owned by a group of which the home directory owner is a\nmember.\"\n desc \"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories in a local interactive user home directory\nare group-owned by a group the user is a member of.\n\n Check the group owner of all files and directories in a local interactive\nuser's home directory with the following command:\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -lLR ///\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj sa 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the group home\ndirectory user, check to see if the user is a member of that group with the\nfollowing command:\n\n # grep smithj /etc/group\n sa:x:100:juan,shelley,bob,smithj\n smithj:x:521:smithj\n\n If the user is not a member of a group that group owns file(s) in a local\ninteractive user's home directory, this is a finding.\n \"\n desc \"fix\", \"\n Change the group of a local interactive user's files and directories to a\ngroup that the interactive user is a member of. To change the group owner of a\nlocal interactive user's files and directories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\" and is a member of the users group.\n\n # chgrp users /home/smithj/\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72025\"\n tag rid: \"SV-86649r2_rule\"\n tag stig_id: \"RHEL-07-020670\"\n tag fix_id: \"F-78377r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n find_args = \"\"\n user_info.groups.each { |curr_group|\n # some key files and secure dirs (like .ssh) are group owned 'root'\n find_args = find_args + \"-not -group #{curr_group} -o root\"\n }\n findings = findings + command(\"find #{user_info.home} -xdev -xautofs #{find_args}\").stdout.split(\"\\n\")\n end\n describe \"Home directory files with incorrect group ownership or not 'root' owned\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.","descriptions":[{"data":"If a local interactive user's files are group-owned by a group of\nwhich the user is not a member, unintended users may be able to access them.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories in a local interactive user home directory\nare group-owned by a group the user is a member of.\n\n Check the group owner of all files and directories in a local interactive\nuser's home directory with the following command:\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR ///\n -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1\n -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r--r-- 1 smithj sa 231 Mar 5 17:06 file3\n\n If any files are found with an owner different than the group home\ndirectory user, check to see if the user is a member of that group with the\nfollowing command:\n\n # grep smithj /etc/group\n sa:x:100:juan,shelley,bob,smithj\n smithj:x:521:smithj\n\n If the user is not a member of a group that group owns file(s) in a local\ninteractive user's home directory, this is a finding.","label":"check"},{"data":"Change the group of a local interactive user's files and directories to a\ngroup that the interactive user is a member of. To change the group owner of a\nlocal interactive user's files and directories, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\" and is a member of the users group.\n\n # chgrp users /home/smithj/","label":"fix"}],"id":"V-72025","impact":0.5,"refs":[],"results":[{"code_desc":"Home directory files with incorrect group ownership or not 'root' owned is expected to be empty","run_time":0.010887705,"start_time":"2022-03-06T22:06:03+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72025.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72025","rid":"SV-86649r2_rule","stig_id":"RHEL-07-020670","fix_id":"F-78377r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories are group-owned by a group of which the home directory owner is a\nmember.","waiver_data":{}},{"code":"control \"V-72027\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories have a mode of 0750 or less permissive.\"\n desc \"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all files and directories contained in a local interactive user home\ndirectory, excluding local initialization files, have a mode of \\\"0750\\\".\n\n Check the mode of all non-initialization files in a local interactive user\nhome directory with the following command:\n\n Files that begin with a \\\".\\\" are excluded from this requirement.\n\n Note: The example will be for the user \\\"smithj\\\", who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -lLR /home/smithj\n -rwxr-x--- 1 smithj smithj 18 Mar 5 17:06 file1\n -rwxr----- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r-x--- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with a mode more permissive than \\\"0750\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Set the mode on files and directories in the local interactive user home\ndirectory with the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\" and is a member of the users group.\n\n # chmod 0750 /home/smithj/\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72027\"\n tag rid: \"SV-86651r2_rule\"\n tag stig_id: \"RHEL-07-020680\"\n tag fix_id: \"F-78379r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -xdev ! -name '.*' -perm /027 ! -type l\").stdout.split(\"\\n\")\n end\n describe \"Home directories with excessive permissions\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.","descriptions":[{"data":"If a local interactive user files have excessive permissions,\nunintended users may be able to access or modify them.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all files and directories contained in a local interactive user home\ndirectory, excluding local initialization files, have a mode of \"0750\".\n\n Check the mode of all non-initialization files in a local interactive user\nhome directory with the following command:\n\n Files that begin with a \".\" are excluded from this requirement.\n\n Note: The example will be for the user \"smithj\", who has a home directory\nof \"/home/smithj\".\n\n # ls -lLR /home/smithj\n -rwxr-x--- 1 smithj smithj 18 Mar 5 17:06 file1\n -rwxr----- 1 smithj smithj 193 Mar 5 17:06 file2\n -rw-r-x--- 1 smithj smithj 231 Mar 5 17:06 file3\n\n If any files are found with a mode more permissive than \"0750\", this is a\nfinding.","label":"check"},{"data":"Set the mode on files and directories in the local interactive user home\ndirectory with the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\" and is a member of the users group.\n\n # chmod 0750 /home/smithj/","label":"fix"}],"id":"V-72027","impact":0.5,"refs":[],"results":[{"code_desc":"Home directories with excessive permissions is expected to be empty","message":"expected `[\"/root/.gem/specs\", \"/root/.gem/specs/rubygems.org%443\", \"/root/.gem/specs/rubygems.org%443/quick\", ...ntrols/example.rb\", \"/home/vagrant/testprofile/inspec.yml\", \"/home/vagrant/testprofile/inspec.lock\"].empty?` to be truthy, got false","run_time":1.35657474,"start_time":"2022-03-06T22:06:03+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72027.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72027","rid":"SV-86651r2_rule","stig_id":"RHEL-07-020680","fix_id":"F-78379r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all files and directories contained in local interactive user home\ndirectories have a mode of 0750 or less permissive.","waiver_data":{}},{"code":"control \"V-72029\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for interactive users are owned by the home\ndirectory user or root.\"\n desc \"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\\\"/home/smithj\\\" and a primary group of \\\"users\\\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.\n \"\n desc \"fix\", \"\n Set the owner of the local initialization files for interactive users to\neither the directory owner or root with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\\\"/home/smithj\\\".\n\n # chown smithj /home/smithj/.[^.]*\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72029\"\n tag rid: \"SV-86653r3_rule\"\n tag stig_id: \"RHEL-07-020690\"\n tag fix_id: \"F-78381r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n findings = findings + command(\"find #{user_info.home} -name '.*' -not -user #{user_info.username} -a -not -user root\").stdout.split(\"\\n\")\n end\n describe \"Files and Directories not owned by the user or root of the parent home directory\" do\n subject { findings.to_a }\n it { should be_empty }\n end\nend\n","desc":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","descriptions":[{"data":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\" and a primary group of \"users\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.","label":"check"},{"data":"Set the owner of the local initialization files for interactive users to\neither the directory owner or root with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\".\n\n # chown smithj /home/smithj/.[^.]*","label":"fix"}],"id":"V-72029","impact":0.5,"refs":[],"results":[{"code_desc":"Files and Directories not owned by the user or root of the parent home directory is expected to be empty","run_time":0.011038655,"start_time":"2022-03-06T22:06:04+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72029.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72029","rid":"SV-86653r3_rule","stig_id":"RHEL-07-020690","fix_id":"F-78381r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for interactive users are owned by the home\ndirectory user or root.","waiver_data":{}},{"code":"control \"V-72031\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for local interactive users are be\ngroup-owned by the users primary group or root.\"\n desc \"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\\\"/home/smithj\\\" and a primary group of \\\"users\\\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.\n \"\n desc \"fix\", \"\n Change the group owner of a local interactive user's files to the group\nfound in \\\"/etc/passwd\\\" for the user. To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\\\"/home/smithj\\\", and has a primary group of users.\n\n # chgrp users /home/smithj/.[^.]*\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72031\"\n tag rid: \"SV-86655r4_rule\"\n tag stig_id: \"RHEL-07-020700\"\n tag fix_id: \"F-78383r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n findings = findings + command(\"find #{user_info.home} -name '.*' -not -gid #{user_info.gid} -not -group root\").stdout.split(\"\\n\")\n end\n describe findings do\n its('length') { should == 0 }\n end\nend\n","desc":"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.","descriptions":[{"data":"Local initialization files for interactive users are used to configure\nthe user's shell environment upon logon. Malicious modification of these files\ncould compromise accounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the local initialization files of all local interactive users are\ngroup-owned by that user's primary Group Identifier (GID).\n\n Check the home directory assignment for all non-privileged users on the\nsystem with the following command:\n\n Note: The example will be for the smithj user, who has a home directory of\n\"/home/smithj\" and a primary group of \"users\".\n\n # cut -d: -f 1,4,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1000:/home/smithj\n\n # grep 1000 /etc/group\n users:x:1000:smithj,jonesj,jacksons\n\n Note: This may miss interactive users that have been assigned a privileged\nUser Identifier (UID). Evidence of interactive use may be obtained from a\nnumber of log files containing system logon information.\n\n Check the group owner of all local interactive user's initialization files\nwith the following command:\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n -rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n -rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\n If all local interactive user's initialization files are not group-owned by\nthat user's primary GID, this is a finding.","label":"check"},{"data":"Change the group owner of a local interactive user's files to the group\nfound in \"/etc/passwd\" for the user. To change the group owner of a local\ninteractive user's home directory, use the following command:\n\n Note: The example will be for the user smithj, who has a home directory of\n\"/home/smithj\", and has a primary group of users.\n\n # chgrp users /home/smithj/.[^.]*","label":"fix"}],"id":"V-72031","impact":0.5,"refs":[],"results":[{"code_desc":"# length is expected to == 0","message":"expected: 0\n got: 1 (using ==)","run_time":0.008577282,"start_time":"2022-03-06T22:06:04+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72031.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72031","rid":"SV-86655r4_rule","stig_id":"RHEL-07-020700","fix_id":"F-78383r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files for local interactive users are be\ngroup-owned by the users primary group or root.","waiver_data":{}},{"code":"control \"V-72033\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files have mode 0740 or less permissive.\"\n desc \"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that all local initialization files have a mode of \\\"0740\\\" or less\npermissive.\n\n Check the mode on all local initialization files with the following command:\n\n Note: The example will be for the \\\"smithj\\\" user, who has a home directory\nof \\\"/home/smithj\\\".\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr----- 1 smithj users 896 Mar 10 2011 .profile\n -rwxr----- 1 smithj users 497 Jan 6 2007 .login\n -rwxr----- 1 smithj users 886 Jan 6 2007 .something\n\n If any local initialization files have a mode more permissive than\n\\\"0740\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the mode of the local initialization files to \\\"0740\\\" with the\nfollowing command:\n\n Note: The example will be for the \\\"smithj\\\" user, who has a home directory\nof \\\"/home/smithj\\\".\n\n # chmod 0740 /home/smithj/.[^.]*\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72033\"\n tag rid: \"SV-86657r3_rule\"\n tag stig_id: \"RHEL-07-020710\"\n tag fix_id: \"F-78385r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n findings = findings + command(\"find #{user_info.home} -xdev -maxdepth 1 -name '.*' -type f -perm /037\").stdout.split(\"\\n\")\n end\n describe findings do\n it { should be_empty }\n end\nend\n","desc":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","descriptions":[{"data":"Local initialization files are used to configure the user's shell\nenvironment upon logon. Malicious modification of these files could compromise\naccounts upon logon.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all local initialization files have a mode of \"0740\" or less\npermissive.\n\n Check the mode on all local initialization files with the following command:\n\n Note: The example will be for the \"smithj\" user, who has a home directory\nof \"/home/smithj\".\n\n # ls -al /home/smithj/.[^.]* | more\n\n -rwxr----- 1 smithj users 896 Mar 10 2011 .profile\n -rwxr----- 1 smithj users 497 Jan 6 2007 .login\n -rwxr----- 1 smithj users 886 Jan 6 2007 .something\n\n If any local initialization files have a mode more permissive than\n\"0740\", this is a finding.","label":"check"},{"data":"Set the mode of the local initialization files to \"0740\" with the\nfollowing command:\n\n Note: The example will be for the \"smithj\" user, who has a home directory\nof \"/home/smithj\".\n\n # chmod 0740 /home/smithj/.[^.]*","label":"fix"}],"id":"V-72033","impact":0.5,"refs":[],"results":[{"code_desc":"# is expected to be empty","message":"expected `#.empty?` to be truthy, got false","run_time":0.010959347,"start_time":"2022-03-06T22:06:04+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72033.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72033","rid":"SV-86657r3_rule","stig_id":"RHEL-07-020710","fix_id":"F-78385r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local initialization files have mode 0740 or less permissive.","waiver_data":{}},{"code":"control \"V-72035\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user initialization files executable search paths\ncontain only paths that resolve to the users home directory.\"\n desc \"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that all local interactive user initialization files' executable\nsearch path statements do not contain statements that will reference a working\ndirectory other than the users' home directory.\n\n Check the executable search path statement for all local interactive user\ninitialization files in the users' home directory with the following commands:\n\n Note: The example will be for the smithj user, which has a home directory\nof \\\"/home/smithj\\\".\n\n # grep -i path /home/smithj/.*\n /home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin\n /home/smithj/.bash_profile:export PATH\n\n If any local interactive user initialization files have executable search\npath statements that include directories outside of their home directory, this\nis a finding.\n \"\n desc \"fix\", \"\n Edit the local interactive user initialization files to change any PATH\nvariable statements that reference directories other than their home directory.\n\n If a local interactive user requires path variables to reference a\ndirectory owned by the application, it must be documented with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72035\"\n tag rid: \"SV-86659r4_rule\"\n tag stig_id: \"RHEL-07-020720\"\n tag fix_id: \"F-78387r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n findings = Set[]\n users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n grep_results = command(\"grep -i path --exclude=\\\".bash_history\\\" #{user_info.home}/.*\").stdout.split(\"\\\\n\")\n grep_results.each do |result|\n result.slice! \"PATH=\"\n # Case when last value in exec search path is :\n if result[-1] == \":\" then\n result = result + \" \"\n end\n result.slice! \"$PATH:\"\n result.gsub! '$HOME', \"#{user_info.home}\"\n result.gsub! '~', \"#{user_info.home}\"\n line_arr = result.split(\":\")\n line_arr.delete_at(0)\n line_arr.each do |line|\n # Don't run test on line that exports PATH and is not commented out\n if !line.start_with?('export') && !line.start_with?('#') then\n # Case when :: found in exec search path or : found at beginning\n if line.strip.empty? then\n curr_work_dir = command(\"pwd\").stdout.gsub(\"\\n\", \"\")\n if curr_work_dir.start_with?(\"#{user_info.home}\") then\n line = curr_work_dir\n end\n end\n # This will fail if non-home directory found in path\n if !line.start_with?(user_info.home)\n findings.add(line)\n end\n end\n end\n end\n end\n describe.one do\n describe etc_fstab do\n its('home_mount_options') { should include 'nosuid' }\n end\n describe \"Initialization files that include executable search paths that include directories outside their home directories\" do\n subject { findings.to_a }\n it { should be_empty }\n end\n end\nend\n","desc":"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).","descriptions":[{"data":"The executable search path (typically the PATH environment variable)\ncontains a list of directories for the shell to search to find executables. If\nthis path includes the current working directory (other than the user's home\ndirectory), executables in these directories may be executed instead of system\ncommands. This variable is formatted as a colon-separated list of directories.\nIf there is an empty entry, such as a leading or trailing colon or two\nconsecutive colons, this is interpreted as the current working directory. If\ndeviations from the default system search path for the local interactive user\nare required, they must be documented with the Information System Security\nOfficer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all local interactive user initialization files' executable\nsearch path statements do not contain statements that will reference a working\ndirectory other than the users' home directory.\n\n Check the executable search path statement for all local interactive user\ninitialization files in the users' home directory with the following commands:\n\n Note: The example will be for the smithj user, which has a home directory\nof \"/home/smithj\".\n\n # grep -i path /home/smithj/.*\n /home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin\n /home/smithj/.bash_profile:export PATH\n\n If any local interactive user initialization files have executable search\npath statements that include directories outside of their home directory, this\nis a finding.","label":"check"},{"data":"Edit the local interactive user initialization files to change any PATH\nvariable statements that reference directories other than their home directory.\n\n If a local interactive user requires path variables to reference a\ndirectory owned by the application, it must be documented with the ISSO.","label":"fix"}],"id":"V-72035","impact":0.5,"refs":[],"results":[{"code_desc":"File System Table File (fstab) home_mount_options is expected to include \"nosuid\"","exception":"RSpec::Core::MultipleExceptionError","message":"expected nil to include \"nosuid\", but it does not respond to `include?`","run_time":0.000512265,"start_time":"2022-03-06T22:06:04+00:00","status":"failed","resource_class":"etc_fstab","resource_params":"[]"},{"code_desc":"Initialization files that include executable search paths that include directories outside their home directories is expected to be empty","exception":"RSpec::Core::MultipleExceptionError","message":"expected `[\"/opt/mssql-tools/bin/\\n/home/vagrant/.bash_profile\", \"PATH=$PATH\", \"/opt/mssql-tools/bin/\\n/home/vagrant/.bash_profile.bak\", \"? \\\\\\n\"].empty?` to be truthy, got false","run_time":0.000312596,"start_time":"2022-03-06T22:06:04+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72035.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72035","rid":"SV-86659r4_rule","stig_id":"RHEL-07-020720","fix_id":"F-78387r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all local interactive user initialization files executable search paths\ncontain only paths that resolve to the users home directory.","waiver_data":{}},{"code":"control \"V-72037\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat local initialization files do not execute world-writable programs.\"\n if input('disable_slow_controls')\n desc \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.\"\n else\n desc \"If user start-up files execute world-writable programs, especially in\nunprotected directories, they could be maliciously modified to destroy user\nfiles or otherwise compromise the system at the user level. If the system is\ncompromised at the user level, it is easier to elevate privileges to eventually\ncompromise the system at the root and network level.\"\n end\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that local initialization files do not execute world-writable\nprograms.\n\n Check the system for world-writable files with the following command:\n\n # find / -xdev -perm -002 -type f -exec ls -ld {} \\\\; | more\n\n For all files listed, check for their presence in the local initialization\nfiles with the following commands:\n\n Note: The example will be for a system that is configured to create users'\nhome directories in the \\\"/home\\\" directory.\n\n # grep /home/*/.*\n\n If any local initialization files are found to reference world-writable\nfiles, this is a finding.\n \"\n desc \"fix\", \"\n Set the mode on files being executed by the local initialization files with\nthe following command:\n\n # chmod 0755 \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72037\"\n tag rid: \"SV-86661r2_rule\"\n tag stig_id: \"RHEL-07-020730\"\n tag fix_id: \"F-78389r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n if input('disable_slow_controls')\n describe \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.\" do\n skip \"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.\"\n end\n else\n ignore_shells = non_interactive_shells.join('|')\n\n #Get home directory for users with UID >= 1000 or UID == 0 and support interactive logins.\n dotfiles = Set[]\n u = users.where{ !shell.match(ignore_shells) && (uid >= 1000 || uid == 0)}.entries\n #For each user, build and execute a find command that identifies initialization files\n #in a user's home directory.\n u.each do |user|\n dotfiles = dotfiles + command(\"find #{user.home} -xdev -maxdepth 2 ( -name '.*' ! -name '.bash_history' ) -type f\").stdout.split(\"\\n\")\n end\n ww_files = Set[]\n ww_files = command('find / -xdev -perm -002 -type f -exec ls {} \\;').stdout.lines\n\n #To reduce the number of commands ran, we use a pattern file in the grep command below\n #So we don't have too long of a grep command, we chunk the list of ww_files\n #into strings not longer than PATTERN_FILE_MAX_LENGTH\n #Based on MAX_ARG_STRLEN, /usr/include/linux/binfmts.h\n #We cut off 100 to leave room for the rest of the arguments\n PATTERN_FILE_MAX_LENGTH=command(\"getconf PAGE_SIZE\").stdout.to_i * 32 - 100\n ww_chunked=[\"\"]\n ww_files.each do |item|\n item = item.strip\n if item.length + \"\\n\".length > PATTERN_FILE_MAX_LENGTH\n raise \"Single pattern is longer than PATTERN_FILE_MAX_LENGTH\"\n end\n if ww_chunked[-1].length + \"\\n\".length + item.length > PATTERN_FILE_MAX_LENGTH\n ww_chunked.append(\"\")\n end\n ww_chunked[-1] += \"\\n\" + item # This will leave an extra newline at the beginning of chunks\n end\n ww_chunked = ww_chunked.map(&:strip) # This gets rid of the beginning newlines\n if ww_chunked[0] == \"\"\n ww_chunked = [] # If we didn't have any ww_files, this will prevent an empty grep pattern\n end\n\n #Check each dotfile for existence of each world-writeable file\n findings = Set[]\n dotfiles.each do |dotfile|\n dotfile = dotfile.strip\n ww_chunked.each do |ww_pattern_file|\n count = command(\"grep -c -f <(echo \\\"#{ww_pattern_file}\\\") \\\"#{dotfile}\\\"\").stdout.strip.to_i\n findings << dotfile if count > 0\n end\n end\n describe \"Local initialization files that are found to reference world-writable files\" do\n subject { findings.to_a }\n it { should be_empty }\n end\n end\nend\n","desc":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","descriptions":[{"data":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that local initialization files do not execute world-writable\nprograms.\n\n Check the system for world-writable files with the following command:\n\n # find / -xdev -perm -002 -type f -exec ls -ld {} \\; | more\n\n For all files listed, check for their presence in the local initialization\nfiles with the following commands:\n\n Note: The example will be for a system that is configured to create users'\nhome directories in the \"/home\" directory.\n\n # grep /home/*/.*\n\n If any local initialization files are found to reference world-writable\nfiles, this is a finding.","label":"check"},{"data":"Set the mode on files being executed by the local initialization files with\nthe following command:\n\n # chmod 0755 ","label":"fix"}],"id":"V-72037","impact":0.5,"refs":[],"results":[{"code_desc":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute.","resource":"","run_time":0.000008098,"skip_message":"This control consistently takes a long to run and has been disabled\n using the disable_slow_controls attribute. You must enable this control for a\n full accredidation for production.","start_time":"2022-03-06T22:06:04+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72037.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72037","rid":"SV-86661r2_rule","stig_id":"RHEL-07-020730","fix_id":"F-78389r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat local initialization files do not execute world-writable programs.","waiver_data":{}},{"code":"control \"V-72039\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all system device files are correctly labeled to prevent unauthorized\nmodification.\"\n desc \"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that all system device files are correctly labeled to prevent\nunauthorized modification.\n\n List all device files on the system that are incorrectly labeled with the\nfollowing commands:\n\n Note: Device files are normally found under \\\"/dev\\\", but applications may\nplace device files in other directories and may necessitate a search of the\nentire system.\n\n #find /dev -context *:device_t:* \\\\( -type c -o -type b \\\\) -printf \\\"%p %Z\\\n \\\"\n\n #find /dev -context *:unlabeled_t:* \\\\( -type c -o -type b \\\\) -printf \\\"%p\n%Z\\\n \\\"\n\n Note: There are device files, such as \\\"/dev/vmci\\\", that are used when the\noperating system is a host virtual machine. They will not be owned by a user on\nthe system and require the \\\"device_t\\\" label to operate. These device files\nare not a finding.\n\n If there is output from either of these commands, other than already noted,\nthis is a finding.\n \"\n desc \"fix\", \"\n Run the following command to determine which package owns the device file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72039\"\n tag rid: \"SV-86663r2_rule\"\n tag stig_id: \"RHEL-07-020900\"\n tag fix_id: \"F-78391r1_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n virtual_machine = input('virtual_machine')\n\n findings = Set[]\n findings = findings + command('find / -xdev -context *:device_t:* \\( -type c -o -type b \\) -printf \"%p %Z\\n\"').stdout.split(\"\\n\")\n findings = findings + command('find / -xdev -context *:unlabeled_t:* \\( -type c -o -type b \\) -printf \"%p %Z\\n\"').stdout.split(\"\\n\")\n findings = findings + command('find / -xdev -context *:vmci_device_t:* \\( -type c -o -type b \\) -printf \"%p %Z\\n\"').stdout.split(\"\\n\")\n\n describe findings do\n if virtual_machine\n its ('length') { should cmp 1 }\n its ('first') { should include '/dev/vmci' }\n else\n its ('length') { should cmp 0 }\n end\n end\nend\n","desc":"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.","descriptions":[{"data":"If an unauthorized or modified device is allowed to exist on the\nsystem, there is the possibility the system may perform unintended or\nunauthorized operations.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that all system device files are correctly labeled to prevent\nunauthorized modification.\n\n List all device files on the system that are incorrectly labeled with the\nfollowing commands:\n\n Note: Device files are normally found under \"/dev\", but applications may\nplace device files in other directories and may necessitate a search of the\nentire system.\n\n #find /dev -context *:device_t:* \\( -type c -o -type b \\) -printf \"%p %Z \"\n\n #find /dev -context *:unlabeled_t:* \\( -type c -o -type b \\) -printf \"%p\n%Z \"\n\n Note: There are device files, such as \"/dev/vmci\", that are used when the\noperating system is a host virtual machine. They will not be owned by a user on\nthe system and require the \"device_t\" label to operate. These device files\nare not a finding.\n\n If there is output from either of these commands, other than already noted,\nthis is a finding.","label":"check"},{"data":"Run the following command to determine which package owns the device file:\n\n # rpm -qf \n\n The package can be reinstalled from a yum repository using the command:\n\n # sudo yum reinstall \n\n Alternatively, the package can be reinstalled from trusted media using the\ncommand:\n\n # sudo rpm -Uvh ","label":"fix"}],"id":"V-72039","impact":0.5,"refs":[],"results":[{"code_desc":"# length is expected to cmp == 0","run_time":0.000336196,"start_time":"2022-03-06T22:06:04+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72039.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72039","rid":"SV-86663r2_rule","stig_id":"RHEL-07-020900","fix_id":"F-78391r1_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all system device files are correctly labeled to prevent unauthorized\nmodification.","waiver_data":{}},{"code":"control \"V-72041\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat file systems containing user home directories are mounted to prevent files\nwith the setuid and setgid bit set from being executed.\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that contain user home directories are mounted with the\n\\\"nosuid\\\" option.\n\n Find the file system(s) that contain the user home directories with the\nfollowing command:\n\n Note: If a separate file system has not been created for the user home\ndirectories (user home directories are mounted under \\\"/\\\"), this is not a\nfinding as the \\\"nosuid\\\" option cannot be used on the \\\"/\\\" system.\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\"\n smithj:1001:/home/smithj\n thomasr:1002:/home/thomasr\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4\nrw,relatime,discard,data=ordered,nosuid 0 2\n\n If a file system found in \\\"/etc/fstab\\\" refers to the user home directory\nfile system and it does not have the \\\"nosuid\\\" option set, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"nosuid\\\" option on\nfile systems that contain user home directories.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72041\"\n tag rid: \"SV-86665r4_rule\"\n tag stig_id: \"RHEL-07-021000\"\n tag fix_id: \"F-78393r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe mount('/home') do\n its('options') { should include 'nosuid' }\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute setuid\nand setgid files with owner privileges. This option must be used for mounting\nany file system not containing approved setuid and setguid files. Executing\nfiles from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that contain user home directories are mounted with the\n\"nosuid\" option.\n\n Find the file system(s) that contain the user home directories with the\nfollowing command:\n\n Note: If a separate file system has not been created for the user home\ndirectories (user home directories are mounted under \"/\"), this is not a\nfinding as the \"nosuid\" option cannot be used on the \"/\" system.\n\n # cut -d: -f 1,3,6 /etc/passwd | egrep \":[1-4][0-9]{3}\"\n smithj:1001:/home/smithj\n thomasr:1002:/home/thomasr\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4\nrw,relatime,discard,data=ordered,nosuid 0 2\n\n If a file system found in \"/etc/fstab\" refers to the user home directory\nfile system and it does not have the \"nosuid\" option set, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that contain user home directories.","label":"fix"}],"id":"V-72041","impact":0.5,"refs":[],"results":[{"code_desc":"Mount /home options is expected to include \"nosuid\"","message":"expected nil to include \"nosuid\", but it does not respond to `include?`","run_time":0.02192046,"start_time":"2022-03-06T22:06:04+00:00","status":"failed","resource_class":"mount","resource_params":"[\"/home\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72041.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72041","rid":"SV-86665r4_rule","stig_id":"RHEL-07-021000","fix_id":"F-78393r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat file systems containing user home directories are mounted to prevent files\nwith the setuid and setgid bit set from being executed.","waiver_data":{}},{"code":"control \"V-72043\" do\n title \"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are used\nwith removable media.\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute\n\\\"setuid\\\" and \\\"setgid\\\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \\\"setuid\\\" and \\\"setguid\\\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that are used for removable media are mounted with the\n\\\"nosuid\\\" option.\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat\nnoauto,owner,ro,nosuid 0 0\n\n If a file system found in \\\"/etc/fstab\\\" refers to removable media and it\ndoes not have the \\\"nosuid\\\" option set, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"nosuid\\\" option on\nfile systems that are associated with removable media.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72043\"\n tag rid: \"SV-86667r2_rule\"\n tag stig_id: \"RHEL-07-021010\"\n tag fix_id: \"F-78395r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n non_removable_media_fs = input('non_removable_media_fs')\n\n file_systems = etc_fstab.params\n if !file_systems.nil? and !file_systems.empty?\n file_systems.each do |file_sys_line|\n if !\"#{non_removable_media_fs}\".include?(file_sys_line['file_system_type']) then\n describe file_sys_line['mount_options'] do\n it { should include 'nosuid' }\n end\n else\n describe \"File system \\\"#{file_sys_line['file_system_type']}\\\" does not correspond to removable media.\" do\n subject { \"#{non_removable_media_fs}\".include?(file_sys_line['file_system_type']) }\n it { should eq true }\n end\n end\n end\n else\n describe \"No file systems were found.\" do\n subject { file_systems.nil? }\n it { should eq true }\n end\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are used for removable media are mounted with the\n\"nosuid\" option.\n\n Check the file systems that are mounted at boot time with the following\ncommand:\n\n # more /etc/fstab\n\n UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat\nnoauto,owner,ro,nosuid 0 0\n\n If a file system found in \"/etc/fstab\" refers to removable media and it\ndoes not have the \"nosuid\" option set, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that are associated with removable media.","label":"fix"}],"id":"V-72043","impact":0.5,"refs":[],"results":[{"code_desc":"File system \"xfs\" does not correspond to removable media. is expected to eq true","run_time":0.000290033,"start_time":"2022-03-06T22:06:04+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"File system \"swap\" does not correspond to removable media. is expected to eq true","run_time":0.000174268,"start_time":"2022-03-06T22:06:04+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"[\"uid=1000\", \"gid=1000\", \"nofail\"] is expected to include \"nosuid\"","message":"expected [\"uid=1000\", \"gid=1000\", \"nofail\"] to include \"nosuid\"","run_time":0.000391382,"start_time":"2022-03-06T22:06:04+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72043.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72043","rid":"SV-86667r2_rule","stig_id":"RHEL-07-021010","fix_id":"F-78395r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are used\nwith removable media.","waiver_data":{}},{"code":"control \"V-72045\" do\n title \"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are\nbeing imported via Network File System (NFS).\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute\n\\\"setuid\\\" and \\\"setgid\\\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \\\"setuid\\\" and \\\"setguid\\\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that are being NFS imported are configured with the\n\\\"nosuid\\\" option.\n\n Find the file system(s) that contain the directories being exported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 0 0\n\n If a file system found in \\\"/etc/fstab\\\" refers to NFS and it does not have\nthe \\\"nosuid\\\" option set, this is a finding.\n\n Verify the NFS is mounted with the \\\"nosuid\\\" option:\n\n # mount | grep nfs | grep nosuid\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"nosuid\\\" option on\nfile systems that are being imported via NFS.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72045\"\n tag rid: \"SV-86669r2_rule\"\n tag stig_id: \"RHEL-07-021020\"\n tag fix_id: \"F-78397r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n nfs_systems = etc_fstab.nfs_file_systems.entries\n if !nfs_systems.nil? and !nfs_systems.empty?\n nfs_systems.each do |partition|\n describe partition do\n its('mount_options') { should include 'nosuid' }\n end\n end\n else\n describe \"No NFS file systems were found.\" do\n subject { nfs_systems.nil? or nfs_systems.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are being NFS imported are configured with the\n\"nosuid\" option.\n\n Find the file system(s) that contain the directories being exported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 0 0\n\n If a file system found in \"/etc/fstab\" refers to NFS and it does not have\nthe \"nosuid\" option set, this is a finding.\n\n Verify the NFS is mounted with the \"nosuid\" option:\n\n # mount | grep nfs | grep nosuid\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"nosuid\" option on\nfile systems that are being imported via NFS.","label":"fix"}],"id":"V-72045","impact":0.5,"refs":[],"results":[{"code_desc":"No NFS file systems were found. is expected to eq true","run_time":0.000116792,"start_time":"2022-03-06T22:06:04+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72045.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72045","rid":"SV-86669r2_rule","stig_id":"RHEL-07-021020","fix_id":"F-78397r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent files with\nthe setuid and setgid bit set from being executed on file systems that are\nbeing imported via Network File System (NFS).","waiver_data":{}},{"code":"control \"V-72047\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all world-writable directories are group-owned by root, sys, bin, or an\napplication group.\"\n desc \"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify all world-writable directories are group-owned by root, sys, bin, or\nan application group.\n\n Check the system for world-writable directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -xdev -perm -002 -type d -fstype xfs -exec ls -lLd {} \\\\;\n drwxrwxrwt 2 root root 40 Aug 26 13:07 /dev/mqueue\n drwxrwxrwt 2 root root 220 Aug 26 13:23 /dev/shm\n drwxrwxrwt 14 root root 4096 Aug 26 13:29 /tmp\n\n If any world-writable directories are not owned by root, sys, bin, or an\napplication group associated with the directory, this is a finding.\n \"\n desc \"fix\", \"\n Change the group of the world-writable directories to root with the\nfollowing command:\n\n # chgrp root \n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72047\"\n tag rid: \"SV-86671r4_rule\"\n tag stig_id: \"RHEL-07-021030\"\n tag fix_id: \"F-78399r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n application_groups = input('application_groups')\n\n ww_dirs = Set[]\n partitions = etc_fstab.params.map{|partition| partition['file_system_type']}.uniq\n partitions.each do |part|\n cmd = \"find / -perm -002 -xdev -type d -fstype #{part} -exec ls -lLd {} \\\\;\"\n ww_dirs = ww_dirs + command(cmd).stdout.split(\"\\n\")\n end\n\n ww_dirs.to_a.each do |curr_dir|\n dir_arr = curr_dir.split(' ')\n describe file(dir_arr.last) do\n its('group') { should be_in [\"root\",\"sys\",\"bin\"] + application_groups }\n end\n end\nend\n","desc":"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.","descriptions":[{"data":"If a world-writable directory has the sticky bit set and is not\ngroup-owned by a privileged Group Identifier (GID), unauthorized users may be\nable to modify files created by others.\n\n The only authorized public directories are those temporary directories\nsupplied with the system or those designed to be temporary file repositories.\nThe setting is normally reserved for directories used by the system and by\nusers for temporary file storage, (e.g., /tmp), and for directories requiring\nglobal read/write access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify all world-writable directories are group-owned by root, sys, bin, or\nan application group.\n\n Check the system for world-writable directories with the following command:\n\n Note: The value after -fstype must be replaced with the filesystem type.\nXFS is used as an example.\n\n # find / -xdev -perm -002 -type d -fstype xfs -exec ls -lLd {} \\;\n drwxrwxrwt 2 root root 40 Aug 26 13:07 /dev/mqueue\n drwxrwxrwt 2 root root 220 Aug 26 13:23 /dev/shm\n drwxrwxrwt 14 root root 4096 Aug 26 13:29 /tmp\n\n If any world-writable directories are not owned by root, sys, bin, or an\napplication group associated with the directory, this is a finding.","label":"check"},{"data":"Change the group of the world-writable directories to root with the\nfollowing command:\n\n # chgrp root ","label":"fix"}],"id":"V-72047","impact":0.5,"refs":[],"results":[{"code_desc":"File /var/tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.156936214,"start_time":"2022-03-06T22:06:04+00:00","status":"passed","resource_class":"file","resource_params":"[\"/var/tmp\"]"},{"code_desc":"File /var/tmp/systemd-private-c3926e6b67c84e0199f629999888189c-chronyd.service-duHdpK/tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.021755467,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/var/tmp/systemd-private-c3926e6b67c84e0199f629999888189c-chronyd.service-duHdpK/tmp\"]"},{"code_desc":"File /tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.053700503,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/tmp\"]"},{"code_desc":"File /tmp/.ICE-unix group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.126343616,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/tmp/.ICE-unix\"]"},{"code_desc":"File /tmp/.Test-unix group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.041124668,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/tmp/.Test-unix\"]"},{"code_desc":"File /tmp/.XIM-unix group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.188993852,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/tmp/.XIM-unix\"]"},{"code_desc":"File /tmp/.X11-unix group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.141808592,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/tmp/.X11-unix\"]"},{"code_desc":"File /tmp/.font-unix group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.01952091,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/tmp/.font-unix\"]"},{"code_desc":"File /tmp/systemd-private-c3926e6b67c84e0199f629999888189c-chronyd.service-HaSM5j/tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.025458872,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/tmp/systemd-private-c3926e6b67c84e0199f629999888189c-chronyd.service-HaSM5j/tmp\"]"},{"code_desc":"File /opt/rh/llvm-toolset-7/root/tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.009164341,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/opt/rh/llvm-toolset-7/root/tmp\"]"},{"code_desc":"File /opt/rh/llvm-toolset-7/root/var/tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.041739983,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/opt/rh/llvm-toolset-7/root/var/tmp\"]"},{"code_desc":"File /opt/rh/devtoolset-7/root/tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.049140051,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/opt/rh/devtoolset-7/root/tmp\"]"},{"code_desc":"File /opt/rh/devtoolset-7/root/var/tmp group is expected to be in \"root\", \"sys\", and \"bin\"","run_time":0.020407583,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/opt/rh/devtoolset-7/root/var/tmp\"]"},{"code_desc":"File /share group is expected to be in \"root\", \"sys\", and \"bin\"","message":"expected `vagrant` to be in the list: `[\"root\", \"sys\", \"bin\"]`","run_time":0.026154589,"start_time":"2022-03-06T22:06:05+00:00","status":"failed","resource_class":"file","resource_params":"[\"/share\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72047.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72047","rid":"SV-86671r4_rule","stig_id":"RHEL-07-021030","fix_id":"F-78399r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all world-writable directories are group-owned by root, sys, bin, or an\napplication group.","waiver_data":{}},{"code":"control \"V-72049\" do\n title \"The Red Hat Enterprise Linux operating system must set the umask value\nto 077 for all local interactive user accounts.\"\n desc \"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \\\"0\\\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the default umask for all local interactive users is \\\"077\\\".\n\n Identify the locations of all local interactive user home directories by\nlooking at the \\\"/etc/passwd\\\" file.\n\n Check all local interactive user initialization files for interactive users\nwith the following command:\n\n Note: The example is for a system that is configured to create users home\ndirectories in the \\\"/home\\\" directory.\n\n # grep -i umask /home/*/.*\n\n If any local interactive user initialization files are found to have a\numask statement that has a value less restrictive than \\\"077\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Remove the umask statement from all local interactive user's initialization\nfiles.\n\n If the account is for an application, the requirement for a umask less\nrestrictive than \\\"077\\\" can be documented with the Information System Security\nOfficer, but the user agreement for access to the account must specify that the\nlocal interactive user must log on to their account first and then switch the\nuser to the application account with the correct option to gain the account's\nenvironment variables.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72049\"\n tag rid: \"SV-86673r2_rule\"\n tag stig_id: \"RHEL-07-021040\"\n tag fix_id: \"F-78401r3_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n non_interactive_shells = input('non_interactive_shells')\n\n # Get all interactive users\n ignore_shells = non_interactive_shells.join('|')\n\n # Get home directory for users with UID >= 1000 or UID == 0 and support interactive logins.\n findings = Set[]\n dotfiles = Set[]\n umasks = {}\n umask_findings = Set[]\n\n # Get UID_MIN from login.defs\n uid_min = 1000\n if file(\"/etc/login.defs\").exist?\n uid_min_val = command(\"grep '^UID_MIN' /etc/login.defs | grep -Po '[0-9]+'\").stdout.split(\"\\n\")\n if !uid_min_val.empty?\n uid_min = uid_min_val[0].to_i\n end\n end\n\n interactive_users = users.where{ !shell.match(ignore_shells) && (uid >= uid_min || uid == 0)}.entries\n\n # For each user, build and execute a find command that identifies initialization files\n # in a user's home directory.\n interactive_users.each do |u|\n\n # Only check if the home directory is local\n is_local = command(\"df -l #{u.home}\").exit_status\n\n if is_local == 0\n # Get user's initialization files\n dotfiles = dotfiles + command(\"find #{u.home} -xdev -maxdepth 2 ( -name '.*' ! -name '.bash_history' ) -type f\").stdout.split(\"\\n\")\n\n # Get user's umask\n umasks.store(u.username,command(\"su -c 'umask' -l #{u.username}\").stdout.chomp(\"\\n\"))\n\n # Check all local initialization files to see whether or not they are less restrictive than 077.\n dotfiles.each do |df|\n if file(df).more_permissive_than?(\"0077\")\n findings = findings + df\n end\n end\n\n # Check umask for all interactive users\n umasks.each do |key,value|\n max_mode = (\"0077\").to_i(8)\n inv_mode = 0777 ^ max_mode\n if inv_mode & (value).to_i(8) != 0\n umask_findings = umask_findings + key\n end\n end\n else\n describe \"This control skips non-local filesystems\" do\n skip \"This control has skipped the #{u.home} home directory for #{u.username} because it is not a local filesystem.\"\n end\n end\n end\n\n # Report on any interactive files that are less restrictive than 077.\n describe \"No interactive user initialization files with a less restrictive umask were found.\" do\n subject { findings.empty? }\n it { should eq true }\n end\n\n # Report on any interactive users that have a umask less restrictive than 077.\n describe \"No users were found with a less restrictive umask were found.\" do\n subject { umask_findings.empty? }\n it { should eq true }\n end\nend\n","desc":"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \"0\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.","descriptions":[{"data":"The umask controls the default access mode assigned to newly created\nfiles. A umask of 077 limits new files to mode 700 or less permissive. Although\numask can be represented as a four-digit number, the first digit representing\nspecial access modes is typically ignored or required to be \"0\". This\nrequirement applies to the globally configured system defaults and the local\ninteractive user defaults for each account on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the default umask for all local interactive users is \"077\".\n\n Identify the locations of all local interactive user home directories by\nlooking at the \"/etc/passwd\" file.\n\n Check all local interactive user initialization files for interactive users\nwith the following command:\n\n Note: The example is for a system that is configured to create users home\ndirectories in the \"/home\" directory.\n\n # grep -i umask /home/*/.*\n\n If any local interactive user initialization files are found to have a\numask statement that has a value less restrictive than \"077\", this is a\nfinding.","label":"check"},{"data":"Remove the umask statement from all local interactive user's initialization\nfiles.\n\n If the account is for an application, the requirement for a umask less\nrestrictive than \"077\" can be documented with the Information System Security\nOfficer, but the user agreement for access to the account must specify that the\nlocal interactive user must log on to their account first and then switch the\nuser to the application account with the correct option to gain the account's\nenvironment variables.","label":"fix"}],"id":"V-72049","impact":0.5,"refs":[],"results":[{"code_desc":"No interactive user initialization files with a less restrictive umask were found. is expected to eq true","run_time":0.000193155,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"No users were found with a less restrictive umask were found. is expected to eq true","run_time":0.000136564,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72049.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72049","rid":"SV-86673r2_rule","stig_id":"RHEL-07-021040","fix_id":"F-78401r3_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must set the umask value\nto 077 for all local interactive user accounts.","waiver_data":{}},{"code":"control \"V-72051\" do\n title \"The Red Hat Enterprise Linux operating system must have cron logging\nimplemented.\"\n desc \"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that \\\"rsyslog\\\" is configured to log cron events.\n\n Check the configuration of \\\"/etc/rsyslog.conf\\\" or\n\\\"/etc/rsyslog.d/*.conf\\\" files for the cron facility with the following\ncommand:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \\\"/etc/rsyslog.conf\\\" or \\\"/etc/rsyslog.d/*.conf\\\" files.\n\n # grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n cron.* /var/log/cron.log\n\n If the command does not return a response, check for cron logging all\nfacilities by inspecting the \\\"/etc/rsyslog.conf\\\" or \\\"/etc/rsyslog.d/*.conf\\\"\nfiles.\n\n Look for the following entry:\n\n *.* /var/log/messages\n\n If \\\"rsyslog\\\" is not logging messages for the cron facility or all\nfacilities, this is a finding.\n \"\n desc \"fix\", \"\n Configure \\\"rsyslog\\\" to log all cron messages by adding or updating the\nfollowing line to \\\"/etc/rsyslog.conf\\\" or a configuration file in the\n/etc/rsyslog.d/ directory:\n\n cron.* /var/log/cron.log\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72051\"\n tag rid: \"SV-86675r2_rule\"\n tag stig_id: \"RHEL-07-021100\"\n tag fix_id: \"F-78403r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n log_pkg_path = input('log_pkg_path')\n\n describe.one do\n describe command(\"grep cron #{log_pkg_path}\") do\n its('stdout.strip') { should match %r{^cron} }\n end\n describe file(\"#{log_pkg_path}\") do\n its('content') { should match %r{^\\*\\.\\* \\/var\\/log\\/messages\\n?$} }\n its('content') { should_not match %r{^*.*\\s+~$.*^*\\.\\* \\/var\\/log\\/messages\\n?$}m }\n end\n end\nend\n","desc":"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.","descriptions":[{"data":"Cron logging can be used to trace the successful or unsuccessful\nexecution of cron jobs. It can also be used to spot intrusions into the use of\nthe cron facility by unauthorized and malicious users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that \"rsyslog\" is configured to log cron events.\n\n Check the configuration of \"/etc/rsyslog.conf\" or\n\"/etc/rsyslog.d/*.conf\" files for the cron facility with the following\ncommand:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \"/etc/rsyslog.conf\" or \"/etc/rsyslog.d/*.conf\" files.\n\n # grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n cron.* /var/log/cron.log\n\n If the command does not return a response, check for cron logging all\nfacilities by inspecting the \"/etc/rsyslog.conf\" or \"/etc/rsyslog.d/*.conf\"\nfiles.\n\n Look for the following entry:\n\n *.* /var/log/messages\n\n If \"rsyslog\" is not logging messages for the cron facility or all\nfacilities, this is a finding.","label":"check"},{"data":"Configure \"rsyslog\" to log all cron messages by adding or updating the\nfollowing line to \"/etc/rsyslog.conf\" or a configuration file in the\n/etc/rsyslog.d/ directory:\n\n cron.* /var/log/cron.log","label":"fix"}],"id":"V-72051","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `grep cron /etc/rsyslog.conf` stdout.strip is expected to match /^cron/","run_time":0.000145821,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"command","resource_params":"[\"grep cron /etc/rsyslog.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72051.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72051","rid":"SV-86675r2_rule","stig_id":"RHEL-07-021100","fix_id":"F-78403r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must have cron logging\nimplemented.","waiver_data":{}},{"code":"control \"V-72053\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is owned by root.\"\n desc \"If the owner of the \\\"cron.allow\\\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"cron.allow\\\" file is owned by root.\n\n Check the owner of the \\\"cron.allow\\\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \\\"cron.allow\\\" file exists and has an owner other than root, this is\na finding.\n \"\n desc \"fix\", \"\n Set the owner on the \\\"/etc/cron.allow\\\" file to root with the following\ncommand:\n\n # chown root /etc/cron.allow\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72053\"\n tag rid: \"SV-86677r3_rule\"\n tag stig_id: \"RHEL-07-021110\"\n tag fix_id: \"F-78405r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n # case where file doesn't exist\n describe file('/etc/cron.allow') do\n it { should_not exist }\n end\n # case where file exists\n describe file('/etc/cron.allow') do\n it { should be_owned_by 'root' }\n end\n end\nend\n","desc":"If the owner of the \"cron.allow\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.","descriptions":[{"data":"If the owner of the \"cron.allow\" file is not set to root, the\npossibility exists for an unauthorized user to view or to edit sensitive\ninformation.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"cron.allow\" file is owned by root.\n\n Check the owner of the \"cron.allow\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \"cron.allow\" file exists and has an owner other than root, this is\na finding.","label":"check"},{"data":"Set the owner on the \"/etc/cron.allow\" file to root with the following\ncommand:\n\n # chown root /etc/cron.allow","label":"fix"}],"id":"V-72053","impact":0.5,"refs":[],"results":[{"code_desc":"File /etc/cron.allow is expected not to exist","run_time":0.000177802,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/cron.allow\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72053.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72053","rid":"SV-86677r3_rule","stig_id":"RHEL-07-021110","fix_id":"F-78405r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is owned by root.","waiver_data":{}},{"code":"control \"V-72055\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is group-owned by root.\"\n desc \"If the group owner of the \\\"cron.allow\\\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"cron.allow\\\" file is group-owned by root.\n\n Check the group owner of the \\\"cron.allow\\\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \\\"cron.allow\\\" file exists and has a group owner other than root,\nthis is a finding.\n \"\n desc \"fix\", \"\n Set the group owner on the \\\"/etc/cron.allow\\\" file to root with the\nfollowing command:\n\n # chgrp root /etc/cron.allow\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72055\"\n tag rid: \"SV-86679r2_rule\"\n tag stig_id: \"RHEL-07-021120\"\n tag fix_id: \"F-78407r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n # case where file doesn't exist\n describe file('/etc/cron.allow') do\n it { should_not exist }\n end\n # case where file exists\n describe file('/etc/cron.allow') do\n its('group') { should eq 'root' }\n end\n end\nend\n","desc":"If the group owner of the \"cron.allow\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.","descriptions":[{"data":"If the group owner of the \"cron.allow\" file is not set to root,\nsensitive information could be viewed or edited by unauthorized users.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"cron.allow\" file is group-owned by root.\n\n Check the group owner of the \"cron.allow\" file with the following command:\n\n # ls -al /etc/cron.allow\n -rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow\n\n If the \"cron.allow\" file exists and has a group owner other than root,\nthis is a finding.","label":"check"},{"data":"Set the group owner on the \"/etc/cron.allow\" file to root with the\nfollowing command:\n\n # chgrp root /etc/cron.allow","label":"fix"}],"id":"V-72055","impact":0.5,"refs":[],"results":[{"code_desc":"File /etc/cron.allow is expected not to exist","run_time":0.000133648,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/cron.allow\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72055.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72055","rid":"SV-86679r2_rule","stig_id":"RHEL-07-021120","fix_id":"F-78407r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the cron.allow file, if it exists, is group-owned by root.","waiver_data":{}},{"code":"control \"V-72057\" do\n title \"The Red Hat Enterprise Linux operating system must disable Kernel core\ndumps unless needed.\"\n desc \"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that kernel core dumps are disabled unless needed.\n\n Check the status of the \\\"kdump\\\" service with the following command:\n\n # systemctl status kdump.service\n kdump.service - Crash recovery kernel arming\n Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)\n Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago\n Main PID: 1130 (code=exited, status=0/SUCCESS)\n kernel arming.\n\n If the \\\"kdump\\\" service is active, ask the System Administrator if the use\nof the service is required and documented with the Information System Security\nOfficer (ISSO).\n\n If the service is active and is not documented, this is a finding.\n \"\n desc \"fix\", \"\n If kernel core dumps are not required, disable the \\\"kdump\\\" service with\nthe following command:\n\n # systemctl disable kdump.service\n\n If kernel core dumps are required, document the need with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72057\"\n tag rid: \"SV-86681r2_rule\"\n tag stig_id: \"RHEL-07-021300\"\n tag fix_id: \"F-78409r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe systemd_service('kdump.service') do\n it { should_not be_running }\n end\nend\n","desc":"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.","descriptions":[{"data":"Kernel core dumps may contain the full contents of system memory at\nthe time of the crash. Kernel core dumps may consume a considerable amount of\ndisk space and may result in denial of service by exhausting the available\nspace on the target file system partition.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that kernel core dumps are disabled unless needed.\n\n Check the status of the \"kdump\" service with the following command:\n\n # systemctl status kdump.service\n kdump.service - Crash recovery kernel arming\n Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)\n Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago\n Main PID: 1130 (code=exited, status=0/SUCCESS)\n kernel arming.\n\n If the \"kdump\" service is active, ask the System Administrator if the use\nof the service is required and documented with the Information System Security\nOfficer (ISSO).\n\n If the service is active and is not documented, this is a finding.","label":"check"},{"data":"If kernel core dumps are not required, disable the \"kdump\" service with\nthe following command:\n\n # systemctl disable kdump.service\n\n If kernel core dumps are required, document the need with the ISSO.","label":"fix"}],"id":"V-72057","impact":0.5,"refs":[],"results":[{"code_desc":"Service kdump.service is expected not to be running","run_time":0.150156982,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"systemd_service","resource_params":"[\"kdump.service\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72057.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72057","rid":"SV-86681r2_rule","stig_id":"RHEL-07-021300","fix_id":"F-78409r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must disable Kernel core\ndumps unless needed.","waiver_data":{}},{"code":"control \"V-72059\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat a separate file system is used for user home directories (such as /home or\nan equivalent).\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a separate file system/partition has been created for\nnon-privileged local interactive user home directories.\n\n Check the home directory assignment for all non-privileged users (those\nwith a UID greater than 1000) on the system with the following command:\n\n #cut -d: -f 1,3,6,7 /etc/passwd | egrep \\\":[1-4][0-9]{3}\\\" | tr \\\":\\\"\n\\\"\\\\t\\\"\n\n adamsj /home/adamsj /bin/bash\n jacksonm /home/jacksonm /bin/bash\n smithj /home/smithj /bin/bash\n\n The output of the command will give the directory/partition that contains\nthe home directories for the non-privileged users on the system (in this\nexample, /home) and users' shell. All accounts with a valid shell (such as\n/bin/bash) are considered interactive users.\n\n Check that a file system/partition has been created for the non-privileged\ninteractive users with the following command:\n\n Note: The partition of /home is used in the example.\n\n # grep /home /etc/fstab\n UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1\n2\n\n If a separate entry for the file system/partition that contains the\nnon-privileged interactive users' home directories does not exist, this is a\nfinding.\n \"\n desc \"fix\", \"Migrate the \\\"/home\\\" directory onto a separate file\nsystem/partition.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72059\"\n tag rid: \"SV-86683r2_rule\"\n tag stig_id: \"RHEL-07-021310\"\n tag fix_id: \"F-78411r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n exempt_home_users = input('exempt_home_users')\n non_interactive_shells = input('non_interactive_shells')\n\n ignore_shells = non_interactive_shells.join('|')\n\n uid_min = login_defs.read_params['UID_MIN'].to_i\n uid_min = 1000 if uid_min.nil?\n\n # excluding root because its home directory is usually \"/root\" (mountpoint \"/\")\n users.where{ !shell.match(ignore_shells) && (uid >= uid_min)}.entries.each do |user_info|\n next if exempt_home_users.include?(\"#{user_info.username}\")\n\n home_mount = command(%(df #{user_info.home} --output=target | tail -1)).stdout.strip\n describe user_info.username do\n context 'with mountpoint' do\n context home_mount do\n it { should_not be_empty }\n it { should_not match(%r(^/$)) }\n end\n end\n end\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for\nnon-privileged local interactive user home directories.\n\n Check the home directory assignment for all non-privileged users (those\nwith a UID greater than 1000) on the system with the following command:\n\n #cut -d: -f 1,3,6,7 /etc/passwd | egrep \":[1-4][0-9]{3}\" | tr \":\"\n\"\\t\"\n\n adamsj /home/adamsj /bin/bash\n jacksonm /home/jacksonm /bin/bash\n smithj /home/smithj /bin/bash\n\n The output of the command will give the directory/partition that contains\nthe home directories for the non-privileged users on the system (in this\nexample, /home) and users' shell. All accounts with a valid shell (such as\n/bin/bash) are considered interactive users.\n\n Check that a file system/partition has been created for the non-privileged\ninteractive users with the following command:\n\n Note: The partition of /home is used in the example.\n\n # grep /home /etc/fstab\n UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1\n2\n\n If a separate entry for the file system/partition that contains the\nnon-privileged interactive users' home directories does not exist, this is a\nfinding.","label":"check"},{"data":"Migrate the \"/home\" directory onto a separate file\nsystem/partition.","label":"fix"}],"id":"V-72059","impact":0.3,"refs":[],"results":[{"code_desc":"vagrant with mountpoint / is expected not to be empty","run_time":0.020638579,"start_time":"2022-03-06T22:06:05+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"vagrant with mountpoint / is expected not to match /^\\/$/","message":"expected \"/\" not to match /^\\/$/\nDiff:\n@@ -1,2 +1,2 @@\n-/^\\/$/\n+\"/\"\n","run_time":0.000795585,"start_time":"2022-03-06T22:06:05+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72059.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72059","rid":"SV-86683r2_rule","stig_id":"RHEL-07-021310","fix_id":"F-78411r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat a separate file system is used for user home directories (such as /home or\nan equivalent).","waiver_data":{}},{"code":"control \"V-72061\" do\n title \"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /var.\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a separate file system/partition has been created for \\\"/var\\\".\n\n Check that a file system/partition has been created for \\\"/var\\\" with the\nfollowing command:\n\n # grep /var /etc/fstab\n UUID=c274f65f /var ext4 noatime,nobarrier 1\n2\n\n If a separate entry for \\\"/var\\\" is not in use, this is a finding.\n \"\n desc \"fix\", \"Migrate the \\\"/var\\\" path onto a separate file system.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72061\"\n tag rid: \"SV-86685r2_rule\"\n tag stig_id: \"RHEL-07-021320\"\n tag fix_id: \"F-78413r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe mount('/var') do\n it { should be_mounted }\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for \"/var\".\n\n Check that a file system/partition has been created for \"/var\" with the\nfollowing command:\n\n # grep /var /etc/fstab\n UUID=c274f65f /var ext4 noatime,nobarrier 1\n2\n\n If a separate entry for \"/var\" is not in use, this is a finding.","label":"check"},{"data":"Migrate the \"/var\" path onto a separate file system.","label":"fix"}],"id":"V-72061","impact":0.3,"refs":[],"results":[{"code_desc":"Mount /var is expected to be mounted","message":"\nMount /var is not mounted\n","run_time":0.022455259,"start_time":"2022-03-06T22:06:05+00:00","status":"failed","resource_class":"mount","resource_params":"[\"/var\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72061.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72061","rid":"SV-86685r2_rule","stig_id":"RHEL-07-021320","fix_id":"F-78413r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /var.","waiver_data":{}},{"code":"control \"V-72063\" do\n title \"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for the system audit data path.\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Determine if the operating system is configured to have the\n\\\"/var/log/audit\\\" path is on a separate file system.\n\n # grep /var/log/audit /etc/fstab\n\n If no result is returned, or the operating system is not configured to have\n\\\"/var/log/audit\\\" on a separate file system, this is a finding.\n\n Verify that \\\"/var/log/audit\\\" is mounted on a separate file system:\n\n # mount | grep \\\"/var/log/audit\\\"\n\n If no result is returned, or \\\"/var/log/audit\\\" is not on a separate file\nsystem, this is a finding.\n \"\n desc \"fix\", \"Migrate the system audit data path onto a separate file system.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72063\"\n tag rid: \"SV-86687r6_rule\"\n tag stig_id: \"RHEL-07-021330\"\n tag fix_id: \"F-78415r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe mount('/var/log/audit') do\n it {should be_mounted}\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Determine if the operating system is configured to have the\n\"/var/log/audit\" path is on a separate file system.\n\n # grep /var/log/audit /etc/fstab\n\n If no result is returned, or the operating system is not configured to have\n\"/var/log/audit\" on a separate file system, this is a finding.\n\n Verify that \"/var/log/audit\" is mounted on a separate file system:\n\n # mount | grep \"/var/log/audit\"\n\n If no result is returned, or \"/var/log/audit\" is not on a separate file\nsystem, this is a finding.","label":"check"},{"data":"Migrate the system audit data path onto a separate file system.","label":"fix"}],"id":"V-72063","impact":0.3,"refs":[],"results":[{"code_desc":"Mount /var/log/audit is expected to be mounted","message":"\nMount /var/log/audit is not mounted\n","run_time":0.099486397,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"mount","resource_params":"[\"/var/log/audit\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72063.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72063","rid":"SV-86687r6_rule","stig_id":"RHEL-07-021330","fix_id":"F-78415r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for the system audit data path.","waiver_data":{}},{"code":"control \"V-72065\" do\n title \"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /tmp (or equivalent).\"\n desc \"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a separate file system/partition has been created for \\\"/tmp\\\".\n\n Check that a file system/partition has been created for \\\"/tmp\\\" with the\nfollowing command:\n\n # systemctl is-enabled tmp.mount\n enabled\n\n If the \\\"tmp.mount\\\" service is not enabled, check to see if \\\"/tmp\\\" is\ndefined in the fstab with a device and mount point:\n\n # grep -i /tmp /etc/fstab\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /tmp ext4\nrw,relatime,discard,data=ordered,nosuid,noexec, 0 0\n\n If \\\"tmp.mount\\\" service is not enabled and the \\\"/tmp\\\" directory is not\ndefined in the fstab with a device and mount point, this is a finding.\n \"\n desc \"fix\", \"\n Start the \\\"tmp.mount\\\" service with the following command:\n\n # systemctl enable tmp.mount\n\n OR\n\n Edit the \\\"/etc/fstab\\\" file and ensure the \\\"/tmp\\\" directory is defined\nin the fstab with a device and mount point.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72065\"\n tag rid: \"SV-86689r3_rule\"\n tag stig_id: \"RHEL-07-021340\"\n tag fix_id: \"F-78417r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe systemd_service('tmp.mount') do\n it { should be_enabled }\n end\n describe etc_fstab.where { mount_point == '/tmp' } do\n its('count') { should cmp 1 }\n it 'Should have a device name specified' do\n expect(subject.device_name[0]).to_not(be_empty)\n end\n end\n end\nend\n","desc":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","descriptions":[{"data":"The use of separate file systems for different paths can protect the\nsystem from failures resulting from a file system becoming full or failing.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a separate file system/partition has been created for \"/tmp\".\n\n Check that a file system/partition has been created for \"/tmp\" with the\nfollowing command:\n\n # systemctl is-enabled tmp.mount\n enabled\n\n If the \"tmp.mount\" service is not enabled, check to see if \"/tmp\" is\ndefined in the fstab with a device and mount point:\n\n # grep -i /tmp /etc/fstab\n UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /tmp ext4\nrw,relatime,discard,data=ordered,nosuid,noexec, 0 0\n\n If \"tmp.mount\" service is not enabled and the \"/tmp\" directory is not\ndefined in the fstab with a device and mount point, this is a finding.","label":"check"},{"data":"Start the \"tmp.mount\" service with the following command:\n\n # systemctl enable tmp.mount\n\n OR\n\n Edit the \"/etc/fstab\" file and ensure the \"/tmp\" directory is defined\nin the fstab with a device and mount point.","label":"fix"}],"id":"V-72065","impact":0.3,"refs":[],"results":[{"code_desc":"Service tmp.mount is expected to be enabled","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `Service tmp.mount` is enabled","run_time":0.000584548,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"systemd_service","resource_params":"[\"tmp.mount\"]"},{"code_desc":"File System Table File (fstab) with mount_point == \"/tmp\" Should have a device name specified","exception":"RSpec::Core::MultipleExceptionError","message":"expected nil to respond to `empty?`","run_time":0.000844135,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"File System Table File (fstab) with mount_point == \"/tmp\" count is expected to cmp == 1","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: 1\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.000545012,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72065.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72065","rid":"SV-86689r3_rule","stig_id":"RHEL-07-021340","fix_id":"F-78417r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a separate file\nsystem for /tmp (or equivalent).","waiver_data":{}},{"code":"control \"V-72067\" do\n title \"The Red Hat Enterprise Linux operating system must implement NIST\nFIPS-validated cryptography for the following: to provision digital signatures,\nto generate cryptographic hashes, and to protect data requiring data-at-rest\nprotections in accordance with applicable federal laws, Executive Orders,\ndirectives, policies, regulations, and standards.\"\n desc \"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system implements DoD-approved encryption to protect\nthe confidentiality of remote access sessions.\n\n Check to see if the \\\"dracut-fips\\\" package is installed with the following\ncommand:\n\n # yum list installed dracut-fips\n\n dracut-fips-033-360.el7_2.x86_64.rpm\n\n If a \\\"dracut-fips\\\" package is installed, check to see if the kernel\ncommand line is configured to use FIPS mode with the following command:\n\n Note: GRUB 2 reads its configuration from the \\\"/boot/grub2/grub.cfg\\\" file\non traditional BIOS-based machines and from the\n\\\"/boot/efi/EFI/redhat/grub.cfg\\\" file on UEFI machines.\n\n # grep fips /boot/grub2/grub.cfg\n /vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0\nrd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us\nrd.lvm.lv=rhel/root rhgb fips=1 quiet\n\n If the kernel command line is configured to use FIPS mode, check to see if\nthe system is in FIPS mode with the following command:\n\n # cat /proc/sys/crypto/fips_enabled\n 1\n\n If a \\\"dracut-fips\\\" package is not installed, the kernel command line does\nnot have a fips entry, or the system has a value of \\\"0\\\" for \\\"fips_enabled\\\"\nin \\\"/proc/sys/crypto\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement DoD-approved encryption by\ninstalling the dracut-fips package.\n\n To enable strict FIPS compliance, the fips=1 kernel option needs to be\nadded to the kernel command line during system installation so key generation\nis done with FIPS-approved algorithms and continuous monitoring tests in place.\n\n Configure the operating system to implement DoD-approved encryption by\nfollowing the steps below:\n\n The fips=1 kernel option needs to be added to the kernel command line\nduring system installation so that key generation is done with FIPS-approved\nalgorithms and continuous monitoring tests in place. Users should also ensure\nthat the system has plenty of entropy during the installation process by moving\nthe mouse around, or if no mouse is available, ensuring that many keystrokes\nare typed. The recommended amount of keystrokes is 256 and more. Less than 256\nkeystrokes may generate a non-unique key.\n\n Install the dracut-fips package with the following command:\n\n # yum install dracut-fips\n\n Recreate the \\\"initramfs\\\" file with the following command:\n\n Note: This command will overwrite the existing \\\"initramfs\\\" file.\n\n # dracut -f\n\n Modify the kernel command line of the current kernel in the \\\"grub.cfg\\\"\nfile by adding the following option to the GRUB_CMDLINE_LINUX key in the\n\\\"/etc/default/grub\\\" file and then rebuild the \\\"grub.cfg\\\" file:\n\n fips=1\n\n Changes to \\\"/etc/default/grub\\\" require rebuilding the \\\"grub.cfg\\\" file\nas follows:\n\n On BIOS-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/grub2/grub.cfg\n\n On UEFI-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg\n\n If /boot or /boot/efi reside on separate partitions, the kernel parameter\nboot= must be added to the kernel command\nline. You can identify a partition by running the df /boot or df /boot/efi\ncommand:\n\n # df /boot\n Filesystem 1K-blocks Used Available Use% Mounted on\n /dev/sda1 495844 53780 416464 12% /boot\n\n To ensure the \\\"boot=\\\" configuration option will work even if device\nnaming changes occur between boots, identify the universally unique identifier\n(UUID) of the partition with the following command:\n\n # blkid /dev/sda1\n /dev/sda1: UUID=\\\"05c000f1-a213-759e-c7a2-f11b7424c797\\\" TYPE=\\\"ext4\\\"\n\n For the example above, append the following string to the kernel command\nline:\n\n boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797\n\n Reboot the system for the changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000033-GPOS-00014\"\n tag satisfies: [\"SRG-OS-000033-GPOS-00014\", \"SRG-OS-000185-GPOS-00079\",\n\"SRG-OS-000396-GPOS-00176\", \"SRG-OS-000405-GPOS-00184\",\n\"SRG-OS-000478-GPOS-00223\"]\n tag gid: \"V-72067\"\n tag rid: \"SV-86691r4_rule\"\n tag stig_id: \"RHEL-07-021350\"\n tag fix_id: \"F-78419r3_fix\"\n tag cci: [\"CCI-000068\", \"CCI-001199\", \"CCI-002450\", \"CCI-002476\"]\n tag nist: [\"AC-17 (2)\", \"SC-28\", \"SC-13\", \"SC-28 (1)\"]\n\n describe package('dracut-fips') do\n it { should be_installed }\n end\n\n all_args = command('grubby --info=ALL | grep \"^args=\" | sed \"s/^args=//g\"').\n stdout.strip.split(\"\\n\").\n map { |s| s.sub(%r{^\"(.*)\"$}, '\\1') } # strip outer quotes if they exist\n\n all_args.each { |args|\n describe args do\n it { should match %r{\\bfips=1\\b} }\n end\n }\n\n describe file('/proc/sys/crypto/fips_enabled') do\n its('content.strip') { should cmp 1 }\n end\nend\n","desc":"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.","descriptions":[{"data":"Use of weak or untested encryption algorithms undermines the purposes\nof using encryption to protect data. The operating system must implement\ncryptographic modules adhering to the higher standards approved by the federal\ngovernment since this provides assurance they have been tested and validated.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements DoD-approved encryption to protect\nthe confidentiality of remote access sessions.\n\n Check to see if the \"dracut-fips\" package is installed with the following\ncommand:\n\n # yum list installed dracut-fips\n\n dracut-fips-033-360.el7_2.x86_64.rpm\n\n If a \"dracut-fips\" package is installed, check to see if the kernel\ncommand line is configured to use FIPS mode with the following command:\n\n Note: GRUB 2 reads its configuration from the \"/boot/grub2/grub.cfg\" file\non traditional BIOS-based machines and from the\n\"/boot/efi/EFI/redhat/grub.cfg\" file on UEFI machines.\n\n # grep fips /boot/grub2/grub.cfg\n /vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0\nrd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us\nrd.lvm.lv=rhel/root rhgb fips=1 quiet\n\n If the kernel command line is configured to use FIPS mode, check to see if\nthe system is in FIPS mode with the following command:\n\n # cat /proc/sys/crypto/fips_enabled\n 1\n\n If a \"dracut-fips\" package is not installed, the kernel command line does\nnot have a fips entry, or the system has a value of \"0\" for \"fips_enabled\"\nin \"/proc/sys/crypto\", this is a finding.","label":"check"},{"data":"Configure the operating system to implement DoD-approved encryption by\ninstalling the dracut-fips package.\n\n To enable strict FIPS compliance, the fips=1 kernel option needs to be\nadded to the kernel command line during system installation so key generation\nis done with FIPS-approved algorithms and continuous monitoring tests in place.\n\n Configure the operating system to implement DoD-approved encryption by\nfollowing the steps below:\n\n The fips=1 kernel option needs to be added to the kernel command line\nduring system installation so that key generation is done with FIPS-approved\nalgorithms and continuous monitoring tests in place. Users should also ensure\nthat the system has plenty of entropy during the installation process by moving\nthe mouse around, or if no mouse is available, ensuring that many keystrokes\nare typed. The recommended amount of keystrokes is 256 and more. Less than 256\nkeystrokes may generate a non-unique key.\n\n Install the dracut-fips package with the following command:\n\n # yum install dracut-fips\n\n Recreate the \"initramfs\" file with the following command:\n\n Note: This command will overwrite the existing \"initramfs\" file.\n\n # dracut -f\n\n Modify the kernel command line of the current kernel in the \"grub.cfg\"\nfile by adding the following option to the GRUB_CMDLINE_LINUX key in the\n\"/etc/default/grub\" file and then rebuild the \"grub.cfg\" file:\n\n fips=1\n\n Changes to \"/etc/default/grub\" require rebuilding the \"grub.cfg\" file\nas follows:\n\n On BIOS-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/grub2/grub.cfg\n\n On UEFI-based machines, use the following command:\n\n # grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg\n\n If /boot or /boot/efi reside on separate partitions, the kernel parameter\nboot= must be added to the kernel command\nline. You can identify a partition by running the df /boot or df /boot/efi\ncommand:\n\n # df /boot\n Filesystem 1K-blocks Used Available Use% Mounted on\n /dev/sda1 495844 53780 416464 12% /boot\n\n To ensure the \"boot=\" configuration option will work even if device\nnaming changes occur between boots, identify the universally unique identifier\n(UUID) of the partition with the following command:\n\n # blkid /dev/sda1\n /dev/sda1: UUID=\"05c000f1-a213-759e-c7a2-f11b7424c797\" TYPE=\"ext4\"\n\n For the example above, append the following string to the kernel command\nline:\n\n boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797\n\n Reboot the system for the changes to take effect.","label":"fix"}],"id":"V-72067","impact":0.7,"refs":[],"results":[{"code_desc":"System Package dracut-fips is expected to be installed","message":"expected that `System Package dracut-fips` is installed","run_time":0.142824617,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"package","resource_params":"[\"dracut-fips\"]"},{"code_desc":"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8 is expected to match /\\bfips=1\\b/","message":"expected \"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8\" to match /\\bfips=1\\b/\nDiff:\n@@ -1,2 +1,2 @@\n-/\\bfips=1\\b/\n+\"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8\"\n","run_time":0.001744012,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8 is expected to match /\\bfips=1\\b/","message":"expected \"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8\" to match /\\bfips=1\\b/\nDiff:\n@@ -1,2 +1,2 @@\n-/\\bfips=1\\b/\n+\"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8\"\n","run_time":0.001662487,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8 is expected to match /\\bfips=1\\b/","message":"expected \"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8\" to match /\\bfips=1\\b/\nDiff:\n@@ -1,2 +1,2 @@\n-/\\bfips=1\\b/\n+\"ro no_timer_check console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 elevator=noop crashkernel=auto LANG=en_US.UTF-8\"\n","run_time":0.001154242,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"File /proc/sys/crypto/fips_enabled content.strip is expected to cmp == 1","message":"\nexpected: 1\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.001652545,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"file","resource_params":"[\"/proc/sys/crypto/fips_enabled\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72067.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000033-GPOS-00014","satisfies":["SRG-OS-000033-GPOS-00014","SRG-OS-000185-GPOS-00079","SRG-OS-000396-GPOS-00176","SRG-OS-000405-GPOS-00184","SRG-OS-000478-GPOS-00223"],"gid":"V-72067","rid":"SV-86691r4_rule","stig_id":"RHEL-07-021350","fix_id":"F-78419r3_fix","cci":["CCI-000068","CCI-001199","CCI-002450","CCI-002476"],"nist":["AC-17 (2)","SC-28","SC-13","SC-28 (1)"]},"title":"The Red Hat Enterprise Linux operating system must implement NIST\nFIPS-validated cryptography for the following: to provision digital signatures,\nto generate cryptographic hashes, and to protect data requiring data-at-rest\nprotections in accordance with applicable federal laws, Executive Orders,\ndirectives, policies, regulations, and standards.","waiver_data":{}},{"code":"control \"V-72069\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify Access Control Lists\n(ACLs).\"\n desc \"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file integrity tool is configured to verify ACLs.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \\\"aide.conf\\\" file is under the \\\"/etc\\\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \\\"aide.conf\\\" file to determine if the \\\"acl\\\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \\\"acl\\\" rule is below:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \\\"acl\\\" rule is not being used on all uncommented selection lines in\nthe \\\"/etc/aide.conf\\\" file, or ACLs are not being checked by another file\nintegrity tool, this is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to check file and directory ACLs.\n\n If AIDE is installed, ensure the \\\"acl\\\" rule is present on all uncommented\nfile and directory selection lists.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72069\"\n tag rid: \"SV-86693r3_rule\"\n tag stig_id: \"RHEL-07-021600\"\n tag fix_id: \"F-78421r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe package(\"aide\") do\n it { should be_installed }\n end\n\n findings = []\n aide_conf.where { !selection_line.start_with? '!' }.entries.each do |selection|\n unless selection.rules.include? 'acl'\n findings.append(selection.selection_line)\n end\n end\n\n describe \"List of monitored files/directories without 'acl' rule\" do\n subject { findings }\n it { should be_empty }\n end\nend\n","desc":"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.","descriptions":[{"data":"ACLs can provide permissions beyond those permitted through the file\nmode and must be verified by file integrity tools.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to verify ACLs.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"acl\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"acl\" rule is below:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"acl\" rule is not being used on all uncommented selection lines in\nthe \"/etc/aide.conf\" file, or ACLs are not being checked by another file\nintegrity tool, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to check file and directory ACLs.\n\n If AIDE is installed, ensure the \"acl\" rule is present on all uncommented\nfile and directory selection lists.","label":"fix"}],"id":"V-72069","impact":0.3,"refs":[],"results":[{"code_desc":"System Package aide is expected to be installed","run_time":0.000867225,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"package","resource_params":"[\"aide\"]"},{"code_desc":"List of monitored files/directories without 'acl' rule is expected to be empty","run_time":0.010856512,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72069.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72069","rid":"SV-86693r3_rule","stig_id":"RHEL-07-021600","fix_id":"F-78421r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify Access Control Lists\n(ACLs).","waiver_data":{}},{"code":"control \"V-72071\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify extended attributes.\"\n desc \"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file integrity tool is configured to verify extended attributes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \\\"aide.conf\\\" file is under the \\\"/etc\\\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \\\"aide.conf\\\" file to determine if the \\\"xattrs\\\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \\\"xattrs\\\" rule follows:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \\\"xattrs\\\" rule is not being used on all uncommented selection lines\nin the \\\"/etc/aide.conf\\\" file, or extended attributes are not being checked by\nanother file integrity tool, this is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to check file and directory extended\nattributes.\n\n If AIDE is installed, ensure the \\\"xattrs\\\" rule is present on all\nuncommented file and directory selection lists.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72071\"\n tag rid: \"SV-86695r3_rule\"\n tag stig_id: \"RHEL-07-021610\"\n tag fix_id: \"F-78423r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe package(\"aide\") do\n it { should be_installed }\n end\n\n findings = []\n aide_conf.where { !selection_line.start_with? '!' }.entries.each do |selection|\n unless selection.rules.include? 'xattrs'\n findings.append(selection.selection_line)\n end\n end\n\n describe \"List of monitored files/directories without 'xattrs' rule\" do\n subject { findings }\n it { should be_empty }\n end\nend\n","desc":"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.","descriptions":[{"data":"Extended attributes in file systems are used to contain arbitrary data\nand file metadata with security implications.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to verify extended attributes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"xattrs\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"xattrs\" rule follows:\n\n All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"xattrs\" rule is not being used on all uncommented selection lines\nin the \"/etc/aide.conf\" file, or extended attributes are not being checked by\nanother file integrity tool, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to check file and directory extended\nattributes.\n\n If AIDE is installed, ensure the \"xattrs\" rule is present on all\nuncommented file and directory selection lists.","label":"fix"}],"id":"V-72071","impact":0.3,"refs":[],"results":[{"code_desc":"System Package aide is expected to be installed","run_time":0.00393913,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"package","resource_params":"[\"aide\"]"},{"code_desc":"List of monitored files/directories without 'xattrs' rule is expected to be empty","run_time":0.010258949,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72071.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72071","rid":"SV-86695r3_rule","stig_id":"RHEL-07-021610","fix_id":"F-78423r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the file integrity tool is configured to verify extended attributes.","waiver_data":{}},{"code":"control \"V-72073\" do\n title \"The Red Hat Enterprise Linux operating system must use a file\nintegrity tool that is configured to use FIPS 140-2 approved cryptographic\nhashes for validating file contents and directories.\"\n desc \"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the file integrity tool is configured to use FIPS 140-2 approved\ncryptographic hashes for validating file contents and directories.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding too\nas the system cannot implement FIPS 140-2 approved cryptographic algorithms and\nhashes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \\\"aide.conf\\\" file is under the \\\"/etc\\\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \\\"aide.conf\\\" file to determine if the \\\"sha512\\\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \\\"sha512\\\" rule follows:\n\n All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \\\"sha512\\\" rule is not being used on all uncommented selection lines\nin the \\\"/etc/aide.conf\\\" file, or another file integrity tool is not using\nFIPS 140-2 approved cryptographic hashes for validating file contents and\ndirectories, this is a finding.\n \"\n desc \"fix\", \"\n Configure the file integrity tool to use FIPS 140-2 cryptographic hashes\nfor validating file and directory contents.\n\n If AIDE is installed, ensure the \\\"sha512\\\" rule is present on all\nuncommented file and directory selection lists.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72073\"\n tag rid: \"SV-86697r3_rule\"\n tag stig_id: \"RHEL-07-021620\"\n tag fix_id: \"F-78425r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe package(\"aide\") do\n it { should be_installed }\n end\n\n exclude_patterns = input('aide_exclude_patterns')\n\n findings = aide_conf.where { !selection_line.start_with?('!') && !exclude_patterns.include?(selection_line) && !rules.include?('sha512')}\n\n describe \"List of monitored files/directories without 'sha512' rule\" do\n subject { findings.selection_lines }\n it { should be_empty }\n end\nend\n","desc":"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.","descriptions":[{"data":"File integrity tools use cryptographic hashes for verifying file\ncontents and directories have not been altered. These hashes must be FIPS 140-2\napproved cryptographic hashes.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the file integrity tool is configured to use FIPS 140-2 approved\ncryptographic hashes for validating file contents and directories.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding too\nas the system cannot implement FIPS 140-2 approved cryptographic algorithms and\nhashes.\n\n Check to see if Advanced Intrusion Detection Environment (AIDE) is\ninstalled on the system with the following command:\n\n # yum list installed aide\n\n If AIDE is not installed, ask the System Administrator how file integrity\nchecks are performed on the system.\n\n If there is no application installed to perform file integrity checks, this\nis a finding.\n\n Note: AIDE is highly configurable at install time. These commands assume\nthe \"aide.conf\" file is under the \"/etc\" directory.\n\n Use the following command to determine if the file is in another location:\n\n # find / -name aide.conf\n\n Check the \"aide.conf\" file to determine if the \"sha512\" rule has been\nadded to the rule list being applied to the files and directories selection\nlists.\n\n An example rule that includes the \"sha512\" rule follows:\n\n All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux\n /bin All # apply the custom rule to the files in bin\n /sbin All # apply the same custom rule to the files in sbin\n\n If the \"sha512\" rule is not being used on all uncommented selection lines\nin the \"/etc/aide.conf\" file, or another file integrity tool is not using\nFIPS 140-2 approved cryptographic hashes for validating file contents and\ndirectories, this is a finding.","label":"check"},{"data":"Configure the file integrity tool to use FIPS 140-2 cryptographic hashes\nfor validating file and directory contents.\n\n If AIDE is installed, ensure the \"sha512\" rule is present on all\nuncommented file and directory selection lists.","label":"fix"}],"id":"V-72073","impact":0.5,"refs":[],"results":[{"code_desc":"System Package aide is expected to be installed","run_time":0.001411776,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"package","resource_params":"[\"aide\"]"},{"code_desc":"List of monitored files/directories without 'sha512' rule is expected to be empty","run_time":0.016717025,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72073.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72073","rid":"SV-86697r3_rule","stig_id":"RHEL-07-021620","fix_id":"F-78425r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a file\nintegrity tool that is configured to use FIPS 140-2 approved cryptographic\nhashes for validating file contents and directories.","waiver_data":{}},{"code":"control \"V-72075\" do\n title \"The Red Hat Enterprise Linux operating system must not allow removable\nmedia to be used as the boot loader unless approved.\"\n desc \"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system is not configured to use a boot loader on removable media.\n\n Note: GRUB 2 reads its configuration from the \\\"/boot/grub2/grub.cfg\\\" file\non traditional BIOS-based machines and from the\n\\\"/boot/efi/EFI/redhat/grub.cfg\\\" file on UEFI machines.\n\n Check for the existence of alternate boot loader configuration files with\nthe following command:\n\n # find / -name grub.cfg\n /boot/grub2/grub.cfg\n\n If a \\\"grub.cfg\\\" is found in any subdirectories other than \\\"/boot/grub2\\\"\nand \\\"/boot/efi/EFI/redhat\\\", ask the System Administrator if there is\ndocumentation signed by the ISSO to approve the use of removable media as a\nboot loader.\n\n Check that the grub configuration file has the set root command in each\nmenu entry with the following commands:\n\n # grep -c menuentry /boot/grub2/grub.cfg\n 1\n # grep 'set root' /boot/grub2/grub.cfg\n set root=(hd0,1)\n\n If the system is using an alternate boot loader on removable media, and\ndocumentation does not exist approving the alternate configuration, this is a\nfinding.\n \"\n desc \"fix\", \"Remove alternate methods of booting the system from removable\nmedia or document the configuration to boot from removable media with the ISSO.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000364-GPOS-00151\"\n tag gid: \"V-72075\"\n tag rid: \"SV-86699r2_rule\"\n tag stig_id: \"RHEL-07-021700\"\n tag fix_id: \"F-78427r1_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n roots = command('grubby --info=ALL | grep \"^root=\" | sed \"s/^root=//g\"').\n stdout.strip.split(\"\\n\")\n\n blocks = roots.map { |root|\n root_file = file(root)\n root_file.symlink? ? root_file.link_path : root_file.path\n }\n\n blocks.each { |block|\n block_file = file(block)\n describe block_file do\n it { should exist }\n its('path') { should match %r{^/dev/} }\n end\n\n if block_file.exist? and block_file.path.match? %r{^/dev/}\n removable = ['/sys/block', block.sub(%r{^/dev/}, ''), 'removable'].join('/')\n describe file(removable) do\n it { should exist }\n its('content.strip') { should eq '0' }\n end\n end\n }\nend\n","desc":"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).","descriptions":[{"data":"Malicious users with removable boot media can gain access to a system\nconfigured to use removable media as the boot loader. If removable media is\ndesigned to be used as the boot loader, the requirement must be documented with\nthe Information System Security Officer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is not configured to use a boot loader on removable media.\n\n Note: GRUB 2 reads its configuration from the \"/boot/grub2/grub.cfg\" file\non traditional BIOS-based machines and from the\n\"/boot/efi/EFI/redhat/grub.cfg\" file on UEFI machines.\n\n Check for the existence of alternate boot loader configuration files with\nthe following command:\n\n # find / -name grub.cfg\n /boot/grub2/grub.cfg\n\n If a \"grub.cfg\" is found in any subdirectories other than \"/boot/grub2\"\nand \"/boot/efi/EFI/redhat\", ask the System Administrator if there is\ndocumentation signed by the ISSO to approve the use of removable media as a\nboot loader.\n\n Check that the grub configuration file has the set root command in each\nmenu entry with the following commands:\n\n # grep -c menuentry /boot/grub2/grub.cfg\n 1\n # grep 'set root' /boot/grub2/grub.cfg\n set root=(hd0,1)\n\n If the system is using an alternate boot loader on removable media, and\ndocumentation does not exist approving the alternate configuration, this is a\nfinding.","label":"check"},{"data":"Remove alternate methods of booting the system from removable\nmedia or document the configuration to boot from removable media with the ISSO.","label":"fix"}],"id":"V-72075","impact":0.5,"refs":[],"results":[{"code_desc":"File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 is expected to exist","message":"expected File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 to exist","run_time":0.000252525,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"file","resource_params":"[\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"]"},{"code_desc":"File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 path is expected to match /^\\/dev\\//","message":"expected \"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\" to match /^\\/dev\\//\nDiff:\n@@ -1,2 +1,2 @@\n-/^\\/dev\\//\n+\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"\n","run_time":0.000556699,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"file","resource_params":"[\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"]"},{"code_desc":"File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 is expected to exist","message":"expected File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 to exist","run_time":0.000297736,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"file","resource_params":"[\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"]"},{"code_desc":"File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 path is expected to match /^\\/dev\\//","message":"expected \"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\" to match /^\\/dev\\//\nDiff:\n@@ -1,2 +1,2 @@\n-/^\\/dev\\//\n+\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"\n","run_time":0.000439098,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"file","resource_params":"[\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"]"},{"code_desc":"File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 is expected to exist","message":"expected File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 to exist","run_time":0.000248361,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"file","resource_params":"[\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"]"},{"code_desc":"File UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870 path is expected to match /^\\/dev\\//","message":"expected \"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\" to match /^\\/dev\\//\nDiff:\n@@ -1,2 +1,2 @@\n-/^\\/dev\\//\n+\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"\n","run_time":0.000385922,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"file","resource_params":"[\"UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72075.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72075","rid":"SV-86699r2_rule","stig_id":"RHEL-07-021700","fix_id":"F-78427r1_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must not allow removable\nmedia to be used as the boot loader unless approved.","waiver_data":{}},{"code":"control \"V-72077\" do\n title \"The Red Hat Enterprise Linux operating system must not have the\ntelnet-server package installed.\"\n desc \"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system is configured to disable non-essential\ncapabilities. The most secure way of ensuring a non-essential capability is\ndisabled is to not have the capability installed.\n\n The telnet service provides an unencrypted remote access service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.\n\n Check to see if the telnet-server package is installed with the following\ncommand:\n\n # yum list installed telnet-server\n\n If the telnet-server package is installed, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable non-essential capabilities by\nremoving the telnet-server package from the system with the following command:\n\n # yum remove telnet-server\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000095-GPOS-00049\"\n tag gid: \"V-72077\"\n tag rid: \"SV-86701r2_rule\"\n tag stig_id: \"RHEL-07-021710\"\n tag fix_id: \"F-78429r1_fix\"\n tag cci: [\"CCI-000381\"]\n tag nist: [\"CM-7 a\"]\n\n describe package('telnet-server') do\n it { should_not be_installed }\n end\nend\n","desc":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.","descriptions":[{"data":"It is detrimental for operating systems to provide, or install by\ndefault, functionality exceeding requirements or mission objectives. These\nunnecessary capabilities or services are often overlooked and therefore may\nremain unsecured. They increase the risk to the platform by providing\nadditional attack vectors.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services, provided by default, may not be\nnecessary to support essential organizational operations (e.g., key missions,\nfunctions).\n\n Examples of non-essential capabilities include, but are not limited to,\ngames, software packages, tools, and demonstration software not related to\nrequirements or providing a wide array of functionality not required for every\nmission, but which cannot be disabled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is configured to disable non-essential\ncapabilities. The most secure way of ensuring a non-essential capability is\ndisabled is to not have the capability installed.\n\n The telnet service provides an unencrypted remote access service that does\nnot provide for the confidentiality and integrity of user passwords or the\nremote session.\n\n If a privileged user were to log on using this service, the privileged user\npassword could be compromised.\n\n Check to see if the telnet-server package is installed with the following\ncommand:\n\n # yum list installed telnet-server\n\n If the telnet-server package is installed, this is a finding.","label":"check"},{"data":"Configure the operating system to disable non-essential capabilities by\nremoving the telnet-server package from the system with the following command:\n\n # yum remove telnet-server","label":"fix"}],"id":"V-72077","impact":0.7,"refs":[],"results":[{"code_desc":"System Package telnet-server is expected not to be installed","run_time":0.049858725,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"package","resource_params":"[\"telnet-server\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72077.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000095-GPOS-00049","gid":"V-72077","rid":"SV-86701r2_rule","stig_id":"RHEL-07-021710","fix_id":"F-78429r1_fix","cci":["CCI-000381"],"nist":["CM-7 a"]},"title":"The Red Hat Enterprise Linux operating system must not have the\ntelnet-server package installed.","waiver_data":{}},{"code":"control \"V-72079\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat auditing is configured to produce records containing information to\nestablish what type of events occurred, where the events occurred, the source\nof the events, and the outcome of the events. These audit records must also\nidentify individual identities of group account users.\"\n desc \"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system produces audit records containing information\nto establish when (date and time) the events occurred.\n\n Check to see if auditing is active by issuing the following command:\n\n # systemctl is-active auditd.service\n active\n\n If the \\\"auditd\\\" status is not active, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to produce audit records containing\ninformation to establish when (date and time) the events occurred.\n\n Enable the auditd service with the following command:\n\n # systemctl start auditd.service\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000038-GPOS-00016\"\n tag satisfies: [\"SRG-OS-000038-GPOS-00016\", \"SRG-OS-000039-GPOS-00017\",\n\"SRG-OS-000042-GPOS-00021\", \"SRG-OS-000254-GPOS-00095\",\n\"SRG-OS-000255-GPOS-00096\"]\n tag gid: \"V-72079\"\n tag rid: \"SV-86703r3_rule\"\n tag stig_id: \"RHEL-07-030000\"\n tag fix_id: \"F-78431r2_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000131\"]\n tag nist: [\"AU-2 d\", \"AU-3\"]\n\n describe service('auditd') do\n it { should be_running }\n end\nend\n","desc":"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.","descriptions":[{"data":"Without establishing what type of events occurred, it would be\ndifficult to establish, correlate, and investigate the events leading up to an\noutage or attack.\n\n Audit record content that may be necessary to satisfy this requirement\nincludes, for example, time stamps, source and destination addresses,\nuser/process identifiers, event descriptions, success/fail indications,\nfilenames involved, and access control or flow control rules invoked.\n\n Associating event types with detected events in the operating system audit\nlogs provides a means of investigating an attack; recognizing resource\nutilization or capacity thresholds; or identifying an improperly configured\noperating system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system produces audit records containing information\nto establish when (date and time) the events occurred.\n\n Check to see if auditing is active by issuing the following command:\n\n # systemctl is-active auditd.service\n active\n\n If the \"auditd\" status is not active, this is a finding.","label":"check"},{"data":"Configure the operating system to produce audit records containing\ninformation to establish when (date and time) the events occurred.\n\n Enable the auditd service with the following command:\n\n # systemctl start auditd.service","label":"fix"}],"id":"V-72079","impact":0.7,"refs":[],"results":[{"code_desc":"Service auditd is expected to be running","run_time":0.079625584,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"service","resource_params":"[\"auditd\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72079.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000038-GPOS-00016","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"],"gid":"V-72079","rid":"SV-86703r3_rule","stig_id":"RHEL-07-030000","fix_id":"F-78431r2_fix","cci":["CCI-000126","CCI-000131"],"nist":["AU-2 d","AU-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat auditing is configured to produce records containing information to\nestablish what type of events occurred, where the events occurred, the source\nof the events, and the outcome of the events. These audit records must also\nidentify individual identities of group account users.","waiver_data":{}},{"code":"control \"V-72081\" do\n title \"The Red Hat Enterprise Linux operating system must shut down upon\naudit processing failure, unless availability is an overriding concern. If\navailability is a concern, the system must alert the designated staff (System\nAdministrator [SA] and Information System Security Officer [ISSO] at a minimum)\nin the event of an audit processing failure.\"\n desc \"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Confirm the audit configuration regarding how auditing processing failures\nare handled.\n\n Check to see what level \\\"auditctl\\\" is set to with following command:\n\n # auditctl -s | grep -i \\\"fail\\\"\n\n failure 2\n\n If the value of \\\"failure\\\" is set to \\\"2\\\", the system is configured to\npanic (shut down) in the event of an auditing failure.\n\n If the value of \\\"failure\\\" is set to \\\"1\\\", the system is configured to\nonly send information to the kernel log regarding the failure.\n\n If the \\\"failure\\\" setting is not set, this is a CAT I finding.\n\n If the \\\"failure\\\" setting is set to any value other than \\\"1\\\" or \\\"2\\\",\nthis is a CAT II finding.\n\n If the \\\"failure\\\" setting is set to \\\"1\\\" but the availability concern is\nnot documented or there is no monitoring of the kernel log, this is a CAT III\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to shut down in the event of an audit\nprocessing failure.\n\n Add or correct the option to shut down the operating system with the\nfollowing command:\n\n # auditctl -f 2\n\n Edit the \\\"/etc/audit/rules.d/audit.rules\\\" file and add the following line:\n\n -f 2\n\n If availability has been determined to be more important, and this decision\nis documented with the ISSO, configure the operating system to notify system\nadministration staff and ISSO staff in the event of an audit processing failure\nwith the following command:\n\n # auditctl -f 1\n\n Edit the \\\"/etc/audit/rules.d/audit.rules\\\" file and add the following line:\n\n -f 1\n\n Kernel log monitoring must also be configured to properly alert designated\nstaff.\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000046-GPOS-00022\"\n tag satisfies: [\"SRG-OS-000046-GPOS-00022\", \"SRG-OS-000047-GPOS-00023\"]\n tag gid: \"V-72081\"\n tag rid: \"SV-86705r4_rule\"\n tag stig_id: \"RHEL-07-030010\"\n tag fix_id: \"F-78433r2_fix\"\n tag cci: [\"CCI-000139\"]\n tag nist: [\"AU-5 a\"]\n\n monitor_kernel_log = input('monitor_kernel_log')\n\n if auditd.status['failure'].nil?\n impact 0.7\n elsif auditd.status['failure'].match?(%r{^1$}) && !monitor_kernel_log\n impact 0.3\n else\n impact 0.5\n end\n\n if !monitor_kernel_log\n describe auditd.status['failure'] do\n it { should match %r{^2$} }\n end\n else\n describe auditd.status['failure'] do\n it { should match %r{^(1|2)$} }\n end\n end\nend\n","desc":"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.","descriptions":[{"data":"It is critical for the appropriate personnel to be aware if a system\nis at risk of failing to process audit logs as required. Without this\nnotification, the security personnel may be unaware of an impending failure of\nthe audit capability, and system operation may be adversely affected.\n\n Audit processing failures include software/hardware errors, failures in the\naudit capturing mechanisms, and audit storage capacity being reached or\nexceeded.\n\n This requirement applies to each audit data storage repository (i.e.,\ndistinct information system component where audit records are stored), the\ncentralized audit storage capacity of organizations (i.e., all audit data\nstorage repositories combined), or both.","label":"default"},{"data":"","label":"rationale"},{"data":"Confirm the audit configuration regarding how auditing processing failures\nare handled.\n\n Check to see what level \"auditctl\" is set to with following command:\n\n # auditctl -s | grep -i \"fail\"\n\n failure 2\n\n If the value of \"failure\" is set to \"2\", the system is configured to\npanic (shut down) in the event of an auditing failure.\n\n If the value of \"failure\" is set to \"1\", the system is configured to\nonly send information to the kernel log regarding the failure.\n\n If the \"failure\" setting is not set, this is a CAT I finding.\n\n If the \"failure\" setting is set to any value other than \"1\" or \"2\",\nthis is a CAT II finding.\n\n If the \"failure\" setting is set to \"1\" but the availability concern is\nnot documented or there is no monitoring of the kernel log, this is a CAT III\nfinding.","label":"check"},{"data":"Configure the operating system to shut down in the event of an audit\nprocessing failure.\n\n Add or correct the option to shut down the operating system with the\nfollowing command:\n\n # auditctl -f 2\n\n Edit the \"/etc/audit/rules.d/audit.rules\" file and add the following line:\n\n -f 2\n\n If availability has been determined to be more important, and this decision\nis documented with the ISSO, configure the operating system to notify system\nadministration staff and ISSO staff in the event of an audit processing failure\nwith the following command:\n\n # auditctl -f 1\n\n Edit the \"/etc/audit/rules.d/audit.rules\" file and add the following line:\n\n -f 1\n\n Kernel log monitoring must also be configured to properly alert designated\nstaff.\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72081","impact":0.5,"refs":[],"results":[{"code_desc":"1 is expected to match /^(1|2)$/","run_time":0.000560786,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72081.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000046-GPOS-00022","satisfies":["SRG-OS-000046-GPOS-00022","SRG-OS-000047-GPOS-00023"],"gid":"V-72081","rid":"SV-86705r4_rule","stig_id":"RHEL-07-030010","fix_id":"F-78433r2_fix","cci":["CCI-000139"],"nist":["AU-5 a"]},"title":"The Red Hat Enterprise Linux operating system must shut down upon\naudit processing failure, unless availability is an overriding concern. If\navailability is a concern, the system must alert the designated staff (System\nAdministrator [SA] and Information System Security Officer [ISSO] at a minimum)\nin the event of an audit processing failure.","waiver_data":{}},{"code":"control \"V-72083\" do\n title \"The Red Hat Enterprise Linux operating system must off-load audit\nrecords onto a different system or media from the system being audited.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system off-loads audit records onto a different system\nor media from the system being audited.\n\n To determine the remote server that the records are being sent to, use the\nfollowing command:\n\n # grep -i remote_server /etc/audisp/audisp-remote.conf\n remote_server = 10.0.21.1\n\n If a remote server is not configured, or the line is commented out, ask the\nSystem Administrator to indicate how the audit logs are off-loaded to a\ndifferent system or media.\n\n If there is no evidence that the audit logs are being off-loaded to another\nsystem or media, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to off-load audit records onto a different\nsystem or media from the system being audited.\n\n Set the remote server option in \\\"/etc/audisp/audisp-remote.conf\\\" with the\nIP address of the log aggregation server.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-72083\"\n tag rid: \"SV-86707r2_rule\"\n tag stig_id: \"RHEL-07-030300\"\n tag fix_id: \"F-78435r1_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n if file('/etc/audisp/audisp-remote.conf').exist?\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('remote_server'.to_s) { should match %r{^\\S+$} }\n its('remote_server'.to_s) { should_not be_in ['localhost', '127.0.0.1'] }\n end\n else\n describe \"File '/etc/audisp/audisp-remote.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '/etc/audisp/audisp-remote.conf' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system off-loads audit records onto a different system\nor media from the system being audited.\n\n To determine the remote server that the records are being sent to, use the\nfollowing command:\n\n # grep -i remote_server /etc/audisp/audisp-remote.conf\n remote_server = 10.0.21.1\n\n If a remote server is not configured, or the line is commented out, ask the\nSystem Administrator to indicate how the audit logs are off-loaded to a\ndifferent system or media.\n\n If there is no evidence that the audit logs are being off-loaded to another\nsystem or media, this is a finding.","label":"check"},{"data":"Configure the operating system to off-load audit records onto a different\nsystem or media from the system being audited.\n\n Set the remote server option in \"/etc/audisp/audisp-remote.conf\" with the\nIP address of the log aggregation server.","label":"fix"}],"id":"V-72083","impact":0.5,"refs":[],"results":[{"code_desc":"File '/etc/audisp/audisp-remote.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually","resource":"","run_time":0.000014542,"skip_message":"File '/etc/audisp/audisp-remote.conf' cannot be found. This check must be performed manually","start_time":"2022-03-06T22:06:06+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72083.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-72083","rid":"SV-86707r2_rule","stig_id":"RHEL-07-030300","fix_id":"F-78435r1_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must off-load audit\nrecords onto a different system or media from the system being audited.","waiver_data":{}},{"code":"control \"V-72085\" do\n title \"The Red Hat Enterprise Linux operating system must encrypt the\ntransfer of audit records off-loaded onto a different system or media from the\nsystem being audited.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system encrypts audit records off-loaded onto a\ndifferent system or media from the system being audited.\n\n To determine if the transfer is encrypted, use the following command:\n\n # grep -i enable_krb5 /etc/audisp/audisp-remote.conf\n enable_krb5 = yes\n\n If the value of the \\\"enable_krb5\\\" option is not set to \\\"yes\\\" or the\nline is commented out, ask the System Administrator to indicate how the audit\nlogs are off-loaded to a different system or media.\n\n If there is no evidence that the transfer of the audit logs being\noff-loaded to another system or media is encrypted, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to encrypt the transfer of off-loaded audit\nrecords onto a different system or media from the system being audited.\n\n Uncomment the \\\"enable_krb5\\\" option in \\\"/etc/audisp/audisp-remote.conf\\\"\nand set it with the following line:\n\n enable_krb5 = yes\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-72085\"\n tag rid: \"SV-86709r2_rule\"\n tag stig_id: \"RHEL-07-030310\"\n tag fix_id: \"F-78437r1_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('enable_krb5'.to_s) { should cmp 'yes' }\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system encrypts audit records off-loaded onto a\ndifferent system or media from the system being audited.\n\n To determine if the transfer is encrypted, use the following command:\n\n # grep -i enable_krb5 /etc/audisp/audisp-remote.conf\n enable_krb5 = yes\n\n If the value of the \"enable_krb5\" option is not set to \"yes\" or the\nline is commented out, ask the System Administrator to indicate how the audit\nlogs are off-loaded to a different system or media.\n\n If there is no evidence that the transfer of the audit logs being\noff-loaded to another system or media is encrypted, this is a finding.","label":"check"},{"data":"Configure the operating system to encrypt the transfer of off-loaded audit\nrecords onto a different system or media from the system being audited.\n\n Uncomment the \"enable_krb5\" option in \"/etc/audisp/audisp-remote.conf\"\nand set it with the following line:\n\n enable_krb5 = yes","label":"fix"}],"id":"V-72085","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/audisp/audisp-remote.conf","resource":"Parse Config File /etc/audisp/audisp-remote.conf","run_time":0.000012562,"skip_message":"Can't find file: /etc/audisp/audisp-remote.conf","start_time":"2022-03-06T22:06:06+00:00","status":"skipped","resource_class":"parse_config_file","resource_params":"[\"/etc/audisp/audisp-remote.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72085.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-72085","rid":"SV-86709r2_rule","stig_id":"RHEL-07-030310","fix_id":"F-78437r1_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must encrypt the\ntransfer of audit records off-loaded onto a different system or media from the\nsystem being audited.","waiver_data":{}},{"code":"control \"V-72087\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when the audit storage volume is\nfull.\"\n desc \"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the action the operating system takes if the disk the audit records\nare written to becomes full.\n\n To determine the action that takes place if the disk is full on the remote\nserver, use the following command:\n\n # grep -i disk_full_action /etc/audisp/audisp-remote.conf\n disk_full_action = single\n\n If the value of the \\\"disk_full_action\\\" option is not \\\"syslog\\\",\n\\\"single\\\", or \\\"halt\\\", or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the action the operating system takes if the disk the audit\nrecords are written to becomes full.\n\n Uncomment or edit the \\\"disk_full_action\\\" option in\n\\\"/etc/audisp/audisp-remote.conf\\\" and set it to \\\"syslog\\\", \\\"single\\\", or\n\\\"halt\\\", such as the following line:\n\n disk_full_action = single\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag gid: \"V-72087\"\n tag rid: \"SV-86711r3_rule\"\n tag stig_id: \"RHEL-07-030320\"\n tag fix_id: \"F-78439r4_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('disk_full_action'.to_s) { should be_in ['syslog', 'single', 'halt'] }\n end\n\n# Test matches ./inspec-profiles/controls/V-73163.rb\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('network_failure_action'.to_s) { should be_in ['syslog', 'single', 'halt'] }\n end\nend\n","desc":"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.","descriptions":[{"data":"Taking appropriate action in case of a filled audit storage volume\nwill minimize the possibility of losing audit records.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the action the operating system takes if the disk the audit records\nare written to becomes full.\n\n To determine the action that takes place if the disk is full on the remote\nserver, use the following command:\n\n # grep -i disk_full_action /etc/audisp/audisp-remote.conf\n disk_full_action = single\n\n If the value of the \"disk_full_action\" option is not \"syslog\",\n\"single\", or \"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the action the operating system takes if the disk the audit\nrecords are written to becomes full.\n\n Uncomment or edit the \"disk_full_action\" option in\n\"/etc/audisp/audisp-remote.conf\" and set it to \"syslog\", \"single\", or\n\"halt\", such as the following line:\n\n disk_full_action = single","label":"fix"}],"id":"V-72087","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/audisp/audisp-remote.conf","resource":"Parse Config File /etc/audisp/audisp-remote.conf","run_time":0.000006069,"skip_message":"Can't find file: /etc/audisp/audisp-remote.conf","start_time":"2022-03-06T22:06:06+00:00","status":"skipped","resource_class":"parse_config_file","resource_params":"[\"/etc/audisp/audisp-remote.conf\"]"},{"code_desc":"Parse Config File /etc/audisp/audisp-remote.conf","resource":"Parse Config File /etc/audisp/audisp-remote.conf","run_time":0.00000989,"skip_message":"Can't find file: /etc/audisp/audisp-remote.conf","start_time":"2022-03-06T22:06:06+00:00","status":"skipped","resource_class":"parse_config_file","resource_params":"[\"/etc/audisp/audisp-remote.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72087.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","gid":"V-72087","rid":"SV-86711r3_rule","stig_id":"RHEL-07-030320","fix_id":"F-78439r4_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when the audit storage volume is\nfull.","waiver_data":{}},{"code":"control \"V-72089\" do\n title \"The Red Hat Enterprise Linux operating system must initiate an action\nto notify the System Administrator (SA) and Information System Security Officer\nISSO, at a minimum, when allocated audit record storage volume reaches 75% of\nthe repository maximum audit record storage capacity.\"\n desc \"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system initiates an action to notify the SA and ISSO\n(at a minimum) when allocated audit record storage volume reaches 75 percent of\nthe repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to with the following command:\n\n # grep -iw log_file /etc/audit/auditd.conf\n log_file = /var/log/audit/audit.log\n\n Check the size of the partition that audit records are written to (with the\nexample being \\\"/var/log/audit/\\\"):\n\n # df -h /var/log/audit/\n 0.9G /var/log/audit\n\n If the audit records are not being written to a partition specifically\ncreated for audit records (in this example \\\"/var/log/audit\\\" is a separate\npartition), determine the amount of space other files in the partition are\ncurrently occupying with the following command:\n\n # du -sh \n 1.8G /var\n\n Determine what the threshold is for the system to take action when 75\npercent of the repository maximum audit record storage capacity is reached:\n\n # grep -iw space_left /etc/audit/auditd.conf\n space_left = 225\n\n If the value of the \\\"space_left\\\" keyword is not set to 25 percent of the\ntotal partition size, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to initiate an action to notify the SA and\nISSO (at a minimum) when allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to:\n\n # grep -iw log_file /etc/audit/auditd.conf\n\n Determine the size of the partition that audit records are written to (with\nthe example being \\\"/var/log/audit/\\\"):\n\n # df -h /var/log/audit/\n\n Set the value of the \\\"space_left\\\" keyword in \\\"/etc/audit/auditd.conf\\\"\nto 25 percent of the partition size.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000343-GPOS-00134\"\n tag gid: \"V-72089\"\n tag rid: \"SV-86713r4_rule\"\n tag stig_id: \"RHEL-07-030330\"\n tag fix_id: \"F-78441r3_fix\"\n tag cci: [\"CCI-001855\"]\n tag nist: [\"AU-5 (1)\"]\n\n if((f = file(audit_log_dir = command(\"dirname #{auditd_conf.log_file}\").stdout.strip)).directory?)\n # Fetch partition sizes in 1K blocks for consistency\n partition_info = command(\"df -B 1K #{audit_log_dir}\").stdout.split(\"\\n\")\n partition_sz_arr = partition_info.last.gsub(/\\s+/m, ' ').strip.split(\" \")\n\n # Get partition size\n partition_sz = partition_sz_arr[1]\n\n # Convert to MB and get 25%\n exp_space_left = partition_sz.to_i / 1024 / 4\n\n describe auditd_conf do\n its('space_left.to_i') { should be >= exp_space_left }\n end\n else\n describe f.directory? do\n it { should be true }\n end\n end\nend\n","desc":"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.","descriptions":[{"data":"If security personnel are not notified immediately when storage volume\nreaches 75 percent utilization, they are unable to plan for audit record\nstorage capacity expansion.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system initiates an action to notify the SA and ISSO\n(at a minimum) when allocated audit record storage volume reaches 75 percent of\nthe repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to with the following command:\n\n # grep -iw log_file /etc/audit/auditd.conf\n log_file = /var/log/audit/audit.log\n\n Check the size of the partition that audit records are written to (with the\nexample being \"/var/log/audit/\"):\n\n # df -h /var/log/audit/\n 0.9G /var/log/audit\n\n If the audit records are not being written to a partition specifically\ncreated for audit records (in this example \"/var/log/audit\" is a separate\npartition), determine the amount of space other files in the partition are\ncurrently occupying with the following command:\n\n # du -sh \n 1.8G /var\n\n Determine what the threshold is for the system to take action when 75\npercent of the repository maximum audit record storage capacity is reached:\n\n # grep -iw space_left /etc/audit/auditd.conf\n space_left = 225\n\n If the value of the \"space_left\" keyword is not set to 25 percent of the\ntotal partition size, this is a finding.","label":"check"},{"data":"Configure the operating system to initiate an action to notify the SA and\nISSO (at a minimum) when allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check the system configuration to determine the partition the audit records\nare being written to:\n\n # grep -iw log_file /etc/audit/auditd.conf\n\n Determine the size of the partition that audit records are written to (with\nthe example being \"/var/log/audit/\"):\n\n # df -h /var/log/audit/\n\n Set the value of the \"space_left\" keyword in \"/etc/audit/auditd.conf\"\nto 25 percent of the partition size.","label":"fix"}],"id":"V-72089","impact":0.5,"refs":[],"results":[{"code_desc":"Audit Daemon Config space_left.to_i is expected to be >= 10234","message":"expected: >= 10234\n got: 75","run_time":0.001085659,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"auditd_conf","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72089.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72089","rid":"SV-86713r4_rule","stig_id":"RHEL-07-030330","fix_id":"F-78441r3_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must initiate an action\nto notify the System Administrator (SA) and Information System Security Officer\nISSO, at a minimum, when allocated audit record storage volume reaches 75% of\nthe repository maximum audit record storage capacity.","waiver_data":{}},{"code":"control \"V-72091\" do\n title \"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) via email when the threshold for the repository maximum audit\nrecord storage capacity is reached.\"\n desc \"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check what action the operating system takes when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i space_left_action /etc/audit/auditd.conf\n space_left_action = email\n\n If the value of the \\\"space_left_action\\\" keyword is not set to \\\"email\\\",\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \\\"space_left_action\\\" keyword in\n\\\"/etc/audit/auditd.conf\\\" and set it to \\\"email\\\".\n\n space_left_action = email\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000343-GPOS-00134\"\n tag gid: \"V-72091\"\n tag rid: \"SV-86715r2_rule\"\n tag stig_id: \"RHEL-07-030340\"\n tag fix_id: \"F-78443r1_fix\"\n tag cci: [\"CCI-001855\"]\n tag nist: [\"AU-5 (1)\"]\n\n describe auditd_conf do\n its('space_left_action.downcase') { should cmp 'email' }\n end\nend\n","desc":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","descriptions":[{"data":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the allocated audit record storage volume reaches 75\npercent of the repository maximum audit record storage capacity.\n\n Check what action the operating system takes when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i space_left_action /etc/audit/auditd.conf\n space_left_action = email\n\n If the value of the \"space_left_action\" keyword is not set to \"email\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \"space_left_action\" keyword in\n\"/etc/audit/auditd.conf\" and set it to \"email\".\n\n space_left_action = email","label":"fix"}],"id":"V-72091","impact":0.5,"refs":[],"results":[{"code_desc":"Audit Daemon Config space_left_action.downcase is expected to cmp == \"email\"","message":"\nexpected: email\n got: syslog\n\n(compared using `cmp` matcher)\n","run_time":0.00140076,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"auditd_conf","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72091.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72091","rid":"SV-86715r2_rule","stig_id":"RHEL-07-030340","fix_id":"F-78443r1_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) via email when the threshold for the repository maximum audit\nrecord storage capacity is reached.","waiver_data":{}},{"code":"control \"V-72093\" do\n title \"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) when the threshold for the repository maximum audit record\nstorage capacity is reached.\"\n desc \"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the threshold for the repository maximum audit record\nstorage capacity is reached.\n\n Check what account the operating system emails when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i action_mail_acct /etc/audit/auditd.conf\n action_mail_acct = root\n\n If the value of the \\\"action_mail_acct\\\" keyword is not set to \\\"root\\\" and\nother accounts for security personnel, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \\\"action_mail_acct\\\" keyword in\n\\\"/etc/audit/auditd.conf\\\" and set it to root and any other accounts associated\nwith security personnel.\n\n action_mail_acct = root\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000343-GPOS-00134\"\n tag gid: \"V-72093\"\n tag rid: \"SV-86717r3_rule\"\n tag stig_id: \"RHEL-07-030350\"\n tag fix_id: \"F-78445r3_fix\"\n tag cci: [\"CCI-001855\"]\n tag nist: [\"AU-5 (1)\"]\n\n describe auditd_conf do\n its('action_mail_acct') { should cmp 'root' }\n end\nend\n","desc":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","descriptions":[{"data":"If security personnel are not notified immediately when the threshold\nfor the repository maximum audit record storage capacity is reached, they are\nunable to expand the audit record storage capacity before records are lost.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system immediately notifies the SA and ISSO (at a\nminimum) via email when the threshold for the repository maximum audit record\nstorage capacity is reached.\n\n Check what account the operating system emails when the threshold for the\nrepository maximum audit record storage capacity is reached with the following\ncommand:\n\n # grep -i action_mail_acct /etc/audit/auditd.conf\n action_mail_acct = root\n\n If the value of the \"action_mail_acct\" keyword is not set to \"root\" and\nother accounts for security personnel, this is a finding.","label":"check"},{"data":"Configure the operating system to immediately notify the SA and ISSO (at a\nminimum) when the threshold for the repository maximum audit record storage\ncapacity is reached.\n\n Uncomment or edit the \"action_mail_acct\" keyword in\n\"/etc/audit/auditd.conf\" and set it to root and any other accounts associated\nwith security personnel.\n\n action_mail_acct = root","label":"fix"}],"id":"V-72093","impact":0.5,"refs":[],"results":[{"code_desc":"Audit Daemon Config action_mail_acct is expected to cmp == \"root\"","run_time":0.001328763,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"auditd_conf","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72093.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000343-GPOS-00134","gid":"V-72093","rid":"SV-86717r3_rule","stig_id":"RHEL-07-030350","fix_id":"F-78445r3_fix","cci":["CCI-001855"],"nist":["AU-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must immediately notify\nthe System Administrator (SA) and Information System Security Officer (ISSO)\n(at a minimum) when the threshold for the repository maximum audit record\nstorage capacity is reached.","waiver_data":{}},{"code":"control \"V-72095\" do\n title \"The Red Hat Enterprise Linux operating system must audit all\nexecutions of privileged functions.\"\n desc \"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system audits the execution of privileged functions\nusing the following command:\n\n # grep -iw execve /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules for \\\"SUID\\\" files are not\ndefined, this is a finding.\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules for \\\"SGID\\\" files are not\ndefined, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to audit the execution of privileged\nfunctions.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000327-GPOS-00127\"\n tag gid: \"V-72095\"\n tag rid: \"SV-86719r7_rule\"\n tag stig_id: \"RHEL-07-030360\"\n tag fix_id: \"F-78447r9_fix\"\n tag cci: [\"CCI-002234\"]\n tag nist: [\"AC-6 (9)\"]\n\n # All execve calls should use 'always,exit'\n describe auditd.syscall('execve') do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n\n # Work with the SUID rules\n describe auditd.syscall('execve').where { fields.include?('euid=0') } do\n its ('arch.uniq') { should include 'b32' }\n its ('arch.uniq') { should include 'b64' }\n end\n\n # Work with the SGID rules\n describe auditd.syscall('execve').where { fields.include?('egid=0') } do\n its ('arch.uniq') { should include 'b32' }\n its ('arch.uniq') { should include 'b64' }\n end\nend\n","desc":"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.","descriptions":[{"data":"Misuse of privileged functions, either intentionally or\nunintentionally by authorized users, or by unauthorized external entities that\nhave compromised information system accounts, is a serious and ongoing concern\nand can have significant adverse impacts on organizations. Auditing the use of\nprivileged functions is one way to detect such misuse and identify the risk\nfrom insider threats and the advanced persistent threat.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system audits the execution of privileged functions\nusing the following command:\n\n # grep -iw execve /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n\n If both the \"b32\" and \"b64\" audit rules for \"SUID\" files are not\ndefined, this is a finding.\n\n If both the \"b32\" and \"b64\" audit rules for \"SGID\" files are not\ndefined, this is a finding.","label":"check"},{"data":"Configure the operating system to audit the execution of privileged\nfunctions.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid\n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid\n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72095","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"execve\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.00033644,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"execve\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000259449,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"execve\" fields include? \"euid=0\" arch.uniq is expected to include \"b32\"","message":"expected [] to include \"b32\"","run_time":0.000310551,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"execve\" fields include? \"euid=0\" arch.uniq is expected to include \"b64\"","message":"expected [] to include \"b64\"","run_time":0.000483327,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"execve\" fields include? \"egid=0\" arch.uniq is expected to include \"b32\"","message":"expected [] to include \"b32\"","run_time":0.000410145,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"execve\" fields include? \"egid=0\" arch.uniq is expected to include \"b64\"","message":"expected [] to include \"b64\"","run_time":0.002283197,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72095.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000327-GPOS-00127","gid":"V-72095","rid":"SV-86719r7_rule","stig_id":"RHEL-07-030360","fix_id":"F-78447r9_fix","cci":["CCI-002234"],"nist":["AC-6 (9)"]},"title":"The Red Hat Enterprise Linux operating system must audit all\nexecutions of privileged functions.","waiver_data":{}},{"code":"control \"V-72097\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chown syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chown\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw chown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"chown\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72097\"\n tag rid: \"SV-86721r5_rule\"\n tag stig_id: \"RHEL-07-030370\"\n tag fix_id: \"F-78449r8_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"chown\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"chown\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw chown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"chown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72097","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"chown\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000259124,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"chown\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000254643,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"chown\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.002228177,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"chown\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000631606,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72097.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72097","rid":"SV-86721r5_rule","stig_id":"RHEL-07-030370","fix_id":"F-78449r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chown syscall.","waiver_data":{}},{"code":"control \"V-72099\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchown syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchown\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchown\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72099\"\n tag rid: \"SV-86723r5_rule\"\n tag stig_id: \"RHEL-07-030380\"\n tag fix_id: \"F-78451r8_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"fchown\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchown\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72099","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"fchown\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000537985,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchown\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000184871,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchown\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000198947,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchown\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000174581,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72099.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72099","rid":"SV-86723r5_rule","stig_id":"RHEL-07-030380","fix_id":"F-78451r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchown syscall.","waiver_data":{}},{"code":"control \"V-72101\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lchown syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"lchown\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw lchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"lchown\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72101\"\n tag rid: \"SV-86725r5_rule\"\n tag stig_id: \"RHEL-07-030390\"\n tag fix_id: \"F-78453r8_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"lchown\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"lchown\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lchown\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lchown /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lchown\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72101","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"lchown\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000185109,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lchown\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.00016905,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lchown\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000184131,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lchown\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000168809,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72101.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72101","rid":"SV-86725r5_rule","stig_id":"RHEL-07-030390","fix_id":"F-78453r8_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lchown syscall.","waiver_data":{}},{"code":"control \"V-72103\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchownat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchownat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fchownat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchownat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000474-GPOS-00219\"]\n tag gid: \"V-72103\"\n tag rid: \"SV-86727r5_rule\"\n tag stig_id: \"RHEL-07-030400\"\n tag fix_id: \"F-78455r7_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\"]\n\n describe auditd.syscall(\"fchownat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchownat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchownat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fchownat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchownat\" syscall, this is a finding.","label":"check"},{"data":"Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72103","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"fchownat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000245524,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchownat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000450042,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchownat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000181354,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchownat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000884014,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72103.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000392-GPOS-00172","SRG-OS-000458-GPOS-00203","SRG-OS-000474-GPOS-00219"],"gid":"V-72103","rid":"SV-86727r5_rule","stig_id":"RHEL-07-030400","fix_id":"F-78455r7_fix","cci":["CCI-000126","CCI-000172"],"nist":["AU-2 d","AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchownat syscall.","waiver_data":{}},{"code":"control \"V-72105\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chmod syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chmod\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing command:\n\n # grep -iw chmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"chmod\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chmod\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72105\"\n tag rid: \"SV-86729r5_rule\"\n tag stig_id: \"RHEL-07-030410\"\n tag fix_id: \"F-78457r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"chmod\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"chmod\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chmod\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw chmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"chmod\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chmod\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72105","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"chmod\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000183634,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"chmod\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000905669,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"chmod\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000197296,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"chmod\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.00100707,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72105.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72105","rid":"SV-86729r5_rule","stig_id":"RHEL-07-030410","fix_id":"F-78457r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chmod syscall.","waiver_data":{}},{"code":"control \"V-72107\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmod syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmod\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing command:\n\n # grep -iw fchmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchmod\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmod\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72107\"\n tag rid: \"SV-86731r5_rule\"\n tag stig_id: \"RHEL-07-030420\"\n tag fix_id: \"F-78459r9_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fchmod\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchmod\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchmod\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw fchmod /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchmod\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fchmod\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72107","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"fchmod\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000551749,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchmod\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.002393052,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchmod\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000641669,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchmod\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000579128,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72107.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72107","rid":"SV-86731r5_rule","stig_id":"RHEL-07-030420","fix_id":"F-78459r9_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmod syscall.","waiver_data":{}},{"code":"control \"V-72109\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmodat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmodat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing command:\n\n # grep -iw fchmodat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fchmodat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fchmodat\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72109\"\n tag rid: \"SV-86733r5_rule\"\n tag stig_id: \"RHEL-07-030430\"\n tag fix_id: \"F-78461r8_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fchmodat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fchmodat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fchmodat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing command:\n\n # grep -iw fchmodat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fchmodat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fchmodat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72109","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"fchmodat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000433814,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchmodat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000367279,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchmodat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000964952,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fchmodat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000486351,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72109.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72109","rid":"SV-86733r5_rule","stig_id":"RHEL-07-030430","fix_id":"F-78461r8_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fchmodat syscall.","waiver_data":{}},{"code":"control \"V-72111\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setxattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"setxattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw setxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"setxattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"setxattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72111\"\n tag rid: \"SV-86735r5_rule\"\n tag stig_id: \"RHEL-07-030440\"\n tag fix_id: \"F-78463r8_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"setxattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"setxattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw setxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"setxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k\nperm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72111","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"setxattr\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.001152591,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"setxattr\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000252649,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"setxattr\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.001629113,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"setxattr\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000732724,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72111.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72111","rid":"SV-86735r5_rule","stig_id":"RHEL-07-030440","fix_id":"F-78463r8_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setxattr syscall.","waiver_data":{}},{"code":"control \"V-72113\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fsetxattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fsetxattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fsetxattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fsetxattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72113\"\n tag rid: \"SV-86737r5_rule\"\n tag stig_id: \"RHEL-07-030450\"\n tag fix_id: \"F-78465r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fsetxattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fsetxattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fsetxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fsetxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fsetxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72113","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"fsetxattr\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000595543,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fsetxattr\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000574473,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fsetxattr\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000318228,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fsetxattr\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000254078,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72113.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72113","rid":"SV-86737r5_rule","stig_id":"RHEL-07-030450","fix_id":"F-78465r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fsetxattr syscall.","waiver_data":{}},{"code":"control \"V-72115\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lsetxattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"lsetxattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw lsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"lsetxattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"lsetxattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72115\"\n tag rid: \"SV-86739r5_rule\"\n tag stig_id: \"RHEL-07-030460\"\n tag fix_id: \"F-78467r10_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"lsetxattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"lsetxattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lsetxattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lsetxattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lsetxattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"lsetxattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72115","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"lsetxattr\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000205243,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lsetxattr\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000185795,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lsetxattr\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.00024927,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lsetxattr\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000191524,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72115.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72115","rid":"SV-86739r5_rule","stig_id":"RHEL-07-030460","fix_id":"F-78467r10_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lsetxattr syscall.","waiver_data":{}},{"code":"control \"V-72117\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe removexattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"removexattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw removexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"removexattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"removexattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72117\"\n tag rid: \"SV-86741r5_rule\"\n tag stig_id: \"RHEL-07-030470\"\n tag fix_id: \"F-78469r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"removexattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"removexattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"removexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw removexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"removexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"removexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295\n-k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72117","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"removexattr\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000188571,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"removexattr\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000815209,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"removexattr\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000264411,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"removexattr\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000730111,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72117.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72117","rid":"SV-86741r5_rule","stig_id":"RHEL-07-030470","fix_id":"F-78469r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe removexattr syscall.","waiver_data":{}},{"code":"control \"V-72119\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fremovexattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"fremovexattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw fremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"fremovexattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"fremovexattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72119\"\n tag rid: \"SV-86743r5_rule\"\n tag stig_id: \"RHEL-07-030480\"\n tag fix_id: \"F-78471r6_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"fremovexattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"fremovexattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"fremovexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw fremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"fremovexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"fremovexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72119","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"fremovexattr\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000196104,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fremovexattr\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000319358,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fremovexattr\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000495716,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"fremovexattr\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.001923771,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72119.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72119","rid":"SV-86743r5_rule","stig_id":"RHEL-07-030480","fix_id":"F-78471r6_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe fremovexattr syscall.","waiver_data":{}},{"code":"control \"V-72121\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lremovexattr syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"lremovexattr\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw lremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"lremovexattr\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"lremovexattr\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000458-GPOS-00203\"\n tag satisfies: [\"SRG-OS-000458-GPOS-00203\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000064-GPOS-00033\"]\n tag gid: \"V-72121\"\n tag rid: \"SV-86745r5_rule\"\n tag stig_id: \"RHEL-07-030490\"\n tag fix_id: \"F-78473r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"lremovexattr\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"lremovexattr\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"lremovexattr\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw lremovexattr /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"lremovexattr\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"lremovexattr\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F\nauid!=4294967295 -k perm_mod\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72121","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"lremovexattr\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000410884,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lremovexattr\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.001399523,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lremovexattr\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000197817,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"lremovexattr\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000185911,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72121.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000458-GPOS-00203","satisfies":["SRG-OS-000458-GPOS-00203","SRG-OS-000392-GPOS-00172","SRG-OS-000064-GPOS-00033"],"gid":"V-72121","rid":"SV-86745r5_rule","stig_id":"RHEL-07-030490","fix_id":"F-78473r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe lremovexattr syscall.","waiver_data":{}},{"code":"control \"V-72123\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe creat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"creat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw creat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S creat F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"creat\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"creat\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules:\n\n -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72123\"\n tag rid: \"SV-86747r5_rule\"\n tag stig_id: \"RHEL-07-030500\"\n tag fix_id: \"F-78475r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"creat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"creat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n\n if os.arch == 'x86_64'\n describe auditd.syscall(\"creat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"creat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"creat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw creat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S creat F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"creat\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"creat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules:\n\n -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72123","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000190435,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000705663,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b32\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.000213783,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000197948,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.002412779,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b32\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000228329,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000386762,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000199416,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b64\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.000194437,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000250754,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000170954,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"creat\" arch == \"b64\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000452267,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72123.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72123","rid":"SV-86747r5_rule","stig_id":"RHEL-07-030500","fix_id":"F-78475r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe creat syscall.","waiver_data":{}},{"code":"control \"V-72125\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"open\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw open /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"open\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"open\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72125\"\n tag rid: \"SV-86749r5_rule\"\n tag stig_id: \"RHEL-07-030510\"\n tag fix_id: \"F-78477r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"open\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n\n if os.arch == 'x86_64'\n describe auditd.syscall(\"open\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"open\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw open /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"open\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"open\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72125","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000495154,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000355269,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b32\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.00053943,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000501367,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000272357,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b32\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000392672,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000440847,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000179272,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b64\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.00019604,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000178492,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000160306,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open\" arch == \"b64\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.00046102,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72125.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72125","rid":"SV-86749r5_rule","stig_id":"RHEL-07-030510","fix_id":"F-78477r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open syscall.","waiver_data":{}},{"code":"control \"V-72127\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe openat syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"openat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw openat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"openat\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"openat\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72127\"\n tag rid: \"SV-86751r5_rule\"\n tag stig_id: \"RHEL-07-030520\"\n tag fix_id: \"F-78479r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"openat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"openat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"openat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"openat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"openat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw openat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"openat\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"openat\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72127","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.0001725,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000484743,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b32\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.00018842,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.001009041,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000198997,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b32\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000607773,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000185981,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000564301,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b64\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.000197366,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.00075385,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000213287,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"openat\" arch == \"b64\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000959462,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72127.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72127","rid":"SV-86751r5_rule","stig_id":"RHEL-07-030520","fix_id":"F-78479r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe openat syscall.","waiver_data":{}},{"code":"control \"V-72129\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open_by_handle_at syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"open_by_handle_at\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw open_by_handle_at /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"open_by_handle_at\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"open_by_handle_at\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72129\"\n tag rid: \"SV-86753r5_rule\"\n tag stig_id: \"RHEL-07-030530\"\n tag fix_id: \"F-78481r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"open_by_handle_at\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"open_by_handle_at\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw open_by_handle_at /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"open_by_handle_at\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"open_by_handle_at\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F\nauid>=1000 -F auid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F\nauid>=1000 -F auid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72129","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000207918,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.00085213,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b32\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.00034284,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000483227,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.00018491,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b32\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000197803,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000184556,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000164023,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b64\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.000207378,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000203121,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000181887,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"open_by_handle_at\" arch == \"b64\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000224682,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72129.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72129","rid":"SV-86753r5_rule","stig_id":"RHEL-07-030530","fix_id":"F-78481r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe open_by_handle_at syscall.","waiver_data":{}},{"code":"control \"V-72131\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe truncate syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"truncate\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw truncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"truncate\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"truncate\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72131\"\n tag rid: \"SV-86755r5_rule\"\n tag stig_id: \"RHEL-07-030540\"\n tag fix_id: \"F-78483r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"truncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"truncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"truncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"truncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"truncate\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw truncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"truncate\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"truncate\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72131","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000180382,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000176018,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b32\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.00061297,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000197449,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000927943,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b32\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.00025196,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000729874,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000173089,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b64\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.001153688,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000189169,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000248677,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"truncate\" arch == \"b64\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000247699,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72131.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72131","rid":"SV-86755r5_rule","stig_id":"RHEL-07-030540","fix_id":"F-78483r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe truncate syscall.","waiver_data":{}},{"code":"control \"V-72133\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ftruncate syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"ftruncate\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw ftruncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"ftruncate\\\" syscall, this is a finding.\n\n If the output does not produce rules containing \\\"-F exit=-EPERM\\\", this is\na finding.\n\n If the output does not produce rules containing \\\"-F exit=-EACCES\\\", this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"ftruncate\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000064-GPOS-00033\"\n tag satisfies: [\"SRG-OS-000064-GPOS-00033\", \"SRG-OS-000458-GPOS-00203\",\n\"SRG-OS-000461-GPOS-00205\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72133\"\n tag rid: \"SV-86757r5_rule\"\n tag stig_id: \"RHEL-07-030550\"\n tag fix_id: \"F-78485r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"ftruncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"ftruncate\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"ftruncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EPERM' }\n end\n describe auditd.syscall(\"ftruncate\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n its('exit.uniq') { should include '-EACCES' }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"ftruncate\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw ftruncate /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"ftruncate\" syscall, this is a finding.\n\n If the output does not produce rules containing \"-F exit=-EPERM\", this is\na finding.\n\n If the output does not produce rules containing \"-F exit=-EACCES\", this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"ftruncate\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F\nauid!=4294967295 -k access\n\n -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F\nauid!=4294967295 -k access\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72133","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000898079,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.00021869,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b32\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.000347061,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.004151316,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000854513,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b32\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000752462,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000720404,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000498894,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b64\" exit.uniq is expected to include \"-EPERM\"","message":"expected [] to include \"-EPERM\"","run_time":0.000499097,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.001303197,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000581692,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"ftruncate\" arch == \"b64\" exit.uniq is expected to include \"-EACCES\"","message":"expected [] to include \"-EACCES\"","run_time":0.000467935,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72133.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000064-GPOS-00033","satisfies":["SRG-OS-000064-GPOS-00033","SRG-OS-000458-GPOS-00203","SRG-OS-000461-GPOS-00205","SRG-OS-000392-GPOS-00172"],"gid":"V-72133","rid":"SV-86757r5_rule","stig_id":"RHEL-07-030550","fix_id":"F-78485r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ftruncate syscall.","waiver_data":{}},{"code":"control \"V-72135\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe semanage command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"semanage\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/sbin/semanage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"semanage\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72135\"\n tag rid: \"SV-86759r4_rule\"\n tag stig_id: \"RHEL-07-030560\"\n tag fix_id: \"F-78487r5_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/semanage'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"semanage\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/semanage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"semanage\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72135","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/sbin/semanage\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000536074,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/sbin/semanage\" action is expected not to include \"never\"","run_time":0.000177223,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72135.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72135","rid":"SV-86759r4_rule","stig_id":"RHEL-07-030560","fix_id":"F-78487r5_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe semanage command.","waiver_data":{}},{"code":"control \"V-72137\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setsebool command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"setsebool\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/sbin/setsebool /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"setsebool\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72137\"\n tag rid: \"SV-86761r4_rule\"\n tag stig_id: \"RHEL-07-030570\"\n tag fix_id: \"F-78489r6_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/setsebool'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setsebool\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/setsebool /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setsebool\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F\nauid!=4294967295 -k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72137","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/sbin/setsebool\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000657311,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/sbin/setsebool\" action is expected not to include \"never\"","run_time":0.00014546,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72137.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72137","rid":"SV-86761r4_rule","stig_id":"RHEL-07-030570","fix_id":"F-78489r6_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setsebool command.","waiver_data":{}},{"code":"control \"V-72139\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chcon command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chcon\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/chcon /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chcon\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72139\"\n tag rid: \"SV-86763r4_rule\"\n tag stig_id: \"RHEL-07-030580\"\n tag fix_id: \"F-78491r6_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/chcon'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chcon\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/chcon /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chcon\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72139","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/chcon\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000618111,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/chcon\" action is expected not to include \"never\"","run_time":0.000145907,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72139.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72139","rid":"SV-86763r4_rule","stig_id":"RHEL-07-030580","fix_id":"F-78491r6_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chcon command.","waiver_data":{}},{"code":"control \"V-72141\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setfiles command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"setfiles\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw /usr/sbin/setfiles /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"setfiles\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000463-GPOS-00207\",\n\"SRG-OS-000465-GPOS-00209\"]\n tag gid: \"V-72141\"\n tag rid: \"SV-86765r5_rule\"\n tag stig_id: \"RHEL-07-030590\"\n tag fix_id: \"F-78493r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/setfiles'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"setfiles\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw /usr/sbin/setfiles /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"setfiles\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295\n-k privileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72141","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/sbin/setfiles\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000616421,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/sbin/setfiles\" action is expected not to include \"never\"","run_time":0.000142537,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72141.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000463-GPOS-00207","SRG-OS-000465-GPOS-00209"],"gid":"V-72141","rid":"SV-86765r5_rule","stig_id":"RHEL-07-030590","fix_id":"F-78493r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe setfiles command.","waiver_data":{}},{"code":"control \"V-72145\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all unsuccessful account access events.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when unsuccessful\naccount access events occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommands:\n\n # grep -i /var/run/faillock /etc/audit/audit.rules\n\n -w /var/run/faillock -p wa -k logins\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when unsuccessful\naccount access events occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /var/run/faillock -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000470-GPOS-00214\",\n\"SRG-OS-000473-GPOS-00218\"]\n tag gid: \"V-72145\"\n tag rid: \"SV-86769r4_rule\"\n tag stig_id: \"RHEL-07-030610\"\n tag fix_id: \"F-78497r4_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/var/run/faillock'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when unsuccessful\naccount access events occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommands:\n\n # grep -i /var/run/faillock /etc/audit/audit.rules\n\n -w /var/run/faillock -p wa -k logins\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when unsuccessful\naccount access events occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /var/run/faillock -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72145","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/var/run/faillock\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.000870638,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/var/run/faillock\" action is expected not to include \"never\"","run_time":0.000178168,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72145.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000470-GPOS-00214","SRG-OS-000473-GPOS-00218"],"gid":"V-72145","rid":"SV-86769r4_rule","stig_id":"RHEL-07-030610","fix_id":"F-78497r4_fix","cci":["CCI-000126","CCI-000172","CCI-002884"],"nist":["AU-2 d","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all unsuccessful account access events.","waiver_data":{}},{"code":"control \"V-72147\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all successful account access events.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when successful account\naccess events occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -i /var/log/lastlog /etc/audit/audit.rules\n\n -w /var/log/lastlog -p wa -k logins\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when successful\naccount access events occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /var/log/lastlog -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000392-GPOS-00172\"\n tag satisfies: [\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000470-GPOS-00214\",\n\"SRG-OS-000473-GPOS-00218\"]\n tag gid: \"V-72147\"\n tag rid: \"SV-86771r3_rule\"\n tag stig_id: \"RHEL-07-030620\"\n tag fix_id: \"F-78499r3_fix\"\n tag cci: [\"CCI-000126\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-2 d\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/var/log/lastlog'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when successful account\naccess events occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -i /var/log/lastlog /etc/audit/audit.rules\n\n -w /var/log/lastlog -p wa -k logins\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when successful\naccount access events occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /var/log/lastlog -p wa -k logins\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72147","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/var/log/lastlog\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.00075538,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/var/log/lastlog\" action is expected not to include \"never\"","run_time":0.000140253,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72147.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000392-GPOS-00172","satisfies":["SRG-OS-000392-GPOS-00172","SRG-OS-000470-GPOS-00214","SRG-OS-000473-GPOS-00218"],"gid":"V-72147","rid":"SV-86771r3_rule","stig_id":"RHEL-07-030620","fix_id":"F-78499r3_fix","cci":["CCI-000126","CCI-000172","CCI-002884"],"nist":["AU-2 d","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all successful account access events.","waiver_data":{}},{"code":"control \"V-72149\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe passwd command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"passwd\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/passwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"passwd\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72149\"\n tag rid: \"SV-86773r5_rule\"\n tag stig_id: \"RHEL-07-030630\"\n tag fix_id: \"F-78501r6_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/passwd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"passwd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/passwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"passwd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72149","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/passwd\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000722737,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/passwd\" action is expected not to include \"never\"","run_time":0.000160463,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72149.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72149","rid":"SV-86773r5_rule","stig_id":"RHEL-07-030630","fix_id":"F-78501r6_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe passwd command.","waiver_data":{}},{"code":"control \"V-72151\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unix_chkpwd command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"unix_chkpwd\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw /usr/sbin/unix_chkpwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"unix_chkpwd\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72151\"\n tag rid: \"SV-86775r5_rule\"\n tag stig_id: \"RHEL-07-030640\"\n tag fix_id: \"F-78503r8_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/unix_chkpwd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unix_chkpwd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw /usr/sbin/unix_chkpwd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unix_chkpwd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72151","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/sbin/unix_chkpwd\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000627354,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/sbin/unix_chkpwd\" action is expected not to include \"never\"","run_time":0.000135768,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72151.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72151","rid":"SV-86775r5_rule","stig_id":"RHEL-07-030640","fix_id":"F-78503r8_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unix_chkpwd command.","waiver_data":{}},{"code":"control \"V-72153\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe gpasswd command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"gpasswd\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/gpasswd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"gpasswd\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72153\"\n tag rid: \"SV-86777r5_rule\"\n tag stig_id: \"RHEL-07-030650\"\n tag fix_id: \"F-78505r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/gpasswd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"gpasswd\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/gpasswd /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"gpasswd\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295\n-k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72153","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/gpasswd\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000205066,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/gpasswd\" action is expected not to include \"never\"","run_time":0.000969876,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72153.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72153","rid":"SV-86777r5_rule","stig_id":"RHEL-07-030650","fix_id":"F-78505r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe gpasswd command.","waiver_data":{}},{"code":"control \"V-72155\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chage command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chage\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/bin/chage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chage\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72155\"\n tag rid: \"SV-86779r5_rule\"\n tag stig_id: \"RHEL-07-030660\"\n tag fix_id: \"F-78507r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/chage'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chage\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/bin/chage /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chage\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k\nprivileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72155","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/chage\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000271069,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/chage\" action is expected not to include \"never\"","run_time":0.000150476,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72155.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72155","rid":"SV-86779r5_rule","stig_id":"RHEL-07-030660","fix_id":"F-78507r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chage command.","waiver_data":{}},{"code":"control \"V-72157\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe userhelper command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"userhelper\\\" command occur.\n\n Check the file system rule in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -i /usr/sbin/userhelper /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"userhelper\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72157\"\n tag rid: \"SV-86781r5_rule\"\n tag stig_id: \"RHEL-07-030670\"\n tag fix_id: \"F-78509r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/userhelper'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged password commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"userhelper\" command occur.\n\n Check the file system rule in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -i /usr/sbin/userhelper /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"userhelper\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F\nauid!=4294967295 -k privileged-passwd\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72157","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/sbin/userhelper\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.00022609,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/sbin/userhelper\" action is expected not to include \"never\"","run_time":0.000167021,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72157.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72157","rid":"SV-86781r5_rule","stig_id":"RHEL-07-030670","fix_id":"F-78509r5_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe userhelper command.","waiver_data":{}},{"code":"control \"V-72159\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe su command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"su\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/bin/su /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"su\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72159\"\n tag rid: \"SV-86783r5_rule\"\n tag stig_id: \"RHEL-07-030680\"\n tag fix_id: \"F-78511r6_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/su'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"su\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/su /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"su\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72159","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/su\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000446365,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/su\" action is expected not to include \"never\"","run_time":0.000545431,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72159.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72159","rid":"SV-86783r5_rule","stig_id":"RHEL-07-030680","fix_id":"F-78511r6_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe su command.","waiver_data":{}},{"code":"control \"V-72161\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudo command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"sudo\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/bin/sudo /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"sudo\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72161\"\n tag rid: \"SV-86785r4_rule\"\n tag stig_id: \"RHEL-07-030690\"\n tag fix_id: \"F-78513r5_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/sudo'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"sudo\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/sudo /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"sudo\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72161","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/sudo\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000723134,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/sudo\" action is expected not to include \"never\"","run_time":0.001154864,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72161.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72161","rid":"SV-86785r4_rule","stig_id":"RHEL-07-030690","fix_id":"F-78513r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudo command.","waiver_data":{}},{"code":"control \"V-72163\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudoers file and all files in the /etc/sudoers.d/ directory.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to access the \\\"/etc/sudoers\\\" file and files\nin the \\\"/etc/sudoers.d/\\\" directory.\n\n Check for modification of the following files being audited by performing\nthe following commands to check the file system rules in\n\\\"/etc/audit/audit.rules\\\":\n\n # grep -i \\\"/etc/sudoers\\\" /etc/audit/audit.rules\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n # grep -i \\\"/etc/sudoers.d/\\\" /etc/audit/audit.rules\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n If the commands do not return output that match the examples, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to access the \\\"/etc/sudoers\\\" file and files\nin the \\\"/etc/sudoers.d/\\\" directory.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72163\"\n tag rid: \"SV-86787r5_rule\"\n tag stig_id: \"RHEL-07-030700\"\n tag fix_id: \"F-78517r6_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_files = ['/etc/sudoers', '/etc/sudoers.d']\n\n if audit_files.any? { |audit_file| file(audit_file).exist? }\n impact 0.5\n else\n impact 0.0\n end\n\n audit_files.each do |audit_file|\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n end\n\n describe \"The #{audit_files} files do not exist\" do\n skip \"The #{audit_files} files do not exist, this requirement is Not Applicable.\"\n end if !audit_files.any? { |audit_file| file(audit_file).exist? }\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to access the \"/etc/sudoers\" file and files\nin the \"/etc/sudoers.d/\" directory.\n\n Check for modification of the following files being audited by performing\nthe following commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -i \"/etc/sudoers\" /etc/audit/audit.rules\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n # grep -i \"/etc/sudoers.d/\" /etc/audit/audit.rules\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n If the commands do not return output that match the examples, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to access the \"/etc/sudoers\" file and files\nin the \"/etc/sudoers.d/\" directory.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/sudoers -p wa -k privileged-actions\n\n -w /etc/sudoers.d/ -p wa -k privileged-actions\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72163","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/etc/sudoers\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.001299769,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/sudoers\" action is expected not to include \"never\"","run_time":0.00112356,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/sudoers.d\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.000455876,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/sudoers.d\" action is expected not to include \"never\"","run_time":0.000289496,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72163.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72163","rid":"SV-86787r5_rule","stig_id":"RHEL-07-030700","fix_id":"F-78517r6_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe sudoers file and all files in the /etc/sudoers.d/ directory.","waiver_data":{}},{"code":"control \"V-72165\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe newgrp command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"newgrp\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -i /usr/bin/newgrp /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"newgrp\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72165\"\n tag rid: \"SV-86789r4_rule\"\n tag stig_id: \"RHEL-07-030710\"\n tag fix_id: \"F-78519r5_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/newgrp'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"newgrp\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -i /usr/bin/newgrp /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"newgrp\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72165","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/newgrp\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000320329,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/newgrp\" action is expected not to include \"never\"","run_time":0.000869125,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72165.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72165","rid":"SV-86789r4_rule","stig_id":"RHEL-07-030710","fix_id":"F-78519r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe newgrp command.","waiver_data":{}},{"code":"control \"V-72167\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chsh command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"chsh\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -i /usr/bin/chsh /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"chsh\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000037-GPOS-00015\"\n tag satisfies: [\"SRG-OS-000037-GPOS-00015\", \"SRG-OS-000042-GPOS-00020\",\n\"SRG-OS-000392-GPOS-00172\", \"SRG-OS-000462-GPOS-00206\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72167\"\n tag rid: \"SV-86791r4_rule\"\n tag stig_id: \"RHEL-07-030720\"\n tag fix_id: \"F-78521r5_fix\"\n tag cci: [\"CCI-000130\", \"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3\", \"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/chsh'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged access commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"chsh\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -i /usr/bin/chsh /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"chsh\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k\nprivileged-priv_change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72167","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/chsh\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000622447,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/chsh\" action is expected not to include \"never\"","run_time":0.000297466,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72167.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000037-GPOS-00015","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"],"gid":"V-72167","rid":"SV-86791r4_rule","stig_id":"RHEL-07-030720","fix_id":"F-78521r5_fix","cci":["CCI-000130","CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3","AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe chsh command.","waiver_data":{}},{"code":"control \"V-72171\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe mount command and syscall.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"mount\\\" command and syscall occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\\\"/etc/audit/audit.rules\\\":\n\n # grep -iw \\\"mount\\\" /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"mount\\\" syscall, this is a finding.\n\n If all uses of the \\\"mount\\\" command are not being audited, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"mount\\\" command and syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72171\"\n tag rid: \"SV-86795r7_rule\"\n tag stig_id: \"RHEL-07-030740\"\n tag fix_id: \"F-78525r9_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"mount\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n\n if os.arch == 'x86_64'\n describe auditd.syscall(\"mount\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\n\n describe auditd.path(\"/usr/bin/mount\") do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"mount\" command and syscall occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -iw \"mount\" /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"mount\" syscall, this is a finding.\n\n If all uses of the \"mount\" command are not being audited, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"mount\" command and syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n -a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72171","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"mount\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.001605075,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"mount\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000483862,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"mount\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000372368,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"mount\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000329883,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with path == \"/usr/bin/mount\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000263887,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with path == \"/usr/bin/mount\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000173269,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72171.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72171","rid":"SV-86795r7_rule","stig_id":"RHEL-07-030740","fix_id":"F-78525r9_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe mount command and syscall.","waiver_data":{}},{"code":"control \"V-72173\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe umount command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"umount\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\\\"/etc/audit/audit.rules\\\":\n\n # grep -iw \\\"/usr/bin/umount\\\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"umount\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72173\"\n tag rid: \"SV-86797r5_rule\"\n tag stig_id: \"RHEL-07-030750\"\n tag fix_id: \"F-78527r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n audit_file = '/bin/umount'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged mount commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"umount\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing series of commands to check the file system rules in\n\"/etc/audit/audit.rules\":\n\n # grep -iw \"/usr/bin/umount\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"umount\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k\nprivileged-mount\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72173","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/bin/umount\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000702933,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/bin/umount\" action is expected not to include \"never\"","run_time":0.000136307,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72173.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72173","rid":"SV-86797r5_rule","stig_id":"RHEL-07-030750","fix_id":"F-78527r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe umount command.","waiver_data":{}},{"code":"control \"V-72175\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postdrop command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"postdrop\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/sbin/postdrop /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"postdrop\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72175\"\n tag rid: \"SV-86799r4_rule\"\n tag stig_id: \"RHEL-07-030760\"\n tag fix_id: \"F-78529r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/postdrop'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"postdrop\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/sbin/postdrop /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"postdrop\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295\n-k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72175","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/sbin/postdrop\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.00074041,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/sbin/postdrop\" action is expected not to include \"never\"","run_time":0.000128658,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72175.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72175","rid":"SV-86799r4_rule","stig_id":"RHEL-07-030760","fix_id":"F-78529r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postdrop command.","waiver_data":{}},{"code":"control \"V-72177\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postqueue command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"postqueue\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/sbin/postqueue /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"postqueue\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72177\"\n tag rid: \"SV-86801r3_rule\"\n tag stig_id: \"RHEL-07-030770\"\n tag fix_id: \"F-78531r5_fix\"\n tag cci: [\"CCI-000135\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/sbin/postqueue'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged postfix commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"postqueue\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/sbin/postqueue /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"postqueue\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F\nauid!=4294967295 -k privileged-postfix\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72177","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/sbin/postqueue\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000615543,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/sbin/postqueue\" action is expected not to include \"never\"","run_time":0.000148906,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72177.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172"],"gid":"V-72177","rid":"SV-86801r3_rule","stig_id":"RHEL-07-030770","fix_id":"F-78531r5_fix","cci":["CCI-000135","CCI-002884"],"nist":["AU-3 (1)","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe postqueue command.","waiver_data":{}},{"code":"control \"V-72179\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ssh-keysign command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"ssh-keysign\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/libexec/openssh/ssh-keysign /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"ssh-keysign\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72179\"\n tag rid: \"SV-86803r3_rule\"\n tag stig_id: \"RHEL-07-030780\"\n tag fix_id: \"F-78533r4_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/libexec/openssh/ssh-keysign'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged ssh commands. The organization must maintain audit trails in\nsufficient detail to reconstruct events to determine the cause and impact of\ncompromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"ssh-keysign\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/libexec/openssh/ssh-keysign /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"ssh-keysign\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F\nauid!=4294967295 -k privileged-ssh\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72179","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/libexec/openssh/ssh-keysign\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000214018,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/libexec/openssh/ssh-keysign\" action is expected not to include \"never\"","run_time":0.000162697,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72179.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72179","rid":"SV-86803r3_rule","stig_id":"RHEL-07-030780","fix_id":"F-78533r4_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe ssh-keysign command.","waiver_data":{}},{"code":"control \"V-72183\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe crontab command.\"\n desc \"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"crontab\\\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \\\"/etc/audit/audit.rules\\\":\n\n # grep -iw /usr/bin/crontab /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"crontab\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000042-GPOS-00020\"\n tag satisfies: [\"SRG-OS-000042-GPOS-00020\", \"SRG-OS-000392-GPOS-00172\",\n\"SRG-OS-000471-GPOS-00215\"]\n tag gid: \"V-72183\"\n tag rid: \"SV-86807r3_rule\"\n tag stig_id: \"RHEL-07-030800\"\n tag fix_id: \"F-78537r4_fix\"\n tag cci: [\"CCI-000135\", \"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-3 (1)\", \"AU-12 c\", \"MA-4 (1) (a)\"]\n\n audit_file = '/usr/bin/crontab'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.","descriptions":[{"data":"Reconstruction of harmful events or forensic analysis is not possible\nif audit records do not contain enough information.\n\n At a minimum, the organization must audit the full-text recording of\nprivileged commands. The organization must maintain audit trails in sufficient\ndetail to reconstruct events to determine the cause and impact of compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"crontab\" command occur.\n\n Check that the following system call is being audited by performing the\nfollowing command to check the file system rules in \"/etc/audit/audit.rules\":\n\n # grep -iw /usr/bin/crontab /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"crontab\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295\n-k privileged-cron\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72183","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/crontab\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.000336737,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/crontab\" action is expected not to include \"never\"","run_time":0.000131469,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72183.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000042-GPOS-00020","satisfies":["SRG-OS-000042-GPOS-00020","SRG-OS-000392-GPOS-00172","SRG-OS-000471-GPOS-00215"],"gid":"V-72183","rid":"SV-86807r3_rule","stig_id":"RHEL-07-030800","fix_id":"F-78537r4_fix","cci":["CCI-000135","CCI-000172","CCI-002884"],"nist":["AU-3 (1)","AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe crontab command.","waiver_data":{}},{"code":"control \"V-72185\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe pam_timestamp_check command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"pam_timestamp_check\\\" command\noccur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw \\\"/usr/sbin/pam_timestamp_check\\\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"pam_timestamp_check\\\" command\noccur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00215\"\n tag gid: \"V-72185\"\n tag rid: \"SV-86809r4_rule\"\n tag stig_id: \"RHEL-07-030810\"\n tag fix_id: \"F-78539r4_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n audit_file = '/sbin/pam_timestamp_check'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"pam_timestamp_check\" command\noccur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw \"/usr/sbin/pam_timestamp_check\" /etc/audit/audit.rules\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"pam_timestamp_check\" command\noccur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F\nauid!=4294967295 -k privileged-pam\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72185","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/sbin/pam_timestamp_check\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.001033506,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/sbin/pam_timestamp_check\" action is expected not to include \"never\"","run_time":0.000226171,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72185.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00215","gid":"V-72185","rid":"SV-86809r4_rule","stig_id":"RHEL-07-030810","fix_id":"F-78539r4_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe pam_timestamp_check command.","waiver_data":{}},{"code":"control \"V-72187\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe init_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"init_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw init_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"init_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"init_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-72187\"\n tag rid: \"SV-86811r5_rule\"\n tag stig_id: \"RHEL-07-030820\"\n tag fix_id: \"F-78541r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"init_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"init_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"init_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw init_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"init_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"init_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S init_module -k module-change\n\n -a always,exit -F arch=b64 -S init_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72187","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"init_module\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.001146151,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"init_module\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000533264,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"init_module\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000864403,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"init_module\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000521883,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72187.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72187","rid":"SV-86811r5_rule","stig_id":"RHEL-07-030820","fix_id":"F-78541r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe init_module syscall.","waiver_data":{}},{"code":"control \"V-72189\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe delete_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"delete_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw delete_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"delete_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"delete_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-72189\"\n tag rid: \"SV-86813r5_rule\"\n tag stig_id: \"RHEL-07-030830\"\n tag fix_id: \"F-78543r7_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"delete_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"delete_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"delete_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw delete_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"delete_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"delete_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S delete_module -k module-change\n\n -a always,exit -F arch=b64 -S delete_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72189","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"delete_module\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000646894,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"delete_module\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000240828,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"delete_module\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000754519,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"delete_module\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000187646,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72189.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72189","rid":"SV-86813r5_rule","stig_id":"RHEL-07-030830","fix_id":"F-78543r7_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe delete_module syscall.","waiver_data":{}},{"code":"control \"V-72191\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe kmod command.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"kmod\\\" command occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw kmod /etc/audit/audit.rules\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n If the command does not return any output, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"kmod\\\" command occur.\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-72191\"\n tag rid: \"SV-86815r5_rule\"\n tag stig_id: \"RHEL-07-030840\"\n tag fix_id: \"F-78545r10_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n audit_file = '/usr/bin/kmod'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should include ['x'] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"kmod\" command occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw kmod /etc/audit/audit.rules\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n If the command does not return any output, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"kmod\" command occur.\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72191","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/usr/bin/kmod\" permissions is expected to include [\"x\"]","message":"expected [] to include [\"x\"]","run_time":0.00026779,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/usr/bin/kmod\" action is expected not to include \"never\"","run_time":0.000708288,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72191.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-72191","rid":"SV-86815r5_rule","stig_id":"RHEL-07-030840","fix_id":"F-78545r10_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe kmod command.","waiver_data":{}},{"code":"control \"V-72197\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/passwd.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/passwd\\\".\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/passwd /etc/audit/audit.rules\n\n -w /etc/passwd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/passwd\\\".\n\n Add or update the following rule \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/passwd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag satisfies: [\"SRG-OS-000004-GPOS-00004\", \"SRG-OS-000239-GPOS-00089\",\n\"SRG-OS-000240-GPOS-00090\", \"SRG-OS-000241-GPOS-00091\",\n\"SRG-OS-000303-GPOS-00120\", \"SRG-OS-000476-GPOS-00221\"]\n tag gid: \"V-72197\"\n tag rid: \"SV-86821r5_rule\"\n tag stig_id: \"RHEL-07-030870\"\n tag fix_id: \"F-78551r4_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/passwd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/passwd\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/passwd /etc/audit/audit.rules\n\n -w /etc/passwd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/passwd\".\n\n Add or update the following rule \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/passwd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72197","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/etc/passwd\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.00030791,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/passwd\" action is expected not to include \"never\"","run_time":0.000244831,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72197.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","satisfies":["SRG-OS-000004-GPOS-00004","SRG-OS-000239-GPOS-00089","SRG-OS-000240-GPOS-00090","SRG-OS-000241-GPOS-00091","SRG-OS-000303-GPOS-00120","SRG-OS-000476-GPOS-00221"],"gid":"V-72197","rid":"SV-86821r5_rule","stig_id":"RHEL-07-030870","fix_id":"F-78551r4_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/passwd.","waiver_data":{}},{"code":"control \"V-72199\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rename syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"rename\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw rename /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"rename\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"rename\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72199\"\n tag rid: \"SV-86823r5_rule\"\n tag stig_id: \"RHEL-07-030880\"\n tag fix_id: \"F-78553r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"rename\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"rename\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"rename\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw rename /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"rename\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"rename\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72199","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"rename\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000533182,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"rename\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.001551587,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"rename\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.003055207,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"rename\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000470464,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72199.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72199","rid":"SV-86823r5_rule","stig_id":"RHEL-07-030880","fix_id":"F-78553r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rename syscall.","waiver_data":{}},{"code":"control \"V-72201\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe renameat syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"renameat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw renameat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"renameat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"renameat\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72201\"\n tag rid: \"SV-86825r5_rule\"\n tag stig_id: \"RHEL-07-030890\"\n tag fix_id: \"F-78555r8_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"renameat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"renameat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"renameat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw renameat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"renameat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"renameat\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72201","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"renameat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000794277,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"renameat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.001660916,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"renameat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.001651801,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"renameat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000506031,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72201.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72201","rid":"SV-86825r5_rule","stig_id":"RHEL-07-030890","fix_id":"F-78555r8_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe renameat syscall.","waiver_data":{}},{"code":"control \"V-72203\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rmdir syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"rmdir\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw rmdir /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"rmdir\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"rmdir\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72203\"\n tag rid: \"SV-86827r5_rule\"\n tag stig_id: \"RHEL-07-030900\"\n tag fix_id: \"F-78557r9_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"rmdir\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"rmdir\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"rmdir\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw rmdir /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"rmdir\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"rmdir\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72203","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"rmdir\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000381616,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"rmdir\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.001922676,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"rmdir\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000752506,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"rmdir\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000288475,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72203.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72203","rid":"SV-86827r5_rule","stig_id":"RHEL-07-030900","fix_id":"F-78557r9_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe rmdir syscall.","waiver_data":{}},{"code":"control \"V-72205\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlink syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlink\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw unlink /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"unlink\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlink\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72205\"\n tag rid: \"SV-86829r5_rule\"\n tag stig_id: \"RHEL-07-030910\"\n tag fix_id: \"F-78559r7_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"unlink\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"unlink\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unlink\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw unlink /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"unlink\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unlink\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72205","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"unlink\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000288294,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"unlink\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000946668,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"unlink\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000191375,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"unlink\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000917545,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72205.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72205","rid":"SV-86829r5_rule","stig_id":"RHEL-07-030910","fix_id":"F-78559r7_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlink syscall.","waiver_data":{}},{"code":"control \"V-72207\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlinkat syscall.\"\n desc \"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlinkat\\\" syscall occur.\n\n Check the file system rules in \\\"/etc/audit/audit.rules\\\" with the\nfollowing commands:\n\n # grep -iw unlinkat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"unlinkat\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"unlinkat\\\" syscall occur.\n\n Add the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000466-GPOS-00210\"\n tag satisfies: [\"SRG-OS-000466-GPOS-00210\", \"SRG-OS-000467-GPOS-00210\",\n\"SRG-OS-000468-GPOS-00212\", \"SRG-OS-000392-GPOS-00172\"]\n tag gid: \"V-72207\"\n tag rid: \"SV-86831r5_rule\"\n tag stig_id: \"RHEL-07-030920\"\n tag fix_id: \"F-78561r10_fix\"\n tag cci: [\"CCI-000172\", \"CCI-002884\"]\n tag nist: [\"AU-12 c\", \"MA-4 (1) (a)\"]\n\n describe auditd.syscall(\"unlinkat\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"unlinkat\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","descriptions":[{"data":"If the system is not configured to audit certain activities and write\nthem to an audit log, it is more difficult to detect and track system\ncompromises and damages incurred during a system compromise.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"unlinkat\" syscall occur.\n\n Check the file system rules in \"/etc/audit/audit.rules\" with the\nfollowing commands:\n\n # grep -iw unlinkat /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"unlinkat\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"unlinkat\" syscall occur.\n\n Add the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n -a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k\ndelete\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-72207","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"unlinkat\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000274389,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"unlinkat\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000183295,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"unlinkat\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000204366,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"unlinkat\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000176464,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72207.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000466-GPOS-00210","satisfies":["SRG-OS-000466-GPOS-00210","SRG-OS-000467-GPOS-00210","SRG-OS-000468-GPOS-00212","SRG-OS-000392-GPOS-00172"],"gid":"V-72207","rid":"SV-86831r5_rule","stig_id":"RHEL-07-030920","fix_id":"F-78561r10_fix","cci":["CCI-000172","CCI-002884"],"nist":["AU-12 c","MA-4 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe unlinkat syscall.","waiver_data":{}},{"code":"control \"V-72209\" do\n title \"The Red Hat Enterprise Linux operating system must send rsyslog output\nto a log aggregation server.\"\n desc \"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify \\\"rsyslog\\\" is configured to send all messages to a log aggregation\nserver.\n\n Check the configuration of \\\"rsyslog\\\" with the following command:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \\\"/etc/rsyslog.conf\\\".\n\n # grep @ /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n *.* @@logagg.site.mil\n\n If there are no lines in the \\\"/etc/rsyslog.conf\\\" or\n\\\"/etc/rsyslog.d/*.conf\\\" files that contain the \\\"@\\\" or \\\"@@\\\" symbol(s), and\nthe lines with the correct symbol(s) to send output to another system do not\ncover all \\\"rsyslog\\\" output, ask the System Administrator to indicate how the\naudit logs are off-loaded to a different system or media.\n\n If the lines are commented out or there is no evidence that the audit logs\nare being sent to another system, this is a finding.\n \"\n desc \"fix\", \"\n Modify the \\\"/etc/rsyslog.conf\\\" or an \\\"/etc/rsyslog.d/*.conf\\\" file to\ncontain a configuration line to send all \\\"rsyslog\\\" output to a log\naggregation system:\n *.* @@\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72209\"\n tag rid: \"SV-86833r2_rule\"\n tag stig_id: \"RHEL-07-031000\"\n tag fix_id: \"F-78563r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n\n if input('alternate_logs')\n describe \"An alternate logging system is used. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"An alternate logging system is used. This check must be performed manually\"\n end\n else\n describe command(\"grep @ #{input('log_pkg_path')} | grep -v \\\"^#\\\"\") do\n its('stdout.strip') { should_not be_empty }\n end\n end\nend\n","desc":"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.","descriptions":[{"data":"Sending rsyslog output to another system ensures that the logs cannot\nbe removed or modified in the event that the system is compromised or has a\nhardware failure.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify \"rsyslog\" is configured to send all messages to a log aggregation\nserver.\n\n Check the configuration of \"rsyslog\" with the following command:\n\n Note: If another logging package is used, substitute the utility\nconfiguration file for \"/etc/rsyslog.conf\".\n\n # grep @ /etc/rsyslog.conf /etc/rsyslog.d/*.conf\n *.* @@logagg.site.mil\n\n If there are no lines in the \"/etc/rsyslog.conf\" or\n\"/etc/rsyslog.d/*.conf\" files that contain the \"@\" or \"@@\" symbol(s), and\nthe lines with the correct symbol(s) to send output to another system do not\ncover all \"rsyslog\" output, ask the System Administrator to indicate how the\naudit logs are off-loaded to a different system or media.\n\n If the lines are commented out or there is no evidence that the audit logs\nare being sent to another system, this is a finding.","label":"check"},{"data":"Modify the \"/etc/rsyslog.conf\" or an \"/etc/rsyslog.d/*.conf\" file to\ncontain a configuration line to send all \"rsyslog\" output to a log\naggregation system:\n *.* @@","label":"fix"}],"id":"V-72209","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `grep @ /etc/rsyslog.conf | grep -v \"^#\"` stdout.strip is expected not to be empty","message":"expected `\"\".empty?` to be falsey, got true","run_time":0.034590958,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"command","resource_params":"[\"grep @ /etc/rsyslog.conf | grep -v \\\"^#\\\"\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72209.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72209","rid":"SV-86833r2_rule","stig_id":"RHEL-07-031000","fix_id":"F-78563r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must send rsyslog output\nto a log aggregation server.","waiver_data":{}},{"code":"control \"V-72211\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the rsyslog daemon does not accept log messages from other servers unless\nthe server is being used for log aggregation.\"\n desc \"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the system is not accepting \\\"rsyslog\\\" messages from other\nsystems unless it is documented as a log aggregation server.\n\n Check the configuration of \\\"rsyslog\\\" with the following command:\n\n # grep imtcp /etc/rsyslog.conf\n $ModLoad imtcp\n # grep imudp /etc/rsyslog.conf\n $ModLoad imudp\n # grep imrelp /etc/rsyslog.conf\n $ModLoad imrelp\n\n If any of the above modules are being loaded in the \\\"/etc/rsyslog.conf\\\"\nfile, ask to see the documentation for the system being used for log\naggregation.\n\n If the documentation does not exist, or does not specify the server as a\nlog aggregation system, this is a finding.\n \"\n desc \"fix\", \"Modify the \\\"/etc/rsyslog.conf\\\" file to remove the \\\"ModLoad\nimtcp\\\", \\\"ModLoad imudp\\\", and \\\"ModLoad imrelp\\\" configuration lines, or\ndocument the system as being used for log aggregation.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72211\"\n tag rid: \"SV-86835r2_rule\"\n tag stig_id: \"RHEL-07-031010\"\n tag fix_id: \"F-78565r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n log_aggregation_server = input('log_aggregation_server')\n\n if log_aggregation_server\n describe file('/etc/rsyslog.conf') do\n its('content') { should match %r{^\\$ModLoad\\s+imtcp.*\\n?$} }\n end\n else\n describe.one do\n describe file('/etc/rsyslog.conf') do\n its('content') { should match %r{\\$ModLoad\\s+imtcp.*\\n?$} }\n end\n describe file('/etc/rsyslog.conf') do\n its('content') { should_not match %r{^\\$ModLoad\\s+imtcp.*\\n?$} }\n end\n end\n end\nend\n","desc":"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.","descriptions":[{"data":"Unintentionally running a rsyslog server accepting remote messages\nputs the system at increased risk. Malicious rsyslog messages sent to the\nserver could exploit vulnerabilities in the server software itself, could\nintroduce misleading information in to the system's logs, or could fill the\nsystem's storage leading to a Denial of Service.\n\n If the system is intended to be a log aggregation server its use must be\ndocumented with the ISSO.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the system is not accepting \"rsyslog\" messages from other\nsystems unless it is documented as a log aggregation server.\n\n Check the configuration of \"rsyslog\" with the following command:\n\n # grep imtcp /etc/rsyslog.conf\n $ModLoad imtcp\n # grep imudp /etc/rsyslog.conf\n $ModLoad imudp\n # grep imrelp /etc/rsyslog.conf\n $ModLoad imrelp\n\n If any of the above modules are being loaded in the \"/etc/rsyslog.conf\"\nfile, ask to see the documentation for the system being used for log\naggregation.\n\n If the documentation does not exist, or does not specify the server as a\nlog aggregation system, this is a finding.","label":"check"},{"data":"Modify the \"/etc/rsyslog.conf\" file to remove the \"ModLoad\nimtcp\", \"ModLoad imudp\", and \"ModLoad imrelp\" configuration lines, or\ndocument the system as being used for log aggregation.","label":"fix"}],"id":"V-72211","impact":0.5,"refs":[],"results":[{"code_desc":"File /etc/rsyslog.conf content is expected to match /\\$ModLoad\\s+imtcp.*\\n?$/","run_time":0.000180573,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/rsyslog.conf\"]"},{"code_desc":"File /etc/rsyslog.conf content is expected not to match /^\\$ModLoad\\s+imtcp.*\\n?$/","run_time":0.000112432,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/rsyslog.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72211.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72211","rid":"SV-86835r2_rule","stig_id":"RHEL-07-031010","fix_id":"F-78565r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the rsyslog daemon does not accept log messages from other servers unless\nthe server is being used for log aggregation.","waiver_data":{}},{"code":"control \"V-72213\" do\n title \"The Red Hat Enterprise Linux operating system must use a virus scan\nprogram.\"\n desc \"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify an anti-virus solution is installed on the system. The anti-virus\nsolution may be bundled with an approved host-based security solution.\n\n If there is no anti-virus solution installed on the system, this is a\nfinding.\n \"\n desc \"fix\", \"Install an antivirus solution on the system.\"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72213\"\n tag rid: \"SV-86837r3_rule\"\n tag stig_id: \"RHEL-07-032000\"\n tag fix_id: \"F-78567r2_fix\"\n tag cci: [\"CCI-001668\"]\n tag nist: [\"SI-3 a\"]\n\n custom_antivirus = input('custom_antivirus')\n\n if ! custom_antivirus\n describe.one do\n describe service('nails') do\n it { should be_running }\n end\n describe service('clamav-daemon.socket') do\n it { should be_running }\n end\n describe service('ds_agent') do\n it { should be_running }\n end\n end\n else\n # Allow user to provide a description of their AV solution\n # for documentation.\n custom_antivirus_description = input('custom_antivirus_description')\n describe \"Antivirus: #{custom_antivirus_description}\" do\n subject { custom_antivirus_description }\n it { should_not cmp 'None' }\n end\n end\nend\n","desc":"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.","descriptions":[{"data":"Virus scanning software can be used to protect a system from\npenetration from computer viruses and to limit their spread through\nintermediate systems.\n\n The virus scanning software should be configured to perform scans\ndynamically on accessed files. If this capability is not available, the system\nmust be configured to scan, at a minimum, all altered files on the system on a\ndaily basis.\n\n If the system processes inbound SMTP mail, the virus scanner must be\nconfigured to scan all received mail.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify an anti-virus solution is installed on the system. The anti-virus\nsolution may be bundled with an approved host-based security solution.\n\n If there is no anti-virus solution installed on the system, this is a\nfinding.","label":"check"},{"data":"Install an antivirus solution on the system.","label":"fix"}],"id":"V-72213","impact":0.7,"refs":[],"results":[{"code_desc":"Service nails is expected to be running","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `Service nails` is running","run_time":0.001046528,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"service","resource_params":"[\"nails\"]"},{"code_desc":"Service clamav-daemon.socket is expected to be running","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `Service clamav-daemon.socket` is running","run_time":0.000338614,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"service","resource_params":"[\"clamav-daemon.socket\"]"},{"code_desc":"Service ds_agent is expected to be running","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `Service ds_agent` is running","run_time":0.000321793,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"service","resource_params":"[\"ds_agent\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72213.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72213","rid":"SV-86837r3_rule","stig_id":"RHEL-07-032000","fix_id":"F-78567r2_fix","cci":["CCI-001668"],"nist":["SI-3 a"]},"title":"The Red Hat Enterprise Linux operating system must use a virus scan\nprogram.","waiver_data":{}},{"code":"control \"V-72217\" do\n title \"The Red Hat Enterprise Linux operating system must limit the number of\nconcurrent sessions to 10 for all accounts and/or account types.\"\n desc \"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system limits the number of concurrent sessions to\n\\\"10\\\" for all accounts and/or account types by issuing the following command:\n\n # grep \\\"maxlogins\\\" /etc/security/limits.conf /etc/security/limits.d/*.conf\n\n * hard maxlogins 10\n\n This can be set as a global domain (with the * wildcard) but may be set\ndifferently for multiple domains.\n\n If the \\\"maxlogins\\\" item is missing, commented out, or the value is not\nset to \\\"10\\\" or less for all domains that have the \\\"maxlogins\\\" item\nassigned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to limit the number of concurrent sessions\nto \\\"10\\\" for all accounts and/or account types.\n\n Add the following line to the top of the /etc/security/limits.conf or in a\n\\\".conf\\\" file defined in /etc/security/limits.d/ :\n\n * hard maxlogins 10\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000027-GPOS-00008\"\n tag gid: \"V-72217\"\n tag rid: \"SV-86841r3_rule\"\n tag stig_id: \"RHEL-07-040000\"\n tag fix_id: \"F-78571r2_fix\"\n tag cci: [\"CCI-000054\"]\n tag nist: [\"AC-10\"]\n\n maxlogins_limit = input('maxlogins_limit')\n\n # Collect any files under limits.d if they exist\n limits_files = directory('/etc/security/limits.d').exist? ? command('ls /etc/security/limits.d/*.conf').stdout.strip.lines : []\n # Add limits.conf to the list\n limits_files.push('/etc/security/limits.conf')\n compliant_files = []\n noncompliant_files = []\n\n limits_files.each do |limits_file|\n # Get any universal limits from each file\n local_limits = limits_conf(limits_file).*\n # If we got an array (results) check further\n if local_limits.is_a?(Array)\n local_limits.each do |temp_limit|\n # For each result check if it is a 'hard' limit for 'maxlogins'\n if temp_limit.include?('hard') && temp_limit.include?('maxlogins')\n # If the limit is in range, push to compliant files\n if temp_limit[-1].to_i <= maxlogins_limit\n compliant_files.push(limits_file)\n # Otherwise add to noncompliant files\n else\n noncompliant_files.push(limits_file)\n end\n end\n end\n end\n end\n\n # It is required that at least 1 file contain compliant configuration\n describe \"Files configuring maxlogins less than or equal to #{maxlogins_limit}\" do\n subject { compliant_files.length }\n it { should be_positive }\n end\n\n # No files should set 'hard' 'maxlogins' to any noncompliant value\n describe \"Files configuring maxlogins greater than #{maxlogins_limit}\" do\n subject { noncompliant_files }\n it { should cmp [] }\n end\nend\n","desc":"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.","descriptions":[{"data":"Operating system management includes the ability to control the number\nof users and user sessions that utilize an operating system. Limiting the\nnumber of allowed users and sessions per user is helpful in reducing the risks\nrelated to DoS attacks.\n\n This requirement addresses concurrent sessions for information system\naccounts and does not address concurrent sessions by single users via multiple\nsystem accounts. The maximum number of concurrent sessions should be defined\nbased on mission needs and the operational environment for each system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system limits the number of concurrent sessions to\n\"10\" for all accounts and/or account types by issuing the following command:\n\n # grep \"maxlogins\" /etc/security/limits.conf /etc/security/limits.d/*.conf\n\n * hard maxlogins 10\n\n This can be set as a global domain (with the * wildcard) but may be set\ndifferently for multiple domains.\n\n If the \"maxlogins\" item is missing, commented out, or the value is not\nset to \"10\" or less for all domains that have the \"maxlogins\" item\nassigned, this is a finding.","label":"check"},{"data":"Configure the operating system to limit the number of concurrent sessions\nto \"10\" for all accounts and/or account types.\n\n Add the following line to the top of the /etc/security/limits.conf or in a\n\".conf\" file defined in /etc/security/limits.d/ :\n\n * hard maxlogins 10","label":"fix"}],"id":"V-72217","impact":0.3,"refs":[],"results":[{"code_desc":"Files configuring maxlogins less than or equal to 10 is expected to be positive","message":"expected `0.positive?` to be truthy, got false","run_time":0.041612032,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"Files configuring maxlogins greater than 10 is expected to cmp == []","run_time":0.00021165,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72217.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000027-GPOS-00008","gid":"V-72217","rid":"SV-86841r3_rule","stig_id":"RHEL-07-040000","fix_id":"F-78571r2_fix","cci":["CCI-000054"],"nist":["AC-10"]},"title":"The Red Hat Enterprise Linux operating system must limit the number of\nconcurrent sessions to 10 for all accounts and/or account types.","waiver_data":{}},{"code":"control \"V-72219\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nprohibit or restrict the use of functions, ports, protocols, and/or services,\nas defined in the Ports, Protocols, and Services Management Component Local\nService Assessment (PPSM CLSA) and vulnerability assessments.\"\n desc \"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Inspect the firewall configuration and running services to verify that it\nis configured to prohibit or restrict the use of functions, ports, protocols,\nand/or services that are unnecessary or prohibited.\n\n Check which services are currently active with the following command:\n\n # firewall-cmd --list-all\n public (default, active)\n interfaces: enp0s3\n sources:\n services: dhcpv6-client dns http https ldaps rpc-bind ssh\n ports:\n masquerade: no\n forward-ports:\n icmp-blocks:\n rich rules:\n\n Ask the System Administrator for the site or program PPSM CLSA. Verify the\nservices allowed by the firewall match the PPSM CLSA.\n\n If there are additional ports, protocols, or services that are not in the\nPPSM CLSA, or there are ports, protocols, or services that are prohibited by\nthe PPSM Category Assurance List (CAL), this is a finding.\n \"\n desc \"fix\", \"Update the host's firewall settings and/or running services to\ncomply with the PPSM CLSA for the site or program and the PPSM CAL.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000096-GPOS-00050\"\n tag satisfies: [\"SRG-OS-000096-GPOS-00050\", \"SRG-OS-000297-GPOS-00115\"]\n tag gid: \"V-72219\"\n tag rid: \"SV-86843r2_rule\"\n tag stig_id: \"RHEL-07-040100\"\n tag fix_id: \"F-78573r1_fix\"\n tag cci: [\"CCI-000382\", \"CCI-002314\"]\n tag nist: [\"CM-7 b\", \"AC-17 (1)\"]\n\n firewalld_services_deny = input('firewalld_services_deny')\n firewalld_hosts_deny = input('firewalld_hosts_deny')\n firewalld_ports_deny = input('firewalld_ports_deny')\n firewalld_zones = input('firewalld_zones')\n iptables_rules = input('iptables_rules')\n\n if service('firewalld').running?\n\n # Check that the rules specified in 'firewalld_host_deny' are not enabled\n describe firewalld do\n firewalld_hosts_deny.each do |rule|\n it { should_not have_rule_enabled(rule) }\n end\n end\n\n # Check to make sure zones are specified\n if firewalld_zones.empty?\n describe \"Firewalld zones are not specified. Check 'firewalld_zones' input.\" do\n subject { firewalld_zones.empty? }\n it { should be false }\n end\n end\n\n # Check that the services specified in 'firewalld_services_deny' and\n # ports specified in 'firewalld_ports_deny' are not enabled\n firewalld_zones.each do |zone|\n if firewalld.has_zone?(zone)\n zone_services = firewalld_services_deny[zone.to_sym]\n zone_ports = firewalld_ports_deny[zone.to_sym]\n\n if !zone_services.nil?\n describe firewalld do\n zone_services.each do |serv|\n it { should_not have_service_enabled_in_zone(serv,zone) }\n end\n end\n else\n describe \"Services for zone '#{zone}' are not specified. Check 'firewalld_services_deny' input.\" do\n subject { zone_services.nil? }\n it { should be false }\n end\n end\n\n if !zone_ports.nil?\n describe firewalld do\n zone_ports.each do |port|\n it { should_not have_port_enabled_in_zone(port,zone) }\n end\n end\n else\n describe \"Ports for zone '#{zone}' are not specified. Check 'firewalld_ports_deny' input.\" do\n subject { zone_ports.nil? }\n it { should be false }\n end\n end\n else\n describe \"Firewalld zone '#{zone}' exists\" do\n subject { firewalld.has_zone?(zone) }\n it { should be true }\n end\n end\n end\n elsif service('iptables').running?\n describe iptables do\n iptables_rules.each do |rule|\n it { should have_rule(rule) }\n end\n end\n else\n describe \"No application firewall is installed\" do\n subject { service('firewalld').running? || service('iptables').running? }\n it { should eq true }\n end\n end\nend\n","desc":"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.","descriptions":[{"data":"In order to prevent unauthorized connection of devices, unauthorized\ntransfer of information, or unauthorized tunneling (i.e., embedding of data\ntypes within data types), organizations must disable or restrict unused or\nunnecessary physical and logical ports/protocols on information systems.\n\n Operating systems are capable of providing a wide variety of functions and\nservices. Some of the functions and services provided by default may not be\nnecessary to support essential organizational operations. Additionally, it is\nsometimes convenient to provide multiple services from a single component\n(e.g., VPN and IPS); however, doing so increases risk over limiting the\nservices provided by any one component.\n\n To support the requirements and principles of least functionality, the\noperating system must support the organizational requirements, providing only\nessential capabilities and limiting the use of ports, protocols, and/or\nservices to only those required, authorized, and approved to conduct official\nbusiness or to address authorized quality of life issues.","label":"default"},{"data":"","label":"rationale"},{"data":"Inspect the firewall configuration and running services to verify that it\nis configured to prohibit or restrict the use of functions, ports, protocols,\nand/or services that are unnecessary or prohibited.\n\n Check which services are currently active with the following command:\n\n # firewall-cmd --list-all\n public (default, active)\n interfaces: enp0s3\n sources:\n services: dhcpv6-client dns http https ldaps rpc-bind ssh\n ports:\n masquerade: no\n forward-ports:\n icmp-blocks:\n rich rules:\n\n Ask the System Administrator for the site or program PPSM CLSA. Verify the\nservices allowed by the firewall match the PPSM CLSA.\n\n If there are additional ports, protocols, or services that are not in the\nPPSM CLSA, or there are ports, protocols, or services that are prohibited by\nthe PPSM Category Assurance List (CAL), this is a finding.","label":"check"},{"data":"Update the host's firewall settings and/or running services to\ncomply with the PPSM CLSA for the site or program and the PPSM CAL.","label":"fix"}],"id":"V-72219","impact":0.5,"refs":[],"results":[{"code_desc":"No application firewall is installed is expected to eq true","message":"\nexpected: true\n got: false\n\n(compared using ==)\n\nDiff:\n@@ -1,2 +1,2 @@\n-true\n+false\n","run_time":0.01334263,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72219.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000096-GPOS-00050","satisfies":["SRG-OS-000096-GPOS-00050","SRG-OS-000297-GPOS-00115"],"gid":"V-72219","rid":"SV-86843r2_rule","stig_id":"RHEL-07-040100","fix_id":"F-78573r1_fix","cci":["CCI-000382","CCI-002314"],"nist":["CM-7 b","AC-17 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nprohibit or restrict the use of functions, ports, protocols, and/or services,\nas defined in the Ports, Protocols, and Services Management Component Local\nService Assessment (PPSM CLSA) and vulnerability assessments.","waiver_data":{}},{"code":"control \"V-72221\" do\n title \"The Red Hat Enterprise Linux operating system must use a FIPS 140-2\napproved cryptographic algorithm for SSH communications.\"\n desc \"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system uses mechanisms meeting the requirements of\napplicable federal laws, Executive orders, directives, policies, regulations,\nstandards, and guidance for authentication to a cryptographic module.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n The location of the \\\"sshd_config\\\" file may vary if a different daemon is\nin use.\n\n Inspect the \\\"Ciphers\\\" configuration with the following command:\n\n # grep -i ciphers /etc/ssh/sshd_config\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n If any ciphers other than \\\"aes128-ctr\\\", \\\"aes192-ctr\\\", or \\\"aes256-ctr\\\"\nare listed, the \\\"Ciphers\\\" keyword is missing, or the returned line is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure SSH to use FIPS 140-2 approved cryptographic algorithms.\n\n Add the following line (or modify the line to have the required value) to\nthe \\\"/etc/ssh/sshd_config\\\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor).\n\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000033-GPOS-00014\"\n tag satisfies: [\"SRG-OS-000033-GPOS-00014\", \"SRG-OS-000120-GPOS-00061\",\n\"SRG-OS-000125-GPOS-00065\", \"SRG-OS-000250-GPOS-00093\",\n\"SRG-OS-000393-GPOS-00173\"]\n tag gid: \"V-72221\"\n tag rid: \"SV-86845r3_rule\"\n tag stig_id: \"RHEL-07-040110\"\n tag fix_id: \"F-78575r3_fix\"\n tag cci: [\"CCI-000068\", \"CCI-000366\", \"CCI-000803\"]\n tag nist: [\"AC-17 (2)\", \"CM-6 b\", \"IA-7\"]\n\n @ciphers_array = inspec.sshd_config.params['ciphers']\n\n unless @ciphers_array.nil?\n @ciphers_array = @ciphers_array.first.split(\",\")\n end\n\n describe @ciphers_array do\n it { should be_in ['aes128-ctr', 'aes192-ctr', 'aes256-ctr'] }\n end\nend\n","desc":"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.","descriptions":[{"data":"Unapproved mechanisms that are used for authentication to the\ncryptographic module are not verified and therefore cannot be relied upon to\nprovide confidentiality or integrity, and DoD data may be compromised.\n\n Operating systems utilizing encryption are required to use FIPS-compliant\nmechanisms for authenticating to cryptographic modules.\n\n FIPS 140-2 is the current standard for validating that mechanisms used to\naccess cryptographic modules utilize authentication that meets DoD\nrequirements. This allows for Security Levels 1, 2, 3, or 4 for use on a\ngeneral purpose computing system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uses mechanisms meeting the requirements of\napplicable federal laws, Executive orders, directives, policies, regulations,\nstandards, and guidance for authentication to a cryptographic module.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n The location of the \"sshd_config\" file may vary if a different daemon is\nin use.\n\n Inspect the \"Ciphers\" configuration with the following command:\n\n # grep -i ciphers /etc/ssh/sshd_config\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n If any ciphers other than \"aes128-ctr\", \"aes192-ctr\", or \"aes256-ctr\"\nare listed, the \"Ciphers\" keyword is missing, or the returned line is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to use FIPS 140-2 approved cryptographic algorithms.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor).\n\n Ciphers aes128-ctr,aes192-ctr,aes256-ctr\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72221","impact":0.5,"refs":[],"results":[{"code_desc":"is expected to be in \"aes128-ctr\", \"aes192-ctr\", and \"aes256-ctr\"","message":"expected `` to be in the list: `[\"aes128-ctr\", \"aes192-ctr\", \"aes256-ctr\"]`","run_time":0.000252849,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72221.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000033-GPOS-00014","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"],"gid":"V-72221","rid":"SV-86845r3_rule","stig_id":"RHEL-07-040110","fix_id":"F-78575r3_fix","cci":["CCI-000068","CCI-000366","CCI-000803"],"nist":["AC-17 (2)","CM-6 b","IA-7"]},"title":"The Red Hat Enterprise Linux operating system must use a FIPS 140-2\napproved cryptographic algorithm for SSH communications.","waiver_data":{}},{"code":"control \"V-72223\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with a communication session are\nterminated at the end of the session or after 10 minutes of inactivity from the\nuser at a command prompt, except to fulfill documented and validated mission\nrequirements.\"\n desc \"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system terminates all network connections associated\nwith a communications session at the end of the session or based on inactivity.\n\n Check the value of the system inactivity timeout with the following command:\n\n # grep -i tmout /etc/profile.d/*\n\n etc/profile.d/tmout.sh:TMOUT=600\n\n /etc/profile.d/tmout.sh:readonly TMOUT\n\n /etc/profile.d/tmout.sh:export TMOUT\n\n If \\\"TMOUT\\\" is not set to \\\"600\\\" or less in a script located in the\n/etc/profile.d/ directory to enforce session termination after inactivity, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to terminate all network connections\nassociated with a communications session at the end of the session or after a\nperiod of inactivity.\n\n Create a script to enforce the inactivity timeout (for example\n/etc/profile.d/tmout.sh) such as:\n\n #!/bin/bash\n\n TMOUT=600\n readonly TMOUT\n export TMOUT\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000163-GPOS-00072\"\n tag gid: \"V-72223\"\n tag rid: \"SV-86847r4_rule\"\n tag stig_id: \"RHEL-07-040160\"\n tag fix_id: \"F-78577r5_fix\"\n tag cci: [\"CCI-001133\", \"CCI-002361\"]\n tag nist: [\"SC-10\", \"AC-12\"]\n\n system_activity_timeout = input('system_activity_timeout')\n\n # Get current TMOUT environment variable (active test)\n describe 'Environment variable TMOUT' do\n subject { os_env('TMOUT').content.to_i }\n it { should be <= system_activity_timeout }\n end\n\n # Check if TMOUT is set in files (passive test)\n files = ['/etc/bashrc'] + ['/etc/profile'] + command(\"find /etc/profile.d/*\").stdout.split(\"\\n\")\n latest_val = nil\n\n files.each do |file|\n readonly = false\n\n # Skip to next file if TMOUT isn't present. Otherwise, get the last occurrence of TMOUT\n next if (values = command(\"grep -Po '.*TMOUT.*' #{file}\").stdout.split(\"\\n\")).empty?\n\n # Loop through each TMOUT match and see if set TMOUT's value or makes it readonly\n values.each_with_index { |value, index|\n\n # Skip if starts with '#' - it represents a comment\n next if !value.match(/^#/).nil?\n # If readonly and value is inline - use that value\n if !value.match(/^readonly[\\s]+TMOUT[\\s]*=[\\s]*[\\d]+$/).nil?\n latest_val = value.match(/[\\d]+/)[0].to_i\n readonly = true\n break\n # If readonly, but, value is not inline - use the most recent value\n elsif !value.match(/^readonly[\\s]+([\\w]+[\\s]+)?TMOUT[\\s]*([\\s]+[\\w]+[\\s]*)*$/).nil?\n # If the index is greater than 0, the configuraiton setting value.\n # Otherwise, the configuration setting value is in the previous file\n # and is already set in latest_val.\n if index >= 1\n latest_val = values[index - 1].match(/[\\d]+/)[0].to_i\n end\n readonly = true\n break\n # Readonly is not set use the lastest value\n else\n latest_val = value.match(/[\\d]+/)[0].to_i\n end\n }\n # Readonly is set - stop processing files\n break if readonly === true\n end\n\n if latest_val.nil?\n describe \"The TMOUT setting is configured\" do\n subject { !latest_val.nil? }\n it { should be true }\n end\n else\n describe\"The TMOUT setting is configured properly\" do\n subject { latest_val }\n it { should be <= system_activity_timeout }\n end\n end\nend\n","desc":"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle session will also free up\nresources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system terminates all network connections associated\nwith a communications session at the end of the session or based on inactivity.\n\n Check the value of the system inactivity timeout with the following command:\n\n # grep -i tmout /etc/profile.d/*\n\n etc/profile.d/tmout.sh:TMOUT=600\n\n /etc/profile.d/tmout.sh:readonly TMOUT\n\n /etc/profile.d/tmout.sh:export TMOUT\n\n If \"TMOUT\" is not set to \"600\" or less in a script located in the\n/etc/profile.d/ directory to enforce session termination after inactivity, this\nis a finding.","label":"check"},{"data":"Configure the operating system to terminate all network connections\nassociated with a communications session at the end of the session or after a\nperiod of inactivity.\n\n Create a script to enforce the inactivity timeout (for example\n/etc/profile.d/tmout.sh) such as:\n\n #!/bin/bash\n\n TMOUT=600\n readonly TMOUT\n export TMOUT","label":"fix"}],"id":"V-72223","impact":0.5,"refs":[],"results":[{"code_desc":"Environment variable TMOUT is expected to be <= 600","run_time":0.023925483,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The TMOUT setting is configured is expected to equal true","message":"\nexpected true\n got false\n","run_time":0.000290933,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72223.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","gid":"V-72223","rid":"SV-86847r4_rule","stig_id":"RHEL-07-040160","fix_id":"F-78577r5_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with a communication session are\nterminated at the end of the session or after 10 minutes of inactivity from the\nuser at a command prompt, except to fulfill documented and validated mission\nrequirements.","waiver_data":{}},{"code":"control \"V-72225\" do\n title \"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner immediately prior to, or as\npart of, remote access logon prompts.\"\n desc \"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify any publicly accessible connection to the operating system displays\nthe Standard Mandatory DoD Notice and Consent Banner before granting access to\nthe system.\n\n Check for the location of the banner file being used with the following\ncommand:\n\n # grep -i banner /etc/ssh/sshd_config\n\n banner /etc/issue\n\n This command will return the banner keyword and the name of the file that\ncontains the ssh banner (in this case \\\"/etc/issue\\\").\n\n If the line is commented out, this is a finding.\n\n View the file specified by the banner keyword to check that it matches the\ntext of the Standard Mandatory DoD Notice and Consent Banner:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n If the system does not display a graphical logon banner or the banner does\nnot match the Standard Mandatory DoD Notice and Consent Banner, this is a\nfinding.\n\n If the text in the file does not match the Standard Mandatory DoD Notice\nand Consent Banner, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the ssh.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment the banner keyword and\nconfigure it to point to a file that will contain the logon banner (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor). An example configuration line is:\n\n banner /etc/issue\n\n Either create the file containing the banner or replace the text in the\nfile with the Standard Mandatory DoD Notice and Consent Banner. The DoD\nrequired text is:\n\n \\\"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\\\"\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000023-GPOS-00006\"\n tag satisfies: [\"SRG-OS-000023-GPOS-00006\", \"SRG-OS-000024-GPOS-00007\",\n\"SRG-OS-000228-GPOS-00088\"]\n tag gid: \"V-72225\"\n tag rid: \"SV-86849r4_rule\"\n tag stig_id: \"RHEL-07-040170\"\n tag fix_id: \"F-78579r4_fix\"\n tag cci: [\"CCI-000048\", \"CCI-000050\", \"CCI-001384\", \"CCI-001385\",\n\"CCI-001386\", \"CCI-001387\", \"CCI-001388\"]\n tag nist: [\"AC-8 a\", \"AC-8 b\", \"AC-8 c 1\", \"AC-8 c 2\", \"AC-8 c 2\", \"AC-8 c\n2\", \"AC-8 c 3\"]\n\n banner_message_text_ral = input('banner_message_text_ral')\n banner_message_text_ral_limited = input('banner_message_text_ral_limited')\n\n #When Banner is commented, not found, disabled, or the specified file does not exist, this is a finding.\n banner_files = [sshd_config.banner].flatten\n\n banner_files.each do |banner_file|\n\n #Banner property is commented out.\n describe \"The SSHD Banner is not set\" do\n subject { banner_file.nil? }\n it { should be false }\n end if banner_file.nil?\n\n #Banner property is set to \"none\"\n describe \"The SSHD Banner is disabled\" do\n subject { banner_file.match(/none/i).nil? }\n it { should be true }\n end if !banner_file.nil? && !banner_file.match(/none/i).nil?\n\n #Banner property provides a path to a file, however, it does not exist.\n describe \"The SSHD Banner is set, but, the file does not exist\" do\n subject { file(banner_file).exist? }\n it { should be true }\n end if !banner_file.nil? && banner_file.match(/none/i).nil? && !file(banner_file).exist?\n\n #Banner property provides a path to a file and it exists.\n describe.one do\n banner = file(banner_file).content.gsub(%r{[\\r\\n\\s]}, '')\n clean_banner = banner_message_text_ral.gsub(%r{[\\r\\n\\s]}, '')\n clean_banner_limited = banner_message_text_ral_limited.gsub(%r{[\\r\\n\\s]}, '')\n\n describe \"The SSHD Banner is set to the standard banner and has the correct text\" do\n subject { banner }\n it { should cmp clean_banner }\n end\n\n describe \"The SSHD Banner is set to the standard limited banner and has the correct text\" do\n subject { banner }\n it { should cmp clean_banner_limited }\n end\n end if !banner_file.nil? && banner_file.match(/none/i).nil? && file(banner_file).exist?\n end\nend\n","desc":"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","descriptions":[{"data":"Display of a standardized and approved use notification before\ngranting access to the publicly accessible operating system ensures privacy and\nsecurity notification verbiage used is consistent with applicable federal laws,\nExecutive Orders, directives, policies, regulations, standards, and guidance.\n\n System use notifications are required only for access via logon interfaces\nwith human users and are not required when such human interfaces do not exist.\n\n The banner must be formatted in accordance with applicable DoD policy. Use\nthe following verbiage for operating systems that can accommodate banners of\n1300 characters:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only.\n\n By using this IS (which includes any device attached to this IS), you\nconsent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"","label":"default"},{"data":"","label":"rationale"},{"data":"Verify any publicly accessible connection to the operating system displays\nthe Standard Mandatory DoD Notice and Consent Banner before granting access to\nthe system.\n\n Check for the location of the banner file being used with the following\ncommand:\n\n # grep -i banner /etc/ssh/sshd_config\n\n banner /etc/issue\n\n This command will return the banner keyword and the name of the file that\ncontains the ssh banner (in this case \"/etc/issue\").\n\n If the line is commented out, this is a finding.\n\n View the file specified by the banner keyword to check that it matches the\ntext of the Standard Mandatory DoD Notice and Consent Banner:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n If the system does not display a graphical logon banner or the banner does\nnot match the Standard Mandatory DoD Notice and Consent Banner, this is a\nfinding.\n\n If the text in the file does not match the Standard Mandatory DoD Notice\nand Consent Banner, this is a finding.","label":"check"},{"data":"Configure the operating system to display the Standard Mandatory DoD Notice\nand Consent Banner before granting access to the system via the ssh.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment the banner keyword and\nconfigure it to point to a file that will contain the logon banner (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor). An example configuration line is:\n\n banner /etc/issue\n\n Either create the file containing the banner or replace the text in the\nfile with the Standard Mandatory DoD Notice and Consent Banner. The DoD\nrequired text is:\n\n \"You are accessing a U.S. Government (USG) Information System (IS) that is\nprovided for USG-authorized use only. By using this IS (which includes any\ndevice attached to this IS), you consent to the following conditions:\n\n -The USG routinely intercepts and monitors communications on this IS for\npurposes including, but not limited to, penetration testing, COMSEC monitoring,\nnetwork operations and defense, personnel misconduct (PM), law enforcement\n(LE), and counterintelligence (CI) investigations.\n\n -At any time, the USG may inspect and seize data stored on this IS.\n\n -Communications using, or data stored on, this IS are not private, are\nsubject to routine monitoring, interception, and search, and may be disclosed\nor used for any USG-authorized purpose.\n\n -This IS includes security measures (e.g., authentication and access\ncontrols) to protect USG interests--not for your personal benefit or privacy.\n\n -Notwithstanding the above, using this IS does not constitute consent to\nPM, LE or CI investigative searching or monitoring of the content of privileged\ncommunications, or work product, related to personal representation or services\nby attorneys, psychotherapists, or clergy, and their assistants. Such\ncommunications and work product are private and confidential. See User\nAgreement for details.\"\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72225","impact":0.5,"refs":[],"results":[{"code_desc":"The SSHD Banner is not set is expected to equal false","message":"\nexpected false\n got true\n","run_time":0.000152849,"start_time":"2022-03-06T22:06:06+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72225.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000023-GPOS-00006","satisfies":["SRG-OS-000023-GPOS-00006","SRG-OS-000024-GPOS-00007","SRG-OS-000228-GPOS-00088"],"gid":"V-72225","rid":"SV-86849r4_rule","stig_id":"RHEL-07-040170","fix_id":"F-78579r4_fix","cci":["CCI-000048","CCI-000050","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"],"nist":["AC-8 a","AC-8 b","AC-8 c 1","AC-8 c 2","AC-8 c 2","AC-8 c\n2","AC-8 c 3"]},"title":"The Red Hat Enterprise Linux operating system must display the\nStandard Mandatory DoD Notice and Consent Banner immediately prior to, or as\npart of, remote access logon prompts.","waiver_data":{}},{"code":"control \"V-72227\" do\n title \"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) authentication communications.\"\n desc \"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP authentication sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \\\"sssd.service\\\" is \\\"active\\\", then LDAP is being used.\n\n Determine the \\\"id_provider\\\" the LDAP is currently using:\n\n # grep -i \\\"id_provider\\\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \\\"id_provider\\\" is set to \\\"ad\\\", this is Not Applicable.\n\n Ensure that LDAP is configured to use TLS by using the following command:\n\n # grep -i \\\"start_tls\\\" /etc/sssd/sssd.conf\n ldap_id_use_start_tls = true\n\n If the \\\"ldap_id_use_start_tls\\\" option is not \\\"true\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement cryptography to protect the\nintegrity of LDAP authentication sessions.\n\n Add or modify the following line in \\\"/etc/sssd/sssd.conf\\\":\n\n ldap_id_use_start_tls = true\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72227\"\n tag rid: \"SV-86851r4_rule\"\n tag stig_id: \"RHEL-07-040180\"\n tag fix_id: \"F-78581r2_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n sssd_id_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*id_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n pam_ldap_enabled = (!command('grep \"^[^#]*pam_ldap\\.so\" /etc/pam.d/*').stdout.strip.empty?)\n\n if !(sssd_id_ldap_enabled or pam_ldap_enabled)\n impact 0.0\n describe \"LDAP not enabled\" do\n skip \"LDAP not enabled using any known mechanisms, this control is Not Applicable.\"\n end\n end\n\n if sssd_id_ldap_enabled\n ldap_id_use_start_tls = command('grep ldap_id_use_start_tls /etc/sssd/sssd.conf')\n describe ldap_id_use_start_tls do\n its('stdout.strip') { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n\n ldap_id_use_start_tls.stdout.strip.each_line do |line|\n describe line do\n it { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n end\n end\n\n if pam_ldap_enabled\n describe command('grep -i ssl /etc/pam_ldap.conf') do\n its('stdout.strip') { should match %r{^ssl start_tls$}}\n end\n end\nend\n","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP authentication sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Ensure that LDAP is configured to use TLS by using the following command:\n\n # grep -i \"start_tls\" /etc/sssd/sssd.conf\n ldap_id_use_start_tls = true\n\n If the \"ldap_id_use_start_tls\" option is not \"true\", this is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP authentication sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_id_use_start_tls = true","label":"fix"}],"id":"V-72227","impact":0,"refs":[],"results":[{"code_desc":"LDAP not enabled","resource":"","run_time":0.000010836,"skip_message":"LDAP not enabled using any known mechanisms, this control is Not Applicable.","start_time":"2022-03-06T22:06:06+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72227.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72227","rid":"SV-86851r4_rule","stig_id":"RHEL-07-040180","fix_id":"F-78581r2_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) authentication communications.","waiver_data":{}},{"code":"control \"V-72229\" do\n title \"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.\"\n desc \"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \\\"sssd.service\\\" is \\\"active\\\", then LDAP is being used.\n\n Determine the \\\"id_provider\\\" the LDAP is currently using:\n\n # grep -i \\\"id_provider\\\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \\\"id_provider\\\" is set to \\\"ad\\\", this is Not Applicable.\n\n Verify the sssd service is configured to require the use of certificates:\n\n # grep -i tls_reqcert /etc/sssd/sssd.conf\n ldap_tls_reqcert = demand\n\n If the \\\"ldap_tls_reqcert\\\" setting is missing, commented out, or does not\nexist, this is a finding.\n\n If the \\\"ldap_tls_reqcert\\\" setting is not set to \\\"demand\\\" or \\\"hard\\\",\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \\\"/etc/sssd/sssd.conf\\\":\n\n ldap_tls_reqcert = demand\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72229\"\n tag rid: \"SV-86853r4_rule\"\n tag stig_id: \"RHEL-07-040190\"\n tag fix_id: \"F-78583r4_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n sssd_id_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*id_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n sssd_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*[a-z]*_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n pam_ldap_enabled = (!command('grep \"^[^#]*pam_ldap\\.so\" /etc/pam.d/*').stdout.strip.empty?)\n\n if !(sssd_id_ldap_enabled or sssd_ldap_enabled or pam_ldap_enabled)\n impact 0.0\n describe \"LDAP not enabled\" do\n skip \"LDAP not enabled using any known mechanisms, this control is Not Applicable.\"\n end\n end\n\n if sssd_id_ldap_enabled\n ldap_id_use_start_tls = command('grep ldap_id_use_start_tls /etc/sssd/sssd.conf')\n describe ldap_id_use_start_tls do\n its('stdout.strip') { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n\n ldap_id_use_start_tls.stdout.strip.each_line do |line|\n describe line do\n it { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n end\n end\n\n if sssd_ldap_enabled\n ldap_tls_cacertdir = command('grep -i ldap_tls_cacertdir /etc/sssd/sssd.conf').\n stdout.strip.scan(%r{^ldap_tls_cacertdir\\s*=\\s*(.*)}).last\n\n describe \"ldap_tls_cacertdir\" do\n subject { ldap_tls_cacertdir }\n it { should_not eq nil }\n end\n\n describe file(ldap_tls_cacertdir.last) do\n it { should exist }\n it { should be_directory }\n end if !ldap_tls_cacertdir.nil?\n end\n\n if pam_ldap_enabled\n tls_cacertdir = command('grep -i tls_cacertdir /etc/pam_ldap.conf').\n stdout.strip.scan(%r{^tls_cacertdir\\s+(.*)}).last\n\n describe \"tls_cacertdir\" do\n subject { tls_cacertdir }\n it { should_not eq nil }\n end\n\n describe file(tls_cacertdir.last) do\n it { should exist }\n it { should be_directory }\n end if !tls_cacertdir.nil?\n end\nend\n","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Verify the sssd service is configured to require the use of certificates:\n\n # grep -i tls_reqcert /etc/sssd/sssd.conf\n ldap_tls_reqcert = demand\n\n If the \"ldap_tls_reqcert\" setting is missing, commented out, or does not\nexist, this is a finding.\n\n If the \"ldap_tls_reqcert\" setting is not set to \"demand\" or \"hard\",\nthis is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_tls_reqcert = demand","label":"fix"}],"id":"V-72229","impact":0,"refs":[],"results":[{"code_desc":"LDAP not enabled","resource":"","run_time":0.000034353,"skip_message":"LDAP not enabled using any known mechanisms, this control is Not Applicable.","start_time":"2022-03-06T22:06:06+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72229.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72229","rid":"SV-86853r4_rule","stig_id":"RHEL-07-040190","fix_id":"F-78583r4_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.","waiver_data":{}},{"code":"control \"V-72231\" do\n title \"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.\"\n desc \"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \\\"sssd.service\\\" is \\\"active\\\", then LDAP is being used.\n\n Determine the \\\"id_provider\\\" that the LDAP is currently using:\n\n # grep -i \\\"id_provider\\\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \\\"id_provider\\\" is set to \\\"ad\\\", this is Not Applicable.\n\n Check the path to the X.509 certificate for peer authentication with the\nfollowing command:\n\n # grep -i tls_cacert /etc/sssd/sssd.conf\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt\n\n Verify the \\\"ldap_tls_cacert\\\" option points to a file that contains the\ntrusted CA certificate.\n\n If this file does not exist, or the option is commented out or missing,\nthis is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \\\"/etc/sssd/sssd.conf\\\":\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72231\"\n tag rid: \"SV-86855r4_rule\"\n tag stig_id: \"RHEL-07-040200\"\n tag fix_id: \"F-78585r3_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n sssd_id_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*id_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n sssd_ldap_enabled = (package('sssd').installed? and\n !command('grep \"^\\s*[a-z]*_provider\\s*=\\s*ldap\" /etc/sssd/sssd.conf').stdout.strip.empty?)\n\n pam_ldap_enabled = (!command('grep \"^[^#]*pam_ldap\\.so\" /etc/pam.d/*').stdout.strip.empty?)\n\n if !(sssd_id_ldap_enabled or sssd_ldap_enabled or pam_ldap_enabled)\n impact 0.0\n describe \"LDAP not enabled\" do\n skip \"LDAP not enabled using any known mechanisms, this control is Not Applicable.\"\n end\n end\n\n if sssd_id_ldap_enabled\n ldap_id_use_start_tls = command('grep ldap_id_use_start_tls /etc/sssd/sssd.conf')\n describe ldap_id_use_start_tls do\n its('stdout.strip') { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n\n ldap_id_use_start_tls.stdout.strip.each_line do |line|\n describe line do\n it { should match %r{^ldap_id_use_start_tls\\s*=\\s*true$}}\n end\n end\n end\n\n if sssd_ldap_enabled\n ldap_tls_cacert = command('grep -i ldap_tls_cacert /etc/sssd/sssd.conf').\n stdout.strip.scan(%r{^ldap_tls_cacert\\s*=\\s*(.*)}).last\n\n describe \"ldap_tls_cacert\" do\n subject { ldap_tls_cacert }\n it { should_not eq nil }\n end\n\n describe file(ldap_tls_cacert.last) do\n it { should exist }\n it { should be_file }\n end if !ldap_tls_cacert.nil?\n end\n\n if pam_ldap_enabled\n tls_cacertfile = command('grep -i tls_cacertfile /etc/pam_ldap.conf').\n stdout.strip.scan(%r{^tls_cacertfile\\s+(.*)}).last\n\n describe \"tls_cacertfile\" do\n subject { tls_cacertfile }\n it { should_not eq nil }\n end\n\n describe file(tls_cacertfile.last) do\n it { should exist }\n it { should be_file }\n end if !tls_cacertfile.nil?\n end\nend\n","desc":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","descriptions":[{"data":"Without cryptographic integrity protections, information can be\naltered by unauthorized users without detection.\n\n Cryptographic mechanisms used for protecting the integrity of information\ninclude, for example, signed hash functions using asymmetric cryptography\nenabling distribution of the public key to verify the hash information while\nmaintaining the confidentiality of the key used to generate the hash.","label":"default"},{"data":"","label":"rationale"},{"data":"If LDAP is not being utilized, this requirement is Not Applicable.\n\n Verify the operating system implements cryptography to protect the\nintegrity of remote LDAP access sessions.\n\n To determine if LDAP is being used for authentication, use the following\ncommand:\n\n # systemctl status sssd.service\n sssd.service - System Security Services Daemon\n Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor\npreset: disabled)\n Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago\n\n If the \"sssd.service\" is \"active\", then LDAP is being used.\n\n Determine the \"id_provider\" that the LDAP is currently using:\n\n # grep -i \"id_provider\" /etc/sssd/sssd.conf\n\n id_provider = ad\n\n If \"id_provider\" is set to \"ad\", this is Not Applicable.\n\n Check the path to the X.509 certificate for peer authentication with the\nfollowing command:\n\n # grep -i tls_cacert /etc/sssd/sssd.conf\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt\n\n Verify the \"ldap_tls_cacert\" option points to a file that contains the\ntrusted CA certificate.\n\n If this file does not exist, or the option is commented out or missing,\nthis is a finding.","label":"check"},{"data":"Configure the operating system to implement cryptography to protect the\nintegrity of LDAP remote access sessions.\n\n Add or modify the following line in \"/etc/sssd/sssd.conf\":\n\n ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt","label":"fix"}],"id":"V-72231","impact":0,"refs":[],"results":[{"code_desc":"LDAP not enabled","resource":"","run_time":0.00000823,"skip_message":"LDAP not enabled using any known mechanisms, this control is Not Applicable.","start_time":"2022-03-06T22:06:06+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72231.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72231","rid":"SV-86855r4_rule","stig_id":"RHEL-07-040200","fix_id":"F-78585r3_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncryptography to protect the integrity of Lightweight Directory Access Protocol\n(LDAP) communications.","waiver_data":{}},{"code":"control \"V-72233\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems have SSH installed.\"\n desc \"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check to see if sshd is installed with the following command:\n\n # yum list installed \\\\*ssh\\\\*\n libssh2.x86_64 1.4.3-8.el7 @anaconda/7.1\n openssh.x86_64 6.6.1p1-11.el7 @anaconda/7.1\n openssh-server.x86_64 6.6.1p1-11.el7 @anaconda/7.1\n\n If the \\\"SSH server\\\" package is not installed, this is a finding.\n \"\n desc \"fix\", \"\n Install SSH packages onto the host with the following commands:\n\n # yum install openssh-server.x86_64\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000423-GPOS-00187\"\n tag satisfies: [\"SRG-OS-000423-GPOS-00187\", \"SRG-OS-000424-GPOS-00188\",\n\"SRG-OS-000425-GPOS-00189\", \"SRG-OS-000426-GPOS-00190\"]\n tag gid: \"V-72233\"\n tag rid: \"SV-86857r3_rule\"\n tag stig_id: \"RHEL-07-040300\"\n tag fix_id: \"F-78587r3_fix\"\n tag cci: [\"CCI-002418\", \"CCI-002420\", \"CCI-002421\", \"CCI-002422\"]\n tag nist: [\"SC-8\", \"SC-8 (2)\", \"SC-8 (1)\", \"SC-8 (2)\"]\n\n describe package('openssh-server') do\n it { should be_installed }\n end\n describe package('openssh-clients') do\n it { should be_installed }\n end\nend\n","desc":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.","descriptions":[{"data":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, logical means (cryptography) do not\nhave to be employed, and vice versa.","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if sshd is installed with the following command:\n\n# yum list installed \\*ssh\\*\nlibssh2.x86_64 1.4.3-8.el7 @anaconda/7.1\nopenssh.x86_64 6.6.1p1-11.el7 @anaconda/7.1\nopenssh-server.x86_64 6.6.1p1-11.el7 @anaconda/7.1\n\nIf the \"SSH server\" package is not installed, this is a finding.","label":"check"},{"data":"Install SSH packages onto the host with the following commands:\n\n# yum install openssh-server.x86_64","label":"fix"}],"id":"V-72233","impact":0.5,"refs":[],"results":[{"code_desc":"System Package openssh-server is expected to be installed","run_time":0.05347826,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"package","resource_params":"[\"openssh-server\"]"},{"code_desc":"System Package openssh-clients is expected to be installed","run_time":0.128547522,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"package","resource_params":"[\"openssh-clients\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72233.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000423-GPOS-00187","satisfies":["SRG-OS-000423-GPOS-00187","SRG-OS-000424-GPOS-00188","SRG-OS-000425-GPOS-00189","SRG-OS-000426-GPOS-00190"],"gid":"V-72233","rid":"SV-86857r3_rule","stig_id":"RHEL-07-040300","fix_id":"F-78587r3_fix","cci":["CCI-002418","CCI-002420","CCI-002421","CCI-002422"],"nist":["SC-8","SC-8 (2)","SC-8 (1)","SC-8 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems have SSH installed.","waiver_data":{}},{"code":"control \"V-72235\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems use SSH for confidentiality and integrity of\ntransmitted and received information as well as information during preparation\nfor transmission.\"\n desc \"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify SSH is loaded and active with the following command:\n\n # systemctl status sshd\n sshd.service - OpenSSH server daemon\n Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)\n Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days\nago\n Main PID: 1348 (sshd)\n CGroup: /system.slice/sshd.service\n 1053 /usr/sbin/sshd -D\n\n If \\\"sshd\\\" does not show a status of \\\"active\\\" and \\\"running\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the SSH service to automatically start after reboot with the\nfollowing command:\n\n # systemctl enable sshd.service\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000423-GPOS-00187\"\n tag satisfies: [\"SRG-OS-000423-GPOS-00187\", \"SRG-OS-000423-GPOS-00188\",\n\"SRG-OS-000423-GPOS-00189\", \"SRG-OS-000423-GPOS-00190\"]\n tag gid: \"V-72235\"\n tag rid: \"SV-86859r3_rule\"\n tag stig_id: \"RHEL-07-040310\"\n tag fix_id: \"F-78589r2_fix\"\n tag cci: [\"CCI-002418\", \"CCI-002420\", \"CCI-002421\", \"CCI-002422\"]\n tag nist: [\"SC-8\", \"SC-8 (2)\", \"SC-8 (1)\", \"SC-8 (2)\"]\n\n describe systemd_service('sshd.service') do\n it { should be_running }\n end\nend\n","desc":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.","descriptions":[{"data":"Without protection of the transmitted information, confidentiality and\nintegrity may be compromised because unprotected communications can be\nintercepted and either read or altered.\n\n This requirement applies to both internal and external networks and all\ntypes of information system components from which information can be\ntransmitted (e.g., servers, mobile devices, notebook computers, printers,\ncopiers, scanners, and facsimile machines). Communication paths outside the\nphysical protection of a controlled boundary are exposed to the possibility of\ninterception and modification.\n\n Protecting the confidentiality and integrity of organizational information\ncan be accomplished by physical means (e.g., employing physical distribution\nsystems) or by logical means (e.g., employing cryptographic techniques). If\nphysical means of protection are employed, then logical means (cryptography) do\nnot have to be employed, and vice versa.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify SSH is loaded and active with the following command:\n\n # systemctl status sshd\n sshd.service - OpenSSH server daemon\n Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)\n Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days\nago\n Main PID: 1348 (sshd)\n CGroup: /system.slice/sshd.service\n 1053 /usr/sbin/sshd -D\n\n If \"sshd\" does not show a status of \"active\" and \"running\", this is a\nfinding.","label":"check"},{"data":"Configure the SSH service to automatically start after reboot with the\nfollowing command:\n\n # systemctl enable sshd.service","label":"fix"}],"id":"V-72235","impact":0.5,"refs":[],"results":[{"code_desc":"Service sshd.service is expected to be running","run_time":0.09237288,"start_time":"2022-03-06T22:06:06+00:00","status":"passed","resource_class":"systemd_service","resource_params":"[\"sshd.service\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72235.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000423-GPOS-00187","satisfies":["SRG-OS-000423-GPOS-00187","SRG-OS-000423-GPOS-00188","SRG-OS-000423-GPOS-00189","SRG-OS-000423-GPOS-00190"],"gid":"V-72235","rid":"SV-86859r3_rule","stig_id":"RHEL-07-040310","fix_id":"F-78589r2_fix","cci":["CCI-002418","CCI-002420","CCI-002421","CCI-002422"],"nist":["SC-8","SC-8 (2)","SC-8 (1)","SC-8 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all networked systems use SSH for confidentiality and integrity of\ntransmitted and received information as well as information during preparation\nfor transmission.","waiver_data":{}},{"code":"control \"V-72237\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic are terminated at the\nend of the session or after 10 minutes of inactivity, except to fulfill\ndocumented and validated mission requirements.\"\n desc \"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \\\"ClientAliveInterval\\\" keyword with the\nfollowing command:\n\n # grep -iw clientaliveinterval /etc/ssh/sshd_config\n\n ClientAliveInterval 600\n\n If \\\"ClientAliveInterval\\\" is not configured, commented out, or has a value\nof \\\"0\\\", this is a finding.\n\n If \\\"ClientAliveInterval\\\" has a value that is greater than \\\"600\\\" and is\nnot documented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to automatically terminate a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \\\"/etc/ssh/sshd_config\\\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveInterval 600\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000163-GPOS-00072\"\n tag satisfies: [\"SRG-OS-000163-GPOS-00072\", \"SRG-OS-000279-GPOS-00109\"]\n tag gid: \"V-72237\"\n tag rid: \"SV-86861r4_rule\"\n tag stig_id: \"RHEL-07-040320\"\n tag fix_id: \"F-78591r2_fix\"\n tag cci: [\"CCI-001133\", \"CCI-002361\"]\n tag nist: [\"SC-10\", \"AC-12\"]\n\n client_alive_interval = input('client_alive_interval')\n\n #This may show slightly confusing results when a ClientAliveInterValue is not\n #specified. Specifically, because the value will be nil and when you try to\n #convert it to an integer using to_i it will convert it to 0 and pass the\n #<= client_alive_interval check. However, the control as a whole will still fail.\n describe sshd_config do\n its(\"ClientAliveInterval.to_i\"){should cmp >= 1}\n its(\"ClientAliveInterval.to_i\"){should cmp <= client_alive_interval}\n its(\"ClientAliveInterval\"){should_not eq nil}\n end\nend\n","desc":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \"ClientAliveInterval\" keyword with the\nfollowing command:\n\n # grep -iw clientaliveinterval /etc/ssh/sshd_config\n\n ClientAliveInterval 600\n\n If \"ClientAliveInterval\" is not configured, commented out, or has a value\nof \"0\", this is a finding.\n\n If \"ClientAliveInterval\" has a value that is greater than \"600\" and is\nnot documented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.","label":"check"},{"data":"Configure the operating system to automatically terminate a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveInterval 600\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72237","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration ClientAliveInterval.to_i is expected to cmp >= 1","message":"\nexpected it to be >= 1\n got: 0\n\n(compared using `cmp` matcher)\n","run_time":0.002387835,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"},{"code_desc":"SSHD Configuration ClientAliveInterval.to_i is expected to cmp <= 600","run_time":0.000206422,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"sshd_config","resource_params":"[]"},{"code_desc":"SSHD Configuration ClientAliveInterval is expected not to eq nil","message":"\nexpected: value != nil\n got: nil\n\n(compared using ==)\n","run_time":0.000204892,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72237.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","satisfies":["SRG-OS-000163-GPOS-00072","SRG-OS-000279-GPOS-00109"],"gid":"V-72237","rid":"SV-86861r4_rule","stig_id":"RHEL-07-040320","fix_id":"F-78591r2_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic are terminated at the\nend of the session or after 10 minutes of inactivity, except to fulfill\ndocumented and validated mission requirements.","waiver_data":{}},{"code":"control \"V-72239\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using RSA rhosts\nauthentication.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon does not allow authentication using RSA rhosts\nauthentication.\n\n To determine how the SSH daemon's \\\"RhostsRSAAuthentication\\\" option is\nset, run the following command:\n\n # grep RhostsRSAAuthentication /etc/ssh/sshd_config\n RhostsRSAAuthentication no\n\n If the value is returned as \\\"yes\\\", the returned line is commented out, or\nno output is returned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the SSH daemon to not allow authentication using RSA rhosts\nauthentication.\n\n Add the following line in \\\"/etc/ssh/sshd_config\\\", or uncomment the line\nand set the value to \\\"no\\\":\n\n RhostsRSAAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72239\"\n tag rid: \"SV-86863r4_rule\"\n tag stig_id: \"RHEL-07-040330\"\n tag fix_id: \"F-78593r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('RhostsRSAAuthentication') { should cmp 'no' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon does not allow authentication using RSA rhosts\nauthentication.\n\n To determine how the SSH daemon's \"RhostsRSAAuthentication\" option is\nset, run the following command:\n\n # grep RhostsRSAAuthentication /etc/ssh/sshd_config\n RhostsRSAAuthentication no\n\n If the value is returned as \"yes\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using RSA rhosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"no\":\n\n RhostsRSAAuthentication no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72239","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration RhostsRSAAuthentication is expected to cmp == \"no\"","message":"\nexpected: no\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.002486382,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72239.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72239","rid":"SV-86863r4_rule","stig_id":"RHEL-07-040330","fix_id":"F-78593r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using RSA rhosts\nauthentication.","waiver_data":{}},{"code":"control \"V-72241\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic terminate after a\nperiod of inactivity.\"\n desc \"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \\\"ClientAliveCountMax\\\" keyword with the\nfollowing command:\n\n # grep -i clientalivecount /etc/ssh/sshd_config\n ClientAliveCountMax 0\n\n If \\\"ClientAliveCountMax\\\" is not set to \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to terminate automatically a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \\\"/etc/ssh/sshd_config\\\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveCountMax 0\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000163-GPOS-00072\"\n tag satisfies: [\"SRG-OS-000163-GPOS-00072\", \"SRG-OS-000279-GPOS-00109\"]\n tag gid: \"V-72241\"\n tag rid: \"SV-86865r4_rule\"\n tag stig_id: \"RHEL-07-040340\"\n tag fix_id: \"F-78595r4_fix\"\n tag cci: [\"CCI-001133\", \"CCI-002361\"]\n tag nist: [\"SC-10\", \"AC-12\"]\n\n if os.release.to_f >= 7.4\n impact 0.0\n describe \"The release is #{os.release}\" do\n skip \"The release is newer than 7.4; this control is Not Applicable.\"\n end\n else\n describe sshd_config do\n its('ClientAliveCountMax') { should cmp '0' }\n end\n end\nend\n","desc":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","descriptions":[{"data":"Terminating an idle SSH session within a short time period reduces the\nwindow of opportunity for unauthorized personnel to take control of a\nmanagement session enabled on the console or console port that has been left\nunattended. In addition, quickly terminating an idle SSH session will also free\nup resources committed by the managed network element.\n\n Terminating network connections associated with communications sessions\nincludes, for example, de-allocating associated TCP/IP address/port pairs at\nthe operating system level and de-allocating networking assignments at the\napplication level if multiple application sessions are using a single operating\nsystem-level network connection. This does not mean that the operating system\nterminates all sessions or network access; it only ends the inactive session\nand releases the resources associated with that session.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system automatically terminates a user session after\ninactivity time-outs have expired.\n\n Check for the value of the \"ClientAliveCountMax\" keyword with the\nfollowing command:\n\n # grep -i clientalivecount /etc/ssh/sshd_config\n ClientAliveCountMax 0\n\n If \"ClientAliveCountMax\" is not set to \"0\", this is a finding.","label":"check"},{"data":"Configure the operating system to terminate automatically a user session\nafter inactivity time-outs have expired or at shutdown.\n\n Add the following line (or modify the line to have the required value) to\nthe \"/etc/ssh/sshd_config\" file (this file may be named differently or be in\na different location if using a version of SSH that is provided by a\nthird-party vendor):\n\n ClientAliveCountMax 0\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72241","impact":0,"refs":[],"results":[{"code_desc":"The release is 7.9.2009","resource":"","run_time":0.00001005,"skip_message":"The release is newer than 7.4; this control is Not Applicable.","start_time":"2022-03-06T22:06:07+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72241.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000163-GPOS-00072","satisfies":["SRG-OS-000163-GPOS-00072","SRG-OS-000279-GPOS-00109"],"gid":"V-72241","rid":"SV-86865r4_rule","stig_id":"RHEL-07-040340","fix_id":"F-78595r4_fix","cci":["CCI-001133","CCI-002361"],"nist":["SC-10","AC-12"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all network connections associated with SSH traffic terminate after a\nperiod of inactivity.","waiver_data":{}},{"code":"control \"V-72243\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using rhosts authentication.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \\\"IgnoreRhosts\\\" option is set, run the\nfollowing command:\n\n # grep -i IgnoreRhosts /etc/ssh/sshd_config\n\n IgnoreRhosts yes\n\n If the value is returned as \\\"no\\\", the returned line is commented out, or\nno output is returned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \\\"/etc/ssh/sshd_config\\\", or uncomment the line\nand set the value to \\\"yes\\\":\n\n IgnoreRhosts yes\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72243\"\n tag rid: \"SV-86867r3_rule\"\n tag stig_id: \"RHEL-07-040350\"\n tag fix_id: \"F-78597r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('IgnoreRhosts') { should cmp 'yes' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \"IgnoreRhosts\" option is set, run the\nfollowing command:\n\n # grep -i IgnoreRhosts /etc/ssh/sshd_config\n\n IgnoreRhosts yes\n\n If the value is returned as \"no\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"yes\":\n\n IgnoreRhosts yes","label":"fix"}],"id":"V-72243","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration IgnoreRhosts is expected to cmp == \"yes\"","message":"\nexpected: yes\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.002793633,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72243.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72243","rid":"SV-86867r3_rule","stig_id":"RHEL-07-040350","fix_id":"F-78597r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using rhosts authentication.","waiver_data":{}},{"code":"control \"V-72245\" do\n title \"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon an SSH logon.\"\n desc \"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify SSH provides users with feedback on when account accesses last\noccurred.\n\n Check that \\\"PrintLastLog\\\" keyword in the sshd daemon configuration file\nis used and set to \\\"yes\\\" with the following command:\n\n # grep -i printlastlog /etc/ssh/sshd_config\n PrintLastLog yes\n\n If the \\\"PrintLastLog\\\" keyword is set to \\\"no\\\", is missing, or is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure SSH to provide users with feedback on when account accesses last\noccurred by setting the required configuration options in \\\"/etc/pam.d/sshd\\\"\nor in the \\\"sshd_config\\\" file used by the system (\\\"/etc/ssh/sshd_config\\\"\nwill be used in the example) (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor).\n\n Modify the \\\"PrintLastLog\\\" line in \\\"/etc/ssh/sshd_config\\\" to match the\nfollowing:\n\n PrintLastLog yes\n\n The SSH service must be restarted for changes to \\\"sshd_config\\\" to take\neffect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72245\"\n tag rid: \"SV-86869r3_rule\"\n tag stig_id: \"RHEL-07-040360\"\n tag fix_id: \"F-78599r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if sshd_config.params['printlastlog'] == ['yes']\n describe sshd_config do\n its('PrintLastLog') { should cmp 'yes' }\n end\n else\n describe pam('/etc/pam.d/sshd') do\n its('lines') { should match_pam_rule('session required pam_lastlog.so showfailed') }\n its('lines') { should match_pam_rule('session required pam_lastlog.so showfailed').all_without_args('silent') }\n end\n end\nend\n","desc":"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.","descriptions":[{"data":"Providing users with feedback on when account accesses via SSH last\noccurred facilitates user recognition and reporting of unauthorized account\nuse.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify SSH provides users with feedback on when account accesses last\noccurred.\n\n Check that \"PrintLastLog\" keyword in the sshd daemon configuration file\nis used and set to \"yes\" with the following command:\n\n # grep -i printlastlog /etc/ssh/sshd_config\n PrintLastLog yes\n\n If the \"PrintLastLog\" keyword is set to \"no\", is missing, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to provide users with feedback on when account accesses last\noccurred by setting the required configuration options in \"/etc/pam.d/sshd\"\nor in the \"sshd_config\" file used by the system (\"/etc/ssh/sshd_config\"\nwill be used in the example) (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor).\n\n Modify the \"PrintLastLog\" line in \"/etc/ssh/sshd_config\" to match the\nfollowing:\n\n PrintLastLog yes\n\n The SSH service must be restarted for changes to \"sshd_config\" to take\neffect.","label":"fix"}],"id":"V-72245","impact":0.5,"refs":[],"results":[{"code_desc":"PAM Config[/etc/pam.d/sshd] lines is expected to include session required pam_lastlog.so showfailed","message":"expected \"account required pam_unix.so\\naccount sufficient pam_localuser.so\\naccount sufficient pam_succeed_if...on optional pam_lastlog.so silent noupdate showfailed\\n-session optional pam_reauthorize.so prepare\" to include session required pam_lastlog.so showfailed\nDiff:\n@@ -1,2 +1,84 @@\n-session required pam_lastlog.so showfailed\n+account required pam_unix.so\n+account sufficient pam_localuser.so\n+account sufficient pam_succeed_if.so uid < 1000 quiet\n+account required pam_permit.so\n+account required pam_nologin.so\n+account required pam_unix.so\n+account sufficient pam_localuser.so\n+account sufficient pam_succeed_if.so uid < 1000 quiet\n+account required pam_permit.so\n+account required pam_unix.so\n+account sufficient pam_localuser.so\n+account sufficient pam_succeed_if.so uid < 1000 quiet\n+account required pam_permit.so\n+account required pam_unix.so\n+account sufficient pam_localuser.so\n+account sufficient pam_succeed_if.so uid < 1000 quiet\n+account required pam_permit.so\n+auth required pam_sepermit.so\n+auth required pam_env.so\n+auth required pam_faildelay.so delay=2000000\n+auth sufficient pam_unix.so nullok try_first_pass\n+auth requisite pam_succeed_if.so uid >= 1000 quiet_success\n+auth required pam_deny.so\n+-auth optional pam_reauthorize.so prepare\n+auth required pam_env.so\n+auth required pam_faildelay.so delay=2000000\n+auth sufficient pam_unix.so nullok try_first_pass\n+auth requisite pam_succeed_if.so uid >= 1000 quiet_success\n+auth required pam_deny.so\n+auth required pam_env.so\n+auth required pam_faildelay.so delay=2000000\n+auth sufficient pam_unix.so nullok try_first_pass\n+auth requisite pam_succeed_if.so uid >= 1000 quiet_success\n+auth required pam_deny.so\n+auth required pam_env.so\n+auth required pam_faildelay.so delay=2000000\n+auth sufficient pam_unix.so nullok try_first_pass\n+auth requisite pam_succeed_if.so uid >= 1000 quiet_success\n+auth required pam_deny.so\n+password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+password required pam_deny.so\n+password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+password required pam_deny.so\n+password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+password required pam_deny.so\n+password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=\n+password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok\n+password required pam_deny.so\n+session optional pam_keyinit.so revoke\n+session required pam_limits.so\n+-session optional pam_systemd.so\n+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\n+session required pam_unix.so\n+session [success=1 default=ignore] pam_succeed_if.so service !~ gdm* service !~ su* quiet\n+session [default=1] pam_lastlog.so nowtmp showfailed\n+session optional pam_lastlog.so silent noupdate showfailed\n+session optional pam_keyinit.so revoke\n+session required pam_limits.so\n+-session optional pam_systemd.so\n+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\n+session required pam_unix.so\n+session optional pam_keyinit.so revoke\n+session required pam_limits.so\n+-session optional pam_systemd.so\n+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\n+session required pam_unix.so\n+session required pam_selinux.so close\n+session required pam_loginuid.so\n+session required pam_selinux.so open env_params\n+session required pam_namespace.so\n+session optional pam_keyinit.so force revoke\n+session optional pam_keyinit.so revoke\n+session required pam_limits.so\n+-session optional pam_systemd.so\n+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid\n+session required pam_unix.so\n+session [success=1 default=ignore] pam_succeed_if.so service !~ gdm* service !~ su* quiet\n+session [default=1] pam_lastlog.so nowtmp showfailed\n+session optional pam_lastlog.so silent noupdate showfailed\n+-session optional pam_reauthorize.so prepare\n","run_time":0.006195942,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/sshd\"]"},{"code_desc":"PAM Config[/etc/pam.d/sshd] lines is expected to include session required pam_lastlog.so showfailed, all without args silent","run_time":0.003192312,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/sshd\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72245.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72245","rid":"SV-86869r3_rule","stig_id":"RHEL-07-040360","fix_id":"F-78599r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon an SSH logon.","waiver_data":{}},{"code":"control \"V-72247\" do\n title \"The Red Hat Enterprise Linux operating system must not permit direct\nlogons to the root account using remote access via SSH.\"\n desc \"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify remote access using SSH prevents users from logging on directly as\nroot.\n\n Check that SSH prevents users from logging on directly as root with the\nfollowing command:\n\n # grep -i permitrootlogin /etc/ssh/sshd_config\n PermitRootLogin no\n\n If the \\\"PermitRootLogin\\\" keyword is set to \\\"yes\\\", is missing, or is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure SSH to stop users from logging on remotely as the root user.\n\n Edit the appropriate \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the\nline for the \\\"PermitRootLogin\\\" keyword and set its value to \\\"no\\\" (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor):\n\n PermitRootLogin no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72247\"\n tag rid: \"SV-86871r3_rule\"\n tag stig_id: \"RHEL-07-040370\"\n tag fix_id: \"F-78601r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('PermitRootLogin') { should cmp 'no' }\n end\nend\n","desc":"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.","descriptions":[{"data":"Even though the communications channel may be encrypted, an additional\nlayer of security is gained by extending the policy of not logging on directly\nas root. In addition, logging on with a user-specific account provides\nindividual accountability of actions performed on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify remote access using SSH prevents users from logging on directly as\nroot.\n\n Check that SSH prevents users from logging on directly as root with the\nfollowing command:\n\n # grep -i permitrootlogin /etc/ssh/sshd_config\n PermitRootLogin no\n\n If the \"PermitRootLogin\" keyword is set to \"yes\", is missing, or is\ncommented out, this is a finding.","label":"check"},{"data":"Configure SSH to stop users from logging on remotely as the root user.\n\n Edit the appropriate \"/etc/ssh/sshd_config\" file to uncomment or add the\nline for the \"PermitRootLogin\" keyword and set its value to \"no\" (this file\nmay be named differently or be in a different location if using a version of\nSSH that is provided by a third-party vendor):\n\n PermitRootLogin no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72247","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration PermitRootLogin is expected to cmp == \"no\"","message":"\nexpected: no\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.00233457,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72247.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72247","rid":"SV-86871r3_rule","stig_id":"RHEL-07-040370","fix_id":"F-78601r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not permit direct\nlogons to the root account using remote access via SSH.","waiver_data":{}},{"code":"control \"V-72249\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using known hosts\nauthentication.\"\n desc \"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \\\"IgnoreUserKnownHosts\\\" option is set,\nrun the following command:\n\n # grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config\n\n IgnoreUserKnownHosts yes\n\n If the value is returned as \\\"no\\\", the returned line is commented out, or\nno output is returned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \\\"/etc/ssh/sshd_config\\\", or uncomment the line\nand set the value to \\\"yes\\\":\n\n IgnoreUserKnownHosts yes\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72249\"\n tag rid: \"SV-86873r3_rule\"\n tag stig_id: \"RHEL-07-040380\"\n tag fix_id: \"F-78603r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('IgnoreUserKnownHosts') { should cmp 'yes' }\n end\nend\n","desc":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","descriptions":[{"data":"Configuring this setting for the SSH daemon provides additional\nassurance that remote logon via SSH will require a password, even in the event\nof misconfiguration elsewhere.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not allow authentication using known hosts\nauthentication.\n\n To determine how the SSH daemon's \"IgnoreUserKnownHosts\" option is set,\nrun the following command:\n\n # grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config\n\n IgnoreUserKnownHosts yes\n\n If the value is returned as \"no\", the returned line is commented out, or\nno output is returned, this is a finding.","label":"check"},{"data":"Configure the SSH daemon to not allow authentication using known hosts\nauthentication.\n\n Add the following line in \"/etc/ssh/sshd_config\", or uncomment the line\nand set the value to \"yes\":\n\n IgnoreUserKnownHosts yes\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72249","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration IgnoreUserKnownHosts is expected to cmp == \"yes\"","message":"\nexpected: yes\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.003869996,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72249.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72249","rid":"SV-86873r3_rule","stig_id":"RHEL-07-040380","fix_id":"F-78603r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow authentication using known hosts\nauthentication.","waiver_data":{}},{"code":"control \"V-72251\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use the SSHv2 protocol.\"\n desc \"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon is configured to only use the SSHv2 protocol.\n\n Check that the SSH daemon is configured to only use the SSHv2 protocol with\nthe following command:\n\n # grep -i protocol /etc/ssh/sshd_config\n Protocol 2\n #Protocol 1,2\n\n If any protocol line other than \\\"Protocol 2\\\" is uncommented, this is a\nfinding.\n \"\n desc \"fix\", \"\n Remove all Protocol lines that reference version \\\"1\\\" in\n\\\"/etc/ssh/sshd_config\\\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor). The \\\"Protocol\\\" line must be as follows:\n\n Protocol 2\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000074-GPOS-00042\"\n tag satisfies: [\"SRG-OS-000074-GPOS-00042\", \"SRG-OS-000480-GPOS-00227\"]\n tag gid: \"V-72251\"\n tag rid: \"SV-86875r4_rule\"\n tag stig_id: \"RHEL-07-040390\"\n tag fix_id: \"F-78605r2_fix\"\n tag cci: [\"CCI-000197\", \"CCI-000366\"]\n tag nist: [\"IA-5 (1) (c)\", \"CM-6 b\"]\n\n if os.release.to_f >= 7.4\n impact 0.0\n describe \"The release is #{os.release}\" do\n skip \"The release is newer than 7.4; this control is Not Applicable.\"\n end\n else\n describe sshd_config do\n its('Protocol') { should cmp '2' }\n end\n end\nend\n","desc":"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.","descriptions":[{"data":"SSHv1 is an insecure implementation of the SSH protocol and has many\nwell-known vulnerability exploits. Exploits of the SSH daemon could provide\nimmediate root access to the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Check the version of the operating system with the following command:\n\n # cat /etc/redhat-release\n\n If the release is 7.4 or newer this requirement is Not Applicable.\n\n Verify the SSH daemon is configured to only use the SSHv2 protocol.\n\n Check that the SSH daemon is configured to only use the SSHv2 protocol with\nthe following command:\n\n # grep -i protocol /etc/ssh/sshd_config\n Protocol 2\n #Protocol 1,2\n\n If any protocol line other than \"Protocol 2\" is uncommented, this is a\nfinding.","label":"check"},{"data":"Remove all Protocol lines that reference version \"1\" in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor). The \"Protocol\" line must be as follows:\n\n Protocol 2\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72251","impact":0,"refs":[],"results":[{"code_desc":"The release is 7.9.2009","resource":"","run_time":0.000009681,"skip_message":"The release is newer than 7.4; this control is Not Applicable.","start_time":"2022-03-06T22:06:07+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72251.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000074-GPOS-00042","satisfies":["SRG-OS-000074-GPOS-00042","SRG-OS-000480-GPOS-00227"],"gid":"V-72251","rid":"SV-86875r4_rule","stig_id":"RHEL-07-040390","fix_id":"F-78605r2_fix","cci":["CCI-000197","CCI-000366"],"nist":["IA-5 (1) (c)","CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use the SSHv2 protocol.","waiver_data":{}},{"code":"control \"V-72253\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use Message Authentication Codes\n(MACs) employing FIPS 140-2 approved cryptographic hash algorithms.\"\n desc \"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n Check that the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers with the following command:\n\n # grep -i macs /etc/ssh/sshd_config\n MACs hmac-sha2-256,hmac-sha2-512\n\n If any ciphers other than \\\"hmac-sha2-256\\\" or \\\"hmac-sha2-512\\\" are listed\nor the returned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for the\n\\\"MACs\\\" keyword and set its value to \\\"hmac-sha2-256\\\" and/or\n\\\"hmac-sha2-512\\\" (this file may be named differently or be in a different\nlocation if using a version of SSH that is provided by a third-party vendor):\n\n MACs hmac-sha2-256,hmac-sha2-512\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000250-GPOS-00093\"\n tag gid: \"V-72253\"\n tag rid: \"SV-86877r3_rule\"\n tag stig_id: \"RHEL-07-040400\"\n tag fix_id: \"F-78607r2_fix\"\n tag cci: [\"CCI-001453\"]\n tag nist: [\"AC-17 (2)\"]\n\n @macs = inspec.sshd_config.params(\"macs\")\n if @macs.nil?\n # fail fast\n describe 'The `sshd_config` setting for `MACs`' do\n subject { @macs }\n it 'should be explicitly set and not commented out' do\n expect(subject).not_to be_nil\n end\n end\n else\n @macs.first.split(\",\").each do |mac|\n describe mac do\n it { should be_in ['hmac-sha2-256', 'hmac-sha2-512'] }\n end\n end\n end\nend\n","desc":"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.","descriptions":[{"data":"DoD information systems are required to use FIPS 140-2 approved\ncryptographic hash functions. The only SSHv2 hash algorithm meeting this\nrequirement is SHA.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers.\n\n Note: If RHEL-07-021350 is a finding, this is automatically a finding as\nthe system cannot implement FIPS 140-2-approved cryptographic algorithms and\nhashes.\n\n Check that the SSH daemon is configured to only use MACs employing FIPS\n140-2-approved ciphers with the following command:\n\n # grep -i macs /etc/ssh/sshd_config\n MACs hmac-sha2-256,hmac-sha2-512\n\n If any ciphers other than \"hmac-sha2-256\" or \"hmac-sha2-512\" are listed\nor the returned line is commented out, this is a finding.","label":"check"},{"data":"Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the\n\"MACs\" keyword and set its value to \"hmac-sha2-256\" and/or\n\"hmac-sha2-512\" (this file may be named differently or be in a different\nlocation if using a version of SSH that is provided by a third-party vendor):\n\n MACs hmac-sha2-256,hmac-sha2-512\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72253","impact":0.5,"refs":[],"results":[{"code_desc":"The `sshd_config` setting for `MACs` should be explicitly set and not commented out","message":"expected: not nil\n got: nil","run_time":0.00018411,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72253.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000250-GPOS-00093","gid":"V-72253","rid":"SV-86877r3_rule","stig_id":"RHEL-07-040400","fix_id":"F-78607r2_fix","cci":["CCI-001453"],"nist":["AC-17 (2)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon is configured to only use Message Authentication Codes\n(MACs) employing FIPS 140-2 approved cryptographic hash algorithms.","waiver_data":{}},{"code":"control \"V-72255\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH public host key files have mode 0644 or less permissive.\"\n desc \"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH public host key files have mode \\\"0644\\\" or less permissive.\n\n Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n The following command will find all SSH public key files on the system:\n\n # find /etc/ssh -name '*.pub' -exec ls -lL {} \\\\;\n\n -rw-r--r-- 1 root root 618 Nov 28 06:43 ssh_host_dsa_key.pub\n -rw-r--r-- 1 root root 347 Nov 28 06:43 ssh_host_key.pub\n -rw-r--r-- 1 root root 238 Nov 28 06:43 ssh_host_rsa_key.pub\n\n If any file has a mode more permissive than \\\"0644\\\", this is a finding.\n \"\n desc \"fix\", \"\n Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n Change the mode of public host key files under \\\"/etc/ssh\\\" to \\\"0644\\\"\nwith the following command:\n\n # chmod 0644 /etc/ssh/*.key.pub\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72255\"\n tag rid: \"SV-86879r2_rule\"\n tag stig_id: \"RHEL-07-040410\"\n tag fix_id: \"F-78609r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n pub_files = command(\"find /etc/ssh -xdev -name '*.pub' -perm /133\").stdout.split(\"\\n\")\n if !pub_files.nil? and !pub_files.empty?\n pub_files.each do |pubfile|\n describe file(pubfile) do\n it { should_not be_executable.by('owner') }\n it { should_not be_executable.by('group') }\n it { should_not be_writable.by('group') }\n it { should_not be_executable.by('others') }\n it { should_not be_writable.by('others') }\n end\n end\n else\n describe \"No files have a more permissive mode.\" do\n subject { pub_files.nil? or pub_files.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.","descriptions":[{"data":"If a public host key file is modified by an unauthorized user, the SSH\nservice may be compromised.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH public host key files have mode \"0644\" or less permissive.\n\n Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n The following command will find all SSH public key files on the system:\n\n # find /etc/ssh -name '*.pub' -exec ls -lL {} \\;\n\n -rw-r--r-- 1 root root 618 Nov 28 06:43 ssh_host_dsa_key.pub\n -rw-r--r-- 1 root root 347 Nov 28 06:43 ssh_host_key.pub\n -rw-r--r-- 1 root root 238 Nov 28 06:43 ssh_host_rsa_key.pub\n\n If any file has a mode more permissive than \"0644\", this is a finding.","label":"check"},{"data":"Note: SSH public key files may be found in other directories on the system\ndepending on the installation.\n\n Change the mode of public host key files under \"/etc/ssh\" to \"0644\"\nwith the following command:\n\n # chmod 0644 /etc/ssh/*.key.pub","label":"fix"}],"id":"V-72255","impact":0.5,"refs":[],"results":[{"code_desc":"No files have a more permissive mode. is expected to eq true","run_time":0.000989573,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72255.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72255","rid":"SV-86879r2_rule","stig_id":"RHEL-07-040410","fix_id":"F-78609r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH public host key files have mode 0644 or less permissive.","waiver_data":{}},{"code":"control \"V-72257\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH private host key files have mode 0640 or less permissive.\"\n desc \"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH private host key files have mode \\\"0640\\\" or less permissive.\n\n The following command will find all SSH private key files on the system and\nlist their modes:\n\n # find / -name '*ssh_host*key' | xargs ls -lL\n\n -rw-r----- 1 root ssh_keys 668 Nov 28 06:43 ssh_host_dsa_key\n -rw-r----- 1 root ssh_keys 582 Nov 28 06:43 ssh_host_key\n -rw-r----- 1 root ssh_keys 887 Nov 28 06:43 ssh_host_rsa_key\n\n If any file has a mode more permissive than \\\"0640\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the mode of SSH private host key files under \\\"/etc/ssh\\\" to\n\\\"0640\\\" with the following command:\n\n # chmod 0640 /path/to/file/ssh_host*key\n\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72257\"\n tag rid: \"SV-86881r3_rule\"\n tag stig_id: \"RHEL-07-040420\"\n tag fix_id: \"F-78611r5_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n key_files = command(\"find /etc/ssh -xdev -name '*ssh_host*key'\").stdout.split(\"\\n\")\n if !key_files.nil? and !key_files.empty?\n key_files.each do |keyfile|\n describe file(keyfile) do\n it { should_not be_more_permissive_than('0640') }\n end\n end\n else\n describe \"No files have a more permissive mode.\" do\n subject { key_files.nil? or key_files.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.","descriptions":[{"data":"If an unauthorized user obtains the private SSH host key file, the\nhost could be impersonated.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH private host key files have mode \"0640\" or less permissive.\n\n The following command will find all SSH private key files on the system and\nlist their modes:\n\n # find / -name '*ssh_host*key' | xargs ls -lL\n\n -rw-r----- 1 root ssh_keys 668 Nov 28 06:43 ssh_host_dsa_key\n -rw-r----- 1 root ssh_keys 582 Nov 28 06:43 ssh_host_key\n -rw-r----- 1 root ssh_keys 887 Nov 28 06:43 ssh_host_rsa_key\n\n If any file has a mode more permissive than \"0640\", this is a finding.","label":"check"},{"data":"Configure the mode of SSH private host key files under \"/etc/ssh\" to\n\"0640\" with the following command:\n\n # chmod 0640 /path/to/file/ssh_host*key","label":"fix"}],"id":"V-72257","impact":0.5,"refs":[],"results":[{"code_desc":"File /etc/ssh/ssh_host_rsa_key is expected not to be more permissive than \"0640\"","run_time":0.053017339,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/ssh/ssh_host_rsa_key\"]"},{"code_desc":"File /etc/ssh/ssh_host_ecdsa_key is expected not to be more permissive than \"0640\"","run_time":0.061568985,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/ssh/ssh_host_ecdsa_key\"]"},{"code_desc":"File /etc/ssh/ssh_host_ed25519_key is expected not to be more permissive than \"0640\"","run_time":0.037209935,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"file","resource_params":"[\"/etc/ssh/ssh_host_ed25519_key\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72257.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72257","rid":"SV-86881r3_rule","stig_id":"RHEL-07-040420","fix_id":"F-78611r5_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH private host key files have mode 0640 or less permissive.","waiver_data":{}},{"code":"control \"V-72259\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Generic Security Service Application\nProgram Interface (GSSAPI) authentication unless needed.\"\n desc \"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not permit GSSAPI authentication unless approved.\n\n Check that the SSH daemon does not permit GSSAPI authentication with the\nfollowing command:\n\n # grep -i gssapiauth /etc/ssh/sshd_config\n GSSAPIAuthentication no\n\n If the \\\"GSSAPIAuthentication\\\" keyword is missing, is set to \\\"yes\\\" and\nis not documented with the Information System Security Officer (ISSO), or the\nreturned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"GSSAPIAuthentication\\\" keyword in \\\"/etc/ssh/sshd_config\\\"\n(this file may be named differently or be in a different location if using a\nversion of SSH that is provided by a third-party vendor) and set the value to\n\\\"no\\\":\n\n GSSAPIAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If GSSAPI authentication is required, it must be documented, to include the\nlocation of the configuration file, with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000364-GPOS-00151\"\n tag gid: \"V-72259\"\n tag rid: \"SV-86883r3_rule\"\n tag stig_id: \"RHEL-07-040430\"\n tag fix_id: \"F-78613r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n if input('gssapi_approved')\n describe sshd_config do\n its('GSSAPIAuthentication') { should cmp 'no' }\n end\n else\n impact 0.0\n describe \"GSSAPI authentication is not approved\" do\n skip \"GSSAPI authentication is not approved, this control is Not Applicable.\"\n end\n end\nend\n","desc":"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.","descriptions":[{"data":"GSSAPI authentication is used to provide additional authentication\nmechanisms to applications. Allowing GSSAPI authentication through SSH exposes\nthe system's GSSAPI to remote hosts, increasing the attack surface of the\nsystem. GSSAPI authentication must be disabled unless needed.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not permit GSSAPI authentication unless approved.\n\n Check that the SSH daemon does not permit GSSAPI authentication with the\nfollowing command:\n\n # grep -i gssapiauth /etc/ssh/sshd_config\n GSSAPIAuthentication no\n\n If the \"GSSAPIAuthentication\" keyword is missing, is set to \"yes\" and\nis not documented with the Information System Security Officer (ISSO), or the\nreturned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"GSSAPIAuthentication\" keyword in \"/etc/ssh/sshd_config\"\n(this file may be named differently or be in a different location if using a\nversion of SSH that is provided by a third-party vendor) and set the value to\n\"no\":\n\n GSSAPIAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If GSSAPI authentication is required, it must be documented, to include the\nlocation of the configuration file, with the ISSO.","label":"fix"}],"id":"V-72259","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration GSSAPIAuthentication is expected to cmp == \"no\"","message":"\nexpected: no\n got: yes\n\n(compared using `cmp` matcher)\n","run_time":0.012166039,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72259.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72259","rid":"SV-86883r3_rule","stig_id":"RHEL-07-040430","fix_id":"F-78613r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Generic Security Service Application\nProgram Interface (GSSAPI) authentication unless needed.","waiver_data":{}},{"code":"control \"V-72261\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Kerberos authentication unless needed.\"\n desc \"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon does not permit Kerberos to authenticate passwords\nunless approved.\n\n Check that the SSH daemon does not permit Kerberos to authenticate\npasswords with the following command:\n\n # grep -i kerberosauth /etc/ssh/sshd_config\n KerberosAuthentication no\n\n If the \\\"KerberosAuthentication\\\" keyword is missing, or is set to \\\"yes\\\"\nand is not documented with the Information System Security Officer (ISSO), or\nthe returned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"KerberosAuthentication\\\" keyword in\n\\\"/etc/ssh/sshd_config\\\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \\\"no\\\":\n\n KerberosAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If Kerberos authentication is required, it must be documented, to include\nthe location of the configuration file, with the ISSO.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000364-GPOS-00151\"\n tag gid: \"V-72261\"\n tag rid: \"SV-86885r3_rule\"\n tag stig_id: \"RHEL-07-040440\"\n tag fix_id: \"F-78615r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n describe sshd_config do\n its('KerberosAuthentication') { should cmp 'no' }\n end\nend\n","desc":"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.","descriptions":[{"data":"Kerberos authentication for SSH is often implemented using Generic\nSecurity Service Application Program Interface (GSSAPI). If Kerberos is enabled\nthrough SSH, the SSH daemon provides a means of access to the system's Kerberos\nimplementation. Vulnerabilities in the system's Kerberos implementation may\nthen be subject to exploitation. To reduce the attack surface of the system,\nthe Kerberos authentication mechanism within SSH must be disabled for systems\nnot using this capability.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon does not permit Kerberos to authenticate passwords\nunless approved.\n\n Check that the SSH daemon does not permit Kerberos to authenticate\npasswords with the following command:\n\n # grep -i kerberosauth /etc/ssh/sshd_config\n KerberosAuthentication no\n\n If the \"KerberosAuthentication\" keyword is missing, or is set to \"yes\"\nand is not documented with the Information System Security Officer (ISSO), or\nthe returned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"KerberosAuthentication\" keyword in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \"no\":\n\n KerberosAuthentication no\n\n The SSH service must be restarted for changes to take effect.\n\n If Kerberos authentication is required, it must be documented, to include\nthe location of the configuration file, with the ISSO.","label":"fix"}],"id":"V-72261","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration KerberosAuthentication is expected to cmp == \"no\"","message":"\nexpected: no\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.007319016,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72261.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000364-GPOS-00151","gid":"V-72261","rid":"SV-86885r3_rule","stig_id":"RHEL-07-040440","fix_id":"F-78615r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not permit Kerberos authentication unless needed.","waiver_data":{}},{"code":"control \"V-72263\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon performs strict mode checking of home directory\nconfiguration files.\"\n desc \"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon performs strict mode checking of home directory\nconfiguration files.\n\n The location of the \\\"sshd_config\\\" file may vary if a different daemon is\nin use.\n\n Inspect the \\\"sshd_config\\\" file with the following command:\n\n # grep -i strictmodes /etc/ssh/sshd_config\n\n StrictModes yes\n\n If \\\"StrictModes\\\" is set to \\\"no\\\", is missing, or the returned line is\ncommented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"StrictModes\\\" keyword in \\\"/etc/ssh/sshd_config\\\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) and set the value to \\\"yes\\\":\n\n StrictModes yes\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72263\"\n tag rid: \"SV-86887r3_rule\"\n tag stig_id: \"RHEL-07-040450\"\n tag fix_id: \"F-78617r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('StrictModes') { should cmp 'yes' }\n end\nend\n","desc":"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.","descriptions":[{"data":"If other users have access to modify user-specific SSH configuration\nfiles, they may be able to log on to the system as another user.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs strict mode checking of home directory\nconfiguration files.\n\n The location of the \"sshd_config\" file may vary if a different daemon is\nin use.\n\n Inspect the \"sshd_config\" file with the following command:\n\n # grep -i strictmodes /etc/ssh/sshd_config\n\n StrictModes yes\n\n If \"StrictModes\" is set to \"no\", is missing, or the returned line is\ncommented out, this is a finding.","label":"check"},{"data":"Uncomment the \"StrictModes\" keyword in \"/etc/ssh/sshd_config\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) and set the value to \"yes\":\n\n StrictModes yes\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72263","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration StrictModes is expected to cmp == \"yes\"","message":"\nexpected: yes\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.00424226,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72263.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72263","rid":"SV-86887r3_rule","stig_id":"RHEL-07-040450","fix_id":"F-78617r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon performs strict mode checking of home directory\nconfiguration files.","waiver_data":{}},{"code":"control \"V-72265\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon uses privilege separation.\"\n desc \"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon performs privilege separation.\n\n Check that the SSH daemon performs privilege separation with the following\ncommand:\n\n # grep -i usepriv /etc/ssh/sshd_config\n\n UsePrivilegeSeparation sandbox\n\n If the \\\"UsePrivilegeSeparation\\\" keyword is set to \\\"no\\\", is missing, or\nthe returned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"UsePrivilegeSeparation\\\" keyword in\n\\\"/etc/ssh/sshd_config\\\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \\\"sandbox\\\" or \\\"yes\\\":\n\n UsePrivilegeSeparation sandbox\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72265\"\n tag rid: \"SV-86889r3_rule\"\n tag stig_id: \"RHEL-07-040460\"\n tag fix_id: \"F-78619r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe sshd_config do\n its('UsePrivilegeSeparation') { should cmp 'sandbox' }\n end\n describe sshd_config do\n its('UsePrivilegeSeparation') { should cmp 'yes' }\n end\n end\nend\n","desc":"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.","descriptions":[{"data":"SSH daemon privilege separation causes the SSH process to drop root\nprivileges when not needed, which would decrease the impact of software\nvulnerabilities in the unprivileged section.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs privilege separation.\n\n Check that the SSH daemon performs privilege separation with the following\ncommand:\n\n # grep -i usepriv /etc/ssh/sshd_config\n\n UsePrivilegeSeparation sandbox\n\n If the \"UsePrivilegeSeparation\" keyword is set to \"no\", is missing, or\nthe returned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"UsePrivilegeSeparation\" keyword in\n\"/etc/ssh/sshd_config\" (this file may be named differently or be in a\ndifferent location if using a version of SSH that is provided by a third-party\nvendor) and set the value to \"sandbox\" or \"yes\":\n\n UsePrivilegeSeparation sandbox\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72265","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration UsePrivilegeSeparation is expected to cmp == \"sandbox\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: sandbox\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.001211588,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"},{"code_desc":"SSHD Configuration UsePrivilegeSeparation is expected to cmp == \"yes\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: yes\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.000423369,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72265.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72265","rid":"SV-86889r3_rule","stig_id":"RHEL-07-040460","fix_id":"F-78619r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon uses privilege separation.","waiver_data":{}},{"code":"control \"V-72267\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow compression or only allows compression after\nsuccessful authentication.\"\n desc \"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the SSH daemon performs compression after a user successfully\nauthenticates.\n\n Check that the SSH daemon performs compression after a user successfully\nauthenticates with the following command:\n\n # grep -i compression /etc/ssh/sshd_config\n Compression delayed\n\n If the \\\"Compression\\\" keyword is set to \\\"yes\\\", is missing, or the\nreturned line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Uncomment the \\\"Compression\\\" keyword in \\\"/etc/ssh/sshd_config\\\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) on the system and set the\nvalue to \\\"delayed\\\" or \\\"no\\\":\n\n Compression no\n\n The SSH service must be restarted for changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72267\"\n tag rid: \"SV-86891r3_rule\"\n tag stig_id: \"RHEL-07-040470\"\n tag fix_id: \"F-78621r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe sshd_config do\n its('Compression') { should cmp 'delayed' }\n end\n describe sshd_config do\n its('Compression') { should cmp 'no' }\n end\n end\nend\n","desc":"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.","descriptions":[{"data":"If compression is allowed in an SSH connection prior to\nauthentication, vulnerabilities in the compression software could result in\ncompromise of the system from an unauthenticated connection, potentially with\nroot privileges.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the SSH daemon performs compression after a user successfully\nauthenticates.\n\n Check that the SSH daemon performs compression after a user successfully\nauthenticates with the following command:\n\n # grep -i compression /etc/ssh/sshd_config\n Compression delayed\n\n If the \"Compression\" keyword is set to \"yes\", is missing, or the\nreturned line is commented out, this is a finding.","label":"check"},{"data":"Uncomment the \"Compression\" keyword in \"/etc/ssh/sshd_config\" (this\nfile may be named differently or be in a different location if using a version\nof SSH that is provided by a third-party vendor) on the system and set the\nvalue to \"delayed\" or \"no\":\n\n Compression no\n\n The SSH service must be restarted for changes to take effect.","label":"fix"}],"id":"V-72267","impact":0.5,"refs":[],"results":[{"code_desc":"SSHD Configuration Compression is expected to cmp == \"delayed\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: delayed\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.000900016,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"},{"code_desc":"SSHD Configuration Compression is expected to cmp == \"no\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: no\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.000349587,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72267.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72267","rid":"SV-86891r3_rule","stig_id":"RHEL-07-040470","fix_id":"F-78621r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the SSH daemon does not allow compression or only allows compression after\nsuccessful authentication.","waiver_data":{}},{"code":"control \"V-72269\" do\n title \"The Red Hat Enterprise Linux operating system must, for networked\nsystems, synchronize clocks with a server that is synchronized to one of the\nredundant United States Naval Observatory (USNO) time servers, a time server\ndesignated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global\nPositioning System (GPS).\"\n desc \"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Check to see if NTP is running in continuous mode:\n\n # ps -ef | grep ntp\n\n If NTP is not running, check to see if \\\"chronyd\\\" is running in continuous\nmode:\n\n # ps -ef | grep chronyd\n\n If NTP or \\\"chronyd\\\" is not running, this is a finding.\n\n If the NTP process is found, then check the \\\"ntp.conf\\\" file for the\n\\\"maxpoll\\\" option setting:\n\n # grep maxpoll /etc/ntp.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is set to \\\"17\\\" or is not set, this is a finding.\n\n If the file does not exist, check the \\\"/etc/cron.daily\\\" subdirectory for\na crontab file controlling the execution of the \\\"ntpd -q\\\" command.\n\n # grep -i \\\"ntpd -q\\\" /etc/cron.daily/*\n # ls -al /etc/cron.* | grep ntp\n\n ntp\n\n If a crontab file does not exist in the \\\"/etc/cron.daily\\\" that executes\nthe \\\"ntpd -q\\\" command, this is a finding.\n\n If the \\\"chronyd\\\" process is found, then check the \\\"chrony.conf\\\" file\nfor the \\\"maxpoll\\\" option setting:\n\n # grep maxpoll /etc/chrony.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is not set or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the \\\"/etc/ntp.conf\\\" or \\\"/etc/chrony.conf\\\" file and add or update\nan entry to define \\\"maxpoll\\\" to \\\"10\\\" as follows:\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If NTP was running and \\\"maxpoll\\\" was updated, the NTP service must be\nrestarted:\n\n # systemctl restart ntpd\n\n If NTP was not running, it must be started:\n\n # systemctl start ntpd\n\n If \\\"chronyd\\\" was running and \\\"maxpoll\\\" was updated, the service must be\nrestarted:\n\n # systemctl restart chronyd.service\n\n If \\\"chronyd\\\" was not running, it must be started:\n\n # systemctl start chronyd.service\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000355-GPOS-00143\"\n tag satisfies: [\"SRG-OS-000355-GPOS-00143\", \"SRG-OS-000356-GPOS-00144\"]\n tag gid: \"V-72269\"\n tag rid: \"SV-86893r5_rule\"\n tag stig_id: \"RHEL-07-040500\"\n tag fix_id: \"F-78623r5_fix\"\n tag cci: [\"CCI-001891\", \"CCI-002046\"]\n tag nist: [\"AU-8 (1) (a)\", \"AU-8 (1) (b)\"]\n\n # Either ntpd or chronyd should be running\n describe.one do\n [service('ntpd'), service('chronyd')].each do |time_service|\n describe time_service do\n it { should be_running }\n it { should be_enabled }\n it { should be_installed }\n end\n end\n end\n\n if service('ntpd').installed?\n time_service = service('ntpd')\n time_sources = ntp_conf('/etc/ntp.conf').server\n max_poll_values = time_sources.map { |val| val.match?(/.*maxpoll.*/) ? val.gsub(/.*maxpoll\\s+(\\d+)(\\s+.*|$)/,'\\1').to_i : 99 }\n ntpdate_crons = command('grep -l \"ntpd -q\" /etc/cron.daily/*').stdout.strip.lines\n\n describe \"ntpd time sources list\" do\n subject { time_sources }\n it { should_not be_empty }\n end\n\n describe.one do\n # Case where maxpoll empty\n describe \"Daily cron jobs for 'ntpd -q'\" do\n subject { ntpdate_crons }\n it { should_not be_empty }\n end\n # All time sources must contain valid maxpoll entries\n describe \"ntpd maxpoll values (99=maxpoll absent)\" do\n subject { max_poll_values }\n it { should all be < 17 }\n end\n end\n end\n\n if service('chronyd').installed?\n time_service = service('chronyd')\n time_sources = ntp_conf('/etc/chrony.conf').server\n max_poll_values = time_sources.map { |val| val.match?(/.*maxpoll.*/) ? val.gsub(/.*maxpoll\\s+(\\d+)(\\s+.*|$)/,'\\1').to_i : 99 }\n\n describe \"chronyd time sources list\" do\n subject { time_sources }\n it { should_not be_empty }\n end\n \n # All time sources must contain valid maxpoll entries\n describe \"chronyd maxpoll values (99=maxpoll absent)\" do\n subject { max_poll_values }\n it { should all be < 17 }\n end\n end\nend\n","desc":"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).","descriptions":[{"data":"Inaccurate time stamps make it more difficult to correlate events and\ncan lead to an inaccurate analysis. Determining the correct time a particular\nevent occurred on a system is critical when conducting forensic analysis and\ninvestigating system events. Sources outside the configured acceptable\nallowance (drift) may be inaccurate.\n\n Synchronizing internal information system clocks provides uniformity of\ntime stamps for information systems with multiple system clocks and systems\nconnected over a network.\n\n Organizations should consider endpoints that may not have regular access to\nthe authoritative time server (e.g., mobile, teleworking, and tactical\nendpoints).","label":"default"},{"data":"","label":"rationale"},{"data":"Check to see if NTP is running in continuous mode:\n\n # ps -ef | grep ntp\n\n If NTP is not running, check to see if \"chronyd\" is running in continuous\nmode:\n\n # ps -ef | grep chronyd\n\n If NTP or \"chronyd\" is not running, this is a finding.\n\n If the NTP process is found, then check the \"ntp.conf\" file for the\n\"maxpoll\" option setting:\n\n # grep maxpoll /etc/ntp.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is set to \"17\" or is not set, this is a finding.\n\n If the file does not exist, check the \"/etc/cron.daily\" subdirectory for\na crontab file controlling the execution of the \"ntpd -q\" command.\n\n # grep -i \"ntpd -q\" /etc/cron.daily/*\n # ls -al /etc/cron.* | grep ntp\n\n ntp\n\n If a crontab file does not exist in the \"/etc/cron.daily\" that executes\nthe \"ntpd -q\" command, this is a finding.\n\n If the \"chronyd\" process is found, then check the \"chrony.conf\" file\nfor the \"maxpoll\" option setting:\n\n # grep maxpoll /etc/chrony.conf\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If the option is not set or the line is commented out, this is a finding.","label":"check"},{"data":"Edit the \"/etc/ntp.conf\" or \"/etc/chrony.conf\" file and add or update\nan entry to define \"maxpoll\" to \"10\" as follows:\n\n server 0.rhel.pool.ntp.org iburst maxpoll 10\n\n If NTP was running and \"maxpoll\" was updated, the NTP service must be\nrestarted:\n\n # systemctl restart ntpd\n\n If NTP was not running, it must be started:\n\n # systemctl start ntpd\n\n If \"chronyd\" was running and \"maxpoll\" was updated, the service must be\nrestarted:\n\n # systemctl restart chronyd.service\n\n If \"chronyd\" was not running, it must be started:\n\n # systemctl start chronyd.service","label":"fix"}],"id":"V-72269","impact":0.5,"refs":[],"results":[{"code_desc":"Service chronyd is expected to be running","run_time":0.000232991,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"service","resource_params":"[\"chronyd\"]"},{"code_desc":"Service chronyd is expected to be enabled","run_time":0.000165534,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"service","resource_params":"[\"chronyd\"]"},{"code_desc":"Service chronyd is expected to be installed","run_time":0.00018048,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"service","resource_params":"[\"chronyd\"]"},{"code_desc":"chronyd time sources list is expected not to be empty","run_time":0.011982066,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"chronyd maxpoll values (99=maxpoll absent) is expected to all be < 17","message":"expected [99, 99, 99, 99] to all be < 17\n\n object at index 0 failed to match:\n expected: < 17\n got: 99\n\n object at index 1 failed to match:\n expected: < 17\n got: 99\n\n object at index 2 failed to match:\n expected: < 17\n got: 99\n\n object at index 3 failed to match:\n expected: < 17\n got: 99","run_time":0.005858494,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72269.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000355-GPOS-00143","satisfies":["SRG-OS-000355-GPOS-00143","SRG-OS-000356-GPOS-00144"],"gid":"V-72269","rid":"SV-86893r5_rule","stig_id":"RHEL-07-040500","fix_id":"F-78623r5_fix","cci":["CCI-001891","CCI-002046"],"nist":["AU-8 (1) (a)","AU-8 (1) (b)"]},"title":"The Red Hat Enterprise Linux operating system must, for networked\nsystems, synchronize clocks with a server that is synchronized to one of the\nredundant United States Naval Observatory (USNO) time servers, a time server\ndesignated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global\nPositioning System (GPS).","waiver_data":{}},{"code":"control \"V-72273\" do\n title \"The Red Hat Enterprise Linux operating system must enable an\napplication firewall, if available.\"\n desc \"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system enabled an application firewall.\n\n Check to see if \\\"firewalld\\\" is installed with the following command:\n\n # yum list installed firewalld\n firewalld-0.3.9-11.el7.noarch.rpm\n\n If the \\\"firewalld\\\" package is not installed, ask the System Administrator\nif another firewall application (such as iptables) is installed.\n\n If an application firewall is not installed, this is a finding.\n\n Check to see if the firewall is loaded and active with the following\ncommand:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago\n\n If \\\"firewalld\\\" does not show a status of \\\"loaded\\\" and \\\"active\\\", this\nis a finding.\n\n Check the state of the firewall:\n\n # firewall-cmd --state\n running\n\n If \\\"firewalld\\\" does not show a state of \\\"running\\\", this is a finding.\n \"\n desc \"fix\", \"\n Ensure the operating system's application firewall is enabled.\n\n Install the \\\"firewalld\\\" package, if it is not on the system, with the\nfollowing command:\n\n # yum install firewalld\n\n Start the firewall via \\\"systemctl\\\" with the following command:\n\n # systemctl start firewalld\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag satisfies: [\"SRG-OS-000480-GPOS-00227\", \"SRG-OS-000480-GPOS-00231\",\n\"SRG-OS-000480-GPOS-00232\"]\n tag gid: \"V-72273\"\n tag rid: \"SV-86897r2_rule\"\n tag stig_id: \"RHEL-07-040520\"\n tag fix_id: \"F-78627r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe package('firewalld') do\n it { should be_installed }\n end\n describe package('iptables') do\n it { should be_installed }\n end\n end\n describe.one do\n describe systemd_service('firewalld.service') do\n it { should be_running }\n end\n\tdescribe systemd_service('iptables.service') do\n it { should be_running }\n end\n end\nend\n","desc":"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.","descriptions":[{"data":"Firewalls protect computers from network attacks by blocking or\nlimiting access to open network ports. Application firewalls limit which\napplications are allowed to communicate over the network.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system enabled an application firewall.\n\n Check to see if \"firewalld\" is installed with the following command:\n\n # yum list installed firewalld\n firewalld-0.3.9-11.el7.noarch.rpm\n\n If the \"firewalld\" package is not installed, ask the System Administrator\nif another firewall application (such as iptables) is installed.\n\n If an application firewall is not installed, this is a finding.\n\n Check to see if the firewall is loaded and active with the following\ncommand:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago\n\n If \"firewalld\" does not show a status of \"loaded\" and \"active\", this\nis a finding.\n\n Check the state of the firewall:\n\n # firewall-cmd --state\n running\n\n If \"firewalld\" does not show a state of \"running\", this is a finding.","label":"check"},{"data":"Ensure the operating system's application firewall is enabled.\n\n Install the \"firewalld\" package, if it is not on the system, with the\nfollowing command:\n\n # yum install firewalld\n\n Start the firewall via \"systemctl\" with the following command:\n\n # systemctl start firewalld","label":"fix"}],"id":"V-72273","impact":0.5,"refs":[],"results":[{"code_desc":"System Package firewalld is expected to be installed","run_time":0.000538232,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"package","resource_params":"[\"firewalld\"]"},{"code_desc":"System Package iptables is expected to be installed","run_time":0.001529886,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"package","resource_params":"[\"iptables\"]"},{"code_desc":"Service firewalld.service is expected to be running","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `Service firewalld.service` is running","run_time":0.001788582,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"systemd_service","resource_params":"[\"firewalld.service\"]"},{"code_desc":"Service iptables.service is expected to be running","exception":"RSpec::Core::MultipleExceptionError","message":"expected that `Service iptables.service` is running","run_time":0.000463229,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"systemd_service","resource_params":"[\"iptables.service\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72273.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","satisfies":["SRG-OS-000480-GPOS-00227","SRG-OS-000480-GPOS-00231","SRG-OS-000480-GPOS-00232"],"gid":"V-72273","rid":"SV-86897r2_rule","stig_id":"RHEL-07-040520","fix_id":"F-78627r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must enable an\napplication firewall, if available.","waiver_data":{}},{"code":"control \"V-72275\" do\n title \"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon logon.\"\n desc \"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify users are provided with feedback on when account accesses last\noccurred.\n\n Check that \\\"pam_lastlog\\\" is used and not silent with the following\ncommand:\n\n # grep pam_lastlog /etc/pam.d/postlogin\n session required pam_lastlog.so showfailed\n\n If \\\"pam_lastlog\\\" is missing from \\\"/etc/pam.d/postlogin\\\" file, or the\nsilent option is present, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to provide users with feedback on when\naccount accesses last occurred by setting the required configuration options in\n\\\"/etc/pam.d/postlogin\\\".\n\n Add the following line to the top of \\\"/etc/pam.d/postlogin\\\":\n\n session required pam_lastlog.so showfailed\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72275\"\n tag rid: \"SV-86899r4_rule\"\n tag stig_id: \"RHEL-07-040530\"\n tag fix_id: \"F-78629r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe pam('/etc/pam.d/postlogin') do\n its('lines') { should match_pam_rule('session .* pam_lastlog.so showfailed') }\n end\n\n describe.one do\n describe sshd_config do\n its('PrintLastLog') { should cmp 'yes' }\n end\n\n describe pam('/etc/pam.d/postlogin') do\n its('lines') { should match_pam_rule('session .* pam_lastlog.so showfailed').all_without_args('silent') }\n end\n end\nend\n","desc":"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.","descriptions":[{"data":"Providing users with feedback on when account accesses last occurred\nfacilitates user recognition and reporting of unauthorized account use.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify users are provided with feedback on when account accesses last\noccurred.\n\n Check that \"pam_lastlog\" is used and not silent with the following\ncommand:\n\n # grep pam_lastlog /etc/pam.d/postlogin\n session required pam_lastlog.so showfailed\n\n If \"pam_lastlog\" is missing from \"/etc/pam.d/postlogin\" file, or the\nsilent option is present, this is a finding.","label":"check"},{"data":"Configure the operating system to provide users with feedback on when\naccount accesses last occurred by setting the required configuration options in\n\"/etc/pam.d/postlogin\".\n\n Add the following line to the top of \"/etc/pam.d/postlogin\":\n\n session required pam_lastlog.so showfailed","label":"fix"}],"id":"V-72275","impact":0.3,"refs":[],"results":[{"code_desc":"PAM Config[/etc/pam.d/postlogin] lines is expected to include session .* pam_lastlog.so showfailed","run_time":0.001450363,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/postlogin\"]"},{"code_desc":"SSHD Configuration PrintLastLog is expected to cmp == \"yes\"","exception":"RSpec::Core::MultipleExceptionError","message":"\nexpected: yes\n got: \n\n(compared using `cmp` matcher)\n","run_time":0.000515919,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"sshd_config","resource_params":"[]"},{"code_desc":"PAM Config[/etc/pam.d/postlogin] lines is expected to include session .* pam_lastlog.so showfailed, all without args silent","exception":"RSpec::Core::MultipleExceptionError","message":"expected \"session [default=1] pam_lastlog.so nowtmp showfailed\\nsession optional pam_lastlog.so silent noupdate showfailed\" to include session .* pam_lastlog.so showfailed, all without args silent\nDiff:\n@@ -1,2 +1,3 @@\n-session .* pam_lastlog.so showfailed\n+session [default=1] pam_lastlog.so nowtmp showfailed\n+session optional pam_lastlog.so silent noupdate showfailed\n","run_time":0.001597913,"start_time":"2022-03-06T22:06:07+00:00","status":"failed","resource_class":"pam","resource_params":"[\"/etc/pam.d/postlogin\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72275.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72275","rid":"SV-86899r4_rule","stig_id":"RHEL-07-040530","fix_id":"F-78629r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must display the date\nand time of the last successful account logon upon logon.","waiver_data":{}},{"code":"control \"V-72277\" do\n title \"The Red Hat Enterprise Linux operating system must not contain .shosts\nfiles.\"\n desc \"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify there are no \\\".shosts\\\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name '*.shosts'\n\n If any \\\".shosts\\\" files are found on the system, this is a finding.\n \"\n desc \"fix\", \"\n Remove any found \\\".shosts\\\" files from the system.\n\n # rm /[path]/[to]/[file]/.shosts\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72277\"\n tag rid: \"SV-86901r2_rule\"\n tag stig_id: \"RHEL-07-040540\"\n tag fix_id: \"F-78631r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe command(\"find / -xdev -xautofs -name '*.shosts'\") do\n its('stdout.strip') { should be_empty }\n end\nend\n","desc":"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.","descriptions":[{"data":"The .shosts files are used to configure host-based authentication for\nindividual users or the system via SSH. Host-based authentication is not\nsufficient for preventing unauthorized access to the system, as it does not\nrequire interactive identification and authentication of a connection request,\nor for the use of two-factor authentication.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify there are no \".shosts\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name '*.shosts'\n\n If any \".shosts\" files are found on the system, this is a finding.","label":"check"},{"data":"Remove any found \".shosts\" files from the system.\n\n# rm /[path]/[to]/[file]/.shosts","label":"fix"}],"id":"V-72277","impact":0.7,"refs":[],"results":[{"code_desc":"Command: `find / -xdev -xautofs -name '*.shosts'` stdout.strip is expected to be empty","run_time":0.920624493,"start_time":"2022-03-06T22:06:07+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -name '*.shosts'\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72277.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72277","rid":"SV-86901r2_rule","stig_id":"RHEL-07-040540","fix_id":"F-78631r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not contain .shosts\nfiles.","waiver_data":{}},{"code":"control \"V-72279\" do\n title \"The Red Hat Enterprise Linux operating system must not contain\nshosts.equiv files.\"\n desc \"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify there are no \\\"shosts.equiv\\\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name shosts.equiv\n\n If any \\\"shosts.equiv\\\" files are found on the system, this is a finding.\n \"\n desc \"fix\", \"\n Remove any found \\\"shosts.equiv\\\" files from the system.\n\n # rm /[path]/[to]/[file]/shosts.equiv\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72279\"\n tag rid: \"SV-86903r2_rule\"\n tag stig_id: \"RHEL-07-040550\"\n tag fix_id: \"F-78633r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe command('find / -xdev -xautofs -name shosts.equiv') do\n its('stdout.strip') { should be_empty }\n end\nend\n","desc":"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.","descriptions":[{"data":"The shosts.equiv files are used to configure host-based authentication\nfor the system via SSH. Host-based authentication is not sufficient for\npreventing unauthorized access to the system, as it does not require\ninteractive identification and authentication of a connection request, or for\nthe use of two-factor authentication.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify there are no \"shosts.equiv\" files on the system.\n\n Check the system for the existence of these files with the following\ncommand:\n\n # find / -name shosts.equiv\n\n If any \"shosts.equiv\" files are found on the system, this is a finding.","label":"check"},{"data":"Remove any found \"shosts.equiv\" files from the system.\n\n# rm /[path]/[to]/[file]/shosts.equiv","label":"fix"}],"id":"V-72279","impact":0.7,"refs":[],"results":[{"code_desc":"Command: `find / -xdev -xautofs -name shosts.equiv` stdout.strip is expected to be empty","run_time":0.840532817,"start_time":"2022-03-06T22:06:08+00:00","status":"passed","resource_class":"command","resource_params":"[\"find / -xdev -xautofs -name shosts.equiv\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72279.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72279","rid":"SV-86903r2_rule","stig_id":"RHEL-07-040550","fix_id":"F-78633r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not contain\nshosts.equiv files.","waiver_data":{}},{"code":"control \"V-72281\" do\n title \"For Red Hat Enterprise Linux operating systems using DNS resolution,\nat least two name servers must be configured.\"\n desc \"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Determine whether the system is using local or DNS name resolution with the\nfollowing command:\n\n # grep hosts /etc/nsswitch.conf\n hosts: files dns\n\n If the DNS entry is missing from the host's line in the\n\\\"/etc/nsswitch.conf\\\" file, the \\\"/etc/resolv.conf\\\" file must be empty.\n\n Verify the \\\"/etc/resolv.conf\\\" file is empty with the following command:\n\n # ls -al /etc/resolv.conf\n -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf\n\n If local host authentication is being used and the \\\"/etc/resolv.conf\\\"\nfile is not empty, this is a finding.\n\n If the DNS entry is found on the host's line of the \\\"/etc/nsswitch.conf\\\"\nfile, verify the operating system is configured to use two or more name servers\nfor DNS resolution.\n\n Determine the name servers used by the system with the following command:\n\n # grep nameserver /etc/resolv.conf\n nameserver 192.168.1.2\n nameserver 192.168.1.3\n\n If less than two lines are returned that are not commented out, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to use two or more name servers for DNS\nresolution.\n\n Edit the \\\"/etc/resolv.conf\\\" file to uncomment or add the two or more\n\\\"nameserver\\\" option lines with the IP address of local authoritative name\nservers. If local host resolution is being performed, the \\\"/etc/resolv.conf\\\"\nfile must be empty. An empty \\\"/etc/resolv.conf\\\" file can be created as\nfollows:\n\n # echo -n > /etc/resolv.conf\n\n And then make the file immutable with the following command:\n\n # chattr +i /etc/resolv.conf\n\n If the \\\"/etc/resolv.conf\\\" file must be mutable, the required\nconfiguration must be documented with the Information System Security Officer\n(ISSO) and the file must be verified by the system file integrity tool.\n \"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72281\"\n tag rid: \"SV-86905r2_rule\"\n tag stig_id: \"RHEL-07-040600\"\n tag fix_id: \"F-78635r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n dns_in_host_line = parse_config_file(\"/etc/nsswitch.conf\",\n {\n comment_char: '#',\n assignment_regex: /^\\s*([^:]*?)\\s*:\\s*(.*?)\\s*$/,\n }\n ).params['hosts'].include?('dns')\n\n describe \"If `local` resolution is being used, a `hosts` entry in /etc/nsswitch.conf having `dns`\" do\n subject { dns_in_host_line }\n it { should be false }\n end if !dns_in_host_line\n\n describe \"If `local` resoultion is being used, the /etc/resolv.conf file should\" do\n subject { parse_config_file(\"/etc/resolv.conf\", { comment_char: '#'}).params }\n it { should be_empty }\n end if !dns_in_host_line\n\n nameservers = parse_config_file(\"/etc/resolv.conf\",\n { comment_char: '#'}\n ).params.keys.grep(/nameserver/)\n\n describe \"The system's nameservers: #{nameservers}\" do\n subject { nameservers }\n it { should_not be nil }\n end if dns_in_host_line\n\n describe \"The number of nameservers\" do\n subject { nameservers.count }\n it { should cmp >= 2 }\n end if dns_in_host_line\nend\n","desc":"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.","descriptions":[{"data":"To provide availability for name resolution services, multiple\nredundant name servers are mandated. A failure in name resolution could lead to\nthe failure of security functions requiring name resolution, which may include\ntime synchronization, centralized authentication, and remote system logging.","label":"default"},{"data":"","label":"rationale"},{"data":"Determine whether the system is using local or DNS name resolution with the\nfollowing command:\n\n # grep hosts /etc/nsswitch.conf\n hosts: files dns\n\n If the DNS entry is missing from the host's line in the\n\"/etc/nsswitch.conf\" file, the \"/etc/resolv.conf\" file must be empty.\n\n Verify the \"/etc/resolv.conf\" file is empty with the following command:\n\n # ls -al /etc/resolv.conf\n -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf\n\n If local host authentication is being used and the \"/etc/resolv.conf\"\nfile is not empty, this is a finding.\n\n If the DNS entry is found on the host's line of the \"/etc/nsswitch.conf\"\nfile, verify the operating system is configured to use two or more name servers\nfor DNS resolution.\n\n Determine the name servers used by the system with the following command:\n\n # grep nameserver /etc/resolv.conf\n nameserver 192.168.1.2\n nameserver 192.168.1.3\n\n If less than two lines are returned that are not commented out, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to use two or more name servers for DNS\nresolution.\n\n Edit the \"/etc/resolv.conf\" file to uncomment or add the two or more\n\"nameserver\" option lines with the IP address of local authoritative name\nservers. If local host resolution is being performed, the \"/etc/resolv.conf\"\nfile must be empty. An empty \"/etc/resolv.conf\" file can be created as\nfollows:\n\n # echo -n > /etc/resolv.conf\n\n And then make the file immutable with the following command:\n\n # chattr +i /etc/resolv.conf\n\n If the \"/etc/resolv.conf\" file must be mutable, the required\nconfiguration must be documented with the Information System Security Officer\n(ISSO) and the file must be verified by the system file integrity tool.","label":"fix"}],"id":"V-72281","impact":0.3,"refs":[],"results":[{"code_desc":"The system's nameservers: [\"nameserver 192.168.1.1\", \"nameserver 10.0.2.3\"] is expected not to equal nil","run_time":0.000248259,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The number of nameservers is expected to cmp >= 2","run_time":0.000218516,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72281.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72281","rid":"SV-86905r2_rule","stig_id":"RHEL-07-040600","fix_id":"F-78635r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"For Red Hat Enterprise Linux operating systems using DNS resolution,\nat least two name servers must be configured.","waiver_data":{}},{"code":"control \"V-72283\" do\n title \"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets.\"\n desc \"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not accept IPv4 source-routed packets.\n\n # grep net.ipv4.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv4.conf.all.accept_source_route = 0\n\n If \\\" net.ipv4.conf.all.accept_source_route \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.accept_source_route\n net.ipv4.conf.all.accept_source_route = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl -system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72283\"\n tag rid: \"SV-86907r2_rule\"\n tag stig_id: \"RHEL-07-040610\"\n tag fix_id: \"F-78637r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.accept_source_route') do\n its('value') { should eq 0 }\n end\nend\n","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not accept IPv4 source-routed packets.\n\n # grep net.ipv4.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv4.conf.all.accept_source_route = 0\n\n If \" net.ipv4.conf.all.accept_source_route \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.accept_source_route\n net.ipv4.conf.all.accept_source_route = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl -system","label":"fix"}],"id":"V-72283","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.all.accept_source_route value is expected to eq 0","run_time":0.029385511,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.all.accept_source_route\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72283.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72283","rid":"SV-86907r2_rule","stig_id":"RHEL-07-040610","fix_id":"F-78637r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets.","waiver_data":{}},{"code":"control \"V-72285\" do\n title \"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets by default.\"\n desc \"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not accept IPv4 source-routed packets by default.\n\n # grep net.ipv4.conf.default.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n net.ipv4.conf.default.accept_source_route = 0\n\n If \\\" net.ipv4.conf.default.accept_source_route \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.accept_source_route\n net.ipv4.conf.default.accept_source_route = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72285\"\n tag rid: \"SV-86909r2_rule\"\n tag stig_id: \"RHEL-07-040620\"\n tag fix_id: \"F-78639r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.accept_source_route') do\n its('value') { should eq 0 }\n end\nend\n","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv4\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not accept IPv4 source-routed packets by default.\n\n # grep net.ipv4.conf.default.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n net.ipv4.conf.default.accept_source_route = 0\n\n If \" net.ipv4.conf.default.accept_source_route \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.accept_source_route\n net.ipv4.conf.default.accept_source_route = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72285","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.default.accept_source_route value is expected to eq 0","run_time":0.033643594,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.default.accept_source_route\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72285.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72285","rid":"SV-86909r2_rule","stig_id":"RHEL-07-040620","fix_id":"F-78639r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward\nInternet Protocol version 4 (IPv4) source-routed packets by default.","waiver_data":{}},{"code":"control \"V-72287\" do\n title \"The Red Hat Enterprise Linux operating system must not respond to\nInternet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP)\nechoes sent to a broadcast address.\"\n desc \"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast\naddress.\n\n # grep net.ipv4.icmp_echo_ignore_broadcasts /etc/sysctl.conf /etc/sysctl.d/*\n\n If \\\" net.ipv4.icmp_echo_ignore_broadcasts\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"1\\\", this is a finding.\n\n Check that the operating system implements the\n\\\"icmp_echo_ignore_broadcasts\\\" variable with the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.icmp_echo_ignore_broadcasts\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n If the returned line does not have a value of \\\"1\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72287\"\n tag rid: \"SV-86911r2_rule\"\n tag stig_id: \"RHEL-07-040630\"\n tag fix_id: \"F-78641r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.icmp_echo_ignore_broadcasts') do\n its('value') { should eq 1 }\n end\nend\n","desc":"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.","descriptions":[{"data":"Responding to broadcast (ICMP) echoes facilitates network mapping and\nprovides a vector for amplification attacks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast\naddress.\n\n # grep net.ipv4.icmp_echo_ignore_broadcasts /etc/sysctl.conf /etc/sysctl.d/*\n\n If \" net.ipv4.icmp_echo_ignore_broadcasts\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the\n\"icmp_echo_ignore_broadcasts\" variable with the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.icmp_echo_ignore_broadcasts\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.icmp_echo_ignore_broadcasts = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72287","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.icmp_echo_ignore_broadcasts value is expected to eq 1","run_time":0.077302277,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.icmp_echo_ignore_broadcasts\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72287.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72287","rid":"SV-86911r2_rule","stig_id":"RHEL-07-040630","fix_id":"F-78641r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not respond to\nInternet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP)\nechoes sent to a broadcast address.","waiver_data":{}},{"code":"control \"V-72289\" do\n title \"The Red Hat Enterprise Linux operating system must prevent Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages from being accepted.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system will not accept IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.default.accept_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \\\" net.ipv4.conf.default.accept_redirects \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the value of the\n\\\"accept_redirects\\\" variables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.accept_redirects'\n net.ipv4.conf.default.accept_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to not accept IPv4 ICMP redirect messages by adding the\nfollowing line to \\\"/etc/sysctl.conf\\\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72289\"\n tag rid: \"SV-86913r3_rule\"\n tag stig_id: \"RHEL-07-040640\"\n tag fix_id: \"F-78643r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.accept_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system will not accept IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.default.accept_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \" net.ipv4.conf.default.accept_redirects \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the value of the\n\"accept_redirects\" variables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.accept_redirects'\n net.ipv4.conf.default.accept_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to not accept IPv4 ICMP redirect messages by adding the\nfollowing line to \"/etc/sysctl.conf\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.default.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72289","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.default.accept_redirects value is expected to eq 0","message":"\nexpected: 0\n got: 1\n\n(compared using ==)\n","run_time":0.055365349,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.default.accept_redirects\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72289.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72289","rid":"SV-86913r3_rule","stig_id":"RHEL-07-040640","fix_id":"F-78643r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages from being accepted.","waiver_data":{}},{"code":"control \"V-72291\" do\n title \"The Red Hat Enterprise Linux operating system must not allow\ninterfaces to perform Internet Protocol version 4 (IPv4) Internet Control\nMessage Protocol (ICMP) redirects by default.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n # grep 'net.ipv4.conf.default.send_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \\\"net.ipv4.conf.default.send_redirects\\\" is not configured in the\n\\\"/etc/sysctl.conf\\\" file or in the /etc/sysctl.d/ directory, is commented out\nor does not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the \\\"default send_redirects\\\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.send_redirects'\n\n net.ipv4.conf.default.send_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72291\"\n tag rid: \"SV-86915r4_rule\"\n tag stig_id: \"RHEL-07-040650\"\n tag fix_id: \"F-78645r4_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.send_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n # grep 'net.ipv4.conf.default.send_redirects' /etc/sysctl.conf\n/etc/sysctl.d/*\n\n If \"net.ipv4.conf.default.send_redirects\" is not configured in the\n\"/etc/sysctl.conf\" file or in the /etc/sysctl.d/ directory, is commented out\nor does not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"default send_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.default.send_redirects'\n\n net.ipv4.conf.default.send_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Configure the system to not allow interfaces to perform IPv4 ICMP redirects\nby default.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72291","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.default.send_redirects value is expected to eq 0","message":"\nexpected: 0\n got: 1\n\n(compared using ==)\n","run_time":0.03562178,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.default.send_redirects\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72291.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72291","rid":"SV-86915r4_rule","stig_id":"RHEL-07-040650","fix_id":"F-78645r4_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not allow\ninterfaces to perform Internet Protocol version 4 (IPv4) Internet Control\nMessage Protocol (ICMP) redirects by default.","waiver_data":{}},{"code":"control \"V-72293\" do\n title \"The Red Hat Enterprise Linux operating system must not send Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not send IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.send_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \\\"net.ipv4.conf.all.send_redirects\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the \\\"all send_redirects\\\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.send_redirects'\n\n net.ipv4.conf.all.send_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to not allow interfaces to perform IPv4 ICMP\nredirects.\n\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72293\"\n tag rid: \"SV-86917r3_rule\"\n tag stig_id: \"RHEL-07-040660\"\n tag fix_id: \"F-78647r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.send_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages contain\ninformation from the system's route table, possibly revealing portions of the\nnetwork topology.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not send IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.send_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \"net.ipv4.conf.all.send_redirects\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"all send_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.send_redirects'\n\n net.ipv4.conf.all.send_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Configure the system to not allow interfaces to perform IPv4 ICMP\nredirects.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.send_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72293","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.all.send_redirects value is expected to eq 0","message":"\nexpected: 0\n got: 1\n\n(compared using ==)\n","run_time":0.062413235,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.all.send_redirects\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72293.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72293","rid":"SV-86917r3_rule","stig_id":"RHEL-07-040660","fix_id":"F-78647r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not send Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.","waiver_data":{}},{"code":"control \"V-72295\" do\n title \"Network interfaces configured on the Red Hat Enterprise Linux\noperating system must not be in promiscuous mode.\"\n desc \"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify network interfaces are not in promiscuous mode unless approved by\nthe ISSO and documented.\n\n Check for the status with the following command:\n\n # ip link | grep -i promisc\n\n If network interfaces are found on the system in promiscuous mode and their\nuse has not been approved by the ISSO and documented, this is a finding.\n \"\n desc \"fix\", \"\n Configure network interfaces to turn off promiscuous mode unless approved\nby the ISSO and documented.\n\n Set the promiscuous mode of an interface to off with the following command:\n\n #ip link set dev multicast off promisc off\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72295\"\n tag rid: \"SV-86919r2_rule\"\n tag stig_id: \"RHEL-07-040670\"\n tag fix_id: \"F-78649r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe command(\"ip link | grep -i promisc\") do\n its('stdout.strip') { should match %r{^$} }\n end\nend\n","desc":"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.","descriptions":[{"data":"Network interfaces in promiscuous mode allow for the capture of all\nnetwork traffic visible to the system. If unauthorized individuals can access\nthese applications, it may allow then to collect information such as logon IDs,\npasswords, and key exchanges between systems.\n\n If the system is being used to perform a network troubleshooting function,\nthe use of these tools must be documented with the Information System Security\nOfficer (ISSO) and restricted to only authorized personnel.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify network interfaces are not in promiscuous mode unless approved by\nthe ISSO and documented.\n\n Check for the status with the following command:\n\n # ip link | grep -i promisc\n\n If network interfaces are found on the system in promiscuous mode and their\nuse has not been approved by the ISSO and documented, this is a finding.","label":"check"},{"data":"Configure network interfaces to turn off promiscuous mode unless approved\nby the ISSO and documented.\n\n Set the promiscuous mode of an interface to off with the following command:\n\n #ip link set dev multicast off promisc off","label":"fix"}],"id":"V-72295","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `ip link | grep -i promisc` stdout.strip is expected to match /^$/","run_time":0.028987496,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"command","resource_params":"[\"ip link | grep -i promisc\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72295.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72295","rid":"SV-86919r2_rule","stig_id":"RHEL-07-040670","fix_id":"F-78649r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"Network interfaces configured on the Red Hat Enterprise Linux\noperating system must not be in promiscuous mode.","waiver_data":{}},{"code":"control \"V-72297\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nprevent unrestricted mail relaying.\"\n desc \"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system is configured to prevent unrestricted mail relaying.\n\n Determine if \\\"postfix\\\" is installed with the following commands:\n\n # yum list installed postfix\n postfix-2.6.6-6.el7.x86_64.rpm\n\n If postfix is not installed, this is Not Applicable.\n\n If postfix is installed, determine if it is configured to reject\nconnections from unknown or untrusted networks with the following command:\n\n # postconf -n smtpd_client_restrictions\n smtpd_client_restrictions = permit_mynetworks, reject\n\n If the \\\"smtpd_client_restrictions\\\" parameter contains any entries other\nthan \\\"permit_mynetworks\\\" and \\\"reject\\\", this is a finding.\n \"\n desc \"fix\", \"\n If \\\"postfix\\\" is installed, modify the \\\"/etc/postfix/main.cf\\\" file to\nrestrict client connections to the local network with the following command:\n\n # postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72297\"\n tag rid: \"SV-86921r3_rule\"\n tag stig_id: \"RHEL-07-040680\"\n tag fix_id: \"F-78651r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n # Only permit_mynetworks and reject should be allowed\n describe.one do\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+permit_mynetworks,\\s*reject\\s*$} }\n end\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+permit_mynetworks\\s*$} }\n end\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+reject\\s*$} }\n end\n describe command('postconf -n smtpd_client_restrictions') do\n its('stdout.strip') { should match %r{^smtpd_client_restrictions\\s+=\\s+reject,\\s*permit_mynetworks\\s*$} }\n end\n end if package('postfix').installed?\n\n describe \"The `postfix` package is not installed\" do\n skip \"The `postfix` package is not installed, this control is Not Applicable\"\n end if !package('postfix').installed?\nend\n","desc":"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.","descriptions":[{"data":"If unrestricted mail relaying is permitted, unauthorized senders could\nuse this host as a mail relay for the purpose of sending spam or other\nunauthorized activity.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is configured to prevent unrestricted mail relaying.\n\n Determine if \"postfix\" is installed with the following commands:\n\n # yum list installed postfix\n postfix-2.6.6-6.el7.x86_64.rpm\n\n If postfix is not installed, this is Not Applicable.\n\n If postfix is installed, determine if it is configured to reject\nconnections from unknown or untrusted networks with the following command:\n\n # postconf -n smtpd_client_restrictions\n smtpd_client_restrictions = permit_mynetworks, reject\n\n If the \"smtpd_client_restrictions\" parameter contains any entries other\nthan \"permit_mynetworks\" and \"reject\", this is a finding.","label":"check"},{"data":"If \"postfix\" is installed, modify the \"/etc/postfix/main.cf\" file to\nrestrict client connections to the local network with the following command:\n\n # postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'","label":"fix"}],"id":"V-72297","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `postconf -n smtpd_client_restrictions` stdout.strip is expected to match /^smtpd_client_restrictions\\s+=\\s+permit_mynetworks,\\s*reject\\s*$/","exception":"RSpec::Core::MultipleExceptionError","message":"expected \"\" to match /^smtpd_client_restrictions\\s+=\\s+permit_mynetworks,\\s*reject\\s*$/\nDiff:\n@@ -1,2 +1,2 @@\n-/^smtpd_client_restrictions\\s+=\\s+permit_mynetworks,\\s*reject\\s*$/\n+\"\"\n","run_time":0.000580248,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"command","resource_params":"[\"postconf -n smtpd_client_restrictions\"]"},{"code_desc":"Command: `postconf -n smtpd_client_restrictions` stdout.strip is expected to match /^smtpd_client_restrictions\\s+=\\s+permit_mynetworks\\s*$/","exception":"RSpec::Core::MultipleExceptionError","message":"expected \"\" to match /^smtpd_client_restrictions\\s+=\\s+permit_mynetworks\\s*$/\nDiff:\n@@ -1,2 +1,2 @@\n-/^smtpd_client_restrictions\\s+=\\s+permit_mynetworks\\s*$/\n+\"\"\n","run_time":0.000412446,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"command","resource_params":"[\"postconf -n smtpd_client_restrictions\"]"},{"code_desc":"Command: `postconf -n smtpd_client_restrictions` stdout.strip is expected to match /^smtpd_client_restrictions\\s+=\\s+reject\\s*$/","exception":"RSpec::Core::MultipleExceptionError","message":"expected \"\" to match /^smtpd_client_restrictions\\s+=\\s+reject\\s*$/\nDiff:\n@@ -1,2 +1,2 @@\n-/^smtpd_client_restrictions\\s+=\\s+reject\\s*$/\n+\"\"\n","run_time":0.000845505,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"command","resource_params":"[\"postconf -n smtpd_client_restrictions\"]"},{"code_desc":"Command: `postconf -n smtpd_client_restrictions` stdout.strip is expected to match /^smtpd_client_restrictions\\s+=\\s+reject,\\s*permit_mynetworks\\s*$/","exception":"RSpec::Core::MultipleExceptionError","message":"expected \"\" to match /^smtpd_client_restrictions\\s+=\\s+reject,\\s*permit_mynetworks\\s*$/\nDiff:\n@@ -1,2 +1,2 @@\n-/^smtpd_client_restrictions\\s+=\\s+reject,\\s*permit_mynetworks\\s*$/\n+\"\"\n","run_time":0.000461704,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"command","resource_params":"[\"postconf -n smtpd_client_restrictions\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72297.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72297","rid":"SV-86921r3_rule","stig_id":"RHEL-07-040680","fix_id":"F-78651r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nprevent unrestricted mail relaying.","waiver_data":{}},{"code":"control \"V-72299\" do\n title \"The Red Hat Enterprise Linux operating system must not have a File\nTransfer Protocol (FTP) server package installed unless needed.\"\n desc \"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify an FTP server has not been installed on the system.\n\n Check to see if an FTP server has been installed with the following\ncommands:\n\n # yum list installed vsftpd\n\n vsftpd-3.0.2.el7.x86_64.rpm\n\n If \\\"vsftpd\\\" is installed and is not documented with the Information\nSystem Security Officer (ISSO) as an operational requirement, this is a finding.\n \"\n desc \"fix\", \"\n Document the \\\"vsftpd\\\" package with the ISSO as an operational requirement\nor remove it from the system with the following command:\n\n # yum remove vsftpd\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72299\"\n tag rid: \"SV-86923r3_rule\"\n tag stig_id: \"RHEL-07-040690\"\n tag fix_id: \"F-78653r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe package('vsftpd') do\n it { should_not be_installed }\n end\n describe parse_config_file('/etc/vsftpd/vsftpd.conf') do\n its('ssl_enable') { should cmp 'YES' }\n its('force_anon_data_ssl') { should cmp 'YES' }\n its('force_anon_logins_ssl') { should cmp 'YES' }\n its('force_local_data_ssl') { should cmp 'YES' }\n its('force_local_logins_ssl') { should cmp 'YES' }\n end\n end\nend\n","desc":"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.","descriptions":[{"data":"The FTP service provides an unencrypted remote access that does not\nprovide for the confidentiality and integrity of user passwords or the remote\nsession. If a privileged user were to log on using this service, the privileged\nuser password could be compromised. SSH or other encrypted file transfer\nmethods must be used in place of this service.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify an FTP server has not been installed on the system.\n\n Check to see if an FTP server has been installed with the following\ncommands:\n\n # yum list installed vsftpd\n\n vsftpd-3.0.2.el7.x86_64.rpm\n\n If \"vsftpd\" is installed and is not documented with the Information\nSystem Security Officer (ISSO) as an operational requirement, this is a finding.","label":"check"},{"data":"Document the \"vsftpd\" package with the ISSO as an operational requirement\nor remove it from the system with the following command:\n\n # yum remove vsftpd","label":"fix"}],"id":"V-72299","impact":0.7,"refs":[],"results":[{"code_desc":"System Package vsftpd is expected not to be installed","run_time":0.000872752,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"package","resource_params":"[\"vsftpd\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72299.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72299","rid":"SV-86923r3_rule","stig_id":"RHEL-07-040690","fix_id":"F-78653r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have a File\nTransfer Protocol (FTP) server package installed unless needed.","waiver_data":{}},{"code":"control \"V-72301\" do\n title \"The Red Hat Enterprise Linux operating system must not have the\nTrivial File Transfer Protocol (TFTP) server package installed if not required\nfor operational support.\"\n desc \"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify a TFTP server has not been installed on the system.\n\n Check to see if a TFTP server has been installed with the following command:\n\n # yum list installed tftp-server\n tftp-server-0.49-9.el7.x86_64.rpm\n\n If TFTP is installed and the requirement for TFTP is not documented with\nthe ISSO, this is a finding.\n \"\n desc \"fix\", \"\n Remove the TFTP package from the system with the following command:\n\n # yum remove tftp-server\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72301\"\n tag rid: \"SV-86925r2_rule\"\n tag stig_id: \"RHEL-07-040700\"\n tag fix_id: \"F-78655r2_fix\"\n tag cci: [\"CCI-000318\", \"CCI-000368\", \"CCI-001812\", \"CCI-001813\",\n\"CCI-001814\"]\n tag nist: [\"CM-3 f\", \"CM-6 c\", \"CM-11 (2)\", \"CM-5 (1)\", \"CM-5 (1)\"]\n\n describe package('tftp-server') do\n it { should_not be_installed }\n end\nend\n","desc":"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.","descriptions":[{"data":"If TFTP is required for operational support (such as the transmission\nof router configurations) its use must be documented with the Information\nSystem Security Officer (ISSO), restricted to only authorized personnel, and\nhave access control rules established.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify a TFTP server has not been installed on the system.\n\n Check to see if a TFTP server has been installed with the following command:\n\n # yum list installed tftp-server\n tftp-server-0.49-9.el7.x86_64.rpm\n\n If TFTP is installed and the requirement for TFTP is not documented with\nthe ISSO, this is a finding.","label":"check"},{"data":"Remove the TFTP package from the system with the following command:\n\n# yum remove tftp-server","label":"fix"}],"id":"V-72301","impact":0.7,"refs":[],"results":[{"code_desc":"System Package tftp-server is expected not to be installed","run_time":0.000296599,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"package","resource_params":"[\"tftp-server\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72301.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72301","rid":"SV-86925r2_rule","stig_id":"RHEL-07-040700","fix_id":"F-78655r2_fix","cci":["CCI-000318","CCI-000368","CCI-001812","CCI-001813","CCI-001814"],"nist":["CM-3 f","CM-6 c","CM-11 (2)","CM-5 (1)","CM-5 (1)"]},"title":"The Red Hat Enterprise Linux operating system must not have the\nTrivial File Transfer Protocol (TFTP) server package installed if not required\nfor operational support.","waiver_data":{}},{"code":"control \"V-72303\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat remote X connections for interactive users are encrypted.\"\n desc \"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify remote X connections for interactive users are encrypted.\n\n Check that remote X connections are encrypted with the following command:\n\n # grep -i x11forwarding /etc/ssh/sshd_config | grep -v \\\"^#\\\"\n\n X11Forwarding yes\n\n If the \\\"X11Forwarding\\\" keyword is set to \\\"no\\\" or is missing, this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure SSH to encrypt connections for interactive users.\n\n Edit the \\\"/etc/ssh/sshd_config\\\" file to uncomment or add the line for the\n\\\"X11Forwarding\\\" keyword and set its value to \\\"yes\\\" (this file may be named\ndifferently or be in a different location if using a version of SSH that is\nprovided by a third-party vendor):\n\n X11Forwarding yes\n\n The SSH service must be restarted for changes to take effect:\n\n # systemctl restart sshd\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72303\"\n tag rid: \"SV-86927r4_rule\"\n tag stig_id: \"RHEL-07-040710\"\n tag fix_id: \"F-78657r6_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe sshd_config do\n its('X11Forwarding') { should cmp 'yes' }\n end\nend\n","desc":"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.","descriptions":[{"data":"Open X displays allow an attacker to capture keystrokes and execute\ncommands remotely.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify remote X connections for interactive users are encrypted.\n\n Check that remote X connections are encrypted with the following command:\n\n # grep -i x11forwarding /etc/ssh/sshd_config | grep -v \"^#\"\n\n X11Forwarding yes\n\n If the \"X11Forwarding\" keyword is set to \"no\" or is missing, this is a\nfinding.","label":"check"},{"data":"Configure SSH to encrypt connections for interactive users.\n\n Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the\n\"X11Forwarding\" keyword and set its value to \"yes\" (this file may be named\ndifferently or be in a different location if using a version of SSH that is\nprovided by a third-party vendor):\n\n X11Forwarding yes\n\n The SSH service must be restarted for changes to take effect:\n\n # systemctl restart sshd","label":"fix"}],"id":"V-72303","impact":0.7,"refs":[],"results":[{"code_desc":"SSHD Configuration X11Forwarding is expected to cmp == \"yes\"","run_time":0.022363432,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"sshd_config","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72303.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72303","rid":"SV-86927r4_rule","stig_id":"RHEL-07-040710","fix_id":"F-78657r6_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat remote X connections for interactive users are encrypted.","waiver_data":{}},{"code":"control \"V-72305\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP\ndaemon is configured to operate in secure mode.\"\n desc \"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the TFTP daemon is configured to operate in secure mode.\n\n Check to see if a TFTP server has been installed with the following\ncommands:\n\n # yum list installed tftp-server\n tftp-server.x86_64 x.x-x.el7 rhel-7-server-rpms\n\n If a TFTP server is not installed, this is Not Applicable.\n\n If a TFTP server is installed, check for the server arguments with the\nfollowing command:\n\n # grep server_args /etc/xinetd.d/tftp\n server_args = -s /var/lib/tftpboot\n\n If the \\\"server_args\\\" line does not have a \\\"-s\\\" option and a\nsubdirectory is not assigned, this is a finding.\n \"\n desc \"fix\", \"\n Configure the TFTP daemon to operate in secure mode by adding the following\nline to \\\"/etc/xinetd.d/tftp\\\" (or modify the line to have the required value):\n\n server_args = -s /var/lib/tftpboot\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72305\"\n tag rid: \"SV-86929r3_rule\"\n tag stig_id: \"RHEL-07-040720\"\n tag fix_id: \"F-78659r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if package('tftp-server').installed?\n impact 0.5\n describe command('grep server_args /etc/xinetd.d/tftp') do\n its('stdout.strip') { should match %r{^\\s*server_args\\s+=\\s+(-s|--secure)\\s(\\/\\S+)$} }\n end\n else\n impact 0.0\n describe \"The TFTP package is not installed\" do\n skip \"If a TFTP server is not installed, this is Not Applicable.\"\n end\n end\nend\n","desc":"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.","descriptions":[{"data":"Restricting TFTP to a specific directory prevents remote users from\ncopying, transferring, or overwriting system files.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the TFTP daemon is configured to operate in secure mode.\n\n Check to see if a TFTP server has been installed with the following\ncommands:\n\n # yum list installed tftp-server\n tftp-server.x86_64 x.x-x.el7 rhel-7-server-rpms\n\n If a TFTP server is not installed, this is Not Applicable.\n\n If a TFTP server is installed, check for the server arguments with the\nfollowing command:\n\n # grep server_args /etc/xinetd.d/tftp\n server_args = -s /var/lib/tftpboot\n\n If the \"server_args\" line does not have a \"-s\" option and a\nsubdirectory is not assigned, this is a finding.","label":"check"},{"data":"Configure the TFTP daemon to operate in secure mode by adding the following\nline to \"/etc/xinetd.d/tftp\" (or modify the line to have the required value):\n\n server_args = -s /var/lib/tftpboot","label":"fix"}],"id":"V-72305","impact":0,"refs":[],"results":[{"code_desc":"The TFTP package is not installed","resource":"","run_time":0.000012685,"skip_message":"If a TFTP server is not installed, this is Not Applicable.","start_time":"2022-03-06T22:06:09+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72305.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72305","rid":"SV-86929r3_rule","stig_id":"RHEL-07-040720","fix_id":"F-78659r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP\ndaemon is configured to operate in secure mode.","waiver_data":{}},{"code":"control \"V-72307\" do\n title \"The Red Hat Enterprise Linux operating system must not have an X\nWindows display manager installed unless approved.\"\n desc \"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that if the system has X Windows System installed, it is authorized.\n\n Check for the X11 package with the following command:\n\n # rpm -qa | grep xorg | grep server\n\n Ask the System Administrator if use of the X Windows System is an\noperational requirement.\n\n If the use of X Windows on the system is not documented with the\nInformation System Security Officer (ISSO), this is a finding.\n \"\n desc \"fix\", \"\n Document the requirement for an X Windows server with the ISSO or remove\nthe related packages with the following commands:\n\n # rpm -e xorg-x11-server-common\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72307\"\n tag rid: \"SV-86931r4_rule\"\n tag stig_id: \"RHEL-07-040730\"\n tag fix_id: \"F-78661r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n x11_enabled = input('x11_enabled')\n\n describe package('xorg-x11-server-common') do\n it { should_not be_installed }\n end if !x11_enabled\n\n describe package('xorg-x11-server-common') do\n it { should be_installed }\n end if x11_enabled\nend\n","desc":"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.","descriptions":[{"data":"Internet services that are not required for system or application\nprocesses must not be active to decrease the attack surface of the system. X\nWindows has a long history of security vulnerabilities and will not be used\nunless approved and documented.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that if the system has X Windows System installed, it is authorized.\n\n Check for the X11 package with the following command:\n\n # rpm -qa | grep xorg | grep server\n\n Ask the System Administrator if use of the X Windows System is an\noperational requirement.\n\n If the use of X Windows on the system is not documented with the\nInformation System Security Officer (ISSO), this is a finding.","label":"check"},{"data":"Document the requirement for an X Windows server with the ISSO or remove\nthe related packages with the following commands:\n\n # rpm -e xorg-x11-server-common","label":"fix"}],"id":"V-72307","impact":0.5,"refs":[],"results":[{"code_desc":"System Package xorg-x11-server-common is expected not to be installed","run_time":0.050685732,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"package","resource_params":"[\"xorg-x11-server-common\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72307.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72307","rid":"SV-86931r4_rule","stig_id":"RHEL-07-040730","fix_id":"F-78661r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have an X\nWindows display manager installed unless approved.","waiver_data":{}},{"code":"control \"V-72309\" do\n title \"The Red Hat Enterprise Linux operating system must not be performing\npacket forwarding unless the system is a router.\"\n desc \"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system is not performing packet forwarding, unless the system is\na router.\n\n # grep net.ipv4.ip_forward /etc/sysctl.conf /etc/sysctl.d/*\n\n net.ipv4.ip_forward = 0\n\n If \\\"net.ipv4.ip_forward\\\" is not configured in the /etc/sysctl.conf file\nor in the /etc/sysctl.d/ directory, is commented out, or does not have a value\nof \\\"0\\\", this is a finding.\n\n Check that the operating system does not implement IP forwarding using the\nfollowing command:\n\n # /sbin/sysctl -a | grep net.ipv4.ip_forward\n net.ipv4.ip_forward = 0\n\n If IP forwarding value is \\\"1\\\" and the system is hosting any application,\ndatabase, or web servers, this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.ip_forward = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72309\"\n tag rid: \"SV-86933r2_rule\"\n tag stig_id: \"RHEL-07-040740\"\n tag fix_id: \"F-78663r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.ip_forward') do\n its('value') { should eq 0 }\n end\nend\n","desc":"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.","descriptions":[{"data":"Routing protocol daemons are typically used on routers to exchange\nnetwork topology information with other routers. If this software is used when\nnot required, system network information may be unnecessarily transmitted\nacross the network.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system is not performing packet forwarding, unless the system is\na router.\n\n # grep net.ipv4.ip_forward /etc/sysctl.conf /etc/sysctl.d/*\n\n net.ipv4.ip_forward = 0\n\n If \"net.ipv4.ip_forward\" is not configured in the /etc/sysctl.conf file\nor in the /etc/sysctl.d/ directory, is commented out, or does not have a value\nof \"0\", this is a finding.\n\n Check that the operating system does not implement IP forwarding using the\nfollowing command:\n\n # /sbin/sysctl -a | grep net.ipv4.ip_forward\n net.ipv4.ip_forward = 0\n\n If IP forwarding value is \"1\" and the system is hosting any application,\ndatabase, or web servers, this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.ip_forward = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72309","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.ip_forward value is expected to eq 0","run_time":0.042540634,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.ip_forward\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72309.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72309","rid":"SV-86933r2_rule","stig_id":"RHEL-07-040740","fix_id":"F-78663r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not be performing\npacket forwarding unless the system is a router.","waiver_data":{}},{"code":"control \"V-72311\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the Network File System (NFS) is configured to use RPCSEC_GSS.\"\n desc \"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify \\\"AUTH_GSS\\\" is being used to authenticate NFS mounts.\n\n To check if the system is importing an NFS file system, look for any\nentries in the \\\"/etc/fstab\\\" file that have a file system type of \\\"nfs\\\" with\nthe following command:\n\n # cat /etc/fstab | grep nfs\n 192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=krb5:krb5i:krb5p\n\n If the system is mounting file systems via NFS and has the sec option\nwithout the \\\"krb5:krb5i:krb5p\\\" settings, the \\\"sec\\\" option has the \\\"sys\\\"\nsetting, or the \\\"sec\\\" option is missing, this is a finding.\n \"\n desc \"fix\", \"\n Update the \\\"/etc/fstab\\\" file so the option \\\"sec\\\" is defined for each\nNFS mounted file system and the \\\"sec\\\" option does not have the \\\"sys\\\"\nsetting.\n\n Ensure the \\\"sec\\\" option is defined as \\\"krb5:krb5i:krb5p\\\".\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72311\"\n tag rid: \"SV-86935r4_rule\"\n tag stig_id: \"RHEL-07-040750\"\n tag fix_id: \"F-78665r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n nfs_systems = etc_fstab.nfs_file_systems.entries\n if !nfs_systems.nil? and !nfs_systems.empty?\n nfs_systems.each do |file_system|\n describe file_system do\n its ('mount_options') { should include 'sec=krb5:krb5i:krb5p' }\n end\n end\n else\n describe \"No NFS file systems were found.\" do\n subject { nfs_systems.nil? or nfs_systems.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.","descriptions":[{"data":"When an NFS server is configured to use RPCSEC_SYS, a selected userid\nand groupid are used to handle requests from the remote user. The userid and\ngroupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS\nmethod of authentication uses certificates on the server and client systems to\nmore securely authenticate the remote mount request.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify \"AUTH_GSS\" is being used to authenticate NFS mounts.\n\n To check if the system is importing an NFS file system, look for any\nentries in the \"/etc/fstab\" file that have a file system type of \"nfs\" with\nthe following command:\n\n # cat /etc/fstab | grep nfs\n 192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=krb5:krb5i:krb5p\n\n If the system is mounting file systems via NFS and has the sec option\nwithout the \"krb5:krb5i:krb5p\" settings, the \"sec\" option has the \"sys\"\nsetting, or the \"sec\" option is missing, this is a finding.","label":"check"},{"data":"Update the \"/etc/fstab\" file so the option \"sec\" is defined for each\nNFS mounted file system and the \"sec\" option does not have the \"sys\"\nsetting.\n\n Ensure the \"sec\" option is defined as \"krb5:krb5i:krb5p\".","label":"fix"}],"id":"V-72311","impact":0.5,"refs":[],"results":[{"code_desc":"No NFS file systems were found. is expected to eq true","run_time":0.000104441,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72311.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72311","rid":"SV-86935r4_rule","stig_id":"RHEL-07-040750","fix_id":"F-78665r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the Network File System (NFS) is configured to use RPCSEC_GSS.","waiver_data":{}},{"code":"control \"V-72313\" do\n title \"SNMP community strings on the Red Hat Enterprise Linux operating\nsystem must be changed from the default.\"\n desc \"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that a system using SNMP is not using default community strings.\n\n Check to see if the \\\"/etc/snmp/snmpd.conf\\\" file exists with the following\ncommand:\n\n # ls -al /etc/snmp/snmpd.conf\n -rw------- 1 root root 52640 Mar 12 11:08 snmpd.conf\n\n If the file does not exist, this is Not Applicable.\n\n If the file does exist, check for the default community strings with the\nfollowing commands:\n\n # grep public /etc/snmp/snmpd.conf\n # grep private /etc/snmp/snmpd.conf\n\n If either of these commands returns any output, this is a finding.\n \"\n desc \"fix\", \"If the \\\"/etc/snmp/snmpd.conf\\\" file exists, modify any lines\nthat contain a community string value of \\\"public\\\" or \\\"private\\\" to another\nstring value.\"\n\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72313\"\n tag rid: \"SV-86937r2_rule\"\n tag stig_id: \"RHEL-07-040800\"\n tag fix_id: \"F-78667r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n if file('/etc/snmp/snmpd.conf').exist?\n impact 0.7\n processed = []\n to_process = ['/etc/snmp/snmpd.conf']\n\n while !to_process.empty?\n in_process = to_process.pop\n next if processed.include? in_process\n processed.push in_process\n\n if file(in_process).directory?\n to_process.concat(\n command(\"find #{in_process} -maxdepth 1 -mindepth 1 -name '*.conf'\").\n stdout.strip.split(\"\\n\").\n select { |f| file(f).file? }\n )\n elsif file(in_process).file?\n to_process.concat(\n command(\"grep -E '^\\\\s*includeFile\\\\s+' #{in_process} | sed 's/^[[:space:]]*includeFile[[:space:]]*//g'\").\n stdout.strip.split(%r{\\n+}).\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n select { |f| file(f).file? }\n )\n to_process.concat(\n command(\"grep -E '^\\\\s*includeDir\\\\s+' #{in_process} | sed 's/^[[:space:]]*includeDir[[:space:]]*//g'\").\n stdout.strip.split(%r{\\n+}).\n map { |f| f.start_with?('/') ? f : File.join('/', f) }. # relative dirs are treated as absolute\n select { |f| file(f).directory? }\n )\n end\n end\n\n config_files = processed.select { |f| file(f).file? }\n\n config_files.each do |config|\n describe file(config) do\n its('content') { should_not match %r{^[^#]*(public|private)} }\n end\n end\n else\n impact 0.0\n describe \"The `snmpd.conf` does not exist\" do\n skip \"The snmpd.conf file does not exist, this control is Not Applicable\"\n end\n end\nend\n","desc":"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.","descriptions":[{"data":"Whether active or not, default Simple Network Management Protocol\n(SNMP) community strings must be changed to maintain security. If the service\nis running with the default authenticators, anyone can gather data about the\nsystem and the network and use the information to potentially compromise the\nintegrity of the system or network(s). It is highly recommended that SNMP\nversion 3 user authentication and message encryption be used in place of the\nversion 2 community strings.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that a system using SNMP is not using default community strings.\n\n Check to see if the \"/etc/snmp/snmpd.conf\" file exists with the following\ncommand:\n\n # ls -al /etc/snmp/snmpd.conf\n -rw------- 1 root root 52640 Mar 12 11:08 snmpd.conf\n\n If the file does not exist, this is Not Applicable.\n\n If the file does exist, check for the default community strings with the\nfollowing commands:\n\n # grep public /etc/snmp/snmpd.conf\n # grep private /etc/snmp/snmpd.conf\n\n If either of these commands returns any output, this is a finding.","label":"check"},{"data":"If the \"/etc/snmp/snmpd.conf\" file exists, modify any lines\nthat contain a community string value of \"public\" or \"private\" to another\nstring value.","label":"fix"}],"id":"V-72313","impact":0,"refs":[],"results":[{"code_desc":"The `snmpd.conf` does not exist","resource":"","run_time":0.000007803,"skip_message":"The snmpd.conf file does not exist, this control is Not Applicable","start_time":"2022-03-06T22:06:09+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72313.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72313","rid":"SV-86937r2_rule","stig_id":"RHEL-07-040800","fix_id":"F-78667r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"SNMP community strings on the Red Hat Enterprise Linux operating\nsystem must be changed from the default.","waiver_data":{}},{"code":"control \"V-72315\" do\n title \"The Red Hat Enterprise Linux operating system access control program\nmust be configured to grant or deny system access to specific hosts and\nservices.\"\n desc \"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If the \\\"firewalld\\\" package is not installed, ask the System Administrator\n(SA) if another firewall application (such as iptables) is installed. If an\napplication firewall is not installed, this is a finding.\n\n Verify the system's access control program is configured to grant or deny\nsystem access to specific hosts.\n\n Check to see if \\\"firewalld\\\" is active with the following command:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago\n\n If \\\"firewalld\\\" is active, check to see if it is configured to grant or\ndeny access to specific hosts or services with the following commands:\n\n # firewall-cmd --get-default-zone\n public\n\n # firewall-cmd --list-all --zone=public\n public (active)\n target: default\n icmp-block-inversion: no\n interfaces: eth0\n sources:\n services: mdns ssh\n ports:\n protocols:\n masquerade: no\n forward-ports:\n icmp-blocks:\n\n If \\\"firewalld\\\" is not active, determine whether \\\"tcpwrappers\\\" is being\nused by checking whether the \\\"hosts.allow\\\" and \\\"hosts.deny\\\" files are empty\nwith the following commands:\n\n # ls -al /etc/hosts.allow\n rw-r----- 1 root root 9 Aug 2 23:13 /etc/hosts.allow\n\n # ls -al /etc/hosts.deny\n -rw-r----- 1 root root 9 Apr 9 2007 /etc/hosts.deny\n\n If \\\"firewalld\\\" and \\\"tcpwrappers\\\" are not installed, configured, and\nactive, ask the SA if another access control program (such as iptables) is\ninstalled and active. Ask the SA to show that the running configuration grants\nor denies access to specific hosts or services.\n\n If \\\"firewalld\\\" is active and is not configured to grant access to\nspecific hosts or \\\"tcpwrappers\\\" is not configured to grant or deny access to\nspecific hosts, this is a finding.\n \"\n desc \"fix\", \"\n If \\\"firewalld\\\" is installed and active on the system, configure rules for\nallowing specific services and hosts.\n\n If \\\"firewalld\\\" is not \\\"active\\\", enable \\\"tcpwrappers\\\" by configuring\n\\\"/etc/hosts.allow\\\" and \\\"/etc/hosts.deny\\\" to allow or deny access to\nspecific hosts.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72315\"\n tag rid: \"SV-86939r3_rule\"\n tag stig_id: \"RHEL-07-040810\"\n tag fix_id: \"F-78669r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n firewalld_services = input('firewalld_services')\n firewalld_hosts_allow = input('firewalld_hosts_allow')\n firewalld_hosts_deny = input('firewalld_hosts_deny')\n firewalld_ports_allow = input('firewalld_ports_allow')\n firewalld_ports_deny = input('firewalld_ports_deny')\n tcpwrappers_allow = input('tcpwrappers_allow')\n tcpwrappers_deny = input('tcpwrappers_deny')\n iptable_rules = input('iptables_rules')\n\n if service('firewalld').running?\n @default_zone = firewalld.default_zone\n\n describe firewalld.where{ zone = @default_zone } do\n its('services') { should be_in firewalld_services }\n end\n\n describe firewalld do\n firewalld_hosts_allow.each do |rule|\n it { should have_rule_enabled(rule) }\n end\n firewalld_hosts_deny.each do |rule|\n it { should_not have_rule_enabled(rule) }\n end\n firewalld_ports_allow.each do |port|\n it { should have_port_enabled_in_zone(port) }\n end\n firewalld_ports_deny.each do |port|\n it { should_not have_port_enabled_in_zone(port) }\n end\n end\n elsif service('iptables').running?\n describe iptables do\n iptable_rules.each do |rule|\n it { should have_rule(rule) }\n end\n end\n else\n describe package('tcp_wrappers') do\n it { should be_installed }\n end\n tcpwrappers_allow.each do |rule|\n describe etc_hosts_allow.where { daemon == rule['daemon'] } do\n its('client_list') { should be rule['client_list'] }\n its('options') { should be rule['options'] }\n end\n end\n tcpwrappers_deny.each do |rule|\n describe etc_hosts_deny.where { daemon == rule['daemon'] } do\n its('client_list') { should be rule['client_list'] }\n its('options') { should be rule['options'] }\n end\n end\n end\nend\n","desc":"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.","descriptions":[{"data":"If the systems access control program is not configured with\nappropriate rules for allowing and denying access to system network resources,\nservices may be accessible to unauthorized hosts.","label":"default"},{"data":"","label":"rationale"},{"data":"If the \"firewalld\" package is not installed, ask the System Administrator\n(SA) if another firewall application (such as iptables) is installed. If an\napplication firewall is not installed, this is a finding.\n\n Verify the system's access control program is configured to grant or deny\nsystem access to specific hosts.\n\n Check to see if \"firewalld\" is active with the following command:\n\n # systemctl status firewalld\n firewalld.service - firewalld - dynamic firewall daemon\n Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)\n Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago\n\n If \"firewalld\" is active, check to see if it is configured to grant or\ndeny access to specific hosts or services with the following commands:\n\n # firewall-cmd --get-default-zone\n public\n\n # firewall-cmd --list-all --zone=public\n public (active)\n target: default\n icmp-block-inversion: no\n interfaces: eth0\n sources:\n services: mdns ssh\n ports:\n protocols:\n masquerade: no\n forward-ports:\n icmp-blocks:\n\n If \"firewalld\" is not active, determine whether \"tcpwrappers\" is being\nused by checking whether the \"hosts.allow\" and \"hosts.deny\" files are empty\nwith the following commands:\n\n # ls -al /etc/hosts.allow\n rw-r----- 1 root root 9 Aug 2 23:13 /etc/hosts.allow\n\n # ls -al /etc/hosts.deny\n -rw-r----- 1 root root 9 Apr 9 2007 /etc/hosts.deny\n\n If \"firewalld\" and \"tcpwrappers\" are not installed, configured, and\nactive, ask the SA if another access control program (such as iptables) is\ninstalled and active. Ask the SA to show that the running configuration grants\nor denies access to specific hosts or services.\n\n If \"firewalld\" is active and is not configured to grant access to\nspecific hosts or \"tcpwrappers\" is not configured to grant or deny access to\nspecific hosts, this is a finding.","label":"check"},{"data":"If \"firewalld\" is installed and active on the system, configure rules for\nallowing specific services and hosts.\n\n If \"firewalld\" is not \"active\", enable \"tcpwrappers\" by configuring\n\"/etc/hosts.allow\" and \"/etc/hosts.deny\" to allow or deny access to\nspecific hosts.","label":"fix"}],"id":"V-72315","impact":0.5,"refs":[],"results":[{"code_desc":"System Package tcp_wrappers is expected to be installed","run_time":0.054908112,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"package","resource_params":"[\"tcp_wrappers\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72315.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72315","rid":"SV-86939r3_rule","stig_id":"RHEL-07-040810","fix_id":"F-78669r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system access control program\nmust be configured to grant or deny system access to specific hosts and\nservices.","waiver_data":{}},{"code":"control \"V-72317\" do\n title \"The Red Hat Enterprise Linux operating system must not have\nunauthorized IP tunnels configured.\"\n desc \"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system does not have unauthorized IP tunnels configured.\n\n Check to see if \\\"libreswan\\\" is installed with the following command:\n\n # yum list installed libreswan\n libreswan.x86-64 3.20-5.el7_4\n\n If \\\"libreswan\\\" is installed, check to see if the \\\"IPsec\\\" service is\nactive with the following command:\n\n # systemctl status ipsec\n ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec\n Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)\n Active: inactive (dead)\n\n If the \\\"IPsec\\\" service is active, check to see if any tunnels are\nconfigured in \\\"/etc/ipsec.conf\\\" and \\\"/etc/ipsec.d/\\\" with the following\ncommands:\n\n # grep -iw conn /etc/ipsec.conf /etc/ipsec.d/*.conf\n\n If there are indications that a \\\"conn\\\" parameter is configured for a\ntunnel, ask the System Administrator if the tunnel is documented with the ISSO.\n\n If \\\"libreswan\\\" is installed, \\\"IPsec\\\" is active, and an undocumented\ntunnel is active, this is a finding.\n \"\n desc \"fix\", \"Remove all unapproved tunnels from the system, or document them\nwith the ISSO.\"\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72317\"\n tag rid: \"SV-86941r2_rule\"\n tag stig_id: \"RHEL-07-040820\"\n tag fix_id: \"F-78671r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n approved_tunnels = input('approved_tunnels')\n\n if package('libreswan').installed? && service('ipsec.service').running?\n impact 0.5\n processed = []\n to_process = ['/etc/ipsec.conf']\n\n while !to_process.empty?\n in_process = to_process.pop\n next if processed.include? in_process\n processed.push in_process\n\n to_process.concat(\n command(\"grep -E '^\\\\s*include\\\\s+' #{in_process} | sed 's/^[[:space:]]*include[[:space:]]*//g'\").\n stdout.strip.split(%r{\\s*\\n+\\s*}).\n map { |f| f.start_with?('/') ? f : File.join(File.dirname(in_process), f) }.\n map { |f|\n dir = f.sub(%r{[^/]*[\\*\\?\\[].*$}, '') # gets the longest ancestor path which doesn't contain wildcards\n command(\"find #{dir} -wholename '#{f}'\").stdout.strip.split(\"\\n\")\n }.\n flatten.\n select { |f| file(f).file? }\n )\n end\n\n conn_grep = processed.map do |conf|\n command(\"grep -E '^\\\\s*conn\\\\s+' #{conf}\").\n stdout.strip.split(%r{\\s*\\n\\s*})\n end.flatten\n\n describe conn_grep do\n it { should all(be_in approved_tunnels) }\n end\n else\n impact 0.0\n describe \"The system does not have libreswan installed or the ipsec.service isn't running\" do\n skip \"The system does not have libreswan installed or the ipsec.service isn't running, this requirement is Not Applicable.\"\n end\n end\nend\n","desc":"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).","descriptions":[{"data":"IP tunneling mechanisms can be used to bypass network filtering. If\ntunneling is required, it must be documented with the Information System\nSecurity Officer (ISSO).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system does not have unauthorized IP tunnels configured.\n\n Check to see if \"libreswan\" is installed with the following command:\n\n # yum list installed libreswan\n libreswan.x86-64 3.20-5.el7_4\n\n If \"libreswan\" is installed, check to see if the \"IPsec\" service is\nactive with the following command:\n\n # systemctl status ipsec\n ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec\n Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)\n Active: inactive (dead)\n\n If the \"IPsec\" service is active, check to see if any tunnels are\nconfigured in \"/etc/ipsec.conf\" and \"/etc/ipsec.d/\" with the following\ncommands:\n\n # grep -iw conn /etc/ipsec.conf /etc/ipsec.d/*.conf\n\n If there are indications that a \"conn\" parameter is configured for a\ntunnel, ask the System Administrator if the tunnel is documented with the ISSO.\n\n If \"libreswan\" is installed, \"IPsec\" is active, and an undocumented\ntunnel is active, this is a finding.","label":"check"},{"data":"Remove all unapproved tunnels from the system, or document them\nwith the ISSO.","label":"fix"}],"id":"V-72317","impact":0,"refs":[],"results":[{"code_desc":"The system does not have libreswan installed or the ipsec.service isn't running","resource":"","run_time":0.000011027,"skip_message":"The system does not have libreswan installed or the ipsec.service isn't running, this requirement is Not Applicable.","start_time":"2022-03-06T22:06:09+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72317.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72317","rid":"SV-86941r2_rule","stig_id":"RHEL-07-040820","fix_id":"F-78671r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not have\nunauthorized IP tunnels configured.","waiver_data":{}},{"code":"control \"V-72319\" do\n title \"The Red Hat Enterprise Linux operating system must not forward IPv6\nsource-routed packets.\"\n desc \"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n If IPv6 is not enabled, the key will not exist, and this is Not Applicable.\n\n Verify the system does not accept IPv6 source-routed packets.\n\n # grep net.ipv6.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv6.conf.all.accept_source_route = 0\n\n If \\\"net.ipv6.conf.all.accept_source_route\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv6.conf.all.accept_source_route\n net.ipv6.conf.all.accept_source_route = 0\n\n If the returned lines do not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter, if IPv6 is enabled, by\nadding the following line to \\\"/etc/sysctl.conf\\\" or a configuration file in\nthe /etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv6.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-72319\"\n tag rid: \"SV-86943r2_rule\"\n tag stig_id: \"RHEL-07-040830\"\n tag fix_id: \"F-78673r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe.one do\n describe kernel_parameter('net.ipv6.conf.all.accept_source_route') do\n its('value') { should eq 0 }\n end\n\t# If IPv6 is disabled in the kernel it will return NIL\n describe kernel_parameter('net.ipv6.conf.all.accept_source_route') do\n its('value') { should eq nil }\n end\n end\nend\n","desc":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.","descriptions":[{"data":"Source-routed packets allow the source of the packet to suggest that\nrouters forward the packet along a different path than configured on the\nrouter, which can be used to bypass network security measures. This requirement\napplies only to the forwarding of source-routed traffic, such as when IPv6\nforwarding is enabled and the system is functioning as a router.","label":"default"},{"data":"","label":"rationale"},{"data":"If IPv6 is not enabled, the key will not exist, and this is Not Applicable.\n\n Verify the system does not accept IPv6 source-routed packets.\n\n # grep net.ipv6.conf.all.accept_source_route /etc/sysctl.conf\n/etc/sysctl.d/*\n\n net.ipv6.conf.all.accept_source_route = 0\n\n If \"net.ipv6.conf.all.accept_source_route\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv6.conf.all.accept_source_route\n net.ipv6.conf.all.accept_source_route = 0\n\n If the returned lines do not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter, if IPv6 is enabled, by\nadding the following line to \"/etc/sysctl.conf\" or a configuration file in\nthe /etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv6.conf.all.accept_source_route = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-72319","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv6.conf.all.accept_source_route value is expected to eq 0","run_time":0.000274086,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv6.conf.all.accept_source_route\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72319.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-72319","rid":"SV-86943r2_rule","stig_id":"RHEL-07-040830","fix_id":"F-78673r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must not forward IPv6\nsource-routed packets.","waiver_data":{}},{"code":"control \"V-72417\" do\n title \"The Red Hat Enterprise Linux operating system must have the required\n packages for multifactor authentication installed.\"\n\n desc \"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).\"\n\n desc \"check\", \"\n Verify the operating system has the packages required for multifactor\n authentication installed.\n\n Check for the presence of the packages required to support multifactor\n authentication with the following commands:\n\n # yum list installed esc\n esc-1.1.0-26.el7.noarch.rpm\n\n # yum list installed pam_pkcs11\n pam_pkcs11-0.6.2-14.el7.noarch.rpm\n\n If the \\\"esc\\\" and \\\"pam_pkcs11\\\" packages are not installed, this is a\n finding.\"\n\n desc \"fix\", \"\n Configure the operating system to implement multifactor authentication by\n installing the required packages.\n\n Install the \\\"esc\\\" and \\\"pam_pkcs11\\\" packages on the system with the\n following command:\n\n # yum install esc pam_pkcs11\"\n\n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00160\", \"SRG-OS-000375-GPOS-00161\", \"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-72417\"\n tag rid: \"SV-87041r4_rule\"\n tag stig_id: \"RHEL-07-041001\"\n tag fix_id: \"F-78769r4_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n mfa_pkg_list = input('mfa_pkg_list')\n smart_card_status = input('smart_card_status')\n\n if smart_card_status.eql?('disabled')\n impact 0.0\n describe \"The system is not smartcard enabled thus this control is Not Applicable\" do\n skip \"The system is not using Smartcards / PIVs to fulfil the MFA requirement, this control is Not Applicable.\"\n end \n elsif mfa_pkg_list.empty?\n describe \"The required Smartcard packages have not beed defined, plese define them in your `inputs`.\" do\n subject { mfa_pkg_list }\n it { should_not be_empty }\n end\n else\n mfa_pkg_list.each do |pkg|\n describe \"The package\" do\n subject { package(\"#{pkg}\") }\n it { should be_installed }\n end\n end\n end\nend\n","desc":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","label":"default"},{"data":"Verify the operating system has the packages required for multifactor\nauthentication installed.\n\nCheck for the presence of the packages required to support multifactor\nauthentication with the following commands:\n\n# yum list installed esc\nesc-1.1.0-26.el7.noarch.rpm\n\n# yum list installed pam_pkcs11\npam_pkcs11-0.6.2-14.el7.noarch.rpm\n\nIf the \"esc\" and \"pam_pkcs11\" packages are not installed, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to implement multifactor authentication by\ninstalling the required packages.\n\nInstall the \"esc\" and \"pam_pkcs11\" packages on the system with the\nfollowing command:\n\n# yum install esc pam_pkcs11","label":"fix"}],"id":"V-72417","impact":0.5,"refs":[],"results":[{"code_desc":"The package is expected to be installed","run_time":0.048572918,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package nss-pam-ldapd` is installed","run_time":0.049055525,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package esc` is installed","run_time":0.001543205,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package pam_pkcs11` is installed","run_time":0.052000905,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package pam_krb5` is installed","run_time":0.050184448,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package opensc` is installed","run_time":0.049486001,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package pcsc-lite-ccid` is installed","run_time":0.048599225,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package gdm` is installed","run_time":0.000564082,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","run_time":0.058591176,"start_time":"2022-03-06T22:06:09+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package authconfig-gtk` is installed","run_time":0.059070047,"start_time":"2022-03-06T22:06:09+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","run_time":0.062333551,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package krb5-workstation` is installed","run_time":0.05181526,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package krb5-pkinit` is installed","run_time":0.343087971,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package pcsc-lite` is installed","run_time":0.000637374,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"Object","resource_params":"[]"},{"code_desc":"The package is expected to be installed","message":"expected that `System Package pcsc-lite-libs` is installed","run_time":0.057271134,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72417.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72417","rid":"SV-87041r4_rule","stig_id":"RHEL-07-041001","fix_id":"F-78769r4_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must have the required\n packages for multifactor authentication installed.","waiver_data":{}},{"code":"control \"V-72427\" do\n title \"The Red Hat Enterprise Linux operating system must implement\n multifactor authentication for access to privileged accounts via pluggable\n authentication modules (PAM).\"\n desc \"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system implements multifactor authentication for\n remote access to privileged accounts via pluggable authentication modules (PAM).\n\n Check the \\\"/etc/sssd/sssd.conf\\\" file for the authentication services that\n are being used with the following command:\n\n # grep services /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf\n\n services = nss, pam\n\n If the \\\"pam\\\" service is not present on all \\\"services\\\" lines, this is a\n finding.\n \"\n desc \"fix\", \"\n Configure the operating system to implement multifactor authentication for\n remote access to privileged accounts via pluggable authentication modules (PAM).\n\n Modify all of the services lines in \\\"/etc/sssd/sssd.conf\\\" or in\n configuration files found under \\\"/etc/sssd/conf.d\\\" to include pam.\"\n\n impact 0.5 \n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00160\", \"SRG-OS-000375-GPOS-00161\",\n\"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-72427\"\n tag rid: \"SV-87051r4_rule\"\n tag stig_id: \"RHEL-07-041002\"\n tag fix_id: \"F-78779r3_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n unless package('sssd').installed?\n impact 0.0\n describe \"The SSSD Package is not installed on the system\" do\n skip \"This control is Not Appliciable without the SSSD Package installed.\"\n end\n else\n if (!(sssd_files = command(\"find /etc/sssd -name *.conf\").stdout.split(\"\\n\")).empty?)\n sssd_files.each do |file|\n describe.one do\n describe parse_config_file(file) do\n its('services') { should include 'pam' }\n end if package('sssd').installed?\n describe command(\"grep -i -E 'services(\\s)*=(\\s)*(.+*)pam' #{file}\") do\n its('stdout.strip') { should include 'pam' }\n end if package('sssd').installed?\n end if package('sssd').installed?\n end\n else\n describe \"The set of SSSD configuration files\" do\n subject { sssd_files.to_a }\n it { should_not be_empty }\n end\n end\n end\nend\n","desc":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\n separate from the information system, ensures that even if the information\n system is compromised, that compromise will not affect credentials stored on\n the authentication device.\n\n Multifactor solutions that require devices separate from information\n systems gaining access include, for example, hardware tokens providing\n time-based or challenge-response authenticators and smart cards such as the\n U.S. Government Personal Identity Verification card and the DoD Common Access\n Card.\n\n A privileged account is defined as an information system account with\n authorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\n authorized user (or an information system) communicating through an external,\n non-organization-controlled network. Remote access methods include, for\n example, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\n function of the device or has the concept of an organizational user (e.g., VPN,\n proxy capability). This does not apply to authentication for the purpose of\n configuring the device itself (management).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements multifactor authentication for\nremote access to privileged accounts via pluggable authentication modules (PAM).\n\n Check the \"/etc/sssd/sssd.conf\" file for the authentication services that\nare being used with the following command:\n\n # grep services /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf\n\n services = nss, pam\n\n If the \"pam\" service is not present on all \"services\" lines, this is a\nfinding.","label":"check"},{"data":"Configure the operating system to implement multifactor authentication for\nremote access to privileged accounts via pluggable authentication modules (PAM).\n\n Modify all of the services lines in \"/etc/sssd/sssd.conf\" or in\nconfiguration files found under \"/etc/sssd/conf.d\" to include pam.","label":"fix"}],"id":"V-72427","impact":0,"refs":[],"results":[{"code_desc":"The SSSD Package is not installed on the system","resource":"","run_time":0.000009471,"skip_message":"This control is Not Appliciable without the SSSD Package installed.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72427.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72427","rid":"SV-87051r4_rule","stig_id":"RHEL-07-041002","fix_id":"F-78779r3_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must implement\n multifactor authentication for access to privileged accounts via pluggable\n authentication modules (PAM).","waiver_data":{}},{"code":"control 'V-72433' do\n title \"The Red Hat Enterprise Linux operating system must implement\ncertificate status checking for PKI authentication.\"\n desc \"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).\n\n\n \"\n desc 'rationale', ''\n desc 'check', \"\n Verify the operating system implements certificate status checking for PKI\nauthentication.\n\n Check to see if Online Certificate Status Protocol (OCSP) is enabled on the\nsystem with the following command:\n\n # grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -v \\\"^#\\\"\n\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n\n There should be at least three lines returned.\n\n If \\\"ocsp_on\\\" is not present in all uncommented \\\"cert_policy\\\" lines in\n\\\"/etc/pam_pkcs11/pam_pkcs11.conf\\\", this is a finding.\n \"\n desc 'fix', \"\n Configure the operating system to do certificate status checking for PKI\nauthentication.\n\n Modify all of the \\\"cert_policy\\\" lines in\n\\\"/etc/pam_pkcs11/pam_pkcs11.conf\\\" to include \\\"ocsp_on\\\".\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00160\", \"SRG-OS-000375-GPOS-00161\",\n\"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-72433\"\n tag rid: \"SV-87057r5_rule\"\n tag stig_id: \"RHEL-07-041003\"\n tag fix_id: \"F-78785r3_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n smart_card_status = input('smart_card_status')\n\n if smart_card_status.eql?('enabled')\n impact 0.5\n if (pam_file = file('/etc/pam_pkcs11/pam_pkcs11.conf')).exist?\n cert_policy_lines = pam_file.content.nil? ? [] :\n pam_file.content.lines.grep(/^(?!.+#).*cert_policy/i)\n if cert_policy_lines.length < 3\n describe 'should contain at least 3 cert policy lines' do\n subject { cert_policy_lines.length }\n it { should >= 3 }\n end\n else\n describe 'each cert policy line should include oscp_on' do\n cert_policy_lines.each do |line|\n subject { line }\n it { should match %r{=[^;]*ocsp_on}i }\n end\n end\n end\n else\n describe pam_file do\n it { should exist }\n end\n end\n else\n impact 0.0\n describe 'The system is not smartcard enabled' do\n skip 'The system is not using Smartcards / PIVs to fulfil the MFA requirement, this control is Not Applicable.'\n end\n end\nend\n","desc":"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).","descriptions":[{"data":"Using an authentication device, such as a CAC or token that is\nseparate from the information system, ensures that even if the information\nsystem is compromised, that compromise will not affect credentials stored on\nthe authentication device.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n A privileged account is defined as an information system account with\nauthorizations of a privileged user.\n\n Remote access is access to DoD nonpublic information systems by an\nauthorized user (or an information system) communicating through an external,\nnon-organization-controlled network. Remote access methods include, for\nexample, dial-up, broadband, and wireless.\n\n This requirement only applies to components where this is specific to the\nfunction of the device or has the concept of an organizational user (e.g., VPN,\nproxy capability). This does not apply to authentication for the purpose of\nconfiguring the device itself (management).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements certificate status checking for PKI\nauthentication.\n\n Check to see if Online Certificate Status Protocol (OCSP) is enabled on the\nsystem with the following command:\n\n # grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -v \"^#\"\n\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n cert_policy = ca, ocsp_on, signature;\n\n There should be at least three lines returned.\n\n If \"ocsp_on\" is not present in all uncommented \"cert_policy\" lines in\n\"/etc/pam_pkcs11/pam_pkcs11.conf\", this is a finding.","label":"check"},{"data":"Configure the operating system to do certificate status checking for PKI\nauthentication.\n\n Modify all of the \"cert_policy\" lines in\n\"/etc/pam_pkcs11/pam_pkcs11.conf\" to include \"ocsp_on\".","label":"fix"}],"id":"V-72433","impact":0.5,"refs":[],"results":[{"code_desc":"File /etc/pam_pkcs11/pam_pkcs11.conf is expected to exist","message":"expected File /etc/pam_pkcs11/pam_pkcs11.conf to exist","run_time":0.000252206,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"file","resource_params":"[\"/etc/pam_pkcs11/pam_pkcs11.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-72433.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00160","SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-72433","rid":"SV-87057r5_rule","stig_id":"RHEL-07-041003","fix_id":"F-78785r3_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must implement\ncertificate status checking for PKI authentication.","waiver_data":{}},{"code":"control \"V-73155\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\n overriding the screensaver lock-delay setting for the graphical user interface.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding a screensaver\n lock after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\n Applicable. The screen program must be installed to lock sessions on the\n console.\n\n Determine which profile the system database is using with the following\n command:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock delay setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\n the path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\n other than \\\"local\\\" is being used.\n\n # grep -i lock-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-delay\n\n If the command does not return a result, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a\n screensaver lock after a 15-minute period of inactivity for graphical user\n interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\n does not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\n if the system is using another database in \\\"/etc/dconf/profile/user\\\", the\n file should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock delay:\n\n /org/gnome/desktop/screensaver/lock-delay\n \"\n\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-73155\"\n tag rid: \"SV-87807r4_rule\"\n tag stig_id: \"RHEL-07-010081\"\n tag fix_id: \"F-79601r2_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n unless package('gnome-desktop3').installed?\n impact 0.0\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n else\n describe command(\"gsettings writable org.gnome.desktop.screensaver lock-delay\") do\n its('stdout.strip') { should cmp 'false' }\n end\n end\n end\n","desc":"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\n work and moves away from the immediate physical vicinity of the information\n system but does not log out because of the temporary nature of the absence.\n Rather than relying on the user to manually lock their operating system session\n prior to vacating the vicinity, operating systems need to be able to identify\n when a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\n determined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding a screensaver\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock delay setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i lock-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-delay\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock delay:\n\n /org/gnome/desktop/screensaver/lock-delay","label":"fix"}],"id":"V-73155","impact":0,"refs":[],"results":[{"code_desc":"The GNOME desktop is not installed","resource":"","run_time":0.000007159,"skip_message":"The GNOME desktop is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73155.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-73155","rid":"SV-87807r4_rule","stig_id":"RHEL-07-010081","fix_id":"F-79601r2_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\n overriding the screensaver lock-delay setting for the graphical user interface.","waiver_data":{}},{"code":"control \"V-73157\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the session idle-delay setting for the graphical user interface.\"\n desc \"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding session idle\ndelay after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the session idle delay setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nthe path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\nother than \\\"local\\\" is being used.\n\n # grep -i idle-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/session/idle-delay\n\n If the command does not return a result, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a session\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nif the system is using another database in /etc/dconf/profile/user, the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the session idle delay:\n\n /org/gnome/desktop/session/idle-delay\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-73157\"\n tag rid: \"SV-87809r4_rule\"\n tag stig_id: \"RHEL-07-010082\"\n tag fix_id: \"F-79603r1_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n unless package('gnome-desktop3').installed?\n impact 0.0\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n else\n describe command(\"gsettings writable org.gnome.desktop.session idle-delay\") do\n its('stdout.strip') { should cmp 'false' }\n end\n end\nend\n","desc":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","descriptions":[{"data":"A session time-out lock is a temporary action taken when a user stops\nwork and moves away from the immediate physical vicinity of the information\nsystem but does not log out because of the temporary nature of the absence.\nRather than relying on the user to manually lock their operating system session\nprior to vacating the vicinity, operating systems need to be able to identify\nwhen a user's session has idled and take action to initiate the session lock.\n\n The session lock is implemented at the point where session activity can be\ndetermined and/or controlled.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding session idle\ndelay after a 15-minute period of inactivity for graphical user interfaces.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the session idle delay setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i idle-delay /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/session/idle-delay\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a session\nlock after a 15-minute period of inactivity for graphical user interfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in /etc/dconf/profile/user, the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the session idle delay:\n\n /org/gnome/desktop/session/idle-delay","label":"fix"}],"id":"V-73157","impact":0,"refs":[],"results":[{"code_desc":"The GNOME desktop is not installed","resource":"","run_time":0.000007752,"skip_message":"The GNOME desktop is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73157.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-73157","rid":"SV-87809r4_rule","stig_id":"RHEL-07-010082","fix_id":"F-79603r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the session idle-delay setting for the graphical user interface.","waiver_data":{}},{"code":"control \"V-73159\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, pwquality\nmust be used.\"\n desc \"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \\\"pwquality\\\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system uses \\\"pwquality\\\" to enforce the password\ncomplexity rules.\n\n Check for the use of \\\"pwquality\\\" with the following command:\n\n # cat /etc/pam.d/system-auth | grep pam_pwquality\n\n password required pam_pwquality.so retry=3\n\n If the command does not return an uncommented line containing the value\n\\\"pam_pwquality.so\\\", this is a finding.\n\n If the value of \\\"retry\\\" is set to \\\"0\\\" or greater than \\\"3\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system to use \\\"pwquality\\\" to enforce password\ncomplexity rules.\n\n Add the following line to \\\"/etc/pam.d/system-auth\\\" (or modify the line to\nhave the required value):\n\n password required pam_pwquality.so retry=3\n\n Note: The value of \\\"retry\\\" should be between \\\"1\\\" and \\\"3\\\".\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000069-GPOS-00037\"\n tag gid: \"V-73159\"\n tag rid: \"SV-87811r4_rule\"\n tag stig_id: \"RHEL-07-010119\"\n tag fix_id: \"F-79605r5_fix\"\n tag cci: [\"CCI-000192\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n max_retry = input('max_retry')\n\n describe pam('/etc/pam.d/passwd') do\n its('lines') { should match_pam_rule('password (required|requisite) pam_pwquality.so') }\n its('lines') { should match_pam_rule('password (required|requisite) pam_pwquality.so').all_with_integer_arg('retry', '>=', 1) }\n its('lines') { should match_pam_rule('password (required|requisite) pam_pwquality.so').all_with_integer_arg('retry', '<=', max_retry) }\n end\nend\n","desc":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \"pwquality\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.","descriptions":[{"data":"Use of a complex password helps to increase the time and resources\nrequired to compromise the password. Password complexity, or strength, is a\nmeasure of the effectiveness of a password in resisting attempts at guessing\nand brute-force attacks. \"pwquality\" enforces complex password construction\nconfiguration and has the ability to limit brute-force attacks on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uses \"pwquality\" to enforce the password\ncomplexity rules.\n\n Check for the use of \"pwquality\" with the following command:\n\n # cat /etc/pam.d/system-auth | grep pam_pwquality\n\n password required pam_pwquality.so retry=3\n\n If the command does not return an uncommented line containing the value\n\"pam_pwquality.so\", this is a finding.\n\n If the value of \"retry\" is set to \"0\" or greater than \"3\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system to use \"pwquality\" to enforce password\ncomplexity rules.\n\n Add the following line to \"/etc/pam.d/system-auth\" (or modify the line to\nhave the required value):\n\n password required pam_pwquality.so retry=3\n\n Note: The value of \"retry\" should be between \"1\" and \"3\".","label":"fix"}],"id":"V-73159","impact":0.5,"refs":[],"results":[{"code_desc":"PAM Config[/etc/pam.d/passwd] lines is expected to include password (required|requisite) pam_pwquality.so","run_time":0.000666005,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/passwd\"]"},{"code_desc":"PAM Config[/etc/pam.d/passwd] lines is expected to include password (required|requisite) pam_pwquality.so, all with arg retry >= 1","run_time":0.001172924,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/passwd\"]"},{"code_desc":"PAM Config[/etc/pam.d/passwd] lines is expected to include password (required|requisite) pam_pwquality.so, all with arg retry <= 3","run_time":0.001362285,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"pam","resource_params":"[\"/etc/pam.d/passwd\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73159.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-73159","rid":"SV-87811r4_rule","stig_id":"RHEL-07-010119","fix_id":"F-79605r5_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat when passwords are changed or new passwords are established, pwquality\nmust be used.","waiver_data":{}},{"code":"control \"V-73161\" do\n title \"The Red Hat Enterprise Linux operating system must prevent binary\nfiles from being executed on file systems that are being imported via Network\nFile System (NFS).\"\n desc \"The \\\"noexec\\\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify file systems that are being NFS imported are configured with the\n\\\"noexec\\\" option.\n\n Find the file system(s) that contain the directories being imported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,noexec 0 0\n\n If a file system found in \\\"/etc/fstab\\\" refers to NFS and it does not have\nthe \\\"noexec\\\" option set, and use of NFS imported binaries is not documented\nwith the Information System Security Officer (ISSO) as an operational\nrequirement, this is a finding.\n\n Verify the NFS is mounted with the \\\"noexec\\\"option:\n\n # mount | grep nfs | grep noexec\n If no results are returned and use of NFS imported binaries is not\ndocumented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.\n \"\n desc \"fix\", \"Configure the \\\"/etc/fstab\\\" to use the \\\"noexec\\\" option on\nfile systems that are being imported via NFS.\"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-73161\"\n tag rid: \"SV-87813r2_rule\"\n tag stig_id: \"RHEL-07-021021\"\n tag fix_id: \"F-79607r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n nfs_systems = etc_fstab.nfs_file_systems.entries\n if !nfs_systems.nil? and !nfs_systems.empty?\n nfs_systems.each do |file_system|\n describe file_system do\n its ('mount_options') { should include 'noexec' }\n end\n end\n else\n describe \"No NFS file systems were found.\" do\n subject { nfs_systems.nil? or nfs_systems.empty? }\n it { should eq true }\n end\n end\nend\n","desc":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","descriptions":[{"data":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify file systems that are being NFS imported are configured with the\n\"noexec\" option.\n\n Find the file system(s) that contain the directories being imported with\nthe following command:\n\n # more /etc/fstab | grep nfs\n\n UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,noexec 0 0\n\n If a file system found in \"/etc/fstab\" refers to NFS and it does not have\nthe \"noexec\" option set, and use of NFS imported binaries is not documented\nwith the Information System Security Officer (ISSO) as an operational\nrequirement, this is a finding.\n\n Verify the NFS is mounted with the \"noexec\"option:\n\n # mount | grep nfs | grep noexec\n If no results are returned and use of NFS imported binaries is not\ndocumented with the Information System Security Officer (ISSO) as an\noperational requirement, this is a finding.","label":"check"},{"data":"Configure the \"/etc/fstab\" to use the \"noexec\" option on\nfile systems that are being imported via NFS.","label":"fix"}],"id":"V-73161","impact":0.5,"refs":[],"results":[{"code_desc":"No NFS file systems were found. is expected to eq true","run_time":0.000123401,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73161.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-73161","rid":"SV-87813r2_rule","stig_id":"RHEL-07-021021","fix_id":"F-79607r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must prevent binary\nfiles from being executed on file systems that are being imported via Network\nFile System (NFS).","waiver_data":{}},{"code":"control \"V-73163\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when there is an error sending\naudit records to a remote system.\"\n desc \"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the action the operating system takes if there is an error sending\naudit records to a remote system.\n\n Check the action that takes place if there is an error sending audit\nrecords to a remote system with the following command:\n\n # grep -i network_failure_action /etc/audisp/audisp-remote.conf\n network_failure_action = syslog\n\n If the value of the \\\"network_failure_action\\\" option is not \\\"syslog\\\",\n\\\"single\\\", or \\\"halt\\\", or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure the action the operating system takes if there is an error\nsending audit records to a remote system.\n\n Uncomment the \\\"network_failure_action\\\" option in\n\\\"/etc/audisp/audisp-remote.conf\\\" and set it to \\\"syslog\\\", \\\"single\\\", or\n\\\"halt\\\".\n\n network_failure_action = syslog\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag gid: \"V-73163\"\n tag rid: \"SV-87815r3_rule\"\n tag stig_id: \"RHEL-07-030321\"\n tag fix_id: \"F-79609r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n describe parse_config_file('/etc/audisp/audisp-remote.conf') do\n its('network_failure_action'.to_s) { should be_in ['syslog', 'single', 'halt'] }\n end\nend\n","desc":"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.","descriptions":[{"data":"Taking appropriate action when there is an error sending audit records\nto a remote system will minimize the possibility of losing audit records.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the action the operating system takes if there is an error sending\naudit records to a remote system.\n\n Check the action that takes place if there is an error sending audit\nrecords to a remote system with the following command:\n\n # grep -i network_failure_action /etc/audisp/audisp-remote.conf\n network_failure_action = syslog\n\n If the value of the \"network_failure_action\" option is not \"syslog\",\n\"single\", or \"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Configure the action the operating system takes if there is an error\nsending audit records to a remote system.\n\n Uncomment the \"network_failure_action\" option in\n\"/etc/audisp/audisp-remote.conf\" and set it to \"syslog\", \"single\", or\n\"halt\".\n\n network_failure_action = syslog","label":"fix"}],"id":"V-73163","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/audisp/audisp-remote.conf","resource":"Parse Config File /etc/audisp/audisp-remote.conf","run_time":0.000008056,"skip_message":"Can't find file: /etc/audisp/audisp-remote.conf","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"parse_config_file","resource_params":"[\"/etc/audisp/audisp-remote.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73163.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","gid":"V-73163","rid":"SV-87815r3_rule","stig_id":"RHEL-07-030321","fix_id":"F-79609r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the audit system takes appropriate action when there is an error sending\naudit records to a remote system.","waiver_data":{}},{"code":"control \"V-73165\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/group.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/group\\\".\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/group /etc/audit/audit.rules\n\n -w /etc/group -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/group\\\".\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/group -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73165\"\n tag rid: \"SV-87817r3_rule\"\n tag stig_id: \"RHEL-07-030871\"\n tag fix_id: \"F-79611r3_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/group'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\n\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/group\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/group /etc/audit/audit.rules\n\n -w /etc/group -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/group\".\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/group -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73165","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/etc/group\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.000363754,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/group\" action is expected not to include \"never\"","run_time":0.000205663,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73165.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73165","rid":"SV-87817r3_rule","stig_id":"RHEL-07-030871","fix_id":"F-79611r3_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/group.","waiver_data":{}},{"code":"control \"V-73167\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/gshadow.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/gshadow\\\".\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/gshadow /etc/audit/audit.rules\n\n -w /etc/gshadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\\\"/etc/gshadow\\\".\n\n Add or update the following rule in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/gshadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73167\"\n tag rid: \"SV-87819r4_rule\"\n tag stig_id: \"RHEL-07-030872\"\n tag fix_id: \"F-79613r3_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/gshadow'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\n\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/gshadow\".\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/gshadow /etc/audit/audit.rules\n\n -w /etc/gshadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n\"/etc/gshadow\".\n\n Add or update the following rule in \"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/gshadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73167","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/etc/gshadow\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.000424442,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/gshadow\" action is expected not to include \"never\"","run_time":0.000221274,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73167.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73167","rid":"SV-87819r4_rule","stig_id":"RHEL-07-030872","fix_id":"F-79613r3_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/gshadow.","waiver_data":{}},{"code":"control \"V-73171\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/shadow.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/shadow /etc/audit/audit.rules\n\n -w /etc/shadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Add or update the following file system rule in\n\\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/shadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73171\"\n tag rid: \"SV-87823r4_rule\"\n tag stig_id: \"RHEL-07-030873\"\n tag fix_id: \"F-79617r4_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/shadow'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\n\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/shadow /etc/audit/audit.rules\n\n -w /etc/shadow -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/shadow.\n\n Add or update the following file system rule in\n\"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/shadow -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-73171","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/etc/shadow\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.000314632,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/shadow\" action is expected not to include \"never\"","run_time":0.000240818,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73171.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73171","rid":"SV-87823r4_rule","stig_id":"RHEL-07-030873","fix_id":"F-79617r4_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/shadow.","waiver_data":{}},{"code":"control \"V-73173\" do\n title \"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/opasswd.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep /etc/security/opasswd /etc/audit/audit.rules\n\n -w /etc/security/opasswd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Add or update the following file system rule in\n\\\"/etc/audit/rules.d/audit.rules\\\":\n\n -w /etc/security/opasswd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect:\n # systemctl restart auditd\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000004-GPOS-00004\"\n tag gid: \"V-73173\"\n tag rid: \"SV-87825r5_rule\"\n tag stig_id: \"RHEL-07-030874\"\n tag fix_id: \"F-79619r6_fix\"\n tag cci: [\"CCI-000018\", \"CCI-000172\", \"CCI-001403\", \"CCI-002130\"]\n tag nist: [\"AC-2 (4)\", \"AU-12 c\", \"AC-2 (4)\", \"AC-2 (4)\"]\n\n audit_file = '/etc/security/opasswd'\n\n if file(audit_file).exist?\n impact 0.5\n else\n impact 0.0\n end\n\n describe auditd.file(audit_file) do\n its('permissions') { should_not cmp [] }\n its('action') { should_not include 'never' }\n end if file(audit_file).exist?\n\n # Resource creates data structure including all usages of file\n perms = auditd.file(audit_file).permissions\n\n perms.each do |perm|\n describe perm do\n it { should include 'w' }\n it { should include 'a' }\n end\n end if file(audit_file).exist?\n\n describe \"The #{audit_file} file does not exist\" do\n skip \"The #{audit_file} file does not exist, this requirement is Not Applicable.\"\n end if !file(audit_file).exist?\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep /etc/security/opasswd /etc/audit/audit.rules\n\n -w /etc/security/opasswd -p wa -k identity\n\n If the command does not return a line, or the line is commented out, this\nis a finding.","label":"check"},{"data":"Configure the operating system to generate audit records for all account\ncreations, modifications, disabling, and termination events that affect\n/etc/opasswd.\n\n Add or update the following file system rule in\n\"/etc/audit/rules.d/audit.rules\":\n\n -w /etc/security/opasswd -p wa -k identity\n\n The audit daemon must be restarted for the changes to take effect:\n # systemctl restart auditd","label":"fix"}],"id":"V-73173","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with file == \"/etc/security/opasswd\" permissions is expected not to cmp == []","message":"\nexpected: []\n got: []\n\n(compared using `cmp` matcher)\n","run_time":0.00084092,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with file == \"/etc/security/opasswd\" action is expected not to include \"never\"","run_time":0.000999732,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73173.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000004-GPOS-00004","gid":"V-73173","rid":"SV-87825r5_rule","stig_id":"RHEL-07-030874","fix_id":"F-79619r6_fix","cci":["CCI-000018","CCI-000172","CCI-001403","CCI-002130"],"nist":["AC-2 (4)","AU-12 c","AC-2 (4)","AC-2 (4)"]},"title":"The Red Hat Enterprise Linux operating system must generate audit\nrecords for all account creations, modifications, disabling, and termination\nevents that affect /etc/opasswd.","waiver_data":{}},{"code":"control \"V-73175\" do\n title \"The Red Hat Enterprise Linux operating system must ignore Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages.\"\n desc \"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system ignores IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.accept_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \\\" net.ipv4.conf.all.accept_redirects \\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"0\\\", this is a finding.\n\n Check that the operating system implements the \\\"accept_redirects\\\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.accept_redirects'\n\n net.ipv4.conf.all.accept_redirects = 0\n\n If the returned line does not have a value of \\\"0\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to ignore IPv4 ICMP redirect messages by adding the\nfollowing line to \\\"/etc/sysctl.conf\\\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-73175\"\n tag rid: \"SV-87827r4_rule\"\n tag stig_id: \"RHEL-07-040641\"\n tag fix_id: \"F-79621r3_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.accept_redirects') do\n its('value') { should eq 0 }\n end\nend\n","desc":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","descriptions":[{"data":"ICMP redirect messages are used by routers to inform hosts that a more\ndirect route exists for a particular destination. These messages modify the\nhost's route table and are unauthenticated. An illicit ICMP redirect message\ncould result in a man-in-the-middle attack.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system ignores IPv4 ICMP redirect messages.\n\n # grep 'net.ipv4.conf.all.accept_redirects' /etc/sysctl.conf /etc/sysctl.d/*\n\n If \" net.ipv4.conf.all.accept_redirects \" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"0\", this is a finding.\n\n Check that the operating system implements the \"accept_redirects\"\nvariables with the following command:\n\n # /sbin/sysctl -a | grep 'net.ipv4.conf.all.accept_redirects'\n\n net.ipv4.conf.all.accept_redirects = 0\n\n If the returned line does not have a value of \"0\", this is a finding.","label":"check"},{"data":"Set the system to ignore IPv4 ICMP redirect messages by adding the\nfollowing line to \"/etc/sysctl.conf\" or a configuration file in the\n/etc/sysctl.d/ directory (or modify the line to have the required value):\n\n net.ipv4.conf.all.accept_redirects = 0\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-73175","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.all.accept_redirects value is expected to eq 0","message":"\nexpected: 0\n got: 1\n\n(compared using ==)\n","run_time":0.033757858,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.all.accept_redirects\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73175.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-73175","rid":"SV-87827r4_rule","stig_id":"RHEL-07-040641","fix_id":"F-79621r3_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must ignore Internet\nProtocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect\nmessages.","waiver_data":{}},{"code":"control \"V-73177\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat all wireless network adapters are disabled.\"\n desc \"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that there are no wireless interfaces configured on the system.\n\n This is N/A for systems that do not have wireless network adapters.\n\n Check for the presence of active wireless interfaces with the following\ncommand:\n\n # nmcli device\n DEVICE TYPE STATE\n eth0 ethernet connected\n wlp3s0 wifi disconnected\n lo loopback unmanaged\n\n If a wireless interface is configured and its use on the system is not\ndocumented with the Information System Security Officer (ISSO), this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the system to disable all wireless network interfaces with the\nfollowing command:\n\n #nmcli radio wifi off\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000424-GPOS-00188\"\n tag gid: \"V-73177\"\n tag rid: \"SV-87829r2_rule\"\n tag stig_id: \"RHEL-07-041010\"\n tag fix_id: \"F-79623r1_fix\"\n tag cci: [\"CCI-001443\", \"CCI-001444\", \"CCI-002418\"]\n tag nist: [\"AC-18 (1)\", \"AC-18 (1)\", \"SC-8\"]\n\n describe command('nmcli device') do\n its('stdout.strip') { should_not match %r{wifi connected} }\n end\nend\n","desc":"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.","descriptions":[{"data":"The use of wireless networking can introduce many different attack\nvectors into the organization's network. Common attack vectors such as\nmalicious association and ad hoc networks will allow an attacker to spoof a\nwireless access point (AP), allowing validated systems to connect to the\nmalicious AP and enabling the attacker to monitor and record network traffic.\nThese malicious APs can also serve to create a man-in-the-middle attack or be\nused to create a denial of service to valid network resources.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that there are no wireless interfaces configured on the system.\n\n This is N/A for systems that do not have wireless network adapters.\n\n Check for the presence of active wireless interfaces with the following\ncommand:\n\n # nmcli device\n DEVICE TYPE STATE\n eth0 ethernet connected\n wlp3s0 wifi disconnected\n lo loopback unmanaged\n\n If a wireless interface is configured and its use on the system is not\ndocumented with the Information System Security Officer (ISSO), this is a\nfinding.","label":"check"},{"data":"Configure the system to disable all wireless network interfaces with the\nfollowing command:\n\n #nmcli radio wifi off","label":"fix"}],"id":"V-73177","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `nmcli device` stdout.strip is expected not to match /wifi connected/","run_time":0.070324573,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"command","resource_params":"[\"nmcli device\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-73177.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000424-GPOS-00188","gid":"V-73177","rid":"SV-87829r2_rule","stig_id":"RHEL-07-041010","fix_id":"F-79623r1_fix","cci":["CCI-001443","CCI-001444","CCI-002418"],"nist":["AC-18 (1)","AC-18 (1)","SC-8"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat all wireless network adapters are disabled.","waiver_data":{}},{"code":"control \"V-77819\" do\n title \"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate users using multifactor authentication via a graphical\nuser logon.\"\n desc \"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system uniquely identifies and authenticates users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Determine which profile the system database is using with the following\ncommand:\n\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Note: The example is using the database local for the system, so the path\nis \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database other\nthan local is being used.\n\n # grep enable-smartcard-authentication /etc/dconf/db/local.d/*\n\n enable-smartcard-authentication=true\n\n If \\\"enable-smartcard-authentication\\\" is set to \\\"false\\\" or the keyword\nis missing, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to uniquely identify and authenticate users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example is using the database local for the system, so if the\nsystem is using another database in \\\"/etc/dconf/profile/user\\\", the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/00-defaults\n\n Edit \\\"[org/gnome/login-screen]\\\" and add or update the following line:\n enable-smartcard-authentication=true\n\n Update the system databases:\n # dconf update\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000375-GPOS-00160\"\n tag satisfies: [\"SRG-OS-000375-GPOS-00161\", \"SRG-OS-000375-GPOS-00162\"]\n tag gid: \"V-77819\"\n tag rid: \"SV-92515r2_rule\"\n tag stig_id: \"RHEL-07-010061\"\n tag fix_id: \"F-84519r4_fix\"\n tag cci: [\"CCI-001948\", \"CCI-001953\", \"CCI-001954\"]\n tag nist: [\"IA-2 (11)\", \"IA-2 (12)\", \"IA-2 (12)\"]\n\n multifactor_enabled = input('multifactor_enabled')\n dconf_user = input('dconf_user')\n\n if package('gnome-desktop3').installed? && (package('pcsc-lite').installed? || package('esc').installed?)\n impact 0.5\n if !dconf_user.nil? && command('whoami').stdout.strip == 'root'\n describe command(\"sudo -u #{dconf_user} dconf read /org/gnome/login-screen/enable-smartcard-authentication\") do\n its('stdout.strip') { should eq multifactor_enabled.to_s }\n end\n else\n describe command(\"dconf read /org/gnome/login-screen/enable-smartcard-authentication\") do\n its('stdout.strip') { should eq multifactor_enabled.to_s }\n end\n end\n else\n impact 0.0\n if !package('gnome-desktop3').installed?\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n end\n\n if !package('pcsc-lite').installed?\n describe \"The pcsc-lite package is not installed\" do\n skip \"The pcsc-lite package is not installed, this control is Not Applicable.\"\n end\n end\n if !package('esc').installed?\n describe \"The esc package is not installed\" do\n skip \"The esc package is not installed, this control is Not Applicable.\"\n end\n end\n end\nend\n","desc":"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.","descriptions":[{"data":"To assure accountability and prevent unauthenticated access, users\nmust be identified and authenticated to prevent potential misuse and compromise\nof the system.\n\n Multifactor solutions that require devices separate from information\nsystems gaining access include, for example, hardware tokens providing\ntime-based or challenge-response authenticators and smart cards such as the\nU.S. Government Personal Identity Verification card and the DoD Common Access\nCard.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system uniquely identifies and authenticates users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Determine which profile the system database is using with the following\ncommand:\n\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Note: The example is using the database local for the system, so the path\nis \"/etc/dconf/db/local.d\". This path must be modified if a database other\nthan local is being used.\n\n # grep enable-smartcard-authentication /etc/dconf/db/local.d/*\n\n enable-smartcard-authentication=true\n\n If \"enable-smartcard-authentication\" is set to \"false\" or the keyword\nis missing, this is a finding.","label":"check"},{"data":"Configure the operating system to uniquely identify and authenticate users\nusing multifactor authentication via a graphical user logon.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example is using the database local for the system, so if the\nsystem is using another database in \"/etc/dconf/profile/user\", the file\nshould be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/00-defaults\n\n Edit \"[org/gnome/login-screen]\" and add or update the following line:\n enable-smartcard-authentication=true\n\n Update the system databases:\n # dconf update","label":"fix"}],"id":"V-77819","impact":0,"refs":[],"results":[{"code_desc":"The GNOME desktop is not installed","resource":"","run_time":0.000013842,"skip_message":"The GNOME desktop is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"},{"code_desc":"The pcsc-lite package is not installed","resource":"","run_time":0.000010141,"skip_message":"The pcsc-lite package is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"},{"code_desc":"The esc package is not installed","resource":"","run_time":0.000009305,"skip_message":"The esc package is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77819.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000375-GPOS-00160","satisfies":["SRG-OS-000375-GPOS-00161","SRG-OS-000375-GPOS-00162"],"gid":"V-77819","rid":"SV-92515r2_rule","stig_id":"RHEL-07-010061","fix_id":"F-84519r4_fix","cci":["CCI-001948","CCI-001953","CCI-001954"],"nist":["IA-2 (11)","IA-2 (12)","IA-2 (12)"]},"title":"The Red Hat Enterprise Linux operating system must uniquely identify\nand must authenticate users using multifactor authentication via a graphical\nuser logon.","waiver_data":{}},{"code":"control \"V-77821\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the Datagram Congestion Control Protocol (DCCP) kernel module is disabled\nunless required.\"\n desc \"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system disables the ability to load the DCCP kernel\nmodule.\n\n # grep -r dccp /etc/modprobe.d/* | grep -i \\\"/bin/true\\\" | grep -v \\\"^#\\\"\n\n install dccp /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of DCCP is not documented with the Information System Security Officer\n(ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use the DCCP kernel\nmodule.\n\n Check to see if the DCCP kernel module is disabled with the following\ncommand:\n\n # grep -i dccp /etc/modprobe.d/* | grep -i \\\"blacklist\\\" | grep -v \\\"^#\\\"\n\n blacklist dccp\n\n If the command does not return any output or the output is not \\\"blacklist\ndccp\\\", and use of the dccp kernel module is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to disable the ability to use the DCCP\nkernel module.\n\n Create a file under \\\"/etc/modprobe.d\\\" with the following command:\n\n # touch /etc/modprobe.d/dccp.conf\n\n Add the following line to the created file:\n\n install dccp /bin/true\n\n Ensure that the DCCP module is blacklisted:\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist dccp\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000378-GPOS-00163\"\n tag gid: \"V-77821\"\n tag rid: \"SV-92517r3_rule\"\n tag stig_id: \"RHEL-07-020101\"\n tag fix_id: \"F-84521r3_fix\"\n tag cci: [\"CCI-001958\"]\n tag nist: [\"IA-3\"]\n\n describe kernel_module('dccp') do\n it { should_not be_loaded }\n it { should be_blacklisted }\n end\nend\n","desc":"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.","descriptions":[{"data":"Disabling DCCP protects the system against exploitation of any flaws\nin the protocol implementation.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system disables the ability to load the DCCP kernel\nmodule.\n\n # grep -r dccp /etc/modprobe.d/* | grep -i \"/bin/true\" | grep -v \"^#\"\n\n install dccp /bin/true\n\n If the command does not return any output, or the line is commented out,\nand use of DCCP is not documented with the Information System Security Officer\n(ISSO) as an operational requirement, this is a finding.\n\n Verify the operating system disables the ability to use the DCCP kernel\nmodule.\n\n Check to see if the DCCP kernel module is disabled with the following\ncommand:\n\n # grep -i dccp /etc/modprobe.d/* | grep -i \"blacklist\" | grep -v \"^#\"\n\n blacklist dccp\n\n If the command does not return any output or the output is not \"blacklist\ndccp\", and use of the dccp kernel module is not documented with the\nInformation System Security Officer (ISSO) as an operational requirement, this\nis a finding.","label":"check"},{"data":"Configure the operating system to disable the ability to use the DCCP\nkernel module.\n\n Create a file under \"/etc/modprobe.d\" with the following command:\n\n # touch /etc/modprobe.d/dccp.conf\n\n Add the following line to the created file:\n\n install dccp /bin/true\n\n Ensure that the DCCP module is blacklisted:\n\n # vi /etc/modprobe.d/blacklist.conf\n\n Add or update the line:\n\n blacklist dccp","label":"fix"}],"id":"V-77821","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Module dccp is expected not to be loaded","run_time":0.010458555,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"kernel_module","resource_params":"[\"dccp\"]"},{"code_desc":"Kernel Module dccp is expected to be blacklisted","run_time":0.009258775,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"kernel_module","resource_params":"[\"dccp\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77821.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000378-GPOS-00163","gid":"V-77821","rid":"SV-92517r3_rule","stig_id":"RHEL-07-020101","fix_id":"F-84521r3_fix","cci":["CCI-001958"],"nist":["IA-3"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the Datagram Congestion Control Protocol (DCCP) kernel module is disabled\nunless required.","waiver_data":{}},{"code":"control \"V-77823\" do\n title \"The Red Hat Enterprise Linux operating system must require\nauthentication upon booting into single-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system must require authentication upon booting into\nsingle-user and maintenance modes.\n\n Check that the operating system requires authentication upon booting into\nsingle-user mode with the following command:\n\n # grep -i execstart /usr/lib/systemd/system/rescue.service | grep -i sulogin\n\n ExecStart=-/bin/sh -c \\\"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\\\"\n\n If \\\"ExecStart\\\" does not have \\\"/usr/sbin/sulogin\\\" as an option, this is\na finding.\n \"\n desc \"fix\", \"\n Configure the operating system to require authentication upon booting into\nsingle-user and maintenance modes.\n\n Add or modify the \\\"ExecStart\\\" line in\n\\\"/usr/lib/systemd/system/rescue.service\\\" to include \\\"/usr/sbin/sulogin\\\":\n\n ExecStart=-/bin/sh -c \\\"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\\\"\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-77823\"\n tag rid: \"SV-92519r2_rule\"\n tag stig_id: \"RHEL-07-010481\"\n tag fix_id: \"F-84523r2_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n describe command(\"grep -i execstart /usr/lib/systemd/system/rescue.service\") do\n its('stdout.strip') { should match %r{/usr/sbin/sulogin} }\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system must require authentication upon booting into\nsingle-user and maintenance modes.\n\n Check that the operating system requires authentication upon booting into\nsingle-user mode with the following command:\n\n # grep -i execstart /usr/lib/systemd/system/rescue.service | grep -i sulogin\n\n ExecStart=-/bin/sh -c \"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\"\n\n If \"ExecStart\" does not have \"/usr/sbin/sulogin\" as an option, this is\na finding.","label":"check"},{"data":"Configure the operating system to require authentication upon booting into\nsingle-user and maintenance modes.\n\n Add or modify the \"ExecStart\" line in\n\"/usr/lib/systemd/system/rescue.service\" to include \"/usr/sbin/sulogin\":\n\n ExecStart=-/bin/sh -c \"/usr/sbin/sulogin; /usr/bin/systemctl --fail\n--no-block default\"","label":"fix"}],"id":"V-77823","impact":0.5,"refs":[],"results":[{"code_desc":"Command: `grep -i execstart /usr/lib/systemd/system/rescue.service` stdout.strip is expected to match /\\/usr\\/sbin\\/sulogin/","run_time":0.017857143,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"command","resource_params":"[\"grep -i execstart /usr/lib/systemd/system/rescue.service\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77823.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-77823","rid":"SV-92519r2_rule","stig_id":"RHEL-07-010481","fix_id":"F-84523r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"The Red Hat Enterprise Linux operating system must require\nauthentication upon booting into single-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-77825\" do\n title \"The Red Hat Enterprise Linux operating system must implement virtual\naddress space randomization.\"\n desc \"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system implements virtual address space randomization.\n\n # grep kernel.randomize_va_space /etc/sysctl.conf /etc/sysctl.d/*\n\n kernel.randomize_va_space = 2\n\n If \\\"kernel.randomize_va_space\\\" is not configured in the /etc/sysctl.conf\nfile or in the /etc/sysctl.d/ directory, is commented out or does not have a\nvalue of \\\"2\\\", this is a finding.\n\n Check that the operating system implements virtual address space\nrandomization with the following command:\n\n # /sbin/sysctl -a | grep kernel.randomize_va_space\n\n kernel.randomize_va_space = 2\n\n If \\\"kernel.randomize_va_space\\\" does not have a value of \\\"2\\\", this is a\nfinding.\n \"\n desc \"fix\", \"\n Configure the operating system implement virtual address space\nrandomization.\n\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a config file in the /etc/sysctl.d/ directory\n(or modify the line to have the required value):\n\n kernel.randomize_va_space = 2\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-77825\"\n tag rid: \"SV-92521r2_rule\"\n tag stig_id: \"RHEL-07-040201\"\n tag fix_id: \"F-84531r2_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n randomize_va_space = input('randomize_va_space')\n\n describe kernel_parameter('kernel.randomize_va_space') do\n its('value') { should eq randomize_va_space }\n end\nend\n","desc":"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.","descriptions":[{"data":"Address space layout randomization (ASLR) makes it more difficult for\nan attacker to predict the location of attack code he or she has introduced\ninto a process's address space during an attempt at exploitation. Additionally,\nASLR also makes it more difficult for an attacker to know the location of\nexisting code in order to repurpose it using return-oriented programming (ROP)\ntechniques.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system implements virtual address space randomization.\n\n # grep kernel.randomize_va_space /etc/sysctl.conf /etc/sysctl.d/*\n\n kernel.randomize_va_space = 2\n\n If \"kernel.randomize_va_space\" is not configured in the /etc/sysctl.conf\nfile or in the /etc/sysctl.d/ directory, is commented out or does not have a\nvalue of \"2\", this is a finding.\n\n Check that the operating system implements virtual address space\nrandomization with the following command:\n\n # /sbin/sysctl -a | grep kernel.randomize_va_space\n\n kernel.randomize_va_space = 2\n\n If \"kernel.randomize_va_space\" does not have a value of \"2\", this is a\nfinding.","label":"check"},{"data":"Configure the operating system implement virtual address space\nrandomization.\n\n Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a config file in the /etc/sysctl.d/ directory\n(or modify the line to have the required value):\n\n kernel.randomize_va_space = 2\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-77825","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter kernel.randomize_va_space value is expected to eq 2","run_time":0.031111642,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"kernel.randomize_va_space\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-77825.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-77825","rid":"SV-92521r2_rule","stig_id":"RHEL-07-040201","fix_id":"F-84531r2_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must implement virtual\naddress space randomization.","waiver_data":{}},{"code":"control \"V-78995\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver lock-enabled setting for the graphical user\ninterface.\"\n desc \"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding the screensaver\nlock-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock-enabled setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nthe path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\nother than \\\"local\\\" is being used.\n\n # grep -i lock-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-enabled\n\n If the command does not return a result, this is a finding.\n\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nif the system is using another database in \\\"/etc/dconf/profile/user\\\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock-enabled setting:\n\n /org/gnome/desktop/screensaver/lock-enabled\n\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-78995\"\n tag rid: \"SV-93701r3_rule\"\n tag stig_id: \"RHEL-07-010062\"\n tag fix_id: \"F-85745r1_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n describe command(\"gsettings writable org.gnome.desktop.screensaver lock-enabled\") do\n its('stdout.strip') { should cmp 'false' }\n end\n else\n impact 0.0\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end\n end \nend\n","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user’s ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding the screensaver\nlock-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the lock-enabled setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i lock-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/lock-enabled\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver lock-enabled setting:\n\n /org/gnome/desktop/screensaver/lock-enabled","label":"fix"}],"id":"V-78995","impact":0,"refs":[],"results":[{"code_desc":"The GNOME desktop is not installed","resource":"","run_time":0.000092067,"skip_message":"The GNOME desktop is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78995.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-78995","rid":"SV-93701r3_rule","stig_id":"RHEL-07-010062","fix_id":"F-85745r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver lock-enabled setting for the graphical user\ninterface.","waiver_data":{}},{"code":"control \"V-78997\" do\n title \"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver idle-activation-enabled setting for the graphical\nuser interface.\"\n desc \"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system prevents a user from overriding the screensaver\nidle-activation-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the idle-activation-enabled setting with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nthe path is \\\"/etc/dconf/db/local.d\\\". This path must be modified if a database\nother than \\\"local\\\" is being used.\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/idle-activation-enabled\n\n If the command does not return a result, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \\\"local\\\" for the system, so\nif the system is using another database in \\\"/etc/dconf/profile/user\\\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver idle-activation-enabled setting:\n\n /org/gnome/desktop/screensaver/idle-activation-enabled\n \"\n tag severity: nil\n tag gtitle: \"SRG-OS-000029-GPOS-00010\"\n tag gid: \"V-78997\"\n tag rid: \"SV-93703r2_rule\"\n tag stig_id: \"RHEL-07-010101\"\n tag fix_id: \"F-85747r1_fix\"\n tag cci: [\"CCI-000057\"]\n tag nist: [\"AC-11 a\"]\n\n if package('gnome-desktop3').installed?\n impact 0.5\n else\n impact 0.0\n end\n\n describe command(\"gsettings writable org.gnome.desktop.screensaver idle-activation-enabled\") do\n its('stdout.strip') { should cmp 'false' }\n end if package('gnome-desktop3').installed?\n\n describe \"The GNOME desktop is not installed\" do\n skip \"The GNOME desktop is not installed, this control is Not Applicable.\"\n end if !package('gnome-desktop3').installed?\nend\n","desc":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","descriptions":[{"data":"A session lock is a temporary action taken when a user stops work and\nmoves away from the immediate physical vicinity of the information system but\ndoes not want to log out because of the temporary nature of the absence.\n\n The session lock is implemented at the point where session activity can be\ndetermined.\n\n The ability to enable/disable a session lock is given to the user by\ndefault. Disabling the user's ability to disengage the graphical user interface\nsession lock provides the assurance that all sessions will lock after the\nspecified period of time.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system prevents a user from overriding the screensaver\nidle-activation-enabled setting for the graphical user interface.\n\n Note: If the system does not have GNOME installed, this requirement is Not\nApplicable. The screen program must be installed to lock sessions on the\nconsole.\n\n Determine which profile the system database is using with the following\ncommand:\n # grep system-db /etc/dconf/profile/user\n\n system-db:local\n\n Check for the idle-activation-enabled setting with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nthe path is \"/etc/dconf/db/local.d\". This path must be modified if a database\nother than \"local\" is being used.\n\n # grep -i idle-activation-enabled /etc/dconf/db/local.d/locks/*\n\n /org/gnome/desktop/screensaver/idle-activation-enabled\n\n If the command does not return a result, this is a finding.","label":"check"},{"data":"Configure the operating system to prevent a user from overriding a\nscreensaver lock after a 15-minute period of inactivity for graphical user\ninterfaces.\n\n Create a database to contain the system-wide screensaver settings (if it\ndoes not already exist) with the following command:\n\n Note: The example below is using the database \"local\" for the system, so\nif the system is using another database in \"/etc/dconf/profile/user\", the\nfile should be created under the appropriate subdirectory.\n\n # touch /etc/dconf/db/local.d/locks/session\n\n Add the setting to lock the screensaver idle-activation-enabled setting:\n\n /org/gnome/desktop/screensaver/idle-activation-enabled","label":"fix"}],"id":"V-78997","impact":0,"refs":[],"results":[{"code_desc":"The GNOME desktop is not installed","resource":"","run_time":0.000009117,"skip_message":"The GNOME desktop is not installed, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78997.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000029-GPOS-00010","gid":"V-78997","rid":"SV-93703r2_rule","stig_id":"RHEL-07-010101","fix_id":"F-85747r1_fix","cci":["CCI-000057"],"nist":["AC-11 a"]},"title":"The Red Hat Enterprise Linux operating system must prevent a user from\noverriding the screensaver idle-activation-enabled setting for the graphical\nuser interface.","waiver_data":{}},{"code":"control \"V-78999\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe create_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"create_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw create_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"create_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"create_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-78999\"\n tag rid: \"SV-93705r3_rule\"\n tag stig_id: \"RHEL-07-030819\"\n tag fix_id: \"F-85749r4_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"create_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"create_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"create_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw create_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"create_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"create_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S create_module -k module-change\n\n -a always,exit -F arch=b64 -S create_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-78999","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"create_module\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.00059507,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"create_module\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000320692,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"create_module\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.00026265,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"create_module\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000169755,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-78999.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-78999","rid":"SV-93705r3_rule","stig_id":"RHEL-07-030819","fix_id":"F-85749r4_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe create_module syscall.","waiver_data":{}},{"code":"control \"V-79001\" do\n title \"The Red Hat Enterprise Linux operating system must audit all uses of\nthe finit_module syscall.\"\n desc \"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \\\"finit_module\\\" syscall occur.\n\n Check the auditing rules in \\\"/etc/audit/audit.rules\\\" with the following\ncommand:\n\n # grep -iw finit_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n If both the \\\"b32\\\" and \\\"b64\\\" audit rules are not defined for the\n\\\"finit_module\\\" syscall, this is a finding.\n \"\n desc \"fix\", \"\n Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \\\"finit_module\\\" syscall occur.\n\n Add or update the following rules in \\\"/etc/audit/rules.d/audit.rules\\\":\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000471-GPOS-00216\"\n tag satisfies: [\"SRG-OS-000471-GPOS-00216\", \"SRG-OS-000477-GPOS-00222\"]\n tag gid: \"V-79001\"\n tag rid: \"SV-93707r3_rule\"\n tag stig_id: \"RHEL-07-030821\"\n tag fix_id: \"F-85751r3_fix\"\n tag cci: [\"CCI-000172\"]\n tag nist: [\"AU-12 c\"]\n\n describe auditd.syscall(\"finit_module\").where {arch == \"b32\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n if os.arch == 'x86_64'\n describe auditd.syscall(\"finit_module\").where {arch == \"b64\"} do\n its('action.uniq') { should eq ['always'] }\n its('list.uniq') { should eq ['exit'] }\n end\n end\nend\n","desc":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","descriptions":[{"data":"Without generating audit records that are specific to the security and\nmission needs of the organization, it would be difficult to establish,\ncorrelate, and investigate the events relating to an incident or identify those\nresponsible for one.\n\n Audit records can be generated from various components within the\ninformation system (e.g., module or policy filter).","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system generates audit records when\nsuccessful/unsuccessful attempts to use the \"finit_module\" syscall occur.\n\n Check the auditing rules in \"/etc/audit/audit.rules\" with the following\ncommand:\n\n # grep -iw finit_module /etc/audit/audit.rules\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n If both the \"b32\" and \"b64\" audit rules are not defined for the\n\"finit_module\" syscall, this is a finding.","label":"check"},{"data":"Configure the operating system to generate audit records when\nsuccessful/unsuccessful attempts to use the \"finit_module\" syscall occur.\n\n Add or update the following rules in \"/etc/audit/rules.d/audit.rules\":\n\n -a always,exit -F arch=b32 -S finit_module -k module-change\n\n -a always,exit -F arch=b64 -S finit_module -k module-change\n\n The audit daemon must be restarted for the changes to take effect.","label":"fix"}],"id":"V-79001","impact":0.5,"refs":[],"results":[{"code_desc":"Auditd Rules with syscall == \"finit_module\" arch == \"b32\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000195266,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"finit_module\" arch == \"b32\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000160114,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"finit_module\" arch == \"b64\" action.uniq is expected to eq [\"always\"]","message":"\nexpected: [\"always\"]\n got: []\n\n(compared using ==)\n","run_time":0.000172403,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"},{"code_desc":"Auditd Rules with syscall == \"finit_module\" arch == \"b64\" list.uniq is expected to eq [\"exit\"]","message":"\nexpected: [\"exit\"]\n got: []\n\n(compared using ==)\n","run_time":0.000190388,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"FilterTable::Table","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-79001.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000471-GPOS-00216","satisfies":["SRG-OS-000471-GPOS-00216","SRG-OS-000477-GPOS-00222"],"gid":"V-79001","rid":"SV-93707r3_rule","stig_id":"RHEL-07-030821","fix_id":"F-85751r3_fix","cci":["CCI-000172"],"nist":["AU-12 c"]},"title":"The Red Hat Enterprise Linux operating system must audit all uses of\nthe finit_module syscall.","waiver_data":{}},{"code":"control \"V-81003\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing\npasswords.\"\n desc \"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that /etc/pam.d/passwd is configured to use /etc/pam.d/system-auth\nwhen changing passwords:\n\n # cat /etc/pam.d/passwd | grep -i substack | grep -i system-auth\n password substack system-auth\n\n If no results are returned, the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Configure PAM to utilize /etc/pam.d/system-auth when changing passwords.\n\n Add the following line to \\\"/etc/pam.d/passwd\\\" (or modify the line to have\nthe required value):\n\n password substack system-auth\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000069-GPOS-00037\"\n tag gid: \"V-81003\"\n tag rid: \"SV-95715r1_rule\"\n tag stig_id: \"RHEL-07-010118\"\n tag fix_id: \"F-87837r1_fix\"\n tag cci: [\"CCI-000192\"]\n tag nist: [\"IA-5 (1) (a)\"]\n\n # Get the content of /etc/pam.d/passwd as an array\n pam_passwd_content = file('/etc/pam.d/passwd').content.strip.split(\"\\n\")\n # Make a new array of any line matching the target pattern:\n # /password\\s+substack\\s+system-auth\n matching_lines = pam_passwd_content.select { |i| i.match(/password\\s+substack\\s+system-auth/) }\n\n describe '/etc/pam.d/passwd' do\n subject { matching_lines }\n it 'substacks system-auth' do\n expect(subject.length).to(eql 1)\n end\n end\nend\n","desc":"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.","descriptions":[{"data":"Pluggable authentication modules (PAM) allow for a modular approach to\nintegrating authentication methods. PAM operates in a top-down processing model\nand if the modules are not listed in the correct order, an important security\nfunction could be bypassed if stack entries are not centralized.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that /etc/pam.d/passwd is configured to use /etc/pam.d/system-auth\nwhen changing passwords:\n\n # cat /etc/pam.d/passwd | grep -i substack | grep -i system-auth\n password substack system-auth\n\n If no results are returned, the line is commented out, this is a finding.","label":"check"},{"data":"Configure PAM to utilize /etc/pam.d/system-auth when changing passwords.\n\n Add the following line to \"/etc/pam.d/passwd\" (or modify the line to have\nthe required value):\n\n password substack system-auth","label":"fix"}],"id":"V-81003","impact":0.5,"refs":[],"results":[{"code_desc":"/etc/pam.d/passwd substacks system-auth","run_time":0.0024757,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81003.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000069-GPOS-00037","gid":"V-81003","rid":"SV-95715r1_rule","stig_id":"RHEL-07-010118","fix_id":"F-87837r1_fix","cci":["CCI-000192"],"nist":["IA-5 (1) (a)"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing\npasswords.","waiver_data":{}},{"code":"control \"V-81005\" do\n title \"Red Hat Enterprise Linux operating systems version 7.2 or newer with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use UEFI, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -iw grub2_password /boot/grub2/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \\\"grub.pbkdf2.sha512\\\", this is a\nfinding.\n\n Verify that the \\\"root\\\" account is set as the \\\"superusers\\\":\n\n # grep -iw \\\"superusers\\\" /boot/grub2/grub.cfg\n set superusers=\\\"root\\\"\n export superusers\n\n If \\\"superusers\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/grub2/grub.cfg file and add or modify the following lines in\nthe \\\"### BEGIN /etc/grub.d/01_users ###\\\" section:\n\n set superusers=\\\"root\\\"\n export superusers\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-81005\"\n tag rid: \"SV-95717r1_rule\"\n tag stig_id: \"RHEL-07-010482\"\n tag fix_id: \"F-87839r2_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n if file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running UEFI\" do\n skip \"The System is running UEFI, this control is Not Applicable.\"\n end\n else\n unless os[:release] >= \"7.2\"\n impact 0.0\n describe \"System running version of RHEL prior to 7.2\" do\n skip \"The System is running an outdated version of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n input('grub_user_boot_files').each do |grub_user_file|\n describe parse_config_file(grub_user_file) do\n its('GRUB2_PASSWORD') { should include \"grub.pbkdf2.sha512\"}\n end\n end\n\n describe parse_config_file(input('grub_main_cfg')) do\n its('set superusers') { should cmp '\"root\"' } \n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use UEFI, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use a\nBIOS, use the following command:\n\n # grep -iw grub2_password /boot/grub2/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \"grub.pbkdf2.sha512\", this is a\nfinding.\n\n Verify that the \"root\" account is set as the \"superusers\":\n\n # grep -iw \"superusers\" /boot/grub2/grub.cfg\n set superusers=\"root\"\n export superusers\n\n If \"superusers\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/grub2/grub.cfg file and add or modify the following lines in\nthe \"### BEGIN /etc/grub.d/01_users ###\" section:\n\n set superusers=\"root\"\n export superusers","label":"fix"}],"id":"V-81005","impact":0.7,"refs":[],"results":[{"code_desc":"Parse Config File /boot/grub2/user.cfg","resource":"Parse Config File /boot/grub2/user.cfg","run_time":0.000011909,"skip_message":"Can't find file: /boot/grub2/user.cfg","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"parse_config_file","resource_params":"[\"/boot/grub2/user.cfg\"]"},{"code_desc":"Parse Config File /boot/grub2/grub.cfg set superusers is expected to cmp == \"\\\"root\\\"\"","run_time":0.00046492,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"parse_config_file","resource_params":"[\"/boot/grub2/grub.cfg\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81005.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-81005","rid":"SV-95717r1_rule","stig_id":"RHEL-07-010482","fix_id":"F-87839r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems version 7.2 or newer with a\nBasic Input/Output System (BIOS) must require authentication upon booting into\nsingle-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-81007\" do\n title \"Red Hat Enterprise Linux operating systems version 7.2 or newer using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.\"\n desc \"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n For systems that use BIOS, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \\\"grub.pbkdf2.sha512\\\", this is a\nfinding.\n\n Verify that the \\\"root\\\" account is set as the \\\"superusers\\\":\n\n # grep -iw \\\"superusers\\\" /boot/efi/EFI/redhat/grub.cfg\n set superusers=\\\"root\\\"\n export superusers\n\n If \\\"superusers\\\" is not set to \\\"root\\\", this is a finding.\n \"\n desc \"fix\", \"\n Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/efi/EFI/redhat/grub.cfg file and add or modify the following\nlines in the \\\"### BEGIN /etc/grub.d/01_users ###\\\" section:\n\n set superusers=\\\"root\\\"\n export superusers\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000080-GPOS-00048\"\n tag gid: \"V-81007\"\n tag rid: \"SV-95719r1_rule\"\n tag stig_id: \"RHEL-07-010491\"\n tag fix_id: \"F-87841r2_fix\"\n tag cci: [\"CCI-000213\"]\n tag nist: [\"AC-3\"]\n\n unless file('/sys/firmware/efi').exist?\n impact 0.0\n describe \"System running BIOS\" do\n skip \"The System is running BIOS, this control is Not Applicable.\"\n end\n else\n unless os[:release] >= \"7.2\"\n impact 0.0\n describe \"System running version of RHEL prior to 7.2\" do\n skip \"The System is running an outdated version of RHEL, this control is Not Applicable.\"\n end\n else\n impact 0.7\n input('grub_uefi_user_boot_files').each do |grub_user_file|\n describe parse_config_file(grub_user_file) do\n its('GRUB2_PASSWORD') { should include \"grub.pbkdf2.sha512\"}\n end\n end\n\n describe parse_config_file(input('grub_uefi_main_cfg')) do\n its('set superusers') { should cmp '\"root\"' } \n end\n end\n end\nend\n","desc":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","descriptions":[{"data":"If the system does not require valid root authentication before it\nboots into single-user or maintenance mode, anyone who invokes single-user or\nmaintenance mode is granted privileged access to all files on the system. GRUB\n2 is the default boot loader for RHEL 7 and is designed to require a password\nto boot into single-user mode or make modifications to the boot menu.","label":"default"},{"data":"","label":"rationale"},{"data":"For systems that use BIOS, this is Not Applicable.\n\n For systems that are running a version of RHEL prior to 7.2, this is Not\nApplicable.\n\n Check to see if an encrypted root password is set. On systems that use\nUEFI, use the following command:\n\n # grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg\n GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]\n\n If the root password does not begin with \"grub.pbkdf2.sha512\", this is a\nfinding.\n\n Verify that the \"root\" account is set as the \"superusers\":\n\n # grep -iw \"superusers\" /boot/efi/EFI/redhat/grub.cfg\n set superusers=\"root\"\n export superusers\n\n If \"superusers\" is not set to \"root\", this is a finding.","label":"check"},{"data":"Configure the system to encrypt the boot password for root.\n\n Generate an encrypted grub2 password for root with the following command:\n\n Note: The hash generated is an example.\n\n # grub2-setpassword\n Enter password:\n Confirm password:\n\n Edit the /boot/efi/EFI/redhat/grub.cfg file and add or modify the following\nlines in the \"### BEGIN /etc/grub.d/01_users ###\" section:\n\n set superusers=\"root\"\n export superusers","label":"fix"}],"id":"V-81007","impact":0,"refs":[],"results":[{"code_desc":"System running BIOS","resource":"","run_time":0.000010374,"skip_message":"The System is running BIOS, this control is Not Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81007.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000080-GPOS-00048","gid":"V-81007","rid":"SV-95719r1_rule","stig_id":"RHEL-07-010491","fix_id":"F-87841r2_fix","cci":["CCI-000213"],"nist":["AC-3"]},"title":"Red Hat Enterprise Linux operating systems version 7.2 or newer using\nUnified Extensible Firmware Interface (UEFI) must require authentication upon\nbooting into single-user and maintenance modes.","waiver_data":{}},{"code":"control \"V-81009\" do\n title \"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nodev option.\"\n desc \"The \\\"nodev\\\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"nodev\\\" option is configured for /dev/shm:\n\n\n # cat /etc/fstab | grep /dev/shm\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \\\"nodev\\\" option is not listed, this is\na finding.\n\n Verify \\\"/dev/shm\\\" is mounted with the \\\"nodev\\\" option:\n\n # mount | grep \\\"/dev/shm\\\" | grep nodev\n\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the system so that /dev/shm is mounted with the\n\\\"nodev\\\" option.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000368-GPOS-00154\"\n tag gid: \"V-81009\"\n tag rid: \"SV-95721r2_rule\"\n tag stig_id: \"RHEL-07-021022\"\n tag fix_id: \"F-87843r2_fix\"\n tag cci: [\"CCI-001764\"]\n tag nist: [\"CM-7 (2)\"]\n\n describe mount('/dev/shm') do\n its('options') { should include 'nodev' }\n end\nend\n","desc":"The \"nodev\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","descriptions":[{"data":"The \"nodev\" mount option causes the system to not interpret\ncharacter or block special devices. Executing character or block special\ndevices from untrusted file systems increases the opportunity for unprivileged\nusers to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"nodev\" option is configured for /dev/shm:\n\n\n # cat /etc/fstab | grep /dev/shm\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"nodev\" option is not listed, this is\na finding.\n\n Verify \"/dev/shm\" is mounted with the \"nodev\" option:\n\n # mount | grep \"/dev/shm\" | grep nodev\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"nodev\" option.","label":"fix"}],"id":"V-81009","impact":0.3,"refs":[],"results":[{"code_desc":"Mount /dev/shm options is expected to include \"nodev\"","run_time":0.044705384,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"mount","resource_params":"[\"/dev/shm\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81009.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81009","rid":"SV-95721r2_rule","stig_id":"RHEL-07-021022","fix_id":"F-87843r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nodev option.","waiver_data":{}},{"code":"control \"V-81011\" do\n title \"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nosuid option.\"\n desc \"The \\\"nosuid\\\" mount option causes the system to not execute\n\\\"setuid\\\" and \\\"setgid\\\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \\\"setuid\\\" and \\\"setguid\\\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"nosuid\\\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \\\"nosuid\\\" option is not listed, this\nis a finding.\n\n Verify \\\"/dev/shm\\\" is mounted with the \\\"nosuid\\\" option:\n\n # mount | grep \\\"/dev/shm\\\" | grep nosuid\n\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the system so that /dev/shm is mounted with the\n\\\"nosuid\\\" option.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000368-GPOS-00154\"\n tag gid: \"V-81011\"\n tag rid: \"SV-95723r2_rule\"\n tag stig_id: \"RHEL-07-021023\"\n tag fix_id: \"F-87845r2_fix\"\n tag cci: [\"CCI-001764\"]\n tag nist: [\"CM-7 (2)\"]\n\n describe mount('/dev/shm') do\n its('options') { should include 'nosuid' }\n end\nend\n","desc":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","descriptions":[{"data":"The \"nosuid\" mount option causes the system to not execute\n\"setuid\" and \"setgid\" files with owner privileges. This option must be used\nfor mounting any file system not containing approved \"setuid\" and \"setguid\"\nfiles. Executing files from untrusted file systems increases the opportunity\nfor unprivileged users to attain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"nosuid\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"nosuid\" option is not listed, this\nis a finding.\n\n Verify \"/dev/shm\" is mounted with the \"nosuid\" option:\n\n # mount | grep \"/dev/shm\" | grep nosuid\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"nosuid\" option.","label":"fix"}],"id":"V-81011","impact":0.3,"refs":[],"results":[{"code_desc":"Mount /dev/shm options is expected to include \"nosuid\"","run_time":0.000474178,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"mount","resource_params":"[\"/dev/shm\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81011.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81011","rid":"SV-95723r2_rule","stig_id":"RHEL-07-021023","fix_id":"F-87845r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe nosuid option.","waiver_data":{}},{"code":"control \"V-81013\" do\n title \"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe noexec option.\"\n desc \"The \\\"noexec\\\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify that the \\\"noexec\\\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \\\"noexec\\\" option is not listed, this\nis a finding.\n\n Verify \\\"/dev/shm\\\" is mounted with the \\\"noexec\\\" option:\n\n # mount | grep \\\"/dev/shm\\\" | grep noexec\n\n If no results are returned, this is a finding.\n \"\n desc \"fix\", \"Configure the system so that /dev/shm is mounted with the\n\\\"noexec\\\" option.\"\n impact 0.3\n tag severity: nil\n tag gtitle: \"SRG-OS-000368-GPOS-00154\"\n tag gid: \"V-81013\"\n tag rid: \"SV-95725r2_rule\"\n tag stig_id: \"RHEL-07-021024\"\n tag fix_id: \"F-87847r2_fix\"\n tag cci: [\"CCI-001764\"]\n tag nist: [\"CM-7 (2)\"]\n\n describe mount('/dev/shm') do\n its('options') { should include 'noexec' }\n end\nend\n","desc":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","descriptions":[{"data":"The \"noexec\" mount option causes the system to not execute binary\nfiles. This option must be used for mounting any file system not containing\napproved binary files as they may be incompatible. Executing files from\nuntrusted file systems increases the opportunity for unprivileged users to\nattain unauthorized administrative access.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify that the \"noexec\" option is configured for /dev/shm:\n\n # cat /etc/fstab | grep /dev/shm\n\n tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0\n\n If any results are returned and the \"noexec\" option is not listed, this\nis a finding.\n\n Verify \"/dev/shm\" is mounted with the \"noexec\" option:\n\n # mount | grep \"/dev/shm\" | grep noexec\n\n If no results are returned, this is a finding.","label":"check"},{"data":"Configure the system so that /dev/shm is mounted with the\n\"noexec\" option.","label":"fix"}],"id":"V-81013","impact":0.3,"refs":[],"results":[{"code_desc":"Mount /dev/shm options is expected to include \"noexec\"","message":"expected [\"rw\", \"nosuid\", \"nodev\", \"seclabel\"] to include \"noexec\"","run_time":0.000625526,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"mount","resource_params":"[\"/dev/shm\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81013.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000368-GPOS-00154","gid":"V-81013","rid":"SV-95725r2_rule","stig_id":"RHEL-07-021024","fix_id":"F-87847r2_fix","cci":["CCI-001764"],"nist":["CM-7 (2)"]},"title":"The Red Hat Enterprise Linux operating system must mount /dev/shm with\nthe noexec option.","waiver_data":{}},{"code":"control \"V-81015\" do\n title \"The Red Hat Enterprise Linux operating system must be configured to\nuse the au-remote plugin.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \\\"au-remote\\\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the \\\"au-remote\\\" plugin is active on the system:\n\n # grep \\\"active\\\" /etc/audisp/plugins.d/au-remote.conf\n\n active = yes\n\n If the \\\"active\\\" setting is not set to \\\"yes\\\", or the line is commented\nout, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/plugins.d/au-remote.conf file and change the value of\n\\\"active\\\" to \\\"yes\\\".\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81015\"\n tag rid: \"SV-95727r1_rule\"\n tag stig_id: \"RHEL-07-030200\"\n tag fix_id: \"F-87849r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n test_file = '/etc/audisp/plugins.d/au-remote.conf'\n\n if file(test_file).exist?\n describe parse_config_file(test_file) do\n its('active') { should match %r{yes$} }\n end\n else\n describe \"File '#{test_file}' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '#{test_file}' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off-load the logs from the system being audited.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the \"au-remote\" plugin is active on the system:\n\n # grep \"active\" /etc/audisp/plugins.d/au-remote.conf\n\n active = yes\n\n If the \"active\" setting is not set to \"yes\", or the line is commented\nout, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/plugins.d/au-remote.conf file and change the value of\n\"active\" to \"yes\".\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81015","impact":0.5,"refs":[],"results":[{"code_desc":"File '/etc/audisp/plugins.d/au-remote.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually","resource":"","run_time":0.000015853,"skip_message":"File '/etc/audisp/plugins.d/au-remote.conf' cannot be found. This check must be performed manually","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81015.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81015","rid":"SV-95727r1_rule","stig_id":"RHEL-07-030200","fix_id":"F-87849r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must be configured to\nuse the au-remote plugin.","waiver_data":{}},{"code":"control \"V-81017\" do\n title \"The Red Hat Enterprise Linux operating system must configure the\nau-remote plugin to off-load audit logs using the audisp-remote daemon.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \\\"au-remote\\\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the \\\"au-remote\\\" plugin is configured to always off-load audit logs\nusing the audisp-remote daemon:\n\n # cat /etc/audisp/plugins.d/au-remote.conf | grep -v \\\"^#\\\"\n\n active = yes\n direction = out\n path = /sbin/audisp-remote\n type = always\n format = string\n\n If the \\\"direction\\\" setting is not set to \\\"out\\\", or the line is\ncommented out, this is a finding.\n\n If the \\\"path\\\" setting is not set to \\\"/sbin/audisp-remote\\\", or the line\nis commented out, this is a finding.\n\n If the \\\"type\\\" setting is not set to \\\"always\\\", or the line is commented\nout, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/plugins.d/au-remote.conf file and add or update the\nfollowing values:\n\n direction = out\n path = /sbin/audisp-remote\n type = always\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81017\"\n tag rid: \"SV-95729r1_rule\"\n tag stig_id: \"RHEL-07-030201\"\n tag fix_id: \"F-87851r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n test_file = '/etc/audisp/plugins.d/au-remote.conf'\n\n if file(test_file).exist?\n describe parse_config_file(test_file) do\n its('direction') { should match %r{out$} }\n its('path') { should match %r{/sbin/audisp-remote$} }\n its('type') { should match %r{always$} }\n end\n else\n describe \"File '#{test_file}' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '#{test_file}' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n Without the configuration of the \"au-remote\" plugin, the audisp-remote\ndaemon will not off load the logs from the system being audited.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the \"au-remote\" plugin is configured to always off-load audit logs\nusing the audisp-remote daemon:\n\n # cat /etc/audisp/plugins.d/au-remote.conf | grep -v \"^#\"\n\n active = yes\n direction = out\n path = /sbin/audisp-remote\n type = always\n format = string\n\n If the \"direction\" setting is not set to \"out\", or the line is\ncommented out, this is a finding.\n\n If the \"path\" setting is not set to \"/sbin/audisp-remote\", or the line\nis commented out, this is a finding.\n\n If the \"type\" setting is not set to \"always\", or the line is commented\nout, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/plugins.d/au-remote.conf file and add or update the\nfollowing values:\n\n direction = out\n path = /sbin/audisp-remote\n type = always\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81017","impact":0.5,"refs":[],"results":[{"code_desc":"File '/etc/audisp/plugins.d/au-remote.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually","resource":"","run_time":0.000009621,"skip_message":"File '/etc/audisp/plugins.d/au-remote.conf' cannot be found. This check must be performed manually","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81017.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81017","rid":"SV-95729r1_rule","stig_id":"RHEL-07-030201","fix_id":"F-87851r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must configure the\nau-remote plugin to off-load audit logs using the audisp-remote daemon.","waiver_data":{}},{"code":"control \"V-81019\" do\n title \"The Red Hat Enterprise Linux operating system must take appropriate\naction when the audisp-remote buffer is full.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the audisp daemon is configured to take an appropriate action when\nthe internal queue is full:\n\n # grep \\\"overflow_action\\\" /etc/audisp/audispd.conf\n\n overflow_action = syslog\n\n If the \\\"overflow_action\\\" option is not \\\"syslog\\\", \\\"single\\\", or\n\\\"halt\\\", or the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/audispd.conf file and add or update the\n\\\"overflow_action\\\" option:\n\n overflow_action = syslog\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81019\"\n tag rid: \"SV-95731r1_rule\"\n tag stig_id: \"RHEL-07-030210\"\n tag fix_id: \"F-87853r3_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n if file('/etc/audisp/audispd.conf').exist?\n describe parse_config_file('/etc/audisp/audispd.conf') do\n its('overflow_action') { should match %r{syslog$|single$|halt$}i }\n end\n else\n describe \"File '/etc/audisp/audispd.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '/etc/audisp/audispd.conf' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When the remote buffer is full, audit logs will not be collected and sent\nto the central log server.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the audisp daemon is configured to take an appropriate action when\nthe internal queue is full:\n\n # grep \"overflow_action\" /etc/audisp/audispd.conf\n\n overflow_action = syslog\n\n If the \"overflow_action\" option is not \"syslog\", \"single\", or\n\"halt\", or the line is commented out, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/audispd.conf file and add or update the\n\"overflow_action\" option:\n\n overflow_action = syslog\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81019","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/audisp/audispd.conf overflow_action is expected to match /syslog$|single$|halt$/i","run_time":0.000377816,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"parse_config_file","resource_params":"[\"/etc/audisp/audispd.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81019.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81019","rid":"SV-95731r1_rule","stig_id":"RHEL-07-030210","fix_id":"F-87853r3_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must take appropriate\naction when the audisp-remote buffer is full.","waiver_data":{}},{"code":"control \"V-81021\" do\n title \"The Red Hat Enterprise Linux operating system must label all\noff-loaded audit logs before sending them to the central log server.\"\n desc \"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.\n\n\n \"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the audisp daemon is configured to label all off-loaded audit logs:\n\n # grep \\\"name_format\\\" /etc/audisp/audispd.conf\n\n name_format = hostname\n\n If the \\\"name_format\\\" option is not \\\"hostname\\\", \\\"fqd\\\", or \\\"numeric\\\",\nor the line is commented out, this is a finding.\n \"\n desc \"fix\", \"\n Edit the /etc/audisp/audispd.conf file and add or update the\n\\\"name_format\\\" option:\n\n name_format = hostname\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000342-GPOS-00133\"\n tag satisfies: [\"SRG-OS-000342-GPOS-00133\", \"SRG-OS-000479-GPOS-00224\"]\n tag gid: \"V-81021\"\n tag rid: \"SV-95733r1_rule\"\n tag stig_id: \"RHEL-07-030211\"\n tag fix_id: \"F-87855r2_fix\"\n tag cci: [\"CCI-001851\"]\n tag nist: [\"AU-4 (1)\"]\n\n if file('/etc/audisp/audispd.conf').exist?\n describe parse_config_file('/etc/audisp/audispd.conf') do\n its('name_format') { should match %r{^hostname$|^fqd$|^numeric$}i }\n end\n else\n describe \"File '/etc/audisp/audispd.conf' cannot be found. This test cannot be checked in a automated fashion and you must check it manually\" do\n skip \"File '/etc/audisp/audispd.conf' cannot be found. This check must be performed manually\"\n end\n end\nend\n","desc":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.","descriptions":[{"data":"Information stored in one location is vulnerable to accidental or\nincidental deletion or alteration.\n\n Off-loading is a common process in information systems with limited audit\nstorage capacity.\n\n When audit logs are not labeled before they are sent to a central log\nserver, the audit data will not be able to be analyzed and tied back to the\ncorrect system.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the audisp daemon is configured to label all off-loaded audit logs:\n\n # grep \"name_format\" /etc/audisp/audispd.conf\n\n name_format = hostname\n\n If the \"name_format\" option is not \"hostname\", \"fqd\", or \"numeric\",\nor the line is commented out, this is a finding.","label":"check"},{"data":"Edit the /etc/audisp/audispd.conf file and add or update the\n\"name_format\" option:\n\n name_format = hostname\n\n The audit daemon must be restarted for changes to take effect:\n\n # service auditd restart","label":"fix"}],"id":"V-81021","impact":0.5,"refs":[],"results":[{"code_desc":"Parse Config File /etc/audisp/audispd.conf name_format is expected to match /^hostname$|^fqd$|^numeric$/i","run_time":0.0003013,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"parse_config_file","resource_params":"[\"/etc/audisp/audispd.conf\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-81021.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000342-GPOS-00133","satisfies":["SRG-OS-000342-GPOS-00133","SRG-OS-000479-GPOS-00224"],"gid":"V-81021","rid":"SV-95733r1_rule","stig_id":"RHEL-07-030211","fix_id":"F-87855r2_fix","cci":["CCI-001851"],"nist":["AU-4 (1)"]},"title":"The Red Hat Enterprise Linux operating system must label all\noff-loaded audit logs before sending them to the central log server.","waiver_data":{}},{"code":"control \"V-92251\" do\n title \"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible on all interfaces.\"\n desc \"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.all.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.all.rp_filter = 1\n\n If \\\"net.ipv4.conf.all.rp_filter\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"1\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.rp_filter\n net.ipv4.conf.all.rp_filter = 1\n\n If the returned line does not have a value of \\\"1\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-92251\"\n tag rid: \"SV-102353r1_rule\"\n tag stig_id: \"RHEL-07-040611\"\n tag fix_id: \"F-98473r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.all.rp_filter') do\n its('value') { should eq 1 }\n end\nend\n","desc":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","descriptions":[{"data":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.all.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.all.rp_filter = 1\n\n If \"net.ipv4.conf.all.rp_filter\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.all.rp_filter\n net.ipv4.conf.all.rp_filter = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.all.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-92251","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.all.rp_filter value is expected to eq 1","run_time":0.056404455,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.all.rp_filter\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92251.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-92251","rid":"SV-102353r1_rule","stig_id":"RHEL-07-040611","fix_id":"F-98473r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible on all interfaces.","waiver_data":{}},{"code":"control \"V-92253\" do\n title \"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible by default.\"\n desc \"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.default.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.default.rp_filter = 1\n\n If \\\"net.ipv4.conf.default.rp_filter\\\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \\\"1\\\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.rp_filter\n net.ipv4.conf.default.rp_filter = 1\n\n If the returned line does not have a value of \\\"1\\\", this is a finding.\n \"\n desc \"fix\", \"\n Set the system to the required kernel parameter by adding the following\nline to \\\"/etc/sysctl.conf\\\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-92253\"\n tag rid: \"SV-102355r1_rule\"\n tag stig_id: \"RHEL-07-040612\"\n tag fix_id: \"F-98475r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n describe kernel_parameter('net.ipv4.conf.default.rp_filter') do\n its('value') { should eq 1 }\n end\nend\n","desc":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","descriptions":[{"data":"Enabling reverse path filtering drops packets with source addresses\nthat should not have been able to be received on the interface they were\nreceived on. It should not be used on systems which are routers for complicated\nnetworks, but is helpful for end hosts and routers serving small networks.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the system uses a reverse-path filter for IPv4:\n\n # grep net.ipv4.conf.default.rp_filter /etc/sysctl.conf /etc/sysctl.d/*\n net.ipv4.conf.default.rp_filter = 1\n\n If \"net.ipv4.conf.default.rp_filter\" is not configured in the\n/etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or\ndoes not have a value of \"1\", this is a finding.\n\n Check that the operating system implements the accept source route variable\nwith the following command:\n\n # /sbin/sysctl -a | grep net.ipv4.conf.default.rp_filter\n net.ipv4.conf.default.rp_filter = 1\n\n If the returned line does not have a value of \"1\", this is a finding.","label":"check"},{"data":"Set the system to the required kernel parameter by adding the following\nline to \"/etc/sysctl.conf\" or a configuration file in the /etc/sysctl.d/\ndirectory (or modify the line to have the required value):\n\n net.ipv4.conf.default.rp_filter = 1\n\n Issue the following command to make the changes take effect:\n\n # sysctl --system","label":"fix"}],"id":"V-92253","impact":0.5,"refs":[],"results":[{"code_desc":"Kernel Parameter net.ipv4.conf.default.rp_filter value is expected to eq 1","run_time":0.038360035,"start_time":"2022-03-06T22:06:10+00:00","status":"passed","resource_class":"kernel_parameter","resource_params":"[\"net.ipv4.conf.default.rp_filter\"]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92253.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-92253","rid":"SV-102355r1_rule","stig_id":"RHEL-07-040612","fix_id":"F-98475r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must use a reverse-path\nfilter for IPv4 network traffic when possible by default.","waiver_data":{}},{"code":"control \"V-92255\" do\n title \"The Red Hat Enterprise Linux operating system must have a host-based\nintrusion detection tool installed.\"\n desc \"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Ask the SA or ISSO if a host-based intrusion detection application is\nloaded on the system. Per OPORD 16-0080, the preferred intrusion detection\nsystem is McAfee HBSS available through the U.S. Cyber Command (USCYBERCOM).\n\n If another host-based intrusion detection application is in use, such as\nSELinux, this must be documented and approved by the local Authorizing Official.\n\n Procedure:\n Examine the system to determine if the Host Intrusion Prevention System\n(HIPS) is installed:\n\n # rpm -qa | grep MFEhiplsm\n\n Verify that the McAfee HIPS module is active on the system:\n\n # ps -ef | grep -i “hipclient”\n\n If the MFEhiplsm package is not installed, check for another intrusion\ndetection system:\n\n # find / -name \n\n Where is the name of the primary application daemon to\ndetermine if the application is loaded on the system.\n\n Determine if the application is active on the system:\n\n # ps -ef | grep -i \n\n If the MFEhiplsm package is not installed and an alternate host-based\nintrusion detection application has not been documented for use, this is a\nfinding.\n\n If no host-based intrusion detection system is installed and running on the\nsystem, this is a finding.\n \"\n desc \"fix\", \"\n Install and enable the latest McAfee HIPS package, available from\nUSCYBERCOM.\n\n Note: If the system does not support the McAfee HIPS package, install and\nenable a supported intrusion detection system application and document its use\nwith the Authorizing Official.\n \"\n impact 0.5\n tag severity: nil\n tag gtitle: \"SRG-OS-000196\"\n tag gid: \"V-92255\"\n tag rid: \"SV-102357r1_rule\"\n tag stig_id: \"RHEL-07-020019\"\n tag fix_id: \"F-98477r1_fix\"\n tag cci: [\"CCI-001263\"]\n tag nist: [\"SI-4 (5)\"]\n\n custom_hips = input('custom_hips')\n\n if ! custom_hips\n describe package('MFEhiplsm') do\n it { should be_installed }\n end\n describe processes(/hipclient/) do\n it { should exist }\n end\n else\n # Special case for SELinux\n sel_mode = command('getenforce').stdout.strip\n custom_hips_daemon = input('custom_hips_daemon')\n max_daemon_processes = input('max_daemon_processes')\n\n describe.one do\n describe \"SELinux mode\" do\n subject { sel_mode }\n it { should cmp 'Enforcing' }\n end\n describe processes(/#{custom_hips_daemon}/) do\n it { should exist }\n its('count') { should be < max_daemon_processes }\n end\n end\n end\nend\n","desc":"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.","descriptions":[{"data":"Adding host-based intrusion detection tools can provide the capability\nto automatically take actions in response to malicious behavior, which can\nprovide additional agility in reacting to network threats. These tools also\noften include a reporting capability to provide network awareness of the\nsystem, which may not otherwise exist in an organization's systems management\nregime.","label":"default"},{"data":"","label":"rationale"},{"data":"Ask the SA or ISSO if a host-based intrusion detection application is\nloaded on the system. Per OPORD 16-0080, the preferred intrusion detection\nsystem is McAfee HBSS available through the U.S. Cyber Command (USCYBERCOM).\n\n If another host-based intrusion detection application is in use, such as\nSELinux, this must be documented and approved by the local Authorizing Official.\n\n Procedure:\n Examine the system to determine if the Host Intrusion Prevention System\n(HIPS) is installed:\n\n # rpm -qa | grep MFEhiplsm\n\n Verify that the McAfee HIPS module is active on the system:\n\n # ps -ef | grep -i “hipclient”\n\n If the MFEhiplsm package is not installed, check for another intrusion\ndetection system:\n\n # find / -name \n\n Where is the name of the primary application daemon to\ndetermine if the application is loaded on the system.\n\n Determine if the application is active on the system:\n\n # ps -ef | grep -i \n\n If the MFEhiplsm package is not installed and an alternate host-based\nintrusion detection application has not been documented for use, this is a\nfinding.\n\n If no host-based intrusion detection system is installed and running on the\nsystem, this is a finding.","label":"check"},{"data":"Install and enable the latest McAfee HIPS package, available from\nUSCYBERCOM.\n\n Note: If the system does not support the McAfee HIPS package, install and\nenable a supported intrusion detection system application and document its use\nwith the Authorizing Official.","label":"fix"}],"id":"V-92255","impact":0.5,"refs":[],"results":[{"code_desc":"System Package MFEhiplsm is expected to be installed","message":"expected that `System Package MFEhiplsm` is installed","run_time":0.000445634,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"package","resource_params":"[\"MFEhiplsm\"]"},{"code_desc":"Processes /hipclient/ is expected to exist","message":"expected Processes /hipclient/ to exist","run_time":0.000238656,"start_time":"2022-03-06T22:06:10+00:00","status":"failed","resource_class":"processes","resource_params":"[/hipclient/]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-92255.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000196","gid":"V-92255","rid":"SV-102357r1_rule","stig_id":"RHEL-07-020019","fix_id":"F-98477r1_fix","cci":["CCI-001263"],"nist":["SI-4 (5)"]},"title":"The Red Hat Enterprise Linux operating system must have a host-based\nintrusion detection tool installed.","waiver_data":{}},{"code":"control \"V-94843\" do\n title \"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled in the GUI.\"\n desc \"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.\"\n desc \"rationale\", \"\"\n desc \"check\", \"\n Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active in the GUI with\nthe following command:\n\n # grep logout /etc/dconf/local.d/*\n\n logout=''\n\n If \\\"logout\\\" is not set to use two single quotations, or is missing, this\nis a finding.\n \"\n desc \"fix\", \"\n Configure the system to disable the Ctrl-Alt-Delete sequence for the GUI\nwith the following command:\n\n # touch /etc/dconf/db/local.d/00-disable-CAD\n\n Add the setting to disable the Ctrl-Alt-Delete sequence for GNOME:\n\n [org/gnome/settings-daemon/plugins/media-keys]\n logout=''\n \"\n impact 0.7\n tag severity: nil\n tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n tag gid: \"V-94843\"\n tag rid: \"SV-104673r1_rule\"\n tag stig_id: \"RHEL-07-020231\"\n tag fix_id: \"F-100967r1_fix\"\n tag cci: [\"CCI-000366\"]\n tag nist: [\"CM-6 b\"]\n\n unless package('gnome-settings-daemon').installed?\n impact 0.0\n describe \"The system does not have GNOME installed\" do\n skip \"The system does not have GNOME installed, this requirement is Not\n Applicable.\"\n end\n else \n describe command(\"gsettings get org.gnome.settings-daemon.media-keys logout\") do\n its('stdout.strip') { should cmp \"''\" }\n end \n end\nend\n","desc":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","descriptions":[{"data":"A locally logged-on user who presses Ctrl-Alt-Delete, when at the\nconsole, can reboot the system. If accidentally pressed, as could happen in the\ncase of a mixed OS environment, this can create the risk of short-term loss of\navailability of systems due to unintentional reboot. In the GNOME graphical\nenvironment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is\nreduced because the user will be prompted before any action is taken.","label":"default"},{"data":"","label":"rationale"},{"data":"Verify the operating system is not configured to reboot the system when\nCtrl-Alt-Delete is pressed.\n\n Check that the ctrl-alt-del.target is masked and not active in the GUI with\nthe following command:\n\n # grep logout /etc/dconf/local.d/*\n\n logout=''\n\n If \"logout\" is not set to use two single quotations, or is missing, this\nis a finding.","label":"check"},{"data":"Configure the system to disable the Ctrl-Alt-Delete sequence for the GUI\nwith the following command:\n\n # touch /etc/dconf/db/local.d/00-disable-CAD\n\n Add the setting to disable the Ctrl-Alt-Delete sequence for GNOME:\n\n [org/gnome/settings-daemon/plugins/media-keys]\n logout=''","label":"fix"}],"id":"V-94843","impact":0,"refs":[],"results":[{"code_desc":"The system does not have GNOME installed","resource":"","run_time":0.00001088,"skip_message":"The system does not have GNOME installed, this requirement is Not\n Applicable.","start_time":"2022-03-06T22:06:10+00:00","status":"skipped","resource_class":"Object","resource_params":"[]"}],"source_location":{"line":2,"ref":"redhat-enterprise-linux-7-stig-baseline-master/controls/V-94843.rb"},"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-94843","rid":"SV-104673r1_rule","stig_id":"RHEL-07-020231","fix_id":"F-100967r1_fix","cci":["CCI-000366"],"nist":["CM-6 b"]},"title":"The Red Hat Enterprise Linux operating system must be configured so\nthat the x86 Ctrl-Alt-Delete key sequence is disabled in the GUI.","waiver_data":{}}],"copyright":"MITRE, 2020","copyright_email":"saf@groups.mitre.org","groups":[{"controls":["V-71849"],"id":"controls/V-71849.rb"},{"controls":["V-71855"],"id":"controls/V-71855.rb"},{"controls":["V-71859"],"id":"controls/V-71859.rb"},{"controls":["V-71861"],"id":"controls/V-71861.rb"},{"controls":["V-71863"],"id":"controls/V-71863.rb"},{"controls":["V-71891"],"id":"controls/V-71891.rb"},{"controls":["V-71893"],"id":"controls/V-71893.rb"},{"controls":["V-71897"],"id":"controls/V-71897.rb"},{"controls":["V-71899"],"id":"controls/V-71899.rb"},{"controls":["V-71901"],"id":"controls/V-71901.rb"},{"controls":["V-71903"],"id":"controls/V-71903.rb"},{"controls":["V-71905"],"id":"controls/V-71905.rb"},{"controls":["V-71907"],"id":"controls/V-71907.rb"},{"controls":["V-71909"],"id":"controls/V-71909.rb"},{"controls":["V-71911"],"id":"controls/V-71911.rb"},{"controls":["V-71913"],"id":"controls/V-71913.rb"},{"controls":["V-71915"],"id":"controls/V-71915.rb"},{"controls":["V-71917"],"id":"controls/V-71917.rb"},{"controls":["V-71919"],"id":"controls/V-71919.rb"},{"controls":["V-71921"],"id":"controls/V-71921.rb"},{"controls":["V-71923"],"id":"controls/V-71923.rb"},{"controls":["V-71925"],"id":"controls/V-71925.rb"},{"controls":["V-71927"],"id":"controls/V-71927.rb"},{"controls":["V-71929"],"id":"controls/V-71929.rb"},{"controls":["V-71931"],"id":"controls/V-71931.rb"},{"controls":["V-71933"],"id":"controls/V-71933.rb"},{"controls":["V-71935"],"id":"controls/V-71935.rb"},{"controls":["V-71937"],"id":"controls/V-71937.rb"},{"controls":["V-71939"],"id":"controls/V-71939.rb"},{"controls":["V-71941"],"id":"controls/V-71941.rb"},{"controls":["V-71943"],"id":"controls/V-71943.rb"},{"controls":["V-71945"],"id":"controls/V-71945.rb"},{"controls":["V-71947"],"id":"controls/V-71947.rb"},{"controls":["V-71949"],"id":"controls/V-71949.rb"},{"controls":["V-71951"],"id":"controls/V-71951.rb"},{"controls":["V-71953"],"id":"controls/V-71953.rb"},{"controls":["V-71955"],"id":"controls/V-71955.rb"},{"controls":["V-71957"],"id":"controls/V-71957.rb"},{"controls":["V-71959"],"id":"controls/V-71959.rb"},{"controls":["V-71961"],"id":"controls/V-71961.rb"},{"controls":["V-71963"],"id":"controls/V-71963.rb"},{"controls":["V-71965"],"id":"controls/V-71965.rb"},{"controls":["V-71967"],"id":"controls/V-71967.rb"},{"controls":["V-71969"],"id":"controls/V-71969.rb"},{"controls":["V-71971"],"id":"controls/V-71971.rb"},{"controls":["V-71973"],"id":"controls/V-71973.rb"},{"controls":["V-71975"],"id":"controls/V-71975.rb"},{"controls":["V-71977"],"id":"controls/V-71977.rb"},{"controls":["V-71979"],"id":"controls/V-71979.rb"},{"controls":["V-71983"],"id":"controls/V-71983.rb"},{"controls":["V-71985"],"id":"controls/V-71985.rb"},{"controls":["V-71987"],"id":"controls/V-71987.rb"},{"controls":["V-71989"],"id":"controls/V-71989.rb"},{"controls":["V-71991"],"id":"controls/V-71991.rb"},{"controls":["V-71993"],"id":"controls/V-71993.rb"},{"controls":["V-71995"],"id":"controls/V-71995.rb"},{"controls":["V-71997"],"id":"controls/V-71997.rb"},{"controls":["V-71999"],"id":"controls/V-71999.rb"},{"controls":["V-72001"],"id":"controls/V-72001.rb"},{"controls":["V-72003"],"id":"controls/V-72003.rb"},{"controls":["V-72005"],"id":"controls/V-72005.rb"},{"controls":["V-72007"],"id":"controls/V-72007.rb"},{"controls":["V-72009"],"id":"controls/V-72009.rb"},{"controls":["V-72011"],"id":"controls/V-72011.rb"},{"controls":["V-72013"],"id":"controls/V-72013.rb"},{"controls":["V-72015"],"id":"controls/V-72015.rb"},{"controls":["V-72017"],"id":"controls/V-72017.rb"},{"controls":["V-72019"],"id":"controls/V-72019.rb"},{"controls":["V-72021"],"id":"controls/V-72021.rb"},{"controls":["V-72023"],"id":"controls/V-72023.rb"},{"controls":["V-72025"],"id":"controls/V-72025.rb"},{"controls":["V-72027"],"id":"controls/V-72027.rb"},{"controls":["V-72029"],"id":"controls/V-72029.rb"},{"controls":["V-72031"],"id":"controls/V-72031.rb"},{"controls":["V-72033"],"id":"controls/V-72033.rb"},{"controls":["V-72035"],"id":"controls/V-72035.rb"},{"controls":["V-72037"],"id":"controls/V-72037.rb"},{"controls":["V-72039"],"id":"controls/V-72039.rb"},{"controls":["V-72041"],"id":"controls/V-72041.rb"},{"controls":["V-72043"],"id":"controls/V-72043.rb"},{"controls":["V-72045"],"id":"controls/V-72045.rb"},{"controls":["V-72047"],"id":"controls/V-72047.rb"},{"controls":["V-72049"],"id":"controls/V-72049.rb"},{"controls":["V-72051"],"id":"controls/V-72051.rb"},{"controls":["V-72053"],"id":"controls/V-72053.rb"},{"controls":["V-72055"],"id":"controls/V-72055.rb"},{"controls":["V-72057"],"id":"controls/V-72057.rb"},{"controls":["V-72059"],"id":"controls/V-72059.rb"},{"controls":["V-72061"],"id":"controls/V-72061.rb"},{"controls":["V-72063"],"id":"controls/V-72063.rb"},{"controls":["V-72065"],"id":"controls/V-72065.rb"},{"controls":["V-72067"],"id":"controls/V-72067.rb"},{"controls":["V-72069"],"id":"controls/V-72069.rb"},{"controls":["V-72071"],"id":"controls/V-72071.rb"},{"controls":["V-72073"],"id":"controls/V-72073.rb"},{"controls":["V-72075"],"id":"controls/V-72075.rb"},{"controls":["V-72077"],"id":"controls/V-72077.rb"},{"controls":["V-72079"],"id":"controls/V-72079.rb"},{"controls":["V-72081"],"id":"controls/V-72081.rb"},{"controls":["V-72083"],"id":"controls/V-72083.rb"},{"controls":["V-72085"],"id":"controls/V-72085.rb"},{"controls":["V-72087"],"id":"controls/V-72087.rb"},{"controls":["V-72089"],"id":"controls/V-72089.rb"},{"controls":["V-72091"],"id":"controls/V-72091.rb"},{"controls":["V-72093"],"id":"controls/V-72093.rb"},{"controls":["V-72095"],"id":"controls/V-72095.rb"},{"controls":["V-72097"],"id":"controls/V-72097.rb"},{"controls":["V-72099"],"id":"controls/V-72099.rb"},{"controls":["V-72101"],"id":"controls/V-72101.rb"},{"controls":["V-72103"],"id":"controls/V-72103.rb"},{"controls":["V-72105"],"id":"controls/V-72105.rb"},{"controls":["V-72107"],"id":"controls/V-72107.rb"},{"controls":["V-72109"],"id":"controls/V-72109.rb"},{"controls":["V-72111"],"id":"controls/V-72111.rb"},{"controls":["V-72113"],"id":"controls/V-72113.rb"},{"controls":["V-72115"],"id":"controls/V-72115.rb"},{"controls":["V-72117"],"id":"controls/V-72117.rb"},{"controls":["V-72119"],"id":"controls/V-72119.rb"},{"controls":["V-72121"],"id":"controls/V-72121.rb"},{"controls":["V-72123"],"id":"controls/V-72123.rb"},{"controls":["V-72125"],"id":"controls/V-72125.rb"},{"controls":["V-72127"],"id":"controls/V-72127.rb"},{"controls":["V-72129"],"id":"controls/V-72129.rb"},{"controls":["V-72131"],"id":"controls/V-72131.rb"},{"controls":["V-72133"],"id":"controls/V-72133.rb"},{"controls":["V-72135"],"id":"controls/V-72135.rb"},{"controls":["V-72137"],"id":"controls/V-72137.rb"},{"controls":["V-72139"],"id":"controls/V-72139.rb"},{"controls":["V-72141"],"id":"controls/V-72141.rb"},{"controls":["V-72145"],"id":"controls/V-72145.rb"},{"controls":["V-72147"],"id":"controls/V-72147.rb"},{"controls":["V-72149"],"id":"controls/V-72149.rb"},{"controls":["V-72151"],"id":"controls/V-72151.rb"},{"controls":["V-72153"],"id":"controls/V-72153.rb"},{"controls":["V-72155"],"id":"controls/V-72155.rb"},{"controls":["V-72157"],"id":"controls/V-72157.rb"},{"controls":["V-72159"],"id":"controls/V-72159.rb"},{"controls":["V-72161"],"id":"controls/V-72161.rb"},{"controls":["V-72163"],"id":"controls/V-72163.rb"},{"controls":["V-72165"],"id":"controls/V-72165.rb"},{"controls":["V-72167"],"id":"controls/V-72167.rb"},{"controls":["V-72171"],"id":"controls/V-72171.rb"},{"controls":["V-72173"],"id":"controls/V-72173.rb"},{"controls":["V-72175"],"id":"controls/V-72175.rb"},{"controls":["V-72177"],"id":"controls/V-72177.rb"},{"controls":["V-72179"],"id":"controls/V-72179.rb"},{"controls":["V-72183"],"id":"controls/V-72183.rb"},{"controls":["V-72185"],"id":"controls/V-72185.rb"},{"controls":["V-72187"],"id":"controls/V-72187.rb"},{"controls":["V-72189"],"id":"controls/V-72189.rb"},{"controls":["V-72191"],"id":"controls/V-72191.rb"},{"controls":["V-72197"],"id":"controls/V-72197.rb"},{"controls":["V-72199"],"id":"controls/V-72199.rb"},{"controls":["V-72201"],"id":"controls/V-72201.rb"},{"controls":["V-72203"],"id":"controls/V-72203.rb"},{"controls":["V-72205"],"id":"controls/V-72205.rb"},{"controls":["V-72207"],"id":"controls/V-72207.rb"},{"controls":["V-72209"],"id":"controls/V-72209.rb"},{"controls":["V-72211"],"id":"controls/V-72211.rb"},{"controls":["V-72213"],"id":"controls/V-72213.rb"},{"controls":["V-72217"],"id":"controls/V-72217.rb"},{"controls":["V-72219"],"id":"controls/V-72219.rb"},{"controls":["V-72221"],"id":"controls/V-72221.rb"},{"controls":["V-72223"],"id":"controls/V-72223.rb"},{"controls":["V-72225"],"id":"controls/V-72225.rb"},{"controls":["V-72227"],"id":"controls/V-72227.rb"},{"controls":["V-72229"],"id":"controls/V-72229.rb"},{"controls":["V-72231"],"id":"controls/V-72231.rb"},{"controls":["V-72233"],"id":"controls/V-72233.rb"},{"controls":["V-72235"],"id":"controls/V-72235.rb"},{"controls":["V-72237"],"id":"controls/V-72237.rb"},{"controls":["V-72239"],"id":"controls/V-72239.rb"},{"controls":["V-72241"],"id":"controls/V-72241.rb"},{"controls":["V-72243"],"id":"controls/V-72243.rb"},{"controls":["V-72245"],"id":"controls/V-72245.rb"},{"controls":["V-72247"],"id":"controls/V-72247.rb"},{"controls":["V-72249"],"id":"controls/V-72249.rb"},{"controls":["V-72251"],"id":"controls/V-72251.rb"},{"controls":["V-72253"],"id":"controls/V-72253.rb"},{"controls":["V-72255"],"id":"controls/V-72255.rb"},{"controls":["V-72257"],"id":"controls/V-72257.rb"},{"controls":["V-72259"],"id":"controls/V-72259.rb"},{"controls":["V-72261"],"id":"controls/V-72261.rb"},{"controls":["V-72263"],"id":"controls/V-72263.rb"},{"controls":["V-72265"],"id":"controls/V-72265.rb"},{"controls":["V-72267"],"id":"controls/V-72267.rb"},{"controls":["V-72269"],"id":"controls/V-72269.rb"},{"controls":["V-72273"],"id":"controls/V-72273.rb"},{"controls":["V-72275"],"id":"controls/V-72275.rb"},{"controls":["V-72277"],"id":"controls/V-72277.rb"},{"controls":["V-72279"],"id":"controls/V-72279.rb"},{"controls":["V-72281"],"id":"controls/V-72281.rb"},{"controls":["V-72283"],"id":"controls/V-72283.rb"},{"controls":["V-72285"],"id":"controls/V-72285.rb"},{"controls":["V-72287"],"id":"controls/V-72287.rb"},{"controls":["V-72289"],"id":"controls/V-72289.rb"},{"controls":["V-72291"],"id":"controls/V-72291.rb"},{"controls":["V-72293"],"id":"controls/V-72293.rb"},{"controls":["V-72295"],"id":"controls/V-72295.rb"},{"controls":["V-72297"],"id":"controls/V-72297.rb"},{"controls":["V-72299"],"id":"controls/V-72299.rb"},{"controls":["V-72301"],"id":"controls/V-72301.rb"},{"controls":["V-72303"],"id":"controls/V-72303.rb"},{"controls":["V-72305"],"id":"controls/V-72305.rb"},{"controls":["V-72307"],"id":"controls/V-72307.rb"},{"controls":["V-72309"],"id":"controls/V-72309.rb"},{"controls":["V-72311"],"id":"controls/V-72311.rb"},{"controls":["V-72313"],"id":"controls/V-72313.rb"},{"controls":["V-72315"],"id":"controls/V-72315.rb"},{"controls":["V-72317"],"id":"controls/V-72317.rb"},{"controls":["V-72319"],"id":"controls/V-72319.rb"},{"controls":["V-72417"],"id":"controls/V-72417.rb"},{"controls":["V-72427"],"id":"controls/V-72427.rb"},{"controls":["V-72433"],"id":"controls/V-72433.rb"},{"controls":["V-73155"],"id":"controls/V-73155.rb"},{"controls":["V-73157"],"id":"controls/V-73157.rb"},{"controls":["V-73159"],"id":"controls/V-73159.rb"},{"controls":["V-73161"],"id":"controls/V-73161.rb"},{"controls":["V-73163"],"id":"controls/V-73163.rb"},{"controls":["V-73165"],"id":"controls/V-73165.rb"},{"controls":["V-73167"],"id":"controls/V-73167.rb"},{"controls":["V-73171"],"id":"controls/V-73171.rb"},{"controls":["V-73173"],"id":"controls/V-73173.rb"},{"controls":["V-73175"],"id":"controls/V-73175.rb"},{"controls":["V-73177"],"id":"controls/V-73177.rb"},{"controls":["V-77819"],"id":"controls/V-77819.rb"},{"controls":["V-77821"],"id":"controls/V-77821.rb"},{"controls":["V-77823"],"id":"controls/V-77823.rb"},{"controls":["V-77825"],"id":"controls/V-77825.rb"},{"controls":["V-78995"],"id":"controls/V-78995.rb"},{"controls":["V-78997"],"id":"controls/V-78997.rb"},{"controls":["V-78999"],"id":"controls/V-78999.rb"},{"controls":["V-79001"],"id":"controls/V-79001.rb"},{"controls":["V-81003"],"id":"controls/V-81003.rb"},{"controls":["V-81005"],"id":"controls/V-81005.rb"},{"controls":["V-81007"],"id":"controls/V-81007.rb"},{"controls":["V-81009"],"id":"controls/V-81009.rb"},{"controls":["V-81011"],"id":"controls/V-81011.rb"},{"controls":["V-81013"],"id":"controls/V-81013.rb"},{"controls":["V-81015"],"id":"controls/V-81015.rb"},{"controls":["V-81017"],"id":"controls/V-81017.rb"},{"controls":["V-81019"],"id":"controls/V-81019.rb"},{"controls":["V-81021"],"id":"controls/V-81021.rb"},{"controls":["V-92251"],"id":"controls/V-92251.rb"},{"controls":["V-92253"],"id":"controls/V-92253.rb"},{"controls":["V-92255"],"id":"controls/V-92255.rb"},{"controls":["V-94843"],"id":"controls/V-94843.rb"}],"license":"Apache-2.0","maintainer":"MITRE SAF Team","name":"redhat-enterprise-linux-7-stig-baseline","parent_profile":"example-inspec-overlay-profile-against-rhel7-stig-baseline-profile","sha256":"6fa03b9ff934febdaa4247039f6ea2357c58f6d2e0e573c7681ffb366ad41d68","status":"loaded","status_message":"","summary":"Inspec Validation Profile for Red Hat Enterprise Linux 7 STIG","supports":[{"platform-name":"centos","release":"7.*"},{"platform-name":"redhat","release":"7.*"}],"title":"redhat-enterprise-linux-7-stig-baseline","version":"2.6.6"}],"statistics":{"duration":22.029998957},"version":"4.52.9"}